Skip to main content

Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
RFC 8630

Revision differences

Document history

Date By Action
2026-05-20
(System) Changed author "T. Bruijnzeels": changed name from "Tim Bruijnzeels" to "T. Bruijnzeels", changed order from "4" to "5"
2026-05-20
(System) Changed author "S. Kent": changed name from "Stephen Kent" to "S. Kent", changed order from "3" to "4"
2026-05-20
(System) Changed author "G. Michaelson": changed name from "George Michaelson" to "G. Michaelson", changed order from "2" to "3"
2026-05-20
(System) Changed author "S. Weiler": changed name from "Sam Weiler" to "S. Weiler", changed order from "1" to "2"
2026-05-20
(System) Changed author "G. Huston": changed name from "Geoff Huston" to "G. Huston", changed order from "0" to "1"
2026-05-20
(System) Metadata update from RFC Editor
2019-08-09
(System)
Received changes through RFC Editor sync (created alias RFC 8630, changed abstract to 'This document defines a Trust Anchor Locator (TAL) for the Resource …
Received changes through RFC Editor sync (created alias RFC 8630, changed abstract to 'This document defines a Trust Anchor Locator (TAL) for the Resource Public Key Infrastructure (RPKI). The TAL allows Relying Parties in the RPKI to download the current Trust Anchor (TA) Certification Authority (CA) certificate from one or more locations and verify that the key of this self-signed certificate matches the key on the TAL. Thus, Relying Parties can be configured with TA keys but can allow these TAs to change the content of their CA certificate. In particular, it allows TAs to change the set of IP Address Delegations and/or Autonomous System Identifier Delegations included in the extension(s) (RFC 3779) of their certificate.

This document obsoletes the previous definition of the TAL as provided in RFC 7730 by adding support for Uniform Resource Identifiers (URIs) (RFC 3986) that use HTTP over TLS (HTTPS) (RFC 7230) as the scheme.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-08-09, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-sidrops-https-tal and RFC 7730)
2019-08-09
(System) RFC published