RE: BFD echo mode

"Nobo Akiya (nobo)" <nobo@cisco.com> Thu, 27 November 2008 09:42 UTC

Return-Path: <rtg-bfd-bounces@ietf.org>
X-Original-To: rtg-bfd-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-bfd-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40D263A6CCF; Thu, 27 Nov 2008 01:42:25 -0800 (PST)
X-Original-To: rtg-bfd@core3.amsl.com
Delivered-To: rtg-bfd@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5548F3A6CCF for <rtg-bfd@core3.amsl.com>; Thu, 27 Nov 2008 01:42:24 -0800 (PST)
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 aUFdJQmEJj88 for <rtg-bfd@core3.amsl.com>; Thu, 27 Nov 2008 01:42:23 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 82ADC3A67E9 for <rtg-bfd@ietf.org>; Thu, 27 Nov 2008 01:42:23 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,674,1220227200"; d="scan'208";a="110789953"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 27 Nov 2008 09:41:53 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id mAR9fqIT027955; Thu, 27 Nov 2008 01:41:52 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id mAR9fm1k008858; Thu, 27 Nov 2008 09:41:52 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Nov 2008 01:41:52 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: BFD echo mode
Date: Thu, 27 Nov 2008 01:41:11 -0800
Message-ID: <F3F69139C275F848A1DB1518DC2C216806859108@xmb-sjc-22c.amer.cisco.com>
In-Reply-To: <77ead0ec0811260956u62e0e27aj66fbdba29453c5ad@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: BFD echo mode
Thread-Index: AclP8GNH/wXPju4nTCy2/AtmdLVmZQAgfngg
References: <77ead0ec0811260956u62e0e27aj66fbdba29453c5ad@mail.gmail.com>
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>, David Ward <dward@cisco.com>, Dave Katz <dkatz@juniper.net>, Nitin Bahadur <nitinb@juniper.net>
X-OriginalArrivalTime: 27 Nov 2008 09:41:52.0810 (UTC) FILETIME=[60DA08A0:01C95074]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1286; t=1227778913; x=1228642913; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=nobo@cisco.com; z=From:=20=22Nobo=20Akiya=20(nobo)=22=20<nobo@cisco.com> |Subject:=20RE=3A=20BFD=20echo=20mode |Sender:=20; bh=A1jTiAer6aJHeVRRAAp4+A4DO1Zj5L1whAP+jXFd1LY=; b=fv3Lk86oMrp+rFzcbYMsIvPhhzm/ASmMgqf1xBLMXeU+uP9UmmpBn1XNAK QSJ8jE8H22dsjF2qtlVEMPg6gizPiuBw9othf/3D3zTWf+H94ay79Tpci91X Ahi8CN2v87;
Authentication-Results: sj-dkim-3; header.From=nobo@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Cc: rtg-bfd@ietf.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

 
Hello Vishwas.

Couple of add-on comments, for single-hop.

> Seeing some vendor documentation it seems they use a seperate 
> port for the echo mode - as the source and the destination 
> address.

I hope vendors aren't using different udp dest port for echo packets.

http://tools.ietf.org/html/draft-ietf-bfd-v4v6-1hop-08 Sec4.1.

BFD Echo packets MUST be transmitted in UDP packets with destination
UDP port 3785 in an IPv4 packet.

> Can the asusmption that the echo mode packet is a BFD packet 
> be made (so the BFD source / dest packet identifiers can be 
> used)? The base BFD spec seems to state the content of the 
> packet need not be specified as the packet is just looped back.

BFD echo packets can be identified by UDP dest port 3785.
Data beyond UDP header is not specified, and that's left up to vendors.

> So I can see how we could look an IP packet in the case of 
> Single Hop (by having the MAC Destination Address of the 
> peer) but having IP address and destination the same (as of 
> the source).

I don't think there's anything that specifies that dest & src addresses
must be the same. For dest addresses tho, it maybe easier to
demultiplex if dest address is the outgoing interface.

Thanx,
Nobo