Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping
RFC 6310

Note: This ballot was opened for revision 16 and is now closed.

(Stewart Bryant) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Lars Eggert) No Objection

(Adrian Farrel) (was Discuss) No Objection

Comment (2011-04-21)
No email
send info
I have updated my Comment for revision 15. Thank you for addressing the nits I had raised.

I have one new Comment that is moved here from a former Discuss...

I appreciate the change wrt MS-PW
I would prefer
OLD
   While this document is worded in terms of single segment PWs, its
   content also applies to T-PEs for MS-PWs ([RFC5254]).  Section 10 of
   [RFC6073] details procedures for generating or relaying PW status by
   an S-PE.
NEW
   This document is scoped only to single segment PWs. The mechanisms
   described in this document could also be applied to T-PEs for MS-PWs
   ([RFC5254]).  Section 10 of [RFC6073] details procedures for generating
   or relaying PW status by an S-PE.
END

(Stephen Farrell) No Objection

(Russ Housley) No Objection

Comment (2011-01-05 for -)
No email
send info
  Appendix B.3: s/Los/Loss/

(Pete Resnick) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection