Secure BFD Sequence Numbers
draft-ietf-bfd-secure-sequence-numbers-09
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Mahesh Jethanandani , Sonal Agarwal , Ashesh Mishra , Ankur Saxena , Alan DeKok | ||
Last updated | 2022-09-30 (Latest revision 2022-03-29) | ||
Replaces | draft-sonal-bfd-secure-sequence-numbers | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Held by WG | |
Document shepherd | Reshad Rahman | ||
Shepherd write-up | Show Last changed 2020-06-14 | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Reshad Rahman <rrahman@cisco.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes two new BFD Authentication mechanism, Meticulous Keyed ISAAC, and Meticulous Keyed FNV1A. These mechanisms can be used to authenticate BFD packets, and secure the sequence number exchange, with less CPU time cost than using MD5 or SHA1, with the tradeoff of decreased security. This document updates RFC 5880.
Authors
Mahesh Jethanandani
Sonal Agarwal
Ashesh Mishra
Ankur Saxena
Alan DeKok
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)