[mpls] issues about draft-mirsky-mpls-bfd-directed-03
peng.shaofu@zte.com.cn Tue, 14 July 2015 07:56 UTC
Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F293C1A902D; Tue, 14 Jul 2015 00:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.21
X-Spam-Level:
X-Spam-Status: No, score=-104.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id viiergymh59l; Tue, 14 Jul 2015 00:56:33 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id DD12D1A8FD4; Tue, 14 Jul 2015 00:56:32 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 2B2009E601ED9; Tue, 14 Jul 2015 15:52:15 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 074D272669410; Tue, 14 Jul 2015 15:56:27 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id t6E7u6N3081855; Tue, 14 Jul 2015 15:56:06 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
To: gregory.mirsky@ericsson.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFC99D6FA7.6101BE65-ON48257E82.0026243E-48257E82.002B973C@zte.com.cn>
From: peng.shaofu@zte.com.cn
Date: Tue, 14 Jul 2015 15:56:05 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2015-07-14 15:55:50, Serialize complete at 2015-07-14 15:55:50
Content-Type: multipart/alternative; boundary="=_alternative 002B973948257E82_="
X-MAIL: mse01.zte.com.cn t6E7u6N3081855
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/r8Gsg46pyTyTpDhkS3HMO-GaujY>
Cc: mpls@ietf.org, spring@ietf.org
Subject: [mpls] issues about draft-mirsky-mpls-bfd-directed-03
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2015 07:56:35 -0000
hi greg As the document says: "When LSP ping is used to bootstrap BFD session this document updates this and defines that LSP Ping MUST include the FEC corresponding to the destination segment and SHOULD NOT include FECs corresponding to some or all of segment imposed by the initiator. " I think that it likes LDP BFD session establishment. The disadvantage is that at egress LSR we can not support many BFD session when many ingress LSR want to create BFD session with the same egerss LSR at the same time, if all these ingress LSR use same Local Discriminator. In fact, SR-tunnel is a special TE-tunnel, both of them can direct flow along specified forwarding path, only different in signal and label stack depth. The FEC contained in the LSP ping echo request message used to bootstrap SR-tunnel BFD should represent the flow characteristic, such as INGRESS-ID, EGRESS-ID, PATH-ID, etc. Maybe we can reuse TE FEC, such as "RSVP IPv4 LSP" as defined in RFC4379. We can create more PATHs for an SR-tunnel, we can configure SR-tunnel BFD or SR-tunnel PATH BFD. The node/adjacency segment FEC as discussed in draft-kumarkini-mpls-spring-lsp-ping are also neccessary for LSP ping/traceroute FEC validation. I would really love your opinion. thanks deccan -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.