Re: [mpls-tp] [mpls] [PWE3] [AHMPLS-TP] Re: pollondraft-he-mpls-tp-csf-03.txt

John E Drake <jdrake@juniper.net> Thu, 02 December 2010 14:56 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A9F228C0CE; Thu, 2 Dec 2010 06:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level:
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.387, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N++8IMbdCOZ6; Thu, 2 Dec 2010 06:56:45 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id 3809428C139; Thu, 2 Dec 2010 06:56:35 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTPez5vvfWsGQROzRZhjeqhamxZq0PMzs@postini.com; Thu, 02 Dec 2010 06:58:01 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Thu, 2 Dec 2010 06:56:19 -0800
From: John E Drake <jdrake@juniper.net>
To: "Manuel.Paul@telekom.de" <Manuel.Paul@telekom.de>, "lieven.levrau@alcatel-lucent.com" <lieven.levrau@alcatel-lucent.com>, "rajiva@cisco.com" <rajiva@cisco.com>, "yljiang@huawei.com" <yljiang@huawei.com>
Date: Thu, 2 Dec 2010 06:57:40 -0800
Thread-Topic: [mpls] [PWE3] [AHMPLS-TP] Re:[mpls-tp] pollondraft-he-mpls-tp-csf-03.txt
Thread-Index: AcuSIsOuufii+EmrRR6zdRegAAiNTAAAEK3wAAHmEwAAAYuYAA==
Message-ID: <5E893DB832F57341992548CDBB33316398C549DE26@EMBX01-HQ.jnpr.net>
References: <4CE51469.2020105@pi.nu><00c201cb9137$0e7b1fd0$6428460a@china.huawei.com><5E893DB832F57341992548CDBB33316398C53F6CF1@EMBX01-HQ.jnpr.net><077E41CFFD002C4CAB7DFA4386A532640301C477@DEMUEXC014.nsn-intra.net><5E893DB832F57341992548CDBB33316398C53F6D0C@EMBX01-HQ.jnpr.net><006701cb91be$e5b529a0$6428460a@china.huawei.com><2CCE3984-04BC-4A59-B2EF-F0D2BBACB594@cisco.com> <E6E66922099CFB4391FAA7A7D3238F9F20AF8DB7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <40FB0FFB97588246A1BEFB05759DC8A004F7B004@S4DE9JSAANI.ost.t-com.de>
In-Reply-To: <40FB0FFB97588246A1BEFB05759DC8A004F7B004@S4DE9JSAANI.ost.t-com.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ahmpls-tp@lists.itu.int" <ahmpls-tp@lists.itu.int>, "pwe3@ietf.org" <pwe3@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] [mpls] [PWE3] [AHMPLS-TP] Re: pollondraft-he-mpls-tp-csf-03.txt
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 14:56:46 -0000

I think you are missing the point.  Viz, any L2 technology will go through a PW and PWs already have a CSF equivalent.  The other TP clients are IP and MPLS, and they have their own detection mechanisms. 

Sent from my iPhone


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Manuel.Paul@telekom.de
> Sent: Thursday, December 02, 2010 6:40 AM
> To: lieven.levrau@alcatel-lucent.com; rajiva@cisco.com;
> yljiang@huawei.com
> Cc: mpls@ietf.org; nurit.sprecher@nsn.com; ahmpls-tp@lists.itu.int;
> pwe3@ietf.org; mpls-tp@ietf.org
> Subject: Re: [mpls] [PWE3] [AHMPLS-TP] Re:[mpls-tp] pollondraft-he-
> mpls-tp-csf-03.txt
> 
> 
> Agree with Lieven.
> 
> We need to avoid making predictions about the capability & complexity
> (& even existence) of a certain client layer technology (most of all
> considering terminal nodes connected by attachment circuits), but still
> provide effective fault notifications in packet transport applications.
> Herefore, IMHO, CSF is helpful and required.
> 
> Of course, we also strongly need to avoid confusing control plane and
> data plane tasks (e.g. relying on LDP session timeouts for fault
> detection).
> 
> Best regards
> Manuel
> 
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > LEVRAU, LIEVEN (LIEVEN)
> > Sent: Thursday, December 02, 2010 2:17 PM
> > To: Rajiv Asati (rajiva); Yuanlong Jiang
> > Cc: mpls@ietf.org; Sprecher,Nurit (NSN - IL/Hod HaSharon); MPLS-TP ad
> hoc
> > team; pwe3@ietf.org; mpls-tp@ietf.org
> > Subject: Re: [mpls] [PWE3] [AHMPLS-TP] Re:[mpls-tp] pollondraft-he-
> mpls-
> > tp-csf-03.txt
> >
> > provocative statement alert- We should as we are talking about MPLS-
> TP and
> > not about IP network layer.
> >
> > ./
> > Lieven
> > -----Original Message-----
> > From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> > Rajiv Asati (rajiva)
> > Sent: 02 December 2010 14:14
> > To: Yuanlong Jiang
> > Cc: Sprecher, Nurit (NSN - IL/Hod HaSharon); MPLS-TP ad hoc team;
> > mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org
> > Subject: Re: [mpls] [PWE3] [AHMPLS-TP] Re: [mpls-tp] pollondraft-he-
> mpls-
> > tp-csf-03.txt
> >
> > Are we ignoring the existence of BFD altogether?
> >
> > Cheers,
> > Rajiv
> >
> > Sent from my Phone
> >
> > On Dec 1, 2010, at 8:19 PM, Yuanlong Jiang <yljiang@huawei.com>
> wrote:
> >
> > > John,
> > >
> > > Typically, IP will only detect a failure in a time scale of
> minutes.
> > > That is one reason why MPLS-TP OAM and Protection & Switching is
> needed.
> > > I am not sure which mechanism in MPLS provides the CSF-like
> capability,
> > could you give more hints?
> > >
> > > Thanks
> > > Yuanlong
> > >
> > > ----- Original Message ----- From: "John E Drake"
> <jdrake@juniper.net>
> > > To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)"
> <nurit.sprecher@nsn.com>om>;
> > "Yuanlong Jiang" <yljiang@huawei.com>om>; "Loa Andersson" <loa@pi.nu>nu>;
> > <mpls@ietf.org>rg>; <mpls-tp@ietf.org>rg>; <pwe3@ietf.org>rg>; "MPLS-TP ad hoc
> > team" <ahmpls-tp@lists.itu.int>
> > > Sent: Wednesday, December 01, 2010 9:29 PM
> > > Subject: RE: [PWE3] [AHMPLS-TP] Re: [mpls-tp] poll ondraft-he-mpls-
> tp-
> > csf-03.txt
> > >
> > >
> > >> Nurit,
> > >>
> > >> As I understand the original requirement from Malcolm Betts, this
> > capability is required for those cases in which a client is unable to
> > detect the failure of its peer.  In MPLS-TP, we have three clients,
> PW, IP,
> > and MPLS, and I am quite sure that IP and MPLS clients can take care
> of
> > themselves wrt detecting peer failure.
> > >>
> > >> Thanks,
> > >>
> > >> John
> > >>
> > >> Sent from my iPhone
> > >>
> > >>> -----Original Message-----
> > >>> From: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> > >>> [mailto:nurit.sprecher@nsn.com]
> > >>> Sent: Wednesday, December 01, 2010 4:47 AM
> > >>> To: John E Drake; Yuanlong Jiang; Loa Andersson; mpls@ietf.org;
> mpls-
> > >>> tp@ietf.org; pwe3@ietf.org; MPLS-TP ad hoc team
> > >>> Subject: RE: [PWE3] [AHMPLS-TP] Re: [mpls-tp] poll ondraft-he-
> mpls-tp-
> > >>> csf-03.txt
> > >>>
> > >>> But what about other client services... e.g. adapted by service-
> LSP
> > and
> > >>> not by PWE3?
> > >>>
> > >>> -----Original Message-----
> > >>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> Behalf
> > Of
> > >>> ext John E Drake
> > >>> Sent: Wednesday, December 01, 2010 2:35 PM
> > >>> To: Yuanlong Jiang; Loa Andersson; mpls@ietf.org; mpls-
> tp@ietf.org;
> > >>> pwe3@ietf.org; MPLS-TP ad hoc team
> > >>> Subject: Re: [PWE3] [AHMPLS-TP] Re: [mpls-tp] poll
> > >>> ondraft-he-mpls-tp-csf-03.txt
> > >>>
> > >>> I am not convinced.  It seems like it belongs in the Pseudo Wire
> > >>> application, which already has this capability.
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>>
> > >>> > -----Original Message-----
> > >>> > From: Yuanlong Jiang [mailto:yljiang@huawei.com]
> > >>> > Sent: Wednesday, December 01, 2010 1:07 AM
> > >>> > To: Loa Andersson; mpls@ietf.org; mpls-tp@ietf.org;
> pwe3@ietf.org;
> > >>> > MPLS-TP ad hoc team
> > >>> > Subject: [AHMPLS-TP] Re: [mpls-tp] poll on draft-he-mpls-tp-
> csf-
> > >>> 03.txt
> > >>> >
> > >>> > Support.
> > >>> >
> > >>> > I believe this mechanism is needed in MPLS-TP.
> > >>> >
> > >>> > Thanks
> > >>> > Yuanlong
> > >>> >
> > >>> > ----- Original Message -----
> > >>> > From: "Loa Andersson" <loa@pi.nu>
> > >>> > To: <mpls@ietf.org>rg>; <mpls-tp@ietf.org>rg>; <pwe3@ietf.org>rg>;
> "MPLS-TP
> > ad
> > >>> > hoc
> > >>> > team" <ahmpls-tp@lists.itu.int>
> > >>> > Sent: Thursday, November 18, 2010 7:56 PM
> > >>> > Subject: [mpls-tp] poll on draft-he-mpls-tp-csf-03.txt
> > >>> >
> > >>> >
> > >>> > > all,
> > >>> > >
> > >>> > > this is to start a two week poll on making
> > >>> > >
> > >>> > > http://www.ietf.org/internet-drafts/draft-he-mpls-tp-csf-
> 03.txt
> > >>> > >
> > >>> > > a mpls working group document.
> > >>> > >
> > >>> > > Please send comments support/not support to the mpls-tp
> maililng
> > >>> > list.
> > >>> > >
> > >>> > > The poll ends Thursday Dec 2, 2010.
> > >>> > >
> > >>> > > /Loa
> > >>> > > --
> > >>> > >
> > >>> > >
> > >>> > > Loa Andersson                         email:
> > >>> > loa.andersson@ericsson.com
> > >>> > > Sr Strategy and Standards Manager            loa@pi.nu
> > >>> > > Ericsson Inc                          phone: +46 10 717 52 13
> > >>> > >                                              +46 767 72 92 13
> > >>> > > _______________________________________________
> > >>> > > mpls-tp mailing list
> > >>> > > mpls-tp@ietf.org
> > >>> > > https://www.ietf.org/mailman/listinfo/mpls-tp
> > >>>
> > >>> _______________________________________________
> > >>> pwe3 mailing list
> > >>> pwe3@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/pwe3
> > >
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www.ietf.org/mailman/listinfo/pwe3
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls