Router Keying for BGPsec
draft-ietf-sidr-rtr-keying-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Sean Turner , Keyur Patel , Randy Bush | ||
| Last updated | 2013-08-27 (Latest revision 2013-02-23) | ||
| Replaces | draft-ymbk-bgpsec-rtr-rekeying | ||
| Replaced by | draft-ietf-sidrops-rtr-keying, RFC 8635 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| 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
BGPsec-speaking routers must be provisioned with private keys and the corresponding public key must be published in the global RPKI (Resource Public Key Infrastructure). This document describes two ways of provisioning public/private keys, router-driven and operator- driven.
Authors
Sean Turner
Keyur Patel
Randy Bush
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)