Re: BFD docs to last call

David Ward <dward@cisco.com> Mon, 24 March 2008 19:16 UTC

In-Reply-To: <DF971101-B25C-45C1-AAED-EAE5BE92F5D5@cisco.com>
References: <E2E4E076-242F-4D07-BAF5-97C3167C4791@cisco.com> <DF971101-B25C-45C1-AAED-EAE5BE92F5D5@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <476D0AB7-9FB8-4D71-AB17-79ACDE7BD2C0@cisco.com>
Content-Transfer-Encoding: 7bit
From: David Ward <dward@cisco.com>
Subject: Re: BFD docs to last call
Date: Mon, 24 Mar 2008 14:14:19 -0500
To: David Ward <dward@cisco.com>
Cc: kireeti@juniper.net, Dave Katz <dkatz@juniper.net>, thomas.nadeau@bt.com, Ross Callon <rcallon@juniper.net>, BFD WG <rtg-bfd@ietf.org>, Rahul Aggarwal <rahul@juniper.net>
Precedence: list
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

oops

On Mar 24, 2008, at 2:01 PM, David Ward wrote:

> All -
>
> These documents have finished WG LC.  One document draft-ietf-bfd- 
> v4v6-1hop, required some clarifying text (thanks Carlos) which has  
> already been submitted. Thus, we are calling WG LC "completed."
>
> There has been a recent modification to the MIB (-04) but, we need  
> another advancement of the MIB to include all the functionality in  
> the documents below. We will progress what we have but the MIB will  
> hold up PS status (we will have official versions thankfully of all  
> of the base documents).
>
> As a WG we will not turn to the point to multipoint spec and the  
> DHCP bootstrapping drafts.
>

                                 s/not/now



Sorry about that ...

-DWard

> Onwards and upwards ...
>
>
> -DWard, Jeff Haas
>
>
>
> On Feb 5, 2008, at 11:51 AM, David Ward wrote:
>
>> All -
>>
>> We would like to last call the entire suite of the BFD protocol  
>> documents. It has been a long time coming but, the extra time has  
>> allowed for many interoperable implementations to be created and  
>> through feedback from implementors; the specifications have been  
>> updated to cover corner cases, clear up language/grammar/ 
>> intention, etc. In general, the documents provide what is  
>> necessary to implement interoperable BFD and should be considered  
>> complete.
>>
>> http://tools.ietf.org/html/draft-ietf-bfd-base-07
>> http://tools.ietf.org/html/draft-ietf-bfd-generic-04
>> http://tools.ietf.org/html/draft-ietf-bfd-v4v6-1hop-07
>> http://tools.ietf.org/html/draft-ietf-bfd-multihop-06
>> http://tools.ietf.org/html/draft-ietf-bfd-mpls-05
>>
>>
>> We have not put the MIB (expired and being updated) and the new  
>> multipoint draft into Last Call. As soon as the MIB is updated we  
>> will get an expert review and then LC.
>>
>>
>> For this last call, if you have comments or nits please have the  
>> subject line include for example: bfd-base-07 (as appropriate) so  
>> that your email clearly specifies which draft you are commenting  
>> on. Given that everyone is so familiar w/ the set of  
>> specifications and the delta to this rev is rather small, we are  
>> going to have a 2.5 week Last Call period. It will end Feb 22, 2008.
>>
>> Many thanks to the implementors and reviewers that provided feedback.
>>
>>
>> -DWard, Jeff Haas
>

Re: BFD docs to last call David Ward
Re: BFD docs to last call David Ward