Re: [OSPF] update "draft-kou-ospf-immediately-replying-hello-00.txt"

This draft was presented in Dallas. A show-of-hands poll in a
Dallas was mixed with more people against than for making it accepting
it as a working group document. We than tabled it to further discussion
on the OSPF WG list.

Speaking as a WG member, my personal opinion is that the WG should
accept this document an an informational of BCP track RFC.

1. This behavior is not new - there are several implementations
that already reply immediately in certain situations.
2. There are many ways of doing this and it is unlikely we will
agree on the exact details of how it should be done. I, for one,
have implemented it differently than documented in this draft.

Thanks,
Acee

Zengjie Kou wrote:

>hi,all
> I updated the draft "draft-kou-ospf-immediately-replying-hello-00.txt". The link is following:
>http://tools.ietf.org/wg/ospf/draft-kou-ospf-immediately-replying-hello-01.txt
> In the new version, interoperation of immediate hello is added and the additional immediate hello
>traffic is avoided by auto configuration.
> The abstract is following:
>This memo documents an extension of the OSPF protocol to reach    
>   "ExStart" state more quickly. Currently, the OSPF behavior requires    
>   the Hello Packet to be sent between the neighbors every    
>   HelloInterval. This document proposes to generalize the use of    
>   Immediately Replying Hello which could reduce the time required to    
>   reach the OSPF "ExStart" state and  expedite the routing table    
>   convergence.  
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www1.ietf.org/mailman/listinfo/ospf
>
>  
>

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf