MPLS Fault Management Operations, Administration, and Maintenance (OAM)
RFC 6427
Yes
No Objection
Recuse
Note: This ballot was opened for revision 07 and is now closed.
(Adrian Farrel; former steering group member) Yes
(Dan Romascanu; former steering group member) No Objection
Hopefully IANA knows what to do, but the note in Section 8.1 is not clear to me. > [Note: An early codepoint allocation was made: 0x0058 Fault OAM (TEMPORARY - expires 2012-07-20)] Do the authors request to transform this temporary codepoint allocation to a permanent one? In any case the Note needs to be taken out at document publication.
(Gonzalo Camarillo; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
Section 2.1: The MPLS Alarm Indication Signal (AIS) message is generated in response to detecting faults in the server (sub-)layer. The AIS message SHOULD be sent as soon as the condition is detected, but MAY be delayed owing to processing in an implementation, and MAY be suppressed if protection is achieved very rapidly. Those "MAY"s aren't protocol options, they're exceptions to the SHOULD. How about instead, "The AIS message SHOULD be sent as soon as the condition is detected, with the obvious exceptions being delay owing to processing in an implementation or complete supression if protection is acheived rapidly." The primary purpose of the AIS message is to suppress alarms in the layer network above the level at which the fault occurs. When the Link Down Indication is set, the AIS message MAY be used to trigger recovery mechanisms. Do you really mean "MAY" here, or rather "can"? Who are you telling that they MAY use the AIS message as the trigger, the implementer of the recovery mechanism (in which case it might be right) or others who need to be aware that recovery mechanisms might be triggered (in which case it is wrong). Section 2.2: Similar use of MAY as above. Please check.
(Peter Saint-Andre; former steering group member) No Objection
Please specify whether the refresh timer can include fractional seconds. Please specify the byte order of the longer fields; typically this is network byte order (i.e., most significant byte first), but not always.
(Robert Sparks; former steering group member) No Objection
Section 8.4 indicates that it will use the term "Private Use", but doesn't. It does use "Experimental Use" - should the first paragraph have called that out instead?
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
The IPR statement from Ericsson is confusing to me. See https://datatracker.ietf.org/ipr/1460/. What does "option b) above" mean?
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
(Wesley Eddy; former steering group member) No Objection
(Stewart Bryant; former steering group member) Recuse