IETF Logo Mail Archive

Re: I-D ACTION:draft-shen-bfd-intf-p2p-nbr-00.txt

Naiming Shen <naiming@cisco.com> Mon, 09 April 2007 07:56 UTC

Return-path: <rtg-bfd-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Haojs-0003X9-DJ; Mon, 09 Apr 2007 03:56:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Haojr-0003X4-0J for rtg-bfd@ietf.org; Mon, 09 Apr 2007 03:56:35 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Haojp-0000Kj-Jp for rtg-bfd@ietf.org; Mon, 09 Apr 2007 03:56:34 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-5.cisco.com with ESMTP; 09 Apr 2007 00:56:33 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l397uWG9027604 for <rtg-bfd@ietf.org>; Mon, 9 Apr 2007 00:56:32 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l397uNEi010212 for <rtg-bfd@ietf.org>; Mon, 9 Apr 2007 07:56:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Apr 2007 00:56:22 -0700
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Apr 2007 00:56:22 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <4528727A-E25E-4C47-9EEA-F996C61F4DD2@cisco.com>
References: <E1HWe9i-0004Zp-AR@stiedprstage1.ietf.org> <3D93D8A8-F2CD-4F5D-BA37-5A2489E2C3DA@cisco.com> <29C50044-05B4-412E-B0D8-4B1B6F38672F@juniper.net> <E69131CB-20D2-4B5C-8485-831D6F038AC9@cisco.com> <448453AC-AAC4-4924-8BF2-87AC85907252@juniper.net> <F9A4058F-65FD-46DB-A3B7-681AB089A3EB@cisco.com> <5B807F72-EEB9-4D11-91E3-4798187CAABB@cisco.com> <078305F4-C44D-4853-8C96-23FF3E2338E2@cisco.com> <4528727A-E25E-4C47-9EEA-F996C61F4DD2@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6CF5DBD6-27D5-4CA5-92D6-35F939030FEB@cisco.com>
Content-Transfer-Encoding: 7bit
From: Naiming Shen <naiming@cisco.com>
Date: Mon, 09 Apr 2007 00:56:21 -0700
To: rtg-bfd@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 09 Apr 2007 07:56:22.0679 (UTC) FILETIME=[90C63270:01C77A7C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=524; t=1176105393; x=1176969393; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=naiming@cisco.com; z=From:=20Naiming=20Shen=20<naiming@cisco.com> |Subject:=20Re=3A=20I-D=20ACTION=3Adraft-shen-bfd-intf-p2p-nbr-00.txt=20 |Sender:=20; bh=WRtrnE6i+VU3uZIxkJ1/r/if0qPTake6hEAW6Cs2DXc=; b=DInu+XQYOXbzMrCMvm9boDvsjJOW326MGvmLMzeoojz5VxeGvBAioCxtkudMLrEqoUTgW3YS J5dbz4ycqKY/u2yaVSFGwQkwNa0BJ2YNsxOgi8d78pSjmML0VoXg5m0OIDinsC6OHB9ymzYWR+ QipTUw9pOdSs/KxqGSzci/Ook=;
Authentication-Results: sj-dkim-1; header.From=naiming@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: Re: I-D ACTION:draft-shen-bfd-intf-p2p-nbr-00.txt
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Errors-To: rtg-bfd-bounces@ietf.org

Just to add one more thing that, even though this draft does not change
anything in terms of BFD base spec, but this scheme does generate unique
error conditions, such as detection of multiple peers over a point-to- 
point
interface. If the implementation does bring the session down, it  
needs to
report this with a new DIAG code to reflect this error. Although the  
detection
mechanism is out side the scope of this document. Thanks to the folks
brought this to my attention. Will fix.

thanks.
- Naiming

v2.23.0 | Report a Bug | By Email