http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1455
------- Comment #13 from jhilman@xxxxxxxxxxxx 2007-04-12 13:41 GMT -------
(In reply to comment #11)
Hi Jim,
While Guy does make some valid points... and the RFC trail he's blazing is
exactly as he says it is, I do have to side with my engineer contact. As he
says, there are many cases in the 802.1AB-2005 standard where octets are called
for specifically, and many cases where integer strings are called for
specifically, and in those cases; the right information is being reported on
the decodes. So to suggest anything other than the integer string the standard
calls for regardless of the references to outside sources would be contracting
the rest of the standard, would it not? I think that Guy is correct in that he
was refering to a 2007 draft of the standard since there is no actual
802.1AB-2007 document as of yet. I also believe this should be clarified so
that everyone knows what page to be on. So in short... I believe that
Wireshark, HP, and Extreme are interpreting the standard incorrectly, and that
Avaya, and my particular vendor is correct. I'd also be interested to see how
other vendors are interpreting this part of the standard.
--
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.