Unicast Router Key Management Protocol (RKMP)
draft-zhang-karp-rkmp-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Dacheng Zhang , Sam Hartman | ||
| Last updated | 2011-07-04 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-zhang-karp-rkmp-00.txt
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 (RKMP) for establishing and managing such keys for routing protocols.
Authors
Dacheng Zhang
(zhangdacheng@huawei.com)
Sam Hartman
(hartmans@painless-security.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)