[Home] . [What's New?] . [Active Ballots] . [Minutes] . [Meetings] . [Maintenance] . [Interpretations] . [Public Docs] . [Committee Docs]
[Local Address Study Group] . [802 Architecture Group] . [Data Center Bridging Task Group] [Time-Sensitive Networking Task Group]
[Email] . [Ancient Email] . [802.1 MIBs] . [802.1 OIDs] . [IEEE 802] . [IEEE 802 PARs]
TSN: [802] . [802a] . [802b] . [802.1D] . [802.1D-2004] . [802.1G] . [802.1H-REV] . [802.1Q] . [802.1Q-2014] . [802.1s] . [802.1v] . [802.1w] . [802.1AB-2005] . [802.1AB-2009] . [802.1AC-2012] . [802.1AC-2016] . [802.1ad] . [802.1ag] . [802.1ah] . [802.1aj] . [802.1ak] . [802.1ap] . [802.1aq] . [802.1Qaw] . [802.1AX-2008] . [802.1Qay] . [802.1Qbc] . [802.1Qbe] . [802.1Qbf] . [802.1AXbk] . [802.1Qbp] . [802.1AX-2014] . [802.1AX-Rev] . [802.1Qbz] . [802.1Qca]
[802.1AS] . [802.1AS-Rev] . [802.1Qat] . [802.1Qav] . [802.1BA] . [802.1Qbu] . [802.1Qbv] . [802.1CB] . [802.1Qcc] . [802.1Qch] . [802.1CM] . [802.1Qcn] . [802.1Qcp] . [802.1Qcr]
Security: [802.1X-2001] . [802.1X-2004] . [802.1X-2010] . [802.1AE] . [802.1af] . [802.1AR] . [802.1AEbn] . [802.1AEbw] . [802.1Xbx] . [802.1ARce] . [802.1AEcg] . [802.1Xck] . [802E]
DCB: [802.1Qau] . [802.1Qaz] . [802.1Qbb] . [802.1Qbg] . [802.1Qbh] . [802.3bd] . [802.1BR] . [802.1Qcd] . [802.1Qcj] . [802c] . OmniRAN: [802.1CF]

Interpretation #7
Request
Situation: An MRPDU is being parsed.  At this point, a VectorAttribute
has just been parsed and the next two bytes in the packet are 0x00
0x01.  According to the grammar, we would expect another
VectorAttribute or an EndMark at this point.  Given that the next byte
is 0x00, it appears to be an EndMark followed by another message with
AttributeType 0x01.  However, these same bytes could be interpreted as
another VectorAttribute.  In this case, the VectorHeader for this
VectorAttribute would be 0x0001 which indicates that LeaveAll is clear
and NumberOfValues is 1.  Specifically, any time that the second,
third, etc VectorAttribute in an AttributeList has LeaveAll clear and
(NumberOfValues < 256), the sequence of bytes appears to not be
distinguishable from an EndMark followed by an AttributeType.  How
should these byte sequences be interpreted in these cases?

Response
This is an error in the PDU specification. The correct specification of EndMark is SHORT (i.e., a 16-bit field, value 0).
802.1 has raised a PAR for a corrigendum to correct the error.

This response was approved by 802.1 at its July 2007 plenary meeting.

Pages copyright © Institute of Electrical and Electronics Engineers, Inc. Please read the rules on Confidentiality Statements and Copyright Notices on Communications. Information on Privacy and opting out of cookies is available. If you have any comments on these pages, please send them to me.

Valid XHTML 1.0 Transitional Valid CSS!

Last modified by jlm, at 3:31pm on Tue, 21 Aug 2007