RPKI Signed Object for Trust Anchor Keys

The information below is for an old version of the document
Document Type Expired Internet-Draft (sidrops WG)
Authors Tim Bruijnzeels  , Carlos Martínez  , Rob Austein 
Last updated 2019-04-22 (latest revision 2018-10-19)
Replaces draft-tbruijnzeels-sidrops-signed-tal
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Trust Anchor Locators (TALs) [I-D.ietf-sidrops-https-tal] 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 for Trust Anchor Keys (TAK), that can be used by Trust Anchors to signal their set of current keys and the location(s) of the accompanying CA certiifcates to Relying Parties, as well as changes to this set in the form of revoked keys and new keys, in order to support both planned and unplanned key rolls without impacting RPKI validation.


Tim Bruijnzeels (tim@nlnetlabs.nl)
Carlos Martínez (carlos@lacnic.net)
Rob Austein (sra@hactrn.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)