Stewart Was this email meant to address my email to the IETF discussion list (from Tues 16 Aug) or just the discussion on MPLS and PWE lists ?
It does to SOME extent, as it leaves open the possibility of the GAL not being at BoS; but it does not rule out that possibility either. However, you did not address my other final comment that a PW that starts in an MPLS-TP domain, can easily leak into a non-TP domain. What does one do then ? (My email also identified a wording issue and what I consider to be a completely inaccurate explanation of what the draft is trying to accomplish.) Y(J)S From: [email protected] [mailto:[email protected]] On Behalf Of Stewart Bryant Sent: Tuesday, August 30, 2011 15:05 To: Luca Martini; IETF Discussion Cc: [email protected]; Vladimir Kleiner; [email protected]; Idan Kaspit; Mishael Wexler; pwe3; [email protected]; Oren Gal; John Shirron; [email protected]; Rotem Cohen Subject: Re: [PWE3] [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw Reviewing this discussion there are three components. 1) The update of RFC5586 to allow PW to use the GAL. 2) The PW OAM application that is to use the GAL. 3) The label stack structure when teh GAL is used with a PW This draft is only concerned with point 1 above. Points 2 and 3 need to be resolved in any PWE3 draft that describes the use of the GAL. To that end the text in draft-ietf-pwe3-mpls-tp-gal-in-pw-01 ======== - Section 4.2<http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586<http://tools.ietf.org/html/rfc5586>], the original text: In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs, and with Sections, and MUST NOT be used with PWs. It MUST always be at the bottom of the label stack (i.e., S bit set to 1). However, in other MPLS environments, this document places no restrictions on where the GAL may appear within the label stack or its use with PWs. is replaced by: In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs, and with Sections, and MAY be used with PWs. It MUST always be at the bottom of the label stack (i.e., S bit set to 1). However, in other MPLS environments, this document places no restrictions on where the GAL may appear within the label stack. ===== should be replaced by ===== - Section 4.2<http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586<http://tools.ietf.org/html/rfc5586>], the original text: In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs, and with Sections, and MUST NOT be used with PWs. It MUST always be at the bottom of the label stack (i.e., S bit set to 1). However, in other MPLS environments, this document places no restrictions on where the GAL may appear within the label stack or its use with PWs. is replaced by: In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs, and with Sections, and MAY be used with PWs. The presence of a GAL indicates that an ACH immediately follows the MPLS label stack. ====== - Stewart
_______________________________________________ Ietf mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf
