Mahesh, should that be added to draft-ietf-bfd-optimizing-authentication? From: Rtg-bfd <[email protected]<mailto:[email protected]>> on behalf of LuHuang <[email protected]<mailto:[email protected]>> Reply-To: LuHuang <[email protected]<mailto:[email protected]>> Date: Monday, April 17, 2017 at 9:19 PM To: Jeffrey Haas <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: Reshad <[email protected]<mailto:[email protected]>>, "Sonal Agarwal (agarwaso)" <[email protected]<mailto:[email protected]>> Subject: 回复： Adoption call for draft-sonal-bfd-secure-sequence-numbers (ending April 30, 2017)
Yes./ support But I think one problem should be considered. If packet loss happens, the sequence number of received packet won't be the expected number or hash value, which should be distinguished from malicious packet. Thanks. -------------------- LuHuang China Mobile Research Institute Mobile: +86 13810820540 Jeffrey Haas <[email protected]<mailto:[email protected]>> 于 2017年4月18日, 星期二, 上午 5:28 写道： Working Group, As part of our discussion at the Working Group session at IETF 98 in Chicago, Sonal Agarwal presented "Secure BFD Sequence Numbers" (draft-sonal-bfd-secure-sequence-numbers-00). This work complements a problem space the Security area had asked us to address as part of the work on optimizing BFD authentication, our adopted draft-ietf-bfd-optimizing-authentication. The discussion on the implementation implictions of the optimizing authentication draft was energetic this last IETF. To drive that solution further along, we will need a technology similar to the one in the proposal. This starts a 2 week adoption call for draft-sonal-bfd-secure-sequence-numbers. Please indicate your support or lack of support for the proposal to the mailing list. Note that part of the discussion was that optimizing BFD is not ready to proceed to Last CAll until we've adopted such a proposal and have properly integrated it into the optimization procedures. -- Jeff and Reshad
