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

Greg Mirsky <gregimirsky@gmail.com> Thu, 02 December 2010 17:58 UTC

Return-Path: <gregimirsky@gmail.com>
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 9D1153A6967; Thu, 2 Dec 2010 09:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.96
X-Spam-Level:
X-Spam-Status: No, score=-2.96 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 jR1wHyJsSNjc; Thu, 2 Dec 2010 09:58:58 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 9ADDB3A69A3; Thu, 2 Dec 2010 09:58:57 -0800 (PST)
Received: by qyk34 with SMTP id 34so4162021qyk.10 for <multiple recipients>; Thu, 02 Dec 2010 10:00:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=S1Sp5IFfwEXftQ0Fe9Ujz76L92xnq3pwyUfjKn7NiKY=; b=sGyISY2Ljcc9XpcSee4WG9Kh0Vp5ah3cJQic3Z+8t8MvMRiUhjFvIBzPgIeyyxhC2l G7LxHzl3icU2w97WI/gU+zv8Z+rR+0ifrLb4we5cmoL6xjhfaHcy1yi4S4tVKINBOqC+ YnqIS/wZU5oJDxLlN7sBAtbF4l5kiXqOJ6oEU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uWq12wb6I5fVPmFUf45+8klqAPrDbE1ul2mXV5tm6b763poZSnlS0iGA6bfOInWQP6 9LY0fGW22AZ7jrq2QsUX3X0S/JcytDIuRrmpkZNlW+kUfdZqHEjKdQh8u6G96hejsDRN j7A7szY8MRvfpOZ/WjpJ3KQAwoosYd4MnTYow=
MIME-Version: 1.0
Received: by 10.224.28.147 with SMTP id m19mr264007qac.255.1291312812969; Thu, 02 Dec 2010 10:00:12 -0800 (PST)
Received: by 10.220.176.68 with HTTP; Thu, 2 Dec 2010 10:00:12 -0800 (PST)
In-Reply-To: <5E893DB832F57341992548CDBB33316398C549DDBE@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>
Date: Thu, 2 Dec 2010 10:00:12 -0800
Message-ID: <AANLkTin3B_-fWy9YJ_ZR4eV+XDrnO1fosEnuvFoz_GG7@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
To: John E Drake <jdrake@juniper.net>
Content-Type: multipart/alternative; boundary=0015175cb07c82cf6a049671319b
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 17:58:59 -0000

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> 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] On Behalf Of
> > LEVRAU, LIEVEN (LIEVEN)
> > Sent: Thursday, December 02, 2010 5:17 AM
> > 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
>