RFC 6490: 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 7730.
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). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6490
- Published
- February 2012
- Authors
- G. Huston; S. Weiler; G. Michaelson; S. Kent
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 7730
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 6491Resource Public Key Infrastructure (RPKI) Objects Issued by IANACurrent
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 6492A Protocol for Provisioning Resource CertificatesCurrent
February 2012
- RFC 6488Signed Object Template for the Resource Public Key Infrastructure (RPKI)Updated
February 2012
- RFC 6487A Profile for X.509 PKIX Resource CertificatesUpdated
February 2012
- RFC 6493The Resource Public Key Infrastructure (RPKI) Ghostbusters RecordCurrent
February 2012
- RFC 6486Manifests for the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
- RFC 6485The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
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?