Use of OUI in SNAP for defining a 'proprietary' protocol
Hi there,
The company I work for is registered at IEEE for an OUI that we use in our ethernet connected embedded devices.
We are currently running the TCP/IP protocol(s), but we would now like to implement a 'proprietary' protocol that we could use for upgrading/managing the firmware in these devices.
My question is, could we use our OUI in some way to 'define' the protocol without violating any "Ethernet standards".
(1) Can I use a 802.3 SNAP frame.... +----------+---------+----------+-----------+----------+ |802.3 MAC |802.2 LLC|802.2 SNAP|Data | CRC | |Header |Header |Header |(38 to | Checksum | |(14 bytes)|(3 bytes)|(5 bytes) |1492 bytes)| (4 bytes)| +----------+---------+----------+-----------+----------+
....and in the 802.2 SNAP header ... +---------------------+---------+ |OUI (Organizationally|Type | |Unique Id) |(2 bytes)| |(3 bytes) | | +---------------------+---------+
.....use the OUI of my company to define a set of 65536 types of protocols??
(2) Use of "ethertype" 888D. When looking at the list of registered 'ethertypes'
Any comments?
Regards /Yxan
read more and respond »Posted 5 years ago by Yxan in Ethernet LAN
