RPKI signed object for TAL
draft-ietf-sidrops-signed-tal-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Tim Bruijnzeels , Carlos M. Martínez | ||
| Last updated | 2018-05-17 (Latest revision 2017-11-13) | ||
| Replaces | draft-tbruijnzeels-sidrops-signed-tal | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
OPSDIR Last Call Review due 2024-04-26
Incomplete
SECDIR Last Call Review due 2024-04-26
Incomplete
GENART Last Call Review due 2024-04-26
Incomplete
|
||
| 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
Trust Anchor Locators (TALs) [RFC7730] are used by Relying Parties in the RPKI to locate and validate Trust Anchor certificates used in RPKI validation. This document defines an RPKI signed object [RFC6488] for a Trust Anchor Locator (TAL) that can be published by Trust Anchor to communicate a new TAL to already deployed Relying Parties. The two primary use cases for this are that 1) a Trust Anchor may wish to change the locations where its TA certificate may be found, and 2) a Trust Anchor may wish to perform a planned migration to a new key. Note that unplanned key rolls are considered out of scope for this document.
Authors
Tim Bruijnzeels
Carlos M. Martínez
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)