This amendment specifies protocols, procedures and managed objects that support the transmission and reception of a set of Link Layer Discovery Protocol (LLDP) Type Length Values (TLVs) that exceed the space available in a single frame. This amendment defines the transmission of multiple frames, additional TLVs and the procedures needed to support the transmission of those TLVs across multiple frames. This amendment maintains existing functionality while communicating with a peer that supports updated functionality. This amendment defines a method to further restrict the size of the LLDP Data Unit (LLDPDU) and extensions in order to meet timing constraints in the network. This amendment also addresses errors and omissions in the description of existing functionality.
The set of TLVs that an LLDP agent exchanges with a peer must fit into a single LLDPDU. The size of the LLDPDU is restricted by the maximum size of the information field for the particular link technology. In some cases, the size of the LLDPDU must be further reduced to meet timing constraints on the network. IEEE Std 802.1AB is widely supported and used in several different environments. Many of these environments have the need to transmit and receive more TLVs than can fit into a single frame. In addition, the number of unique TLVs in use continues to grow. Standards organizations and vendors can define their own sets of TLVs. Environments that need to advertise more information than can fit into a single LLDPDU currently have no solution other than defining a new and incompatible protocol. Given the popularity and wide deployment of LLDP there is a need to allow a migration to a version of the LLDP protocol that supports the transmission and reception of sets of TLVs that exceed the space provided by a single frame.
|PAR & CSD||Full title: Draft Standard for Local and Metropolitan Area Networks — Station and Media Access Control Connectivity Discovery — Amendment: Support for Multiframe Protocol Data Units
PAR (Approved: 05 Sep 2019; Expires: 31 Dec 2023)
|15 Oct 2021||P802.1ABdh, Draft 2.1 comment disposition|
|21 Sep 2021||P802.1ABdh, Draft 2.1|
|21 Sep 2021||P802.1ABdh, Draft 2.0 comment disposition|
|15 July 2021||P802.1ABdh, Draft 2.0|
|27 May 2021||P802.1ABdh, Draft 1.2 comment disposition|
|6 May 2021||P802.1ABdh, Draft 1.2|
|6 May 2021||P802.1ABdh, Draft 1.1 comment disposition|
|13 April 2021||P802.1ABdh, Draft 1.1|
|23 Mar 2021||P802.1ABdh, Draft 1.0 – comment disposition|
|1 Feb 2021||P802.1ABdh, Draft 1.0|
|20 Jan 2021||P802.1ABdh, Draft 0.2 – comment disposition|
|21 Dec 2020||P802.1ABdh, Draft 0.2|
|6 Nov 2020||P802.1ABdh, Draft 0.1 – comment disposition|
|1 Oct 2020||P802.1ABdh, Draft 0.1|
|21 Sep 2020||P802.1ABdh, Draft 0.0|
The above list includes only the latest version of (proposed) dispositions. See the project folder for a complete list. The dates listed are the website file dates; they may differ from the creation dates in the documents.
Important NOTICE on contributions.
The above list includes only the latest version of updated documents and omits those superseded by subsequent discussion or inclusion in the current draft (see filenames beginning “dh-” in the 2019 and 2020 public directories for a complete list). The dates listed are the website file dates; they may differ from the creation dates in the documents.
Please contact the Editor if you have comments to this page.