Requested revision
Standard: | 802.1Q, 802.1AB, 802.1AX | Clause: | See below |
Clause title: | RATIONALE FOR REVISION: |
Rationale for revision
Previous maintenance request (#132) calls for the removal of D2.7
(Link Agg TLVs) from 802.1Q as these are also documented in
802.1AX-REV. However:
- The TLVs are documented in AX-REV but the related managed objects in
the 802.1AB MIB extension are still documented in 802.1Q
- The MIB object in Q that represents the link agg capability/status
(Table F-1 in AX-REV) make use of a textual convention taken from
802.1AB which no longer corresponds to the current definition of the
field.
This is a mess - really, when this TLV was extracted into AX-REV, the
corresponding MIB objects should have been documented there. Also,
while Table F-1 uses bit numbering from 1 to 8, the MIB object uses
the BITS data type that naturally numbers from 0 to 7...
Proposed text
Various alternative possibilities:
1) Fix the textual convention in AB to match Table F-1.
2) Write a new textual convention in the extension MIB in Q-2014 Cor-1
that corresponds to Table F-1 and use that in the object defs in Q.
3) Deprecate the objects in Q (via Q-2014-Cor-1) and write a (very
short) extension MIB to go in AX-REV.
Option 2) is probably the most expedient solution, but leaves the
long-term problem that the next time we change the TLV in AX we also
have to fix Q.
Impact on existing networks
<replace this text with a description of impact on existing networks>
Originator
Name: | Tony Jeffree | Email: | tony@jeffree.co.uk |
Affiliation: | Broadcom/HP | ||
Submitted: | 2015-01-06 |