RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

[Alexander Vainshtein <Alexander.Vainshtein@xxxxxxxxxxx>]

Stewart,

I believe that your item #1 is presumably addressed by draft-ietf-pwe3-gal-in-pw (with the changes you’ve proposed), draft-nadeau-pwe3-vccv-2 is an attempt to address your item #2, and your item #3 is not yet addressed.  Is this understanding correct?

 

I also think that one of the items in the discussion was the restriction on ECMP in MPLS to skip reserved labels. I am not sure if it has been properly addressed anywhere, so should not it constitute item #4?

 

Regards,

     Sasha

 

From: Stewart Bryant [mailto:stbryant@xxxxxxxxx]
Sent: Tuesday, August 30, 2011 3:05 PM
To: Luca Martini; IETF Discussion
Cc: John E Drake; mpls@xxxxxxxx; Alexander Vainshtein; ietf@xxxxxxxx; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen; pwe3-chairs@xxxxxxxxxxxxxx; iesg@xxxxxxxx
Subject: Re: [mpls] [PWE3] 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. (GAL Applicability and Usage) in [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. (GAL Applicability and Usage) in [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

This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof.

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf