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 18:26 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 817F428C163; Thu, 2 Dec 2010 10:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level:
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=0.348, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0pGF7s8h4eid; Thu, 2 Dec 2010 10:26:51 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 23A2E28C174; Thu, 2 Dec 2010 10:26:40 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTPflHz4A7nHMUG5AnVoqhHhMnspHIlnz@postini.com; Thu, 02 Dec 2010 10:28:07 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 10:25:19 -0800
From: John E Drake <jdrake@juniper.net>
To: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 2 Dec 2010 10:26:39 -0800
Thread-Topic: [mpls] [PWE3] [AHMPLS-TP] Re: [mpls-tp] pollondraft-he-mpls-tp-csf-03.txt
Thread-Index: AcuSSsfMxMZ2TXE3QHCJd682cs9NOAAAzZqQ
Message-ID: <5E893DB832F57341992548CDBB33316398C549E14C@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> <5E893DB832F57341992548CDBB33316398C549DDBE@EMBX01-HQ.jnpr.net> <AANLkTin3B_-fWy9YJ_ZR4eV+XDrnO1fosEnuvFoz_GG7@mail.gmail.com>
In-Reply-To: <AANLkTin3B_-fWy9YJ_ZR4eV+XDrnO1fosEnuvFoz_GG7@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5E893DB832F57341992548CDBB33316398C549E14CEMBX01HQjnprn_"
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, MPLS-TP ad hoc team <ahmpls-tp@lists.itu.int>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "Rajiv Asati \(rajiva\)" <rajiva@cisco.com>
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 18:26:57 -0000

At this level of discussion, what's your point?

Sent from my iPhone

From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Thursday, December 02, 2010 10:00 AM
To: John E Drake
Cc: LEVRAU, LIEVEN (LIEVEN); Rajiv Asati (rajiva); Yuanlong Jiang; 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

Dear John,
I think that MPLS-TP OAM CC/CV/RDI solution is based on BFD. It is not BFD in its entirety but is a subset with some aspects being specific for MPLS-TP and not part of RFC 5880.

Regards,
Greg
On Thu, Dec 2, 2010 at 5:45 AM, John E Drake <jdrake@juniper.net<mailto:jdrake@juniper.net>> wrote:
That statement is incorrect.  MPLS-TP uses BFD for CC/CV/RDI (http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-cc-cv-rdi/)


Sent from my iPhone


> -----Original Message-----
> From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of
> LEVRAU, LIEVEN (LIEVEN)
> Sent: Thursday, December 02, 2010 5:17 AM
> To: Rajiv Asati (rajiva); Yuanlong Jiang
> Cc: mpls@ietf.org<mailto:mpls@ietf.org>; Sprecher, Nurit (NSN - IL/Hod HaSharon); MPLS-TP ad
> hoc team; pwe3@ietf.org<mailto:pwe3@ietf.org>; mpls-tp@ietf.org<mailto: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> [mailto: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<mailto:mpls@ietf.org>; mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>; pwe3@ietf.org<mailto: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<mailto: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<mailto:jdrake@juniper.net>>
> > To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)"
> <nurit.sprecher@nsn.com<mailto:nurit.sprecher@nsn.com>>; "Yuanlong Jiang" <yljiang@huawei.com<mailto:yljiang@huawei.com>>; "Loa
> Andersson" <loa@pi.nu<mailto:loa@pi.nu>>; <mpls@ietf.org<mailto:mpls@ietf.org>>; <mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>>;
> <pwe3@ietf.org<mailto:pwe3@ietf.org>>; "MPLS-TP ad hoc team" <ahmpls-tp@lists.itu.int<mailto: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<mailto:nurit.sprecher@nsn.com>]
> >>> Sent: Wednesday, December 01, 2010 4:47 AM
> >>> To: John E Drake; Yuanlong Jiang; Loa Andersson; mpls@ietf.org<mailto:mpls@ietf.org>;
> mpls-
> >>> tp@ietf.org<mailto:tp@ietf.org>; pwe3@ietf.org<mailto: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> [mailto: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<mailto:mpls@ietf.org>; mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>;
> >>> pwe3@ietf.org<mailto: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<mailto:yljiang@huawei.com>]
> >>> > Sent: Wednesday, December 01, 2010 1:07 AM
> >>> > To: Loa Andersson; mpls@ietf.org<mailto:mpls@ietf.org>; mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>;
> pwe3@ietf.org<mailto: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<mailto:loa@pi.nu>>
> >>> > To: <mpls@ietf.org<mailto:mpls@ietf.org>>; <mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>>; <pwe3@ietf.org<mailto:pwe3@ietf.org>>; "MPLS-
> TP ad
> >>> > hoc
> >>> > team" <ahmpls-tp@lists.itu.int<mailto: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<mailto:loa.andersson@ericsson.com>
> >>> > > Sr Strategy and Standards Manager            loa@pi.nu<mailto:loa@pi.nu>
> >>> > > Ericsson Inc                          phone: +46 10 717 52 13
> >>> > >                                              +46 767 72 92 13
> >>> > > _______________________________________________
> >>> > > mpls-tp mailing list
> >>> > > mpls-tp@ietf.org<mailto:mpls-tp@ietf.org>
> >>> > > https://www.ietf.org/mailman/listinfo/mpls-tp
> >>>
> >>> _______________________________________________
> >>> pwe3 mailing list
> >>> pwe3@ietf.org<mailto:pwe3@ietf.org>
> >>> https://www.ietf.org/mailman/listinfo/pwe3
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org<mailto:pwe3@ietf.org>
> > https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> mpls mailing list
> mpls@ietf.org<mailto:mpls@ietf.org>
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org<mailto:mpls@ietf.org>
> https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls