Minutes for 0037: New MEPoperational is operational status

Standard: 802.1Q-2011 Clause: 20.9 Draft with fix: Status: Rejected
Submitter: Weiying Cheng Date: 2012-06-21 Rationale: There is administrative state defined for MEP (MEPActive), but there is ...
Show Request Show Preformatted Request
Date Meeting Text Status
2012-07-17 Jul 2012 Plenary This needs to be studied. Target for Q-rev if needed Received
2012-09-12 Sep 2012 Interim MEPactive regulates all of the MEP state machines in parallel with BEGIN. There is not much opportunity for foul ups that would make an operational and an administrative pair for MEP active that would not be visible from the ieee8021CfmConfigErrorListTable. The MEPactive variable is a "come from" variable that controls all of the MEP state machines by forcing them to the reset state. It is driven by the state of the dot1agCfmMepActive administrative object. When the object and variable transition between TRUE or FALSE, the state machines should start or stop operation with no discernible lag. The most likely reason that a MEP that is administratively enabled is that the physical port on which it is supposed to reside is physically absent. This could be discovered by examining the dot1agCfmMepIfIndex object; a 0 value indicates that the MEP has no port on which to run. Any configuration problems can be detected using the ieee8021CfmConfigErrorListTable. While it is true that an "operational state" variable could therefore differ from the state of dot1agCfmMepActive, the Working Group feels that the additional information supplied by an operational object would be of too little utility to justify its implementation. A note will be added as per issue 0036 that will indicate this in the document. Rejected

Back