RFC 7730: Resource Public Key Infrastructure (RPKI) Trust Anchor Locator
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8630.
Current document in this lineage: 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). This document obsoletes RFC 6490 by adding support for multiple URIs in a TAL.
Document record
- Document ID
- RFC7730
- Published
- January 2016
- Authors
- G. Huston; S. Weiler; G. Michaelson; S. Kent
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
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 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 8183An Out-of-Band Setup Protocol for Resource Public Key Infrastructure (RPKI) Production ServicesCurrent
July 2017
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8211Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)Current
September 2017
- RFC 7132Threat Model for BGP Path SecurityCurrent
February 2014
- RFC 8416Simplified Local Internet Number Resource Management with the RPKI (SLURM)Current
August 2018
- RFC 6907Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying PartiesCurrent
March 2013
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?