IETF Logo Mail Archive

Re: [mpls-tp] Comment on draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00

Nitin Bahadur <nitinb@juniper.net> Thu, 08 July 2010 20:14 UTC

Return-Path: <nitinb@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 F2CF63A67D4 for <mpls-tp@core3.amsl.com>; Thu, 8 Jul 2010 13:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 gm69su5ERGSA for <mpls-tp@core3.amsl.com>; Thu, 8 Jul 2010 13:14:00 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id 538BC3A6836 for <mpls-tp@ietf.org>; Thu, 8 Jul 2010 13:13:58 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKTDYxhMHziXa2/3jH8D4k9O7y+lPTArop@postini.com; Thu, 08 Jul 2010 13:14:03 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 8 Jul 2010 13:07:33 -0700
From: Nitin Bahadur <nitinb@juniper.net>
To: Lavanya Srivatsa <lavanya.srivatsa@aricent.com>, MPLS TP <mpls-tp@ietf.org>
Date: Thu, 8 Jul 2010 13:07:30 -0700
Thread-Topic: Comment on draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00
Thread-Index: AcsZvzUPupWrtNc6SSaE4r2vhdTVswFGfybU
Message-ID: <C85B7E12.1275A%nitinb@juniper.net>
In-Reply-To: <AF085525D89CCA4EB233BE7E5BF2FDAB1694267FF2@GUREXMB02.ASIAN.AD.ARICENT.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.4.0.100208
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mpls-tp] Comment on draft-ietf-mpls-tp-lsp-ping-bfd-procedures-00
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, 08 Jul 2010 20:14:03 -0000

That is correct. Fixed in next revision.

Thanks
Nitin


On 7/2/10 1:18 AM, "Lavanya Srivatsa" <lavanya.srivatsa@aricent.com> wrote:

Hello authors of the draft,

In section 3 “Running BFD over MPLS-TP LSPs”, it is stated that while sending BFD packets, there may be a need to identify the MEP/MIP.

Identification of MEP, I agree.
However, IMO, BFD control packet being sent to a MIP is not correct.

A MIP does not generate/initiate packets by itself but only responds to packets being sent to it such as ping requests and traceroute requests. Since BFD is intended only for end points of an LSP/PW, I don’t think the need to identify MIPs while sending BFD control packets is necessary. So IMHO, this statement needs a rephrase.
Please let me know if you agree.

- Lavanya

________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

v2.8.7 | Report a Bug | By Email