LDP Hello Cryptographic Authentication
draft-zheng-mpls-ldp-hello-crypto-auth-02
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Lianshu Zheng , Manav Bhatia | ||
Last updated | 2011-06-28 (Latest revision 2011-03-14) | ||
Replaced by | draft-ietf-mpls-ldp-hello-crypto-auth, RFC 7349 | ||
RFC stream | (None) | ||
Formats | |||
Reviews |
SECDIR Early review
by Donald Eastlake
Ready w/nits
|
||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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 introduces a new optional Cryptographic Authentication TLV that LDP can use to secure its Hello messages. It secures the Hello messages against spoofing attacks and some well known attacks against the IP header. This document describes how the National Institute of Standards and Technology (NIST) Secure Hash Standard family of algorithms should be used to secure LDP Hello messages.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)