RFC 8211: Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)
In plain English — editorial summary, not part of the RFC
This document analyzes actions by or against a Certification Authority (CA) or an independent repository manager in the RPKI that can adversely affect the Internet Number Resources (INRs) associated with that CA or its subordinate CAs. The analysis is done from the perspective of an affected INR holder. The analysis is based on examination of the data items in the RPKI repository, as controlled by a CA (or an independent repository manager) and fetched by Relying Parties (RPs). The analysis does not purport to be comprehensive; it does represent an orderly way to analyze a number of ways that errors by or attacks against a CA or repository manager can affect the RPKI and routing decisions based on RPKI data.
Document record
- Document ID
- RFC8211
- Published
- September 2017
- Authors
- S. Kent; D. Ma
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 7730Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
January 2016
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6907Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying PartiesCurrent
March 2013
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
- RFC 8210The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1Current
September 2017
- RFC 8209A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification RequestsCurrent
September 2017
- RFC 8208BGPsec Algorithms, Key Formats, and Signature FormatsObsoleted
September 2017
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?