Minutes for 0109: IEEE8021-SPANNING-TREE MIB module - PathCost

Standard: 802.1Q-2012 Clause: 17.7.3, 17.4.3 Draft with fix: 802.1Q-REV Status: Published
Submitter: Raphael Garti Date: 2013-05-06 Rationale: ieee8021SpanningTreePortPathCost has MAX-ACCESS of read-write and it is ...
Show Request Show Preformatted Request
Date Meeting Text Status
2013-05-15 May 2013 Interim It is not clear if any change is needed, though some revised DESCRIPTION might help to explain the background and usage. Technical Review – Ben Mack-Crane. Initial View: The name "ieee8021MstpCistPortPathCost" used in the description for ieee8021MstpCistPortAdminPathCost does not appear to exist. That is, there is no oper object to go with the admin object. It is possible that the ieee8021MstpCistPortCistPathCost object is intended to be the oper object, but its description does not appear to be consistent with this use. However, this description is eerily similar to the description for ieee8021MstpCistPathCost. If ieee8021MstpCistPortCistPathCost is intended to be the oper object its description should be changed accordingly. Since the object is read-write the description for ieee8021SpanningTreePortPathCost would benefit from the following change: "802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN." changed to "Table 13-4 recommends defaults and ranges for Port Path Cost values, in inverse proportion to the speed of the attached LAN. If this object is used to set the Path Cost it is possible to restore the default setting using the ieee8021SpanningTreeRstpPortAdminPathCost object.“ The name "ieee8021SpanningTreePortPathCost32" should be "ieee8021SpanningTreePortPathCost" Target for 802.1Qrev, if needed Technical experts review
2013-07-15 Jul 2013 Plenary Technical Review by Ben Mack-Crane concluded on revised text as follows: 1. (p727/line 6) The name "ieee8021MstpCistPortPathCost" used in the description for ieee8021MstpCistPortAdminPathCost does not appear to exist. That is, there is no oper object to go with the admin object. It is possible that the ieee8021MstpCistPortCistPathCost object is intended to be the oper object, but its description does not appear to be consistent with this use. However, this description is eerily similar to the description for ieee8021MstpCistPathCost. If ieee8021MstpCistPortCistPathCost is intended to be the oper object its description should be changed accordingly. 2. (p646/line 44) Since the object is read-write the description for ieee8021SpanningTreePortPathCost would benefit from the following change: "802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN." changed to "Table 13-4 recommends defaults and ranges for Port Path Cost values, in inverse proportion to the speed of the attached LAN. If this object is used to set the Path Cost it is possible to restore the default setting using the ieee8021SpanningTreeRstpPortAdminPathCost object." A similar bit of description should be added for the ieee8021MstpPortPathCost object, since it is also read-write, since an admin object is added per Maintenance 108 3. (p725/line 25) The name "ieee8021SpanningTreePortPathCost32" should be "ieee8021SpanningTreePortPathCost" Editor requested to update draft for 802.1Qrev Ready for Ballot
2013-09-03 Sep 2013 Interim Technical Review by Ben Mack-Crane revised based on eidtor feedback, to be as follows: 1) (p727/line 8) The name "ieee8021MstpCistPortPathCost" used in the description for ieee8021MstpCistPortAdminPathCost does not exist.  That is, there is no oper object to go with the admin object. - Change "This complements the object ieee8021MstpCistPortPathCost, which returns the operational value of the path cost. " to " This complements the object ieee8021MstpCistPortCistPathCost, which returns the operational value of the port path cost." - The ieee8021MstpCistPortCistPathCost object is intended to be the oper object for ieee8021MstpCistPortAdminPathCost, but its description is not consistent with this use. Change the description of this object to " In an MSTP Bridge, the Port's Port Path Cost parameter value for the CIST." and change the references to REFERENCE "13.27.25, 17.13.11 of IEEE Std 802.1D" - ieee8021MstpCistPathCost lacks references. Insert on page 720 line 50 REFERENCE "13.9:d, 13.10" - Table entry for ieee8021MstpCistPortAdminPathCost page 507 line 7 change " IEEE 802.1Da 13.22 p), 17.13.1" to "13.27.25, 17.13.11 of IEEE Std 802.1D " - Table entry for ieee8021MstpCistPortCistRegionalRootId page 507 line 30 change "13.10 c), 13.11, 13.27.47 " to "13.9 c), 13.11" - Table entry for ieee8021MstpCistPortCistPathCost page 507 line 31 change "13.10 d), 13.11, 13.27.47 " to "13.27.25" - Table entry for ieee8021MstpCistPathCost page 506 line 17 change "—" to "13.9 d), 13.11“ 2) (p646/line 44) Since the object is read-write the description for ieee8021SpanningTreePortPathCost would benefit from the following change: "802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN." changed to "Table 13-4 recommends defaults and ranges for Port Path Cost values, in inverse proportion to the speed of the attached LAN. If this object is used to set the Path Cost it is possible to restore the default setting using the ieee8021SpanningTreeRstpPortAdminPathCost object." A similar bit of description should be added to the ieee8021MstpPortPathCost object, “… Table 13-4 recommends defaults and ranges for Port Path Cost values, in inverse proportion to the speed of the attached LAN. If this object is used to set the Path Cost it is possible to restore the default setting using the ieee8021MstpPortAdminPathCost object” 3) (p725/line 25) The name "ieee8021SpanningTreePortPathCost32" should be "ieee8021SpanningTreePortPathCost" Editor is requested to update draft for 802.1Qrev Ready for Ballot
2013-11-12 Nov 2013 Plenary Included in D1.3, 802.1Q-REV is in WG ballot recirc Ready for Ballot
2014-01-22 Jan 2014 Plenary 802.1Q-REV is in sponsor ballot Balloting
2014-03-18 Mar 2014 Plenary 802.1Q-REV is in sponsor ballot recirc Balloting
2014-05-14 May 2014 Interim 802.1Q-REV is in sponsor ballot recirc Balloting
2014-07-15 Jul 2014 Plenary 802.1Q-REV is in sponsor ballot recirc Balloting
2014-07-15 Sep 2014 Interim 802.1Q-REV is in sponsor ballot recirc Balloting
2014-11-04 Nov 2014 Plenary 802.1Q-2014 is approved. Published

Back