Resource Public Key Infrastructure (RPKI) Trust Anchor Locator

This document defines a Trust Anchor Locator (TAL) for the Resource Public Key Infrastructure (RPKI) . This format may be used to distribute trust anchor material using a mix of out-of-band and online means. Procedures used by Relying Parties (RPs) to verify RPKI signed objects SHOULD support this format to facilitate interoperability between creators of trust anchor material and RPs. This document obsoletes by adding support for HTTPS URIs in a TAL.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The TAL format defined in this document differs from the definition in in that: it allows for the use of the HTTPS scheme in URIs ; and it allows for the inclusion of an optional comment section. Note that current Relying Parties may not support this new format yet. Therefore it is RECOMMENDED that a Trust Anchor operator maintains a TAL file for a time as well until they are satisfied that RP tooling has been updated.

This document does not propose a new format for trust anchor material. A trust anchor in the RPKI is represented by a self-signed X.509 Certification Authority (CA) certificate, a format commonly used in PKIs and widely supported by RP software. This document specifies a format for data used to retrieve and verify the authenticity of a trust anchor in a very simple fashion. That data is referred to as the TAL. The motivation for defining the TAL is to enable selected data in the trust anchor to change, without needing to redistribute the trust anchor per se. In the RPKI, certificates contain an RFC3779 extension, that can contain a set of IP Address Delegations and/or Autonomous System Identifier Delegations. In this document we refer to these delegations as the Internet Number Resources (INR) contained in an RPKI certificate. The set of INRs associated with an entity acting as a trust anchor is likely to change over time. Thus, if one were to use the common PKI convention of distributing a trust anchor to RPs in a secure fashion, then this procedure would need to be repeated whenever the INR set for the entity acting as a trust anchor changed. By distributing the TAL (in a secure fashion), instead of distributing the trust anchor, this problem is avoided, i.e., the TAL is constant so long as the trust anchor's public key and its location do not change. The TAL is analogous to the TrustAnchorInfo data structure specified in , which is on the Standards Track. That specification could be used to represent the TAL, if one defined an rsync or HTTPS URI extension for that data structure. However, the TAL format was adopted by RPKI implementors prior to the PKIX trust anchor work, and the RPKI implementer community has elected to utilize the TAL format, rather than define the requisite extension. The community also prefers the simplicity of the ASCII encoding of the TAL, versus the binary (ASN.1) encoding for TrustAnchorInfo.

In this document we define a Trust Anchor URI as a URI that can be used to retrieved a current Trust Anchor certificate. This URI MUST be either an rsync URI , or an HTTPS URI . The TAL is an ordered sequence of: an optional comment section consisting of one or more lines each starting with the '#' character, followed by human readable informational UTF-8 text, conforming to the restrictions defined in section 2 of , and ending with a line break, a URI section, that is comprised of one or more ordered lines, each containing a Trust Anchor URI, and ending with a line break, a line break, a subjectPublicKeyInfo in DER format , encoded in Base64 (see Section 4 of ). To avoid long lines, line breaks MAY be inserted into the Base64-encoded string. Note that line breaks in this file can use either <CRLF> or <LF>.

Each Trust Anchor URI in the TAL MUST reference a single object. It MUST NOT reference a directory or any other form of collection of objects. The referenced object MUST be a self-signed CA certificate that conforms to the RPKI certificate profile . This certificate is the trust anchor in certification path discovery and validation . The validity interval of this trust anchor is chosen such that the "notBefore" time predates the moment that this certificate is published, and the "notAfter" time is after the planned time of re-issuance of this certificate. The INR extension(s) of this trust anchor MUST contain a non-empty set of number resources. It MUST NOT use the "inherit" form of the INR extension(s). The INR set described in this certificate is the set of number resources for which the issuing entity is offering itself as a putative trust anchor in the RPKI . The public key used to verify the trust anchor MUST be the same as the subjectPublicKeyInfo in the CA certificate and in the TAL. The trust anchor MUST contain a stable key which does not change when the certificate is reissued due to changes in the INR extension(s), when the certificate is renewed prior to expiration. Because the public key in the TAL and the trust anchor MUST be stable, this motivates operation of that CA in an offline mode. In that case a subordinate CA certificate containing the same INRs, or in theory any sub-set of INRs, can be issued for online operations. This allows the entity that issues the trust anchor to keep the corresponding private key of this certificate offline, while issuing all relevant child certificates under the immediate subordinate CA. This measure also allows the Certificate Revocation List (CRL) issued by that entity to be used to revoke the subordinate CA certificate in the event of suspected key compromise of this online operational key pair that is potentially more vulnerable. The trust anchor MUST be published at a stable URI. When the trust anchor is reissued for any reason, the replacement CA certificate MUST be accessible using the same URI. Because the trust anchor is a self-signed certificate, there is no corresponding CRL that can be used to revoke it, nor is there a manifest that lists this certificate. If an entity wishes to withdraw a self-signed CA certificate as a putative trust anchor, for any reason, including key rollover, the entity MUST remove the object from the location referenced in the TAL. Where the TAL contains two or more Trust Anchor URIs, then the same self-signed CA certificate MUST be found at each referenced location. In order to increase operational resilience, it is RECOMMENDED that the domain name parts of each of these URIs resolve to distinct IP addresses that are used by a diverse set of repository publication points, and these IP addresses be included in distinct Route Origin Authorizations (ROAs) objects signed by different CAs.

# This TAL is intended for documentation purposes only. # Do not attempt to use this in a production setting. rsync://rpki.example.org/rpki/hedgehog/root.cer https://rpki.example.org/rpki/hedgehog/root.cer MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAovWQL2lh6knDx GUG5hbtCXvvh4AOzjhDkSHlj22gn/1oiM9IeDATIwP44vhQ6L/xvuk7W6 Kfa5ygmqQ+xOZOwTWPcrUbqaQyPNxokuivzyvqVZVDecOEqs78q58mSp9 nbtxmLRW7B67SJCBSzfa5XpVyXYEgYAjkk3fpmefU+AcxtxvvHB5OVPIa BfPcs80ICMgHQX+fphvute9XLxjfJKJWkhZqZ0v7pZm2uhkcPx1PMGcrG ee0WSDC3fr3erLueagpiLsFjwwpX6F+Ms8vqz45H+DKmYKvPSstZjCCq9 aJ0qANT9OtnfSDOS+aLRPjZryCNyvvBHxZXqj5YCGKtwIDAQAB

In order to use the TAL to retrieve and validate a (putative) trust anchor, an RP SHOULD: Retrieve the object referenced by (one of) the Trust Anchor URI(s) contained in the TAL. Confirm that the retrieved object is a current, self-signed RPKI CA certificate that conforms to the profile as specified in . Confirm that the public key in the TAL matches the public key in the retrieved object. Perform other checks, as deemed appropriate (locally), to ensure that the RP is willing to accept the entity publishing this self- signed CA certificate to be a trust anchor. These tests apply to the validity of attestations made in the context of the RPKI relating to all resources described in the INR extension of this certificate. An RP SHOULD perform these functions for each instance of TAL that it is holding for this purpose every time the RP performs a resynchronization across the local repository cache. In any case, an RP also SHOULD perform these functions prior to the expiration of the locally cached copy of the retrieved trust anchor referenced by the TAL. In the case where a TAL contains multiple Trust Anchor URIs, an RP MAY use a locally defined preference rule to select the URI to retrieve the self-signed RPKI CA certificate that is to be used as a trust anchor. Some examples are: Using the order provided in the TAL Selecting the Trust Anchor URI randomly from the available list Creating a prioritized list of URIs based on RP-specific parameters, such as connection establishment delay If the connection to the preferred URI fails, or the retrieved CA certificate public key does not match the TAL public key, the RP SHOULD retrieve the CA certificate from the next URI, according to the local preference ranking of URIs.

Please note that the RSYNC protocol provides neither transport security nor any means by which the Relying Party can validate that they are connected to the proper host. There it is RECOMMENDED that HTTPS is used as the preferred scheme. Note that, although a Man in the Middle (MITM) cannot produce a CA certificate that would be considered valid according to the process described in Section 3, this attack can prevent that the Relying Party learns about an updated CA certificate. Relying Parties MUST do TLS certificate and host name validation when they fetch a CA certificate using an HTTPS URI on a TAL. RPs SHOULD log any TLS certificate or host name validation issues found, so that an operator can investigate the cause. It is RECOMMENDED that Relying Parties and Repository Servers follow the Best Current Practices outlined in on the use of HTTP over TLS (HTTPS) . Relying Parties SHOULD do TLS certificate and host name validation using subjectAltName dNSName identities as described in . The rules and guidelines defined in apply here, with the following considerations: Relying Parties and Repository Servers SHOULD support the DNS-ID identifier type. The DNS-ID identifier type SHOULD be present in Repository Server certificates. DNS names in Repository Server certificates SHOULD NOT contain the wildcard character "*". A Common Name (CN) field may be present in a Repository Server certificate's subject name but SHOULD NOT be used for authentication within the rules described in . This protocol does not require the use of SRV-IDs. This protocol does not require the use of URI-IDs.

Compromise of a trust anchor private key permits unauthorized parties to masquerade as a trust anchor, with potentially severe consequences. Reliance on an inappropriate or incorrect trust anchor has similar potentially severe consequences. This TAL does not directly provide a list of resources covered by the referenced self-signed CA certificate. Instead, the RP is referred to the trust anchor itself and the INR extension(s) within this certificate. This provides necessary operational flexibility, but it also allows the certificate issuer to claim to be authoritative for any resource. Relying parties should either have great confidence in the issuers of such certificates that they are configuring as trust anchors, or they should issue their own self-signed certificate as a trust anchor and, in doing so, impose constraints on the subordinate certificates.

This document has no actions for IANA.

This approach to trust anchor material was originally described by Robert Kisteleki. The authors acknowledge the contributions of Rob Austein and Randy Bush, who assisted with drafting this document and with helpful review comments. The authors acknowledge work of Roque Gagliano, Terry Manderson, and Carlos Martinez Cagnazzo in developing the ideas behind the inclusion of multiple URIs in the TAL. The authors acknowledge Job Snijders for suggesting the inclusion of comments at the start of the TAL.