|Clause title:||System Capabilities TLV|
Rationale for revision
(Notified to me by U Arunkumar - email@example.com) In Figure 8-10, the TLV Information String length is shown as 4 but the TLV Information String shows 3 fields and a total of 5 octets. It looks to me as if the chassis ID subtype field has crept into this diagram during the revision - this field does not appear in the 2005 version of the standard. Mr Arunkumar also asks: "MAC Service Access Point (MSAP) is normally a concatenated value of Chassis ID and Port ID which is used in the transmission and reception of LLDPDUs. In IEEE 802.1AB 2009 standard, there is a possibility to have multiple (agents) instances running on same interface (for Nearest Bridge/ Nearest non-TPMR Bridge/Nearest Customer Bridge). Our understanding is that the MSAP will be common for all the agents running on the same port. i.e. the MSAP ID will be that of the common MSAP of the port (between the MAC entity and Mux/Demux shim and not the MSAP between the Mux/Demux shim and LLC as per figure 6-7). Please let us know if our understanding is correct. If the MSAP ID not going to be the same of the multiple LLDP agents on a port, could you enlighten us on how the unique MSAP ID will be derived."
Strike the chassis ID field from the diagram. Possibly a need to clarify the text in 6.7. At the very least, the reference to (7.2) in the first para doesn't seem to be quite right to me.
Impact on existing networks