Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-TPLinearProtectionApplicability to MS-PW"
"Daniel Cohn" <DanielC@orckit.com> Tue, 14 June 2011 11:31 UTC
Return-Path: <DanielC@orckit.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942C211E80B7; Tue, 14 Jun 2011 04:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.733
X-Spam-Level:
X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, HS_INDEX_PARAM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_29=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqcEPxttvqaF; Tue, 14 Jun 2011 04:30:56 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by ietfa.amsl.com (Postfix) with ESMTP id 4632811E8071; Tue, 14 Jun 2011 04:30:54 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC2A86.BA816F8A"
Date: Tue, 14 Jun 2011 14:30:42 +0300
Message-ID: <44F4E579A764584EA9BDFD07D0CA081306CF3547@tlvmail1>
In-reply-to: <077E41CFFD002C4CAB7DFA4386A5326403F64A13@DEMUEXC014.nsn-intra.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mpls] [PWE3] Seeking feedback on I-D "MPLS-TPLinearProtectionApplicability to MS-PW"
Thread-Index: AcwpxQYkt1VB87JDQZmWlDJG9yJyKgAABTPQAADcskAABE5ygAAADmpwAADpDNAAJfe4EA==
References: <OF7EF3F6D6.7AE4C202-ON482578AE.00430DDE-482578AE.0044404E@zte.com.cn><A3C5DF08D38B6049839A6F553B331C76E9BDCA9A38@ILPTMAIL02.ecitele.com> <077E41CFFD002C4CAB7DFA4386A5326403F64953@DEMUEXC014.nsn-intra.net> <44F4E579A764584EA9BDFD07D0CA081306CF33B5@tlvmail1> <A3C5DF08D38B6049839A6F553B331C76E9BDCA9AB7@ILPTMAIL02.ecitele.com> <077E41CFFD002C4CAB7DFA4386A5326403F64A13@DEMUEXC014.nsn-intra.net>
From: Daniel Cohn <DanielC@orckit.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, ext Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: ma.yuxia@zte.com.cn, mpls@ietf.org, pwe3@ietf.org
Subject: Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-TPLinearProtectionApplicability to MS-PW"
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 11:31:02 -0000
Hi Nurit, The exact same argument can be made for LSP linear protection as in draft-ietf-mpls-tp-linear-protection - it protects LSRs (transit LERs) but doesn't protect head/tail LERs. So why not drop LSP linear protection altogether and protect the client service layer instead? Protection is a statistical business. Protecting S-PE will improve availability, even when T-PE is not protected - especially when you remember that typically there are many more S-PEs than T-PEs in a given PW. Also as the T-PE is typically closest to the edge, a T-PE will typically carry less PWs than an S-PE so S-PE protection would be more significant for the operator. AC protection (required in order to protect T-PE) using ICCP or similar, as Greg pointed out, is not defined as part of the MPLS-TP framework. In the most extreme case, which is gradually becoming the norm, operators deploy MPLS to the customer edge, so the T-PE will actually be a CE in which case CE/T-PE protection is technically an impossibility. On the other hand, there is a clear MPLS-TP requirement to provide protection for MPLS-TP transport paths, which includes PWs. The purpose of this draft is to meet this requirement, for which there is currently no solution. If you have an alternative solution please share it with the list so we can discuss it. Thanks, Daniel From: Sprecher, Nurit (NSN - IL/Hod HaSharon) [mailto:nurit.sprecher@nsn.com] Sent: Monday, June 13, 2011 6:23 PM To: ext Alexander Vainshtein; Daniel Cohn Cc: mpls@ietf.org; pwe3@ietf.org; ma.yuxia@zte.com.cn Subject: RE: [mpls] [PWE3] Seeking feedback on I-D "MPLS-TPLinearProtectionApplicability to MS-PW" If you do it on the client service layer, you can protect also the T-PE... Why do you want to protect only against a failure of the S-PE? The PW starts at the T-PE... From: ext Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com] Sent: Monday, June 13, 2011 6:11 PM To: Daniel Cohn Cc: mpls@ietf.org; pwe3@ietf.org; Sprecher, Nurit (NSN - IL/Hod HaSharon); ma.yuxia@zte.com.cn Subject: RE: [mpls] [PWE3] Seeking feedback on I-D "MPLS-TPLinearProtectionApplicability to MS-PW" Daniel and all, Please see some comments inline below. Regards, Sasha From: Daniel Cohn [mailto:DanielC@orckit.com] Sent: Monday, June 13, 2011 5:55 PM To: Sprecher, Nurit (NSN - IL/Hod HaSharon); Alexander Vainshtein; ma.yuxia@zte.com.cn Cc: mpls@ietf.org; pwe3@ietf.org Subject: RE: [mpls] [PWE3] Seeking feedback on I-D "MPLS-TPLinearProtection Applicability to MS-PW" Hi, Thanks all for the feedback. I believe we all agree that PW protection is only required in the event of S-PE failure at an MS-PW - this is clearly stated in the draft. Now, both Sasha and Nurit mention that the PW redundancy mechanism can meet the MPLS-TP PW protection requirements. First of all a word on scalability. Please note that in an MPLS-TP environment without a control plane, the PW redundancy mechanism must also rely on proactive connectivity check for fast failure detection to meet the sub-50 ms requirement. [[[Sasha]]] IMO there is nothing specific to MPLS-TP here. Detecting S-PE failures based on the control plane would not fast enough. Therefore any scalability considerations that apply to the PW protection draft apply to the PW redundancy draft as well.[[[Sasha]]] I have not raised the scalability issue. My issue was limited applicability scope when compared to PW redundancy. E.g., the PW redundancy mechanisms take care of dual-homed CEs in SS- and MS-PWs - something that liner protection of PWs cannot do. Also wrt scalability, there is no such thing as "scales" or "doesn't scale" - scalability is not a binary concept. You can say that PW protection scales worse than LSP protection, just like you can say that LSP protection scales worse than interface protection. Which didn't stop IETF from defining LSP protection for scenarios where interface protection doesn't do the job. Now let's turn our attention back to whether the PW redundancy draaft can be used to meet MPLS-TP PW protection requirements. I can identify the following reasons why in its current form it doesn't: - It explicitly ("outside the scope") does not define protection triggers and how to handle coexisting triggers, as requested in RFC 5654 (MPLS-TP Requirements), reqs #75, #76 and #79 [[[Sasha]]] So what? Definition of triggers is orthogonal to how coordinated protection switching happens. - It does not support the ability to distinguish between different types of triggers (i.e. one end doesn't know why the other end triggered switch), as requested in RFC 5654 (MPLS-TP Requirements), req #77 - It does not define revertive/nonrevertive behavior, as requested in RFC 5654 (MPLS-TP Requirements), req #64 - It does not define holdoff support, which is especially important to avoid race conditions with LSP protection when it exists - It doesn't support 1+1 mode, as requested in RFC 5654 (MPLS-TP Requirements), req #65 [[[Sasha]]] All these claims are correct - and this should not be a surprise, because MPLS-TP requirements have been defined much later than the PW redundancy mechanism. But I do not think that this justifies co-existence of two different mechanisms. - It's a two-phase protocol, with the consequent impact on timing[[[Sasha]]] Could you please elaborate? - It doesn't define retransmission of protection coordination messages, so loss of a single PDU can result in switchover not taking place, thus not supporting sub-50 ms recovery in this case [[[Sasha]]] The PW redundancy protocol runs either on top of LDP (which benefits from TCP retransmissions) or on top of static PW status messages (where retransmission is defined). In summary, PW redundancy was not designed with TP requirements in mind, and as such does not meet the TP requirements. Of course modifications may be introduced, but why reinvent the wheel when there is a protocol (draft-ietf-mpls-tp-linear-protection-06) in the standards track that supports all the above requirements and can be applied to MS-PW protection with minor modifications? [[[Sasha]]] As I said, because the applicability scope is by far too narrow to justify a dedicated protocol. Regards, Daniel From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Sprecher, Nurit (NSN - IL/Hod HaSharon) Sent: Monday, June 13, 2011 4:02 PM To: ext Alexander Vainshtein; ma.yuxia@zte.com.cn Cc: mpls@ietf.org; pwe3@ietf.org Subject: Re: [mpls] [PWE3] Seeking feedback on I-D "MPLS-TPLinearProtection Applicability to MS-PW" Hi, I would like to second Sasha. End-to-end PW protection (with diverse paths) does not scale, and put hard restrictions on the utilization of the resources. MPLS-TP PWs are carried across the network inside MPLS-TP LSPs. Therefore, an obvious way to provide protection for a PW is to protect the LSP that carries it. If the PW is a multi-segment PW, then LSP recovery can only protect the PW in individual segments. This means that a single LSP recovery action cannot protect against a failure of a PW switching point (an S-PE). When protecting against an AC or T/S-PE failure by dual connectivity, PW redundancy mechanisms provide means for the PEs to coordinate over which LSP the traffic of the PW is carried. I also doubt why there is a need for additional mechanism. Best regards, Nurit From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of ext Alexander Vainshtein Sent: Monday, June 13, 2011 3:43 PM To: ma.yuxia@zte.com.cn Cc: mpls@ietf.org; pwe3@ietf.org Subject: Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-TP LinearProtection Applicability to MS-PW" Dear Ma and all, Adding the PWE3 WG to my response. The PW redundancy mechanism supports linear protection of MS-PWs as one of many additional application use cases: Appendix A of the PW redundancy Bit draft <http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/?include _text=1> describes 5 application uses cases in addition to MS-PW with single-homed CEs (which is listed there as use case 5). And it is equally applicable to IP/MPLS and MPLS - with the help of the Static PW Status Messages draft <http://datatracker.ietf.org/doc/draft-ietf-pwe3-static-pw-status/?inclu de_text=1> ( if, for whatever reason, you do not want to, or cannot, use RFC 4447 <http://datatracker.ietf.org/doc/rfc4447/?include_text=1> ). Hence I doubt the need for yet another PW redundancy mechanism with narrow scope of applicability. Regards, Sasha From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ma.yuxia@zte.com.cn Sent: Monday, June 13, 2011 3:25 PM To: mpls@ietf.org Subject: Re: [mpls] Seeking feedback on I-D "MPLS-TP Linear Protection Applicability to MS-PW" Hi all, The linear protection mechanism for LSP and PW(including MS-PW) should be the same and it is valuable to describe it clearly. BTW, there is a typo, it is "T-PE Z" instead of "T-PE B". " Figure 1 illustrates such a scenario, where two MS-PWs are established between T-PE A and T-PE B, over S-PEs 1-2 and 3-4 respectively. Each PW segment is established over an LSP (e.g. PW- s12 over LSP12). " -----Original Message----- From: Daniel Cohn Sent: Tuesday, May 17, 2011 4:14 PM To: mpls Subject: Seeking feedback on I-D "MPLS-TP Linear Protection Applicability to MS-PW" Importance: High Hi MPLSers, I uploaded "MPLS-TP Linear Protection Applicability to MS-PW" I-D (http://tools.ietf.org/html/draft-cohn-mpls-tp-pw-protection-00) The abstract goes: One of the requirements of the MPLS transport profile [RFC 5654] is to provide linear protection for transport paths, which include both LSPs and PWs. The functional architecture described in [SurvivFwk] is applicable to both LSP and PWs, however [LinearProt] does not explicitly describe mechanisms for PW protection in MPLS-TP. This document extends the applicability of the linear protection mechanism described in [LinearProt] to MPLS-TP segmented PWs (MS-PWs) as defined in [RFC 6073]. Could you please review it and send feedback to the mailing list or directly to the author? Looking forward to your feedback, Daniel 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. 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.
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Alexander Vainshtein
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… binny jeshan
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… binny jeshan
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Daniel Cohn
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Alexander Vainshtein
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Gregory Mirsky
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Daniel Cohn
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Daniel Cohn
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Maarten vissers
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Daniel Cohn
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Alexander Vainshtein
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Alexander Vainshtein
- Re: [PWE3] [mpls] Seeking feedback on I-D "MPLS-T… Daniel Cohn
- [PWE3] 答复: RE: [mpls] Seeking feedback on I-D "MP… ma.yuxia
- [PWE3] R: [mpls] Seeking feedback on I-D "MPLS-TP… D'Alessandro Alessandro Gerardo