metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP182

RFC 6916: Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)

In plain English — editorial summary, not part of the RFC

This document specifies the process that Certification Authorities (CAs) and Relying Parties (RPs) participating in the Resource Public Key Infrastructure (RPKI) will need to follow to transition to a new (and probably cryptographically stronger) algorithm set. The process is expected to be completed over a timescale of several years. Consequently, no emergency transition is specified. The transition procedure defined in this document supports only a top-down migration (parent migrates before children).

Document record

Document ID
RFC6916
Published
April 2013
Authors
R. Gagliano; S. Kent; S. Turner
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
rtg
Pages
20
Also known as
BCP182

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6916-algorithm-agility-procedure-for-the-resource-public-key-infrastructure-rpki