Re: [mpls-tp] Demultiplexing to BFD sessions

"Shahram Davari" <davari@broadcom.com> Fri, 11 June 2010 18:03 UTC

Return-Path: <davari@broadcom.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 86BDF3A6A16 for <mpls-tp@core3.amsl.com>; Fri, 11 Jun 2010 11:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 5OdlWTtNx3xV for <mpls-tp@core3.amsl.com>; Fri, 11 Jun 2010 11:03:22 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 7FA9B3A6977 for <mpls-tp@ietf.org>; Fri, 11 Jun 2010 11:03:22 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 11 Jun 2010 11:03:12 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Fri, 11 Jun 2010 11:03:12 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Mach Chen" <mach@huawei.com>, "Mukund Mani" <mukund.mani@gmail.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Fri, 11 Jun 2010 11:03:10 -0700
Thread-Topic: [mpls-tp] Demultiplexing to BFD sessions
Thread-Index: AcsJTarPL4Ybsaw3RXKOM7IlM2cdkAAQpUIQ
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD693F1709EB2@SJEXCHCCR02.corp.ad.broadcom.com>
References: <AANLkTikZurkVBrPNBjL-v7zdZ9dTLUBDuBnNDPsCrnJf@mail.gmail.com> <2F87F171744E4F28B6391D07C5E4E618@m55527c>
In-Reply-To: <2F87F171744E4F28B6391D07C5E4E618@m55527c>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 600CA5EA3KC970250-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [mpls-tp] Demultiplexing to BFD sessions
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: Fri, 11 Jun 2010 18:03:23 -0000

Hi,

Why would one need to run more than one BFD session over an LSP?

Thanks,
Shahram

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Mach Chen
Sent: Friday, June 11, 2010 3:05 AM
To: Mukund Mani; mpls-tp@ietf.org
Subject: Re: [mpls-tp] Demultiplexing to BFD sessions

Hi Mukund,

I also have the same question about this.

As to the BFD discriminator, IMHO, we should keep using it as it be, because 
it may not be enough to demultiplex the BFD session only based on the label, 
this is especially true when there are more than two BFD sessions over the 
LSP.

BTW, it seems that explicit null label distribution is not excluded (and 
IMHO it should be excluded as PHP) in MPLS-TP (do I miss something?) , and 
it is one of the issues that LSP-Ping for BFD session bootstrap is trying to 
reslove.

Best regards,
Mach

--------------------------------------------------
From: "Mukund Mani" <mukund.mani@gmail.com>
Sent: Friday, June 11, 2010 2:24 PM
To: <mpls-tp@ietf.org>
Subject: [mpls-tp] Demultiplexing to BFD sessions

> Hi TP-Group
> **
> *draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00 *states in Section 3
>
> "When using BFD over MPLS-TP LSPs, the BFD discriminator MUST either be
> signaled via LSP-Ping or be statically configured."
>
> *draft-ietf-mpls-tp-bfd-cc-cv-00 *states in Section 3.5.6
>
> "MPLS labels at peer MEPs are used to provide context for the received BFD
> packets."
>
> As I understand from the statement in the CC/CV draft, since discriminator
> values are not required for demultiplexing to the BFD session anymore, we
> will not need LSP Ping to bootstrap BFD session for TP LSP.
>
> But *draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00 *specifies that LSP 
> Ping
> can also be used to signal BFD discriminator.
>
> So is LSP Ping still really needed in the context of BFD over MPLS-TP?
>
> Also as a part of MPLS-TP OAM could somebody explain why such a deviation 
> is
> taken from the BFD-BASE mode of demultiplexing which even BFD-MPLS uses
> (discriminator values instead of MPLS labels), but MPLS-TP goes in for
> demultiplexing using labels....
>
> Could somebody please clarify this..?
>
>
> With Regards
> Mukund
> <http://tools.ietf.org/html/draft-ietf-mpls-tp-bfd-cc-cv-00>
>



> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
> 
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp