Authenticating BFD using HMAC-SHA-2 procedures
draft-ietf-bfd-hmac-sha-05
| Document | Type |
Expired Internet-Draft
(bfd WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dacheng Zhang , Manav Bhatia , Vishwas Manral , Mahesh Jethanandani | ||
| Last updated | 2017-03-22 (Latest revision 2014-07-31) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Waiting for Implementation | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the mechanism to authenticate Bidirectional Forwarding Detection (BFD) protocol packets using Hashed Message Authentication Mode (HMAC) with the SHA-256, SHA-384, and SHA-512 algorithms. The described mechanism uses the Generic Cryptographic Authentication and Generic Meticulous Cryptographic Authentication sections to carry the authentication data. This document updates, but does not supersede, the cryptographic authentication mechanism specified in RFC 5880.
Authors
Dacheng Zhang
Manav Bhatia
Vishwas Manral
Mahesh Jethanandani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)