RFC 6482: A Profile for Route Origin Authorizations (ROAs)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9582.
Current version: RFC 9582 — A Profile for Route Origin Authorizations (ROAs)
In plain English — editorial summary, not part of the RFC
This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6482
- Published
- February 2012
- Authors
- M. Lepinski; S. Kent; D. Kong
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 9582
Topics
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 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
February 2012
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 9829Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number ExtensionsCurrent
July 2025
- RFC 6481A Profile for Resource Certificate Repository StructureCurrent
February 2012
- RFC 6487A Profile for X.509 PKIX Resource CertificatesUpdated
February 2012
- RFC 6489Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)Current
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?