IETF Logo Mail Archive

issues about draft-ietf-bfd-rfc5884-clarifications-02

peng.shaofu@zte.com.cn Wed, 15 July 2015 09:21 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B82481A0103 for <rtg-bfd@ietfa.amsl.com>; Wed, 15 Jul 2015 02:21:46 -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 kv5_7lUxx_JL for <rtg-bfd@ietfa.amsl.com>; Wed, 15 Jul 2015 02:21:44 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 1754A1A00BF for <rtg-bfd@ietf.org>; Wed, 15 Jul 2015 02:21:43 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 9606AC657757F for <rtg-bfd@ietf.org>; Wed, 15 Jul 2015 17:17:20 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id E1F4A3F4C18E for <rtg-bfd@ietf.org>; Wed, 15 Jul 2015 17:21:35 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id t6F9LARZ083728 for <rtg-bfd@ietf.org>; Wed, 15 Jul 2015 17:21:10 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
To: rtg-bfd@ietf.org
Subject: issues about draft-ietf-bfd-rfc5884-clarifications-02
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFBF0A0F7B.44E43B3D-ON48257E83.00335600-48257E83.003360F2@zte.com.cn>
From: peng.shaofu@zte.com.cn
Date: Wed, 15 Jul 2015 17:21:09 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2015-07-15 17:20:50, Serialize complete at 2015-07-15 17:20:50
Content-Type: multipart/alternative; boundary="=_alternative 003360F148257E83_="
X-MAIL: mse01.zte.com.cn t6F9LARZ083728
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/23DXUmYsLk8V1WzIyWr2fvau68M>
X-Mailman-Approved-At: Wed, 15 Jul 2015 07:30:04 -0700
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2015 09:21:46 -0000

hi authors

It is neccessary to address the case that different ingress LSR establish 
BFD session with the same egress LSR, with same FEC, same local 
descriminator.
I think it is very useful to introduce a BFD Initiator TLV to LSP ping 
echo request message, to distinguish different ingress LSR. So that 
ingress allocate LD based on tuple <FEC, LSP> as defined in this draft, 
but egress allocate LD based on tuple <Initiator, FEC, RD>.

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.

v2.23.0 | Report a Bug | By Email