Minutes for 0121: System Capabilities TLV, Structure of the LLDP MIB, LLDP MIB module - version 2

Standard: IEEE 802.1AB-2009 Clause: 8.5.8, 11.2, 11.5.2 Draft with fix: 802.1AB-cor-2 Submitted: 2013-07-10
Show Request Show Preformatted Request
Date Meeting Text Status
2013-07-15 Jul 2013 Plenary < Note: This was originally incorrectly numbered 0119 > Issue 1 is already fixed per Maintenance #32 Technical review of issues 2 & 3 assigned to Norm Finn. Initial view: The text of 9.2.5.7 makes it very clear that msgTxInterval is per-agent (per destination MAC address). However, the MIB variable lldpV2MessageTxInterval is per-system. There is clearly a problem that needs to be fixed. These points need investigation : 1. Is the list in 199 complete and accurate? 2. Should we fix the MIB to have more functionality? 3. Should we fix the state machine text to match the MIB but have less functionality? Technical experts review
2013-09-03 Sep 2013 Interim Issue 1 is already fixed per Maintenance #32 issue 2: The text of 9.2.5.7 makes it very clear that msgTxInterval is per-agent (per destination MAC address). However, the MIB variable lldpV2MessageTxInterval is per-system. There is clearly a problem that needs to be fixed. Norm Finn will study further… Issue 3: The text in the MIB certainly differs from the text in section 9.2.5.22. The MIB has no +1, 9.2.5.22 does. The corresponding text in 802.1AB-2005 doesn't have the +1. Clearly a conscious change was made in the 2009 text, but not to the MIB. As to which one is correct, I'd lean towards the +1. The difference is that, without the +1, the receiver times out at exactly the same time that the Nth frame is expected to arrive. The +1 makes much more sense. Fix MIB DESCRIPTION Technical experts review
2013-11-12 Nov 2013 Plenary Issue 1 is already fixed per Maintenance #32 Issue 2: The text of 9.2.5.7 makes it very clear that msgTxInterval (et al) is per-agent (per destination MAC address). However, the MIB variable lldpV2MessageTxInterval is per-system. Solve by adding per-instance variables in parallel to the current variables. The current global variables now supply default values for new rows created in the per-instance variables. Do not delete the current universal variables, but make it clear in the DESCRIPTIONS of the new variables added to lldpV2ManAddrConfigTxPortsEntry that the default value of these variables when a new row is created is the current value of the corresponding global variables that now exist. This goes in revised DESCRIPTION clauses of the current variables, also, of course. Per Agent MIB objects should be maintained under lldpV2PortConfigTable. The new table would be as follows: lldpV2PortConfigTable lldpV2PortConfigIfIndex (Table index) lldpV2PortConfigDestAddressIndex (Table index) lldpV2PortConfigAdminStatus adminStatus, 9.2.5.1 lldpV2MessageTxInterval msgTxInterval, 9.2.5.7 lldpV2MessageTxHoldMultiplier msgTxHold, 9.2.5.6 lldpV2ReinitDelay reinitDelay, 9.2.5.10 lldpV2NotificationInterval msgTxInterval, 9.2.5.7 lldpV2TxCreditMax txCreditMax, 9.2.5.17 lldpV2MessageFastTx msgFastTx, 9.2.5.5 lldpV2TxFastInit txFastInit, 9.2.5.19 lldpV2PortConfigNotificationEnable — lldpV2PortConfigTLVsTxEnable 9.1.2.1 Issue 3: The text in the MIB certainly differs from the text in section 9.2.5.22. The MIB has no +1, 9.2.5.22 does. The corresponding text in 802.1AB-2005 doesn't have the +1. Clearly a conscious change was made in the 2009 text, but not to the MIB. As to which one is correct, I'd lean towards the +1. The difference is that, without the +1, the receiver times out at exactly the same time that the Nth frame is expected to arrive. The +1 makes much more sense. Fix MIB DESCRIPTION to include TTL = min(65535, (lldpV2MessageTxInterval * lldpV2MessageTxHoldMultiplier) + 1) Complete then Ballot
2014-01-22 Jan 2014 Plenary Editor will prepare an initial draft of 802.1AB-Cor2 after PAR approval Complete then Ballot
2014-03-18 Mar 2014 Plenary Editor will prepare an initial draft of 802.1AB-Cor2 after PAR approval, for the May meeting Complete then Ballot
2014-05-14 May 2014 Interim No update. Complete then Ballot
2014-07-17 Jul 2014 Plenary Fixed in 802.1AB-Cor2/D0.2. Balloting
2014-07-17 Sep 2014 Interim Fixed in 802.1AB-Cor2/D0.2. Balloting
2014-07-17 Nov 2014 Plenary Fixed in 802.1AB-Cor2/D0.2. Balloting
2014-07-17 Jan 2015 Interim Fixed in 802.1AB-Cor2/D0.2. Balloting

Back