BGPsec Router Certificate Rollover
draft-ietf-sidr-bgpsec-rollover-05
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Roque Gagliano , Keyur Patel , Brian Weis | ||
| Last updated | 2016-09-22 (Latest revision 2016-03-21) | ||
| Replaces | draft-rogaglia-sidr-bgpsec-rollover | ||
| Replaced by | draft-ietf-sidrops-bgpsec-rollover, RFC 8634 | ||
| 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 will need to address the impact from regular and emergency rollover processes for the BGPsec End-Entity (EE) certificates that will be performed by Certificate Authorities (CAs) participating at the Resource Public Key Infrastructure (RPKI). Rollovers of BGPsec EE certificates must be carefully managed in order to synchronize distribution of router public keys and the usage of those pubic keys by BGPsec routers. This document provides general recommendations for that process, as well as describing reasons why the rollover of BGPsec EE certificates might be necessary.
Authors
Roque Gagliano
Keyur Patel
Brian Weis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)