Re: BFD UDP ports

David Ward <dward@cisco.com> Sat, 06 December 2008 15:35 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 665AD3A69F3; Sat, 6 Dec 2008 07:35:57 -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 C47C83A69F3 for <rtg-bfd@core3.amsl.com>; Sat, 6 Dec 2008 07:35:56 -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=[AWL=0.000, 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 xakLN3Qgl5mf for <rtg-bfd@core3.amsl.com>; Sat, 6 Dec 2008 07:35:55 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 94F133A6923 for <rtg-bfd@ietf.org>; Sat, 6 Dec 2008 07:35:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,724,1220227200"; d="scan'208";a="30242384"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 06 Dec 2008 15:35:50 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mB6FZolU023607; Sat, 6 Dec 2008 10:35:50 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mB6FZoYw013476; Sat, 6 Dec 2008 15:35:50 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 6 Dec 2008 10:35:50 -0500
Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 6 Dec 2008 10:35:49 -0500
In-Reply-To: <F3F69139C275F848A1DB1518DC2C216806945B2F@xmb-sjc-22c.amer.cisco.com>
References: <77ead0ec0812041230w6f9e0172i19eb8a08437fd023@mail.gmail.com> <C55D9EE3.31BC4%nitinb@juniper.net> <F3F69139C275F848A1DB1518DC2C2168068E4E84@xmb-sjc-22c.amer.cisco.com> <77ead0ec0812050939q837b20fh54105e245e7e0fb6@mail.gmail.com> <F3F69139C275F848A1DB1518DC2C216806945B2F@xmb-sjc-22c.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <C8E3EBAB-AEA7-488F-B5E5-53AECDE21B12@cisco.com>
Content-Transfer-Encoding: 7bit
From: David Ward <dward@cisco.com>
Subject: Re: BFD UDP ports
Date: Sat, 06 Dec 2008 09:35:48 -0600
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 06 Dec 2008 15:35:50.0007 (UTC) FILETIME=[50ECE070:01C957B8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3065; t=1228577750; x=1229441750; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dward@cisco.com; z=From:=20David=20Ward=20<dward@cisco.com> |Subject:=20Re=3A=20BFD=20UDP=20ports |Sender:=20 |To:=20=22Nobo=20Akiya=20(nobo)=22=20<nobo@cisco.com>; bh=iOH+evHw8YPN3lXEtftzB8gIF6VHFp6ygu3PJM+xBEw=; b=AEICIw05dP8tKc0KPnlAKp5IckMjGqJRXPUNJBRz6j16/JMcsxzLPBDHpV l+EwAsx+SMy5AIrZ1Ci1Qz/wR7pSPbfjKu4cA8OXQ43XuZhLJBqyMKfEslM/ f3j1fAtkIZ;
Authentication-Results: rtp-dkim-2; header.From=dward@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 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

See the description of the "control" session in echo mode.

-DWard

On Dec 5, 2008, at 7:25 PM, Nobo Akiya (nobo) wrote:

>
> 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
>>>
>>