MPLS Fault Management Operations, Administration, and Maintenance (OAM)
draft-ietf-mpls-tp-fault-07
Yes
(Adrian Farrel)
No Objection
(Gonzalo Camarillo)
(Jari Arkko)
(Ron Bonica)
(Sean Turner)
(Stephen Farrell)
(Wesley Eddy)
Recuse
(Stewart Bryant)
Note: This ballot was opened for revision 07 and is now closed.
Adrian Farrel Former IESG member
Yes
Yes
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
(2011-09-20)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
(2011-09-21)
Unknown
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 IESG member
No Objection
No Objection
(2011-09-12)
Unknown
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 IESG member
No Objection
No Objection
(2011-09-21)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
(2011-09-21)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
()
Unknown
Wesley Eddy Former IESG member
No Objection
No Objection
()
Unknown
Stewart Bryant Former IESG member
Recuse
Recuse
()
Unknown