802.1 Tools
  • Home
  • Maintenance
    • All items
    • Open items
    • Closed items
    • Items for review
    • Status
  • Meetings
  • Help
  • Log in
  1. Maintenance Items
  2. 0090
  3. Request
Requested revision
Standard:802.1Q-2011Clause:D
Clause title:IEEE 802.1 organizationally specific TLVs
Rationale for revision
Submitted on behalf of David Law:

I have a question in relation to the MIB entries that seem to defined
with wrong indexes in IEEE Std 802.1AB-2009. I understand the same
errors exist in the LLDP-EXT-DOT1-V2-MIB-201103230000Z.txt MIB but the
following are excerpts from IEEE Std 802.1AB-2009. For example,
lldpV2Xdot1RemManVidEntry describes the management VLAN ID of a
specified neighbour. However, lldpV2RemIndex is not included by the
indexes. The same bug exists on the lldpV2Xdot1RemVidUsageDigestEntry.


-----

Name:                   lldpV2Xdot1RemManVidEntry
Type:                     OBJECT-TYPE
OID:                        1.3.111.2.802.1.1.13.1.5.32962.1.3.6.1
Full path: iso(1).org(3).ieee(111).standards-association-numbers-series-standards(2).lan-man-stds(802).ieee802dot1(1).ieee802dot1mibs(1).lldpV2MIB(13).lldpV2Objects(1).lldpV2Extensions(5).lldpV2Xdot1MIB(32962).lldpV2Xdot1Objects(1).lldpV2Xdot1RemoteData(3).lldpV2Xdot1RemManVidTable(6).lldpV2Xdot1RemManVidEntry(1)
Module:                 LLDP-EXT-DOT1-V2-MIB

Parent:                  lldpV2Xdot1RemManVidTable First child:
    lldpV2Xdot1RemManVid

Numerical syntax:         Null
Base syntax:         LldpV2Xdot1RemManVidEntry Composed syntax:
LldpV2Xdot1RemManVidEntry
Status:                  current
Max access:         not-accessible
Sequences:           1: lldpV2Xdot1RemManVid - Unsigned32(66 - gauge32)
Indexes:                1: lldpV2RemTimeMark
                              2: lldpV2RemLocalIfIndex
                              3: lldpV2RemLocalDestMACAddress

Reference:           D.2.6

Description:          Management VID information received
                             through the given port/destination address pair.


Name:                   lldpV2Xdot1RemVidUsageDigestEntry
Type:                     OBJECT-TYPE
OID:                        1.3.111.2.802.1.1.13.1.5.32962.1.3.5.1
Full path: iso(1).org(3).ieee(111).standards-association-numbers-series-standards(2).lan-man-stds(802).ieee802dot1(1).ieee802dot1mibs(1).lldpV2MIB(13).lldpV2Objects(1).lldpV2Extensions(5).lldpV2Xdot1MIB(32962).lldpV2Xdot1Objects(1).lldpV2Xdot1RemoteData(3).lldpV2Xdot1RemVidUsageDigestTable(5).lldpV2Xdot1RemVidUsageDigestEntry(1)
Module:                 LLDP-EXT-DOT1-V2-MIB

Parent:                  lldpV2Xdot1RemVidUsageDigestTable First
child:            lldpV2Xdot1RemVidUsageDigest

Numerical syntax:         Null
Base syntax:         LldpV2Xdot1RemVidUsageDigestEntry Composed
syntax:        LldpV2Xdot1RemVidUsageDigestEntry
Status:                  current
Max access:         not-accessible
Sequences:           1: lldpV2Xdot1RemVidUsageDigest - Unsigned32(66 - gauge32)
Indexes:                1: lldpV2RemTimeMark
                              2: lldpV2RemLocalIfIndex
                              3: lldpV2RemLocalDestMACAddress

Reference:           D.2.5

Description:          Usage digest information received on
                             the given port/destination address pair.
Proposed text
Include lldpV2RemIndex in the indexes for these two objects.
Impact on existing networks
Minimal. These are optional objects; the only impact would be seen in networks where the corresponding TLVs are received from more than one remote system on a given destination address.
Originator
Name:Tony JeffreeEmail:tony@jeffree.co.uk
Affiliation:HP/Broadcom
Submitted:2012-12-10