Router Keying for BGPsec
draft-ietf-sidr-rtr-keying-16
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Randy Bush , Sean Turner , Keyur Patel | ||
| Last updated | 2018-09-13 (Latest revision 2018-08-30) | ||
| Replaces | draft-ymbk-bgpsec-rtr-rekeying | ||
| Replaced by | RFC 8635 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | Waiting for WG Chair Go-Ahead | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sidrops-rtr-keying | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Alvaro Retana | ||
| 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 are provisioned with private keys in order to sign BGPsec announcements. The corresponding public keys are published in the global Resource Public Key Infrastructure, enabling verification of BGPsec messages. This document describes two methods of generating the public-private key-pairs: router-driven and operator-driven.
Authors
Randy Bush
Sean Turner
Keyur Patel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)