Re: I-D Action: draft-ietf-bfd-optimizing-authentication-10.txt

[Jeffrey Haas <[e-mail]>]

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?

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?

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