Authenticating BFD using HMAC-SHA-2 procedures
draft-ietf-bfd-hmac-sha-05
| Document | Type | Expired Internet-Draft (bfd WG) | |
|---|---|---|---|
| Last updated | 2017-03-22 (latest revision 2014-07-31) | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | Waiting for Implementation (wg milestone: Jan 2015 - Submit the cryptogra... ) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-bfd-hmac-sha-05.txt
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
(zhangdacheng@huawei.com)
Manav Bhatia
(manav.bhatia@alcatel-lucent.com)
Vishwas Manral
(vishwas@ionosnetworks.com)
Mahesh Jethanandani
(mjethanandani@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)