Key Management for Pairwise Routing Protocol
draft-mahesh-karp-rkmp-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mahesh Jethanandani , Brian Weis , Keyur Patel , Dacheng Zhang , Sam Hartman | ||
| Last updated | 2012-09-09 (Latest revision 2012-03-08) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
When running routing protocols such as BGP or RSVP-TE, two routers need to exchange routing messages in a unicast (one-to-one) fashion. In order to authenticate these messages using symmetric cryptography, a secret key needs to be established. This document defines a Router Key Management Protocol for establishing and managing such keys for routing protocols.
Authors
Mahesh Jethanandani
Brian Weis
Keyur Patel
Dacheng Zhang
Sam Hartman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)