Hi Mahesh and Jeff,
On 2020-07-20, 9:29 PM, "Rtg-bfd on behalf of Mahesh Jethanandani"
<rtg-bfd-boun...@ietf.org on behalf of mjethanand...@gmail.com> wrote:
Hi Jeff,
> On Jul 20, 2020, at 5:48 PM, Jeffrey Haas <jh...@pfrc.org> wrote:
>
> Mahesh,
>
> While reviewing version -10, I had the following questions:
>
> For the state machine changes, in the Init->Init state, we have NULL auth.
> While this is a "boring" transition, it's also happening at a very slow
part
> of the state machine; timers should be once a second. Is there a strong
> argument to use NULL here?
Not particularly. The reason to choose NULL was because of the (limited)
impact it would have. But if the WG feels otherwise, I can change it to Auth.
<RR> I don't have a strong opinion on this yet. But if we change INIT->INIT to
be Auth, we should be consistent and change Down->Down to Auth too?
Regards,
Reshad.
>
> In section 3:
> : Sequence Number: The sequence number for this packet. Implementation
> : may use sequence numbers (bfd.XmitAuthSeq) as defined in BFD
> : [RFC5880], or secure sequence numbers as defined in Secure BFD
> : Sequence Numbers [I-D.ietf-bfd-secure-sequence-numbers].
>
> In the core BFD spec, it distinguishes between occasional and meticulous
> modes and uses different code points to determine what you do. I suspect
> your intent is that we always use meticulous mode here?
Yes, the intent was meticulous. I can clarify that.
>
> -- Jeff
>
>
> On Mon, Jul 13, 2020 at 01:56:14PM -0700, Mahesh Jethanandani wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
>>> This draft is a work item of the Bidirectional Forwarding Detection WG
of the IETF.
>>>
>>> Title : Optimizing BFD Authentication
>>> Authors : Mahesh Jethanandani
>>> Ashesh Mishra
>>> Ankur Saxena
>>> Manav Bhatia
>>> Filename :
draft-ietf-bfd-optimizing-authentication-10.txt
>>> Pages : 8
>>> Date : 2020-07-13
>>>
>>> Abstract:
>>> This document describes an optimization to BFD Authentication as
>>> described in Section 6.7 of BFD RFC 5880. This document updates RFC
>>> 5880.
>
>
Mahesh Jethanandani
mjethanand...@gmail.com
