Router Keying for BGPsec
draft-ymbk-bgpsec-rtr-rekeying-00
Document | Type |
Replaced Internet-Draft
(sidr WG)
Expired & archived
|
|
---|---|---|---|
Authors | Sean Turner , Keyur Patel , Randy Bush | ||
Last updated | 2012-06-19 (Latest revision 2012-03-05) | ||
Replaced by | draft-ietf-sidr-rtr-keying | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-sidr-rtr-keying | |
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 Resource PKI. This document describes two ways of doing so, 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.)