http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1455
------- Comment #14 from jyoung@xxxxxxx 2007-04-12 15:48 GMT -------
Hello John,
As you suggested in comment #13 this really needs to be clarified. The IEEE
has a web page specfically devoted to questions of specification
interpretation:
http://standards.ieee.org/reading/ieee/interp/
There's even an email address available to perhaps expedite the process. Do
you think you or your engineer would be up to submitting a request for
interpretation to the IEEE?
A Wireshark fix (if it should be necessary) shoudn't be very difficult, but we
really need to know for sure what's broke before we fix it. ;-)
My late-night bleary-eyed re-reading of the 2005 LLDP spec has me even more
uncertain of what is correct. Section 9 talks about how bits are to be
numbered within an octet and how larger than one octet sequences are to be
layed out.
The fact is that multiple interpretations are now currently deployed.
I have alerted both Avaya and Extreme of this discrepency but they have not yet
responded.
Interestingly here's how an Extreme S300-24 switch running EW7.6.3b6 currently
parses the PMD Auto-neg field received from an Avaya 4621SW running v2.8
firmware when connected directly to one another.
[snip]
> Extended TLV Info 802.3 OUI (hex value) = 00-12-0f
> -MAC PHY Configuration & Status
> -Auto-negotiation Support & Status : Supported, enabled
> -Advertised capability bits (hex value): 536
> 100baseTXFD
> 100baseT2FD
> fdxSPause
> fdxBPause
> 1000baseXFD
> b1000baseT
> -Operational MAU Type : 16
[snip]
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
