RFC 8630: Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8630
- Published
- August 2019
- Authors
- G. Huston; S. Weiler; G. Michaelson; S. Kent; T. Bruijnzeels
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
- Obsoletes:
- RFC 7730
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 6490 (2012)
- RFC 7730 (2016)
- RFC 8630 (2019)
Read the full history of Resource Public Key Infrastructure (RPKI) Trust Anchor Locator →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8634BGPsec Router Certificate RolloverCurrent
August 2019
- RFC 8635Router Keying for BGPsecCurrent
August 2019
- RFC 8624Algorithm Implementation Requirements and Usage Guidance for DNSSECObsoleted
June 2019
- RFC 8639Subscription to YANG NotificationsCurrent
September 2019
- RFC 8640Dynamic Subscription to YANG Events and Datastores over NETCONFCurrent
September 2019
- RFC 8641Subscription to YANG Notifications for Datastore UpdatesCurrent
September 2019
- RFC 8618Compacted-DNS (C-DNS): A Format for DNS Packet CaptureCurrent
September 2019
- RFC 8642Policy Behavior for Well-Known BGP CommunitiesCurrent
August 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?