Using the Generic Associated Channel Label for Pseudowire in the MPLS Transport Profile (MPLS-TP)
RFC 6423

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

(Stewart Bryant) Yes

(Adrian Farrel) (was Discuss) Yes

Comment (2011-09-21)
No email
send info
Section 1

   [RFC5586] defines a generalized label-based exception mechanism using 
   the Generic Associated Channel Label (GAL) to work together with the 
   ACH for use with LSPs but places restrictions on GAL usage with PWs.  

   This document removes the restriction imposed by [RFC5586]. 

Please clarify one or more restrictions?

---

Section 3

   This indicates that the GAL can be used for MPLS-TP LSPs and Sections, 
   but not for PWs using an MPLS-TP PSN. 

What does it mean for a PW to use an MPLS-TP PSN?
Perhaps...

   but not for PWs in an MPLS-TP network.

---

Nits

Title
s/Pseudowire/Pseudowires/

---

Abstract
s/[RFC5586]/RFC 5586/

---

Section 1
s/associated control channel/Associated Channel/  (per RFC 5085)

---

Section 1
s/generalizes this for use in the/generalizes this for use as the/

---

Section 3 para 1

Delete "appropriate" or fix as suggested by Stephen

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Wesley Eddy) No Objection

(Stephen Farrell) No Objection

Comment (2011-09-16)
No email
send info
typo: s/architectures appropriate/architectures as appropriate/
in section 3

(Russ Housley) No Objection

(Pete Resnick) No Objection

(Dan Romascanu) No Objection

Comment (2011-09-22)
No email
send info
OAM is defined in the terminology section but never used. I suggest to drop it. 

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection