RFC 9691: A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs)
In plain English — editorial summary, not part of the RFC
A Trust Anchor Locator (TAL) is used by Relying Parties (RPs) in the Resource Public Key Infrastructure (RPKI) to locate and validate a Trust Anchor (TA) Certification Authority (CA) certificate used in RPKI validation. This document defines an RPKI signed object for a Trust Anchor Key (TAK). A TAK object can be used by a TA to signal to RPs the location(s) of the accompanying CA certificate for the current public key, as well as the successor public key and the location(s) of its CA certificate. This object helps to support planned key rollovers without impacting RPKI validation.
Document record
- Document ID
- RFC9691
- Published
- December 2024
- Authors
- C. Martinez; G. Michaelson; T. Harrison; T. Bruijnzeels; R. Austein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9323A Profile for RPKI Signed Checklists (RSCs)Current
November 2022
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 2560X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPObsoleted
June 1999
- RFC 9829Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number ExtensionsCurrent
July 2025
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?