[mpls-tp] Demultiplexing to BFD sessions

Mukund Mani <mukund.mani@gmail.com> Fri, 11 June 2010 06:24 UTC

Return-Path: <mukund.mani@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 66B9E3A69CF for <mpls-tp@core3.amsl.com>; Thu, 10 Jun 2010 23:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level:
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
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 v0-O0Fy8QTaL for <mpls-tp@core3.amsl.com>; Thu, 10 Jun 2010 23:24:14 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 496183A68D6 for <mpls-tp@ietf.org>; Thu, 10 Jun 2010 23:24:14 -0700 (PDT)
Received: by vws9 with SMTP id 9so785524vws.31 for <mpls-tp@ietf.org>; Thu, 10 Jun 2010 23:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=NLSd6rx/OVEuT5ls1qRfb/fXCZdUhZ/KnnvsrkHkAl0=; b=Y5T/CxKkT/rgE5UXJl2H2/9nHroIERs/ULCxTIVQLViTxhfK02nBEzXGdcqEqDh727 orkLlc1KEoqEQ0i9TWMiH4q/qI/gdPmbSw4eCnKq+iFWfKeHugqwc91GMWW+Xx6ihPLi SbX/o9hF6LYwK2WsIAvSJ/pFK2H0GPwqfpWD0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bMStLDzshXkB8WEA7xf4Ynr+bEn2QSI2wtOFKvT1vFCp0VMniaPDqScDCIpdbmdC50 HmAOzV5pU/ODNFjc9b2OB+WiWl733JR/4stg+GKeUCydjH0Je0jHF+KOpcPwYp6lJaXj 5wZKJcWHl2sAdKtUHAoVM8qrvD3kna9Z6q9Oc=
MIME-Version: 1.0
Received: by 10.224.23.131 with SMTP id r3mr283462qab.378.1276237453550; Thu, 10 Jun 2010 23:24:13 -0700 (PDT)
Received: by 10.229.97.201 with HTTP; Thu, 10 Jun 2010 23:24:11 -0700 (PDT)
Date: Fri, 11 Jun 2010 11:54:11 +0530
Message-ID: <AANLkTikZurkVBrPNBjL-v7zdZ9dTLUBDuBnNDPsCrnJf@mail.gmail.com>
From: Mukund Mani <mukund.mani@gmail.com>
To: mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=0014850438aa1165d80488bb30ee
Subject: [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 06:24:15 -0000

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>