]> BBN Technologies

10 Moulton St. Cambridge MA 02138 US david@mandelberg.org

Secure Inter-Domain Routing The Resource Public Key Infrastructure (RPKI) is a global authorization infrastructure that allows the holder of Internet Number Resources (INRs) to make verifiable statements about those resources. Network operators, e.g., Internet Service Providers (ISPs), can use the RPKI to validate BGP route origination assertions. In the future, ISPs also will be able to use the RPKI to validate the path of a BGP route. Some ISPs locally use BGP with private address space or private AS numbers (see RFC6890). These local BGP routes cannot be verified by the global RPKI, and SHOULD be considered invalid based on the global RPKI (see RFC6491). The mechanisms described below provide ISPs with a way to make local assertions about private (reserved) INRs while using the RPKI's assertions about all other INRs.

The Resource Public Key Infrastructure (RPKI) is a global authorization infrastructure that allows the holder of Internet Number Resources (INRs) to make verifiable statements about those resources. For example, the holder of a block of IP(v4 or v6) addresses can issue a Route Origination Authorization (ROA) to authorize an Autonomous System (AS) to originate routes for that block. Internet Service Providers (ISPs) can then use the RPKI to validate BGP routes. (Validation of the origin of a route is described in , and validation of the path of a route is described in .) However, some ISPs locally use BGP with private address space (, , ) or private AS numbers (, ). These local BGP routes cannot be verified by the global RPKI, and SHOULD be considered invalid when using the RPKI. For example, recommends the creation of ROAs that would invalidate routes for reserved and unallocated address space. This document specifies two new mechanisms to enable ISPs to make local assertions about some INRs while using the RPKI's assertions about all other INRs. These mechanisms primarily support the second use case in , and may additionally support the third use case. The second use case describes use of addresses or use of public address space not allocated to the ISP that is using it. The third use case describes a situation in which an ISP publishes a variant of the RPKI hierarchy (for its customers). In this variant some prefixes and/or AS numbers are different from what the RPKI repository system presents to the general ISP population. The result is that routes for consumers of this variant hierarchy will be re-directed (via routing). Note that it also is possible to use SLURM to (locally) manipulate assertions about non-private INRs, e.g., allocated address space that is not globally routed. Network operators who elect to use SLURM in this fashion should use extreme caution. (The fact that SLURM can be used in this fashion is not an endorsement of such use by the author.) Both mechanisms are specified in terms of abstract sets of assertions. For Origin Validation , an assertion is a tuple of {IP prefix, prefix length, maximum length, AS number} as used by rpki-rtr version 0 and version 1. For BGPsec, an assertion is a tuple of {AS number, subject key identifier, router public key} as used by rpki-rtr version 1. (For the remainder of this document, these assertions are called Origin Validation assertions and BGPsec assertions, respectively.) Output Filtering, described in , filters out (removes from consideration for routing decisions) any assertions in the RPKI about locally reserved INRs. Locally Adding Assertions, described in , adds local assertions about locally reserved INRs. The combination of both mechanisms is described in . To ensure local consistency, the effect of SLURM MUST be atomic. That is, the output of the relying party must be either the same as if SLURM were not used, or it must reflect the entire SLURM configuration. For an example of why this is required, consider the case of two local routes for the same prefix but different origin AS numbers. Both routes are configured with Locally Adding Assertions. If neither addition occurs, then both routes could be in the unknown state . If both additions occur then both routes would be in the valid state. However, if one addition occurs and the other does not, then one could be invalid while the other is valid. In general, the primary output of an RPKI relying party is the data it sends to routers over the rpki-rtr protocol. The rpki-rtr protocol enables routers to query a relying party for all assertions it knows about (Reset Query) or for an update of only the changes in assertions (Serial Query). The mechanisms specified in this document are to be applied to the result set for a Reset Query, and to both the old and new sets that are compared for a Serial Query. Relying party software MAY modify other forms of output in comparable ways, but that is outside the scope of this document.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

To prevent the global RPKI from affecting routes with locally reserved INRs, a relying party is locally configured with a (possibly empty) list of IP prefixes and/or AS numbers that are used locally. (In general, these IP prefixes and AS numbers will be taken from reserved INR spaces.) Any Origin Validation assertions where the IP prefix is equal to or subsumed by a locally reserved IP prefix, are removed from the relying party's output. (Note that an Origin Validation assertion is not removed due to its AS number matching a locally reserved AS number.) Any BGPsec assertion where the AS number is equal to a locally reserved AS number is removed from the relying party's output.

Each relying party is locally configured with a (possibly empty) list of assertions. This list is added to the relying party's output.

Relying party software SHOULD support the following configuration format for Validation Output Filtering and Locally Adding Assertions. The format is defined using the Augmented Backus-Naur Form (ABNF) notation and core rules from and the rules <IPv4address> and <IPv6address> from Appendix A of . See for an example SLURM file. A SLURM configuration file, <SLURMFile>, consists of a head and a body. The head identifies the file as a SLURM configuration file, specifies the version of SLURM for which the file was written, and optionally contains other information described below. The body contains the configuration for Validation Output Filtering and Locally Adding Assertions.

SLURMFile = head body head = firstLine *(commentLine / headLine) body = *(commentLine / bodyLine) firstLine = %x53.4c.55.52.4d SP "1.0" EOL ; "SLURM 1.0" commentLine = *WSP [comment] EOL headLine = *WSP headCommand [ 1*WSP [comment] ] EOL bodyLine = *WSP bodyCommand [ 1*WSP [comment] ] EOL comment = "#" *(VCHAR / WSP) EOL = CRLF / LF

The head may specify a target. If present, the target string identifies the environment in which the SLURM file is intended to be used. The meaning of the target string, if any, is determined by the user. If a target is present, a relying party SHOULD verify that that the target is an acceptable value, and reject the SLURM file if the target is not acceptable. For example, the relying party could be configured to accept SLURM files only if they do not specify a target, have a target value of "hostname=rpki.example.com", or have a target value of "as=65536". If more than one target line is present, all targets must be acceptable to the RP.

headCommand = target target = %x74.61.72.67.65.74 1*WSP ; "target" 1*VCHAR

The body contains zero or more configuration lines for Validation Output Filtering and Locally Adding Assertions. Each <del> command specifies an INR to use for Validation Output Filtering. Each <add> command specifies an assertion to use for Locally Adding Assertions.

bodyCommand = add / del add = %x61.64.64 1*WSP ; "add" addItem del = %x64.65.6c 1*WSP ; "del" delItem addItem = addItemPrefixAS / addItemASKey ; Add a mapping from a prefix and max length to an AS number. addItemPrefixAS = %x6f.72.69.67.69.6e.61.74.69.6f.6e 1*WSP ; "origination" IPprefixMaxLen 1*WSP ASnum ; Add a mapping from an AS number to a router public key. addItemASKey = %x62.67.70.73.65.63 1*WSP ; "bgpsec" ASnum 1*WSP RouterSKI 1*WSP RouterPubKey delItem = delItemPrefix / delItemAS ; Filter prefix-AS mappings, using the given prefix delItemPrefix = %x6f.72.69.67.69.6e.61.74.69.6f.6e 1*WSP ; "origination" IPprefix ; Filter AS-key mappings for the given AS delItemAS = %x62.67.70.73.65.63 1*WSP ; "bgpsec" ASnum IPprefix = IPv4prefix / IPv6prefix IPprefixMaxLen = IPv4prefixMaxLen / IPv6prefixMaxLen IPv4prefix = IPv4address "/" 1*2DIGIT IPv6prefix = IPv6address "/" 1*3DIGIT ; In the following two rules, if the maximum length component is ; missing, it is treated as equal to the prefix length. IPv4prefixMaxLen = IPv4prefix ["-" 1*2DIGIT] IPv6prefixMaxLen = IPv6prefix ["-" 1*3DIGIT] ASnum = 1*DIGIT ; This is the Base64 [RFC4648] encoding of a router certificate's ; Subject Key Identifer, as described in ; [I-D.ietf-sidr-bgpsec-pki-profiles] and [RFC6487]. This is the ; value of the ASN.1 OCTET STRING without the ASN.1 tag or length ; fields. RouterSKI = Base64 ; This is the Base64 [RFC4648] encoding of a router public key's ; subjectPublicKeyInfo value, as described in ; [I-D.ietf-sidr-bgpsec-algs]. This is the full ASN.1 DER encoding ; of the subjectPublicKeyInfo, including the ASN.1 tag and length ; values of the subjectPublicKeyInfo SEQUENCE. RouterPubKey = Base64 Base64 = 1*(ALPHA / DIGIT / "+" / "/") 0*2"="

An implementation MAY support the concurrent use of multiple SLURM files. In this case, the resulting inputs to Validation Output Filtering and Locally Adding Assertions are the respective unions of the inputs from each file. The envisioned typical use case for multiple files is when the files have distinct scopes. For example, an organization may belong to two separate networks that use different private-use IP prefixes and AS numbers. To detect conflict between multiple SLURM files, a relying party SHOULD issue a warning in the following cases: There may be conflicting changes to Origin Validation assertions if there exists an IP address X and distinct SLURM files Y,Z such that X is contained by any prefix in any <addItemPrefixAS> or <delItemPrefix> in file Y and X is contained by any prefix in any <addItemPrefixAS> or <delItemPrefix> in file Z. There may be conflicting changes to BGPsec assertions if there exists an AS number X and distinct SLURM files Y,Z such that X is used in any <addItemASKey> or <delItemAS> in file Y and X is used in any <addItemASKey> or <delItemAS> in file Z.

In the envisioned typical use case, a relying party uses both output filtering and locally added assertions. In this case, the resulting assertions MUST be the same as if output filtering were performed before locally adding assertions. I.e., locally added assertions MUST NOT be removed by output filtering.

None.

The mechanisms described in this document provide a network operator with additional ways to control its own network while making use of RPKI data. These mechanisms are applied only locally; they do not influence how other network operators interpret RPKI data. Nonetheless, care should be taken in how these mechanisms are employed.

The author would like to thank Stephen Kent for his guidance and detailed reviews of this document. Thanks go to Wesley Wang for the idea behind the target command, to Declan Ma for the idea behind use of multiple SLURM files, and to Richard Hansen for his careful reviews.

&rfc1918; &rfc1930; &rfc4193; &rfc6482; &rfc6483; &rfc6491; &rfc6598; &rfc6810; &rfc6890; &rfc6996; &I-D.ietf-sidr-bgpsec-overview; &I-D.ietf-sidr-lta-use-cases; &I-D.ietf-sidr-rpki-rtr-rfc6810-bis; &rfc2119; &rfc3986; &rfc4648; &rfc5234; &rfc6487; &I-D.ietf-sidr-bgpsec-pki-profiles;

SLURM 1.0 # This file is only intended to be used on a relying party running # on rpki.example.com. target hostname=rpki.example.com # this is a comment # Reserve IP prefixes for local use. del origination 10.0.0.0/24 del origination fd0b:dd1d:2dcc::/48 # Reserve AS numbers for local use. del bgpsec 64512 del bgpsec 64513 # Allow either 64512 or 64513 to originate routes to 10.0.0.0/24. add origination 10.0.0.0/24 64512 add origination 10.0.0.0/24 64513 # 64512 originates fd0b:dd1d:2dcc::/52 and sub-prefixes up to length # 56. add origination fd0b:dd1d:2dcc::/52-56 64512 # However, 64513 originates fd0b:dd1d:2dcc:42::/64. add origination fd0b:dd1d:2dcc:42::/64 64513 # 64513 also originates fd0b:dd1d:2dcc:100::/52 add origination fd0b:dd1d:2dcc:100::/52 64513 # Authorize router keys to sign BGPsec paths on behalf of the # specified ASes. Note that the Base64 strings used in this # example are not valid SKIs or router public keys, due to line # length restrictions in RFCs. add bgpsec 64512 Zm9v VGhpcyBpcyBub3QgYSByb3V0ZXIgcHVibGljIGtleQ== add bgpsec 64512 YmFy b3IgYSBmbG9jayBvZiBkdWNrcw== add bgpsec 64513 YWJj bWF5YmUgYSBkaWZmZXJlbnQgYXZpYW4gY2Fycmllcj8=