> On Mar 22, 2017, at 12:35 PM, Jeffrey Haas <[email protected]> wrote: > > This update is scheduled to be discussed at the upcoming session at IETF-98 > in Chicago. > > The likely discussion is whether the new draft from Sonal should be > specifically tied to the advancement of the optimization draft. Our prior > discussion with Alan had suggested some concern about the sequence number > issues when we're using NULL authentication. > > I suspect some good discussion will happen on this topic at the upcoming > session and encourage the members of the Working Group to read both drafts > in preparation.
Yes, it would be helpful to read both the drafts in preparation for the discussion. Optimized authentication is not a substitute for sequence number obfuscation draft, and vice-versa. They offer different levels of cost/benefit, where Draft Cost Benefit ==== ==== ====== sequence number obfuscation Low Medium (does not authenticate the complete packet) optimized authentication Medium High (authenticates entire “state change” packets) full authentication High High (authenticates all packets) > > -- Jeff > >> On Jan 3, 2017, at 4:37 PM, [email protected] wrote: >> >> >> A new version of I-D, draft-ietf-bfd-optimizing-authentication-02.txt >> has been successfully submitted by Mahesh Jethanandani and posted to the >> IETF repository. >> >> Name: draft-ietf-bfd-optimizing-authentication >> Revision: 02 >> Title: Optimizing BFD Authentication >> Document date: 2017-01-05 >> Group: bfd >> Pages: 8 >> URL: >> https://www.ietf.org/internet-drafts/draft-ietf-bfd-optimizing-authentication-02.txt >> Status: >> https://datatracker.ietf.org/doc/draft-ietf-bfd-optimizing-authentication/ >> Htmlized: >> https://tools.ietf.org/html/draft-ietf-bfd-optimizing-authentication-02 >> Diff: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-optimizing-authentication-02 >> >> Abstract: >> This document describes an optimization to BFD Authentication as >> described in Section 6.7 of BFD [RFC5880]. >> >> >> >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> The IETF Secretariat >
