RE: BFD UDP ports

"Nobo Akiya (nobo)" <nobo@cisco.com> Sat, 06 December 2008 01:26 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 94D813A6986; Fri, 5 Dec 2008 17:26:22 -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 131E73A692E for <rtg-bfd@core3.amsl.com>; Fri, 5 Dec 2008 17:26:21 -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 gj3D+wUMd3Nw for <rtg-bfd@core3.amsl.com>; Fri, 5 Dec 2008 17:26:19 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id DC9BB3A690E for <rtg-bfd@ietf.org>; Fri, 5 Dec 2008 17:26:19 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,723,1220227200"; d="scan'208";a="207637306"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 06 Dec 2008 01:26:15 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mB61QFhP019752; Fri, 5 Dec 2008 17:26:15 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mB61QFHt027764; Sat, 6 Dec 2008 01:26:15 GMT
Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Dec 2008 17:26:15 -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 UDP ports
Date: Fri, 05 Dec 2008 17:25:43 -0800
Message-ID: <F3F69139C275F848A1DB1518DC2C216806945B2F@xmb-sjc-22c.amer.cisco.com>
In-Reply-To: <77ead0ec0812050939q837b20fh54105e245e7e0fb6@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: BFD UDP ports
Thread-Index: AclXAHscOGI0fpI6RW+3V+3v1Fv5EgAQFf7A
References: <77ead0ec0812041230w6f9e0172i19eb8a08437fd023@mail.gmail.com> <C55D9EE3.31BC4%nitinb@juniper.net> <F3F69139C275F848A1DB1518DC2C2168068E4E84@xmb-sjc-22c.amer.cisco.com> <77ead0ec0812050939q837b20fh54105e245e7e0fb6@mail.gmail.com>
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 06 Dec 2008 01:26:15.0148 (UTC) FILETIME=[A18AAAC0:01C95741]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3000; t=1228526775; x=1229390775; c=relaxed/simple; s=sjdkim1004; 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=20UDP=20ports |Sender:=20; bh=fKkaGeSqH0n2tGJnYV4hhs7mstFKUC+8w5lkuXZkNHA=; b=qkngsdvC/snTpe1liOlCJRLkCt9pC20KQxsDyTUPZKLqkYD/3ouZCWD/WN sdCo500E8YELBXardXtdDnjqoggM4TKJUsI04T0EIxzcLgHdotcsnkGEaQQX CJhru+WdYWNxDpOXZrD260XRQm14gBjvFt7VbuYEk0axGMruX0a90=;
Authentication-Results: sj-dkim-1; header.From=nobo@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: rtg-bfd@ietf.org, David Ward <dward@cisco.com>, Dave Katz <dkatz@juniper.net>
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.

> Another question I had in mind was regarding the use of the 
> "echo mode". Should we allow parallel sending of echo as well 
> as asynch packets, or at one time only one mechanism needs to 
> be active?

In echo mode, async packets are alos needed to support prarameter
changes. But the base draft Sec 6.4 suggests that the rate can be
slower since echo packets are checking the liveliness.

Thanx,
Nobo

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com] 
> Sent: Saturday, December 06, 2008 2:40 AM
> To: Nobo Akiya (nobo)
> Cc: Nitin Bahadur; David Ward; Dave Katz; rtg-bfd@ietf.org
> Subject: Re: BFD UDP ports
> 
> Hi Nitin/ Nobo,
> 
> Thanks for your replies. So I guess we will have to use the 
> same port for IPv4 and IPv6 then, hack the OS or whatever other way.
> 
> Nobo, I agree we should make the recomendation as a MAY 
> instead of a may as I had suggested.
> 
> Another question I had in mind was regarding the use of the 
> "echo mode". Should we allow parallel sending of echo as well 
> as asynch packets, or at one time only one mechanism needs to 
> be active?
> 
> Thanks again,
> Vishwas
> 
> > Hello Vishwas, Nitin.
> >
> >>
> >> On 12/4/08 12:30 PM, "Vishwas Manral" 
> <vishwas.ietf@gmail.com> wrote:
> >>
> >> > Hi
> >> >
> >> > 1. I am a bit confused about using the same BFD destination port 
> >> > for
> >> > IPv4 and IPv6. Shouldn't we have different port numbers? 
> I realized 
> >> > that even RIP which uses UDP uses different ports for 
> IPv4 and IPv6.
> >> > Using the same port can be an issue in a few heavily 
> used OS. Has 
> >> > anyone implemented BFD for IPv6?
> >>
> >> Using the same port should be for v4 & v6 should be fine. 
> I know of 
> >> at least
> >> 1 implementation ;-)
> >>
> >> Thanks
> >> Nitin
> >>
> >
> > I know of another implementation which same dest port is 
> used for v4 &
> > v6 =)
> >
> >> 2. As BFD source port is not used for packet replies and as the 
> >> Source address/ ifindex may be a unique identifier for a 
> source, do 
> >> we need not have the condition which states "source port number 
> >> SHOULD be unique among all BFD sessions on the system". Can we 
> >> downgrade this condition to a may?
> >
> > I tripped over this requirement as well, and I agree that 
> measurement 
> > of the wording strength is a bit confusing.
> >
> > One soft correction on your statement is that source port 
> MAY be used 
> > as a demultiplexing *aid*.
> >
> > http://tools.ietf.org/html/draft-ietf-bfd-v4v6-1hop-08 Sec4.1:
> >
> >   An implementation MAY use the UDP port source number to aid in
> >   demultiplexing incoming BFD Control packets, but ultimately the
> >   mechanisms in [BFD] MUST be used to demultiplex incoming 
> packets to
> >   the proper session.
> >
> > Thanx,
> > Nobo
> >
>