draft-ietf-bfd-stability-10 comments

[Jeffrey Haas <[e-mail]>]

Authors,

As we finish up work on the authentication features now that secure sequence is heading toward completion, it's time to reconcile your draft vs. our current learnings in that other work.

The main change that seems appropriate is noting that any meticulous keyed authentication mechanism will provide the necessary loss detection as desired in this draft.

This draft discusses that in the absence of any other desired mechanism, NULL auth, as documented in optimizing authentication, is appropriate.  

The text related to secure sequence numbers needs updating.  But that said, the updates are simpler because the mechanism has evolved to using sequence numbers the same as the other mechanisms, and providing its benefit in the authentication data portion of the PDU.

Could you update the draft vs. the current state of things and refresh it in the data tracker?  I suspect we'll rapidly converge on text for last call.

Thanks!

-- Jeff