Skip to main content

Multiple Repository Publication Points support in the Resource Public Key Infrastructure (RPKI)

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Roque Gagliano , Terry Manderson , Carlos M. Martínez
Last updated 2013-11-23 (Latest revision 2013-05-22)
Replaces draft-rogaglia-sidr-multiple-publication-points
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The Resource Public Key Infrastructure (RPKI) depends on Relying Parties (RP) ability to access its Trust Anchors' certificate specified in the different "Trust Anchor Locator (TAL)" files and the Repository Objects located at the Certificate Authorities (CA) repositories hosted in its respective publication point. This document updates [RFC6490] by allowing multiple URI associated to a single public key in a TAL file and introduces the concept of multiple repository publication point operators for every CA in the RPKI. This document provides also recommendation for the RP behavior when analyzing signed objects that include multiple publications points.


Roque Gagliano
Terry Manderson
Carlos M. Martínez

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)