Chris Maynard
changed
bug 3123
| What |
Removed |
Added |
| Attachment #10954 Flags |
|
review_for_checkin?
|
Comment # 2
on bug 3123
from Chris Maynard
Created attachment 10954 [details]
Don't perform any OUI lookups.
My reading of 802a-2003's section 12.3 OUI Extended Ethertype gives no
indication that the 802a dissector should limit its OUI lookup to the LLC
oui_vals[] table.
However, the general OUI lookup isn't necessarily correct either. For example,
section 12.3 states, "The value used for the OUI component of the protocol
identifier is an OUI value assigned to the organization that has developed the
vendor-specific protocol." But are *these* OUI's the same as those listed at
http://standards.ieee.org/develop/regauth/oui/oui.txt? Or should they instead
come from a separate, extended OUI lookup? From what I can tell, it's the
latter.
But on the IEEE's site, I also find
http://standards.ieee.org/develop/regauth/oui36/index.html, which states that,
"OUI-36 is a 36-bit identifier that can be used as an Individual Address Block
(IAB) or as an extended OUI." It then goes on to say that, "Applications
making use of an OUI-36 should make no assumptions about the bit pattern that
will be present in the (24-bit most-significant) OUI portion of the assigned
OUI-36."
Given that, I concluded that the right thing to do is not to perform any OUI
lookup at all ... at least not until a separate, explicit extended OUI list is
published. There is a OUI36 list here:
http://standards.ieee.org/develop/regauth/oui36/oui36.txt, but it's not clear
that these would be the only ones present in an extended OUI field, and even if
they are, we're specifically told not to make any assumptions about the bit
pattern that will be present, so that sort of makes it difficult to perform
reliable lookups.
Finally, while perusing the IEEE site, I noticed that ethertypes are apparently
updated daily like OUI's are: See
http://standards.ieee.org/develop/regauth/ethertype/public.html. Maybe it
would be possible to update them at the same frequency as we do the OUI's from
http://standards.ieee.org/develop/regauth/oui/oui.txt?
You are receiving this mail because:
- You are the assignee for the bug.
- You are watching all bug changes.