LC comments single hop

Carlos Garcia Braschi <cgbraschi@gmail.com> Fri, 08 July 2005 10:05 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=mCgN2wkeJGxVivZfFNUMpedr/nVbnScWUe2hFY/qfSBKThUWnv5XgxOBmJZ+FaVGsWZCW7AvoIgGwxr7+EeIEqybK9u9QK1k1aoETb93nzHS+kttn8ppjPiZhdGUEAuzQ+ZN8wqj3HlE4IfCBF42f0ZQkc/G2Js7lfEfUUPXMMs=
Message-ID: <9e31186f0507080305174144e@mail.gmail.com>
Date: Fri, 08 Jul 2005 12:05:22 +0200
From: Carlos Garcia Braschi <cgbraschi@gmail.com>
To: rtg-bfd@ietf.org, dward@cisco.com, dkatz@juniper.net
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: LC comments single hop
Precedence: list
Reply-To: Carlos Garcia Braschi <cgbraschi@gmail.com>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

Hello, 

It may be a contrived case, but:
In the context of using BFD with RIP
If 
- The RIP messages are used to detect with whom to establish BFD
sessions. That is, BFD sessions are established with senders from
which announcements are received.
- One of the two sides is a passive RIP listener.

(This may make sense where the passive listener is redistributing the
received routes to another protocol).

Then
The non-passive side cannot take the "Active" role in the BFD session,
as it does not know where to send the BFD packets (until it receives
one with My Discriminator different from zero).

A similar case may happen with static routes (when they are not symmetrical).

I don't know if this contrived case warrants changing the wording on
point 3 of the 1-hop draft, from:
'As such, both sides of a session MUST take the "Active" role'
to
'As such, both sides of a session SHOULD take the "Active" role'

Regards,
Carlos.

> Date: Wed, 6 Jul 2005 11:09:38 -0500
> From: David Ward <dward@cisco.com>
> Subject: WG Last call on base and single hop
> To: rtg-bfd@ietf.org, dward@cisco.com, jhaas@nexthop.com
> Cc: dkatz@juniper.net
> Message-ID: <20050706110938.K13750@cfcentral.cisco.com>
> Content-Type: text/plain; charset=us-ascii
> 
> All -
>         As the base specifiction for BFD has stabilized as well as the
> single hop specification, we are going to have a 3 week WG Last Call ending
> July 31st. Assuming no major revisions (famous last words) will be required,
> we will shepherd the drafts forward at that time.
> 
> If you have comments, please reply to the WG and authors with the subject line:
> 
> subject: LC comments < base spec | single hop>
> 
> Here are the pointers to the docs.
> 
> http://www.ietf.org/internet-drafts/draft-ietf-bfd-v4v6-1hop-02.txt
> 
> http://www.ietf.org/internet-drafts/draft-ietf-bfd-base-02.txt
> 
> In other news, as Dave and I agreed in the last WG meeting, we will be
> submitting a "generic applicability" draft on how an app can boostrap BFD
> sessions so that we don't need individual drafts for each of our favorite
> protocols. Stay tuned.
> 
> The new draft MIB may or may not be published in time for Paris.
> 
> 
> -DWard
> 
>

LC comments single hop Carlos Garcia Braschi