idnits 2.17.00 (12 Aug 2021) /tmp/idnits23251/draft-ietf-sidr-bgpsec-pki-profiles-19.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC6487, but the abstract doesn't seem to directly say this. It does mention RFC6487 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC6487, updated by this document, for RFC5378 checks: 2006-06-09) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 30, 2016) is 1967 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ID.sidr-rfc6485bis' is mentioned on line 334, but not defined ** Obsolete undefined reference: RFC 6485 (Obsoleted by RFC 7935) == Missing Reference: 'RFC6818' is mentioned on line 416, but not defined == Outdated reference: draft-ietf-sidr-bgpsec-protocol has been published as RFC 8205 == Outdated reference: draft-ietf-sidr-bgpsec-algs has been published as RFC 8208 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Secure Inter-Domain Routing Working Group M. Reynolds 3 Internet-Draft IPSw 4 Updates: 6487 (if approved) S. Turner 5 Intended status: Standard Track sn3rd 6 Expires: July 3, 2017 S. Kent 7 BBN 8 December 30, 2016 10 A Profile for BGPsec Router Certificates, 11 Certificate Revocation Lists, and Certification Requests 12 draft-ietf-sidr-bgpsec-pki-profiles-19 14 Abstract 16 This document defines a standard profile for X.509 certificates used 17 to enable validation of Autonomous System (AS) paths in the Border 18 Gateway Protocol (BGP), as part of an extension to that protocol 19 known as BGPsec. BGP is the standard for inter-domain routing in the 20 Internet; it is the "glue" that holds the Internet together. BGPsec 21 is being developed as one component of a solution that addresses the 22 requirement to provide security for BGP. The goal of BGPsec is to 23 provide full AS path validation based on the use of strong 24 cryptographic primitives. The end-entity (EE) certificates specified 25 by this profile are issued (to routers within an Autonomous System). 26 Each of these certificates is issued under a Resource Public Key 27 Infrastructure (RPKI) Certification Authority (CA) certificate. 28 These CA certificates and EE certificates both contain the AS 29 Identifier Delegation extension. An EE certificate of this type 30 asserts that the router(s) holding the corresponding private key are 31 authorized to emit secure route advertisements on behalf of the 32 AS(es) specified in the certificate. This document also profiles the 33 format of certification requests, and specifies Relying Party (RP) 34 certificate path validation procedures for these EE certificates. 35 This document extends the RPKI; therefore, this documents updates the 36 RPKI Resource Certificates Profile (RFC 6487). 38 Status of this Memo 40 This Internet-Draft is submitted in full conformance with the 41 provisions of BCP 78 and BCP 79. 43 Internet-Drafts are working documents of the Internet Engineering 44 Task Force (IETF). Note that other groups may also distribute 45 working documents as Internet-Drafts. The list of current Internet- 46 Drafts is at http://datatracker.ietf.org/drafts/current/. 48 Internet-Drafts are draft documents valid for a maximum of six months 49 and may be updated, replaced, or obsoleted by other documents at any 50 time. It is inappropriate to use Internet-Drafts as reference 51 material or to cite them other than as "work in progress." 53 Copyright Notice 55 Copyright (c) 2016 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with respect 63 to this document. Code Components extracted from this document must 64 include Simplified BSD License text as described in Section 4.e of 65 the Trust Legal Provisions and are provided without warranty as 66 described in the Simplified BSD License. 68 Table of Contents 70 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 71 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 72 2. Describing Resources in Certificates . . . . . . . . . . . . . 3 73 3. Updates to [RFC6487] . . . . . . . . . . . . . . . . . . . . . 5 74 3.1 BGPsec Router Certificate Fields . . . . . . . . . . . . . 5 75 3.1.1. Subject . . . . . . . . . . . . . . . . . . . . . . . 5 76 3.1.2. Subject Public Key Info . . . . . . . . . . . . . . . 5 77 3.1.3. BGPsec Router Certificate Version 3 Extension Fields . 6 78 3.1.3.1. Basic Constraints . . . . . . . . . . . . . . . . 6 79 3.1.3.2. Extended Key Usage . . . . . . . . . . . . . . . . 6 80 3.1.3.3. Subject Information Access . . . . . . . . . . . . 6 81 3.1.3.4. IP Resources . . . . . . . . . . . . . . . . . . . 6 82 3.1.3.5. AS Resources . . . . . . . . . . . . . . . . . . . 6 83 3.2. BGPsec Router Certificate Request Profile . . . . . . . . 7 84 3.3. BGPsec Router Certificate Validation . . . . . . . . . . . 7 85 3.4. Router Certificates and Signing Functions in the RPKI . . 8 86 4. Design Notes . . . . . . . . . . . . . . . . . . . . . . . . . 8 87 5. Implementation Considerations . . . . . . . . . . . . . . . . . 9 88 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 89 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 90 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 91 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 92 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10 93 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 94 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 12 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 97 1. Introduction 99 This document defines a profile for X.509 end-entity (EE) 100 certificates [RFC5280] for use in the context of certification of 101 Autonomous System (AS) paths in the BGPsec. Such certificates are 102 termed "BGPsec Router Certificates". The holder of the private key 103 associated with a BGPsec Router Certificate is authorized to send 104 secure route advertisements (BGPsec UPDATEs) on behalf of the AS(es) 105 named in the certificate. A router holding the private key is 106 authorized to send route advertisements (to its peers) identifying 107 the router's ASN as the source of the advertisements. A key property 108 provided by BGPsec is that every AS along the AS PATH can verify that 109 the other ASes along the path have authorized the advertisement of 110 the given route (to the next AS along the AS PATH). 112 This document is a profile of [RFC6487], which is a profile of 113 [RFC5280]; thus this document updates [RFC6487]. It establishes 114 requirements imposed on a Resource Certificate that is used as a 115 BGPsec Router Certificate, i.e., it defines constraints for 116 certificate fields and extensions for the certificate to be valid in 117 this context. This document also profiles the certification requests 118 used to acquire BGPsec Router Certificates. Finally, this document 119 specifies the Relying Party (RP) certificate path validation 120 procedures for these certificates. 122 1.1. Terminology 124 It is assumed that the reader is familiar with the terms and concepts 125 described in "A Profile for X.509 PKIX Resource Certificates" 126 [RFC6487], "BGPsec Protocol Specification" [ID.sidr-bgpsec-protocol], 127 "A Border Gateway Protocol 4 (BGP-4)" [RFC4271], "BGP Security 128 Vulnerabilities Analysis" [RFC4272], "Considerations in Validating 129 the Path in BGP" [RFC5123], and "Capability Advertisement with BGP-4" 130 [RFC5492]. 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 134 "OPTIONAL" in this document are to be interpreted as described in 135 [RFC2119]. 137 2. Describing Resources in Certificates 139 Figure 1 depicts some of the entities in the RPKI and some of the 140 products generated by RPKI entities. IANA issues a Certification 141 Authority (CA) certificate to each Regional Internet Registry (RIR). 142 The RIR, in turn, issues a CA certificate to an Internet Service 143 Provider (ISP). The ISP in turn issues EE Certificates to itself to 144 enable verification of signatures on RPKI signed objects. The CA 145 also generates Certificate Revocation Lists (CRLs). These CA and EE 146 certificates are referred to as "Resource Certificates", and are 147 profiled in [RFC6487]. [RFC6480] envisioned using Resource 148 Certificates to enable verification of Manifests [RFC6486] and Route 149 Origin Authorizations (ROAs) [RFC6482]. ROAs and Manifests include 150 the Resource Certificates used to verify them. 152 +---------+ +------+ 153 | CA Cert |---| IANA | 154 +---------+ +------+ 155 \ 156 +---------+ +-----+ 157 | CA Cert |---| RIR | 158 +---------+ +-----+ 159 \ 160 +---------+ +-----+ 161 | CA Cert |---| ISP | 162 +---------+ +-----+ 163 / | | | 164 +-----+ / | | | +-----+ 165 | CRL |--+ | | +---| ROA | 166 +-----+ | | +-----+ 167 | | +----------+ 168 +----+ | +---| Manifest | 169 +-| EE |---+ +----------+ 170 | +----+ 171 +-----+ 172 Figure 1 174 This document defines another type of Resource Certificate, which is 175 referred to as a "BGPsec Router Certificate". The purpose of this 176 certificate is explained in Section 1 and falls within the scope of 177 appropriate uses defined within [RFC6484]. The issuance of BGPsec 178 Router Certificates has minimal impact on RPKI CAs because the RPKI 179 CA certificate and CRL profile remain unchanged (i.e., they are as 180 specified in [RFC6487]). Further, the algorithms used to generate 181 RPKI CA certificates that issue the BGPsec Router Certificates and 182 the CRLs necessary to check the validity of the BGPsec Router 183 Certificates remain unchanged (i.e., they are as specified in 184 [RFC7935]). The only impact is that RPKI CAs will need to be able to 185 process a profiled certificate request (see Section 5) signed with 186 algorithms found in [ID.sidr-bgpsec-algs]. The use of BGPsec Router 187 Certificates in no way affects RPKI RPs that process Manifests and 188 ROAs because the public key found in the BGPsec Router Certificate is 189 used only to verify the signature on the BGPsec certificate request 190 (only CAs process these) and the signature on a BGPsec Update Message 191 [ID.sidr-bgpsec-protocol] (only BGPsec routers process these). 193 This document enumerates only the differences between this profile 194 and the profile in [RFC6487]. Note that BGPsec Router Certificates 195 are EE certificates and as such there is no impact on process 196 described in [RFC6916]. 198 3. Updates to [RFC6487] 200 3.1 BGPsec Router Certificate Fields 202 A BGPsec Router Certificate is consistent with the profile in 203 [RFC6487] as modified by the specifications in this section. As 204 such, it is a valid X.509 public key certificate and consistent with 205 the PKIX profile [RFC5280]. The differences between this profile and 206 the profile in [RFC6487] are specified in this section. 208 3.1.1. Subject 210 This field identifies the router to which the certificate has been 211 issued. Consistent with [RFC6487], only two attributes are allowed 212 in the Subject field: common name and serial number. Moreover, the 213 only common name encoding options that are supported are 214 printableString and UTF8String. For BGPsec Router Certificates, it 215 is RECOMMENDED that the common name attribute contain the literal 216 string "ROUTER-" followed by the 32-bit AS Number [RFC3779] encoded 217 as eight hexadecimal digits and that the serial number attribute 218 contain the 32-bit BGP Identifier [RFC4271] (i.e., the router ID) 219 encoded as eight hexadecimal digits. If there is more than one AS 220 number, the choice of which to include in the common name is at the 221 discretion of the Issuer. If the same certificate is issued to more 222 than one router (hence the private key is shared among these 223 routers), the choice of the router ID used in this name is at the 224 discretion of the Issuer. Note that router IDs are not guaranteed to 225 be unique across the Internet, and thus the Subject name in a BGPsec 226 Router Certificate issued using this convention also is not 227 guaranteed to be unique across different issuers. However, each 228 certificate issued by an individual CA MUST contain a Subject name 229 that is unique to that CA context. 231 3.1.2. Subject Public Key Info 233 Refer to section 3.1 of [ID.sidr-bgpsec-algs]. 235 3.1.3. BGPsec Router Certificate Version 3 Extension Fields 237 3.1.3.1. Basic Constraints 239 BGPsec speakers are EEs; therefore, the Basic Constraints extension 240 must not be present, as per [RFC6487]. 242 3.1.3.2. Extended Key Usage 244 BGPsec Router Certificates MUST include the Extended Key Usage (EKU) 245 extension. As specified in [RFC6487] this extension must be marked 246 as non-critical. This document defines one EKU for BGPsec Router 247 Certificates: 249 id-kp OBJECT IDENTIFIER ::= 250 { iso(1) identified-organization(3) dod(6) internet(1) 251 security(5) mechanisms(5) pkix(7) kp(3) } 253 id-kp-bgpsec-router OBJECT IDENTIFIER ::= { id-kp 30 } 255 A BGPsec router MUST require the extended key usage extension to be 256 present in a BGPsec Router Certificate it receives. If multiple 257 KeyPurposeId values are included, the BGPsec routers need not 258 recognize all of them, as long as the required KeyPurposeId value is 259 present. BGPsec routers MUST reject certificates that do not contain 260 the BGPsec Router EKU even if they include the anyExtendedKeyUsage 261 OID defined in [RFC5280]. 263 3.1.3.3. Subject Information Access 265 This extension is not used in BGPsec Router Certificates. It MUST be 266 omitted. 268 3.1.3.4. IP Resources 270 This extension is not used in BGPsec Router Certificates. It MUST be 271 omitted. 273 3.1.3.5. AS Resources 275 Each BGPsec Router Certificate MUST include the AS Resource 276 Identifier Delegation extension, as specified in section 4.8.11 of 277 [RFC6487]. The AS Resource Identifier Delegation extension MUST 278 include one or more AS numbers, and the "inherit" element MUST NOT be 279 specified. 281 3.2. BGPsec Router Certificate Request Profile 283 Refer to section 6 of [RFC6487]. The only differences between this 284 profile and the profile in [RFC6487] are: 286 o The Basic Constraints extension: 288 If included, the CA MUST NOT honor the cA boolean if set to TRUE. 290 o The Extended Key Usage extension: 292 If included, id-kp-bgpsec-router MUST be present (see Section 293 3.1). If included, the CA MUST honor the request for id-kp- 294 bgpsec-router. 296 o The Subject Information Access extension: 298 If included, the CA MUST NOT honor the request to include the 299 extension. 301 o The SubjectPublicKeyInfo field is specified in [ID.sidr-bgpsec- 302 algs]. 304 o The request is signed with the algorithms specified in [ID.sidr- 305 bgpsec-algs]. 307 3.3. BGPsec Router Certificate Validation 309 The validation procedure used for BGPsec Router Certificates is 310 identical to the validation procedure described in Section 7 of 311 [RFC6487] (and any RFC that updates this procedure), as modified 312 below. For example, in step 3: "The certificate contains all field 313 that must be present" - refers to the fields that are required by 314 this specification. 316 The differences are as follows: 318 o BGPsec Router Certificates MUST include the BGPsec Router EKU 319 defined in Section 3.1.3.2. 321 o BGPsec Router Certificates MUST NOT include the SIA extension. 323 o BGPsec Router Certificates MUST NOT include the IP Resource 324 extension. 326 o BGPsec Router Certificates MUST include the AS Resource Identifier 327 Delegation extension. 329 o BGPsec Router Certificate MUST include the subjectPublicKeyInfo 330 described in [ID.sidr-bgpsec-algs]. 332 NOTE: BGPsec RPs will need to support the algorithms in [ID.sidr- 333 bgpsec-algs], which are used to validate BGPsec signatures, as well 334 as the algorithms in [ID.sidr-rfc6485bis], which are needed to 335 validate signatures on BGPsec certificates, RPKI CA certificates, and 336 RPKI CRLs. 338 3.4. Router Certificates and Signing Functions in the RPKI 340 As described in Section 1, the primary function of BGPsec route 341 certificates in the RPKI is for use in the context of certification 342 of Autonomous System (AS) paths in the BGPsec protocol. 344 The private key associated with a router EE certificate may be used 345 multiple times in generating signatures in multiple instances of the 346 BGPsec_Path Attribute Signature Segments [ID.sidr-bgpsec-protocol]. 347 I.e., the BGPsec router certificate is used to validate multiple 348 signatures. 350 BGPsec router certificates are stored in the issuing CA's repository, 351 where a repository following RFC6481 MUST use a .cer filename 352 extension for the certificate file. 354 4. Design Notes 356 The BGPsec Router Certificate profile is based on the Resource 357 Certificate profile as specified in [RFC7935]. As a result, many of 358 the design choices herein are a reflection of the design choices that 359 were taken in that prior work. The reader is referred to [RFC6484] 360 for a fuller discussion of those choices. 362 CAs are required by the Certificate Policy (CP) [RFC6484] to issue 363 properly formed BGPsec Router Certificates regardless of what is 364 present in the certification request so there is some flexibility 365 permitted in the certificate requests: 367 o BGPsec Router Certificates are always EE certificates; therefore, 368 requests to issue a CA certificate result in EE certificates; 370 o BGPsec Router Certificates are always EE certificates; therefore, 371 requests for Key Usage extension values keyCertSign and cRLSign 372 result in certificates with neither of these values; 374 o BGPsec Router Certificates always include the BGPsec Rouer EKU 375 value; therefore, request without the value result in certificates 376 with the value; and, 378 o BGPsec Router Certificates never include the Subject Information 379 Access extension; therefore, request with this extension result in 380 certificates without the extension. 382 Note that this behavior is similar to the CA including the AS 383 Resource Identifier Delegation extension in issued BGPsec Router 384 Certificates despite the fact it is not present in the request. 386 5. Implementation Considerations 388 This document permits the operator to include a list of ASNs in a 389 BGPsec Router Certificate. In that case, the router certificate would 390 become invalid if any one of the ASNs is removed from any superior CA 391 certificate along the path to a trust anchor. Operators could choose 392 to avoid this possibility by issuing a separate BGPsec Router 393 Certificate for each distinct ASN, so that the router certificates 394 for ASNs that are retained in the superior CA certificate would 395 remain valid. 397 6. Security Considerations 399 The Security Considerations of [RFC6487] apply. 401 A BGPsec Router Certificate will fail RPKI validation, as defined in 402 [RFC6487], because the cryptographic algorithms used are different. 403 Consequently, a RP needs to identify the EKU to determine the 404 appropriate Validation constraint. 406 A BGPsec Router Certificate is an extension of the RPKI [RFC6480] to 407 encompass routers. It is a building block BGPsec and is used to 408 validate signatures on BGPsec Signature-Segment origination of 409 Signed-Path segments [ID.sidr-bgpsec-protocol]. Thus its essential 410 security function is the secure binding of one or more AS numbers to 411 a public key, consistent with the RPKI allocation/assignment 412 hierarchy. 414 Hash functions [ID.sidr-bgpsec-algs] are used when generating the two 415 key identifier extensions included in BGPsec certificates. However 416 as noted in [RFC6818], collision resistance is not a required 417 property of one-way hash functions when used to generate key 418 identifiers. Regardless, hash collisions are unlikely, but they are 419 possible and if detected an operator should be alerted. A subject 420 key identifier collision might cause the incorrect certificate to be 421 selected from the cache, resulting in a failed signature validation. 423 7. IANA Considerations 425 This document makes use of two object identifiers in the SMI Registry 426 for PKIX. One is for the ASN.1 module in Appendix A and it comes 427 from the SMI Security for PKIX Module Identifier IANA registry (id- 428 mod-bgpsec-eku). The other is for the BGPsec router EKU defined in 429 Section 3.1.3.2 and Appendix A and it comes from the SMI Security for 430 PKIX Extended Key Purpose IANA registry. These OIDs were assigned 431 before management of the PKIX Arc was handed to IANA. No IANA 432 allocations are request of IANA, but please update the references in 433 those registries when this document is published by the RFC editor. 435 8. Acknowledgements 437 We would like to thank Geoff Huston, George Michaelson, and Robert 438 Loomans for their work on [RFC6487], which this work is based on. In 439 addition, the efforts of Matt Lepinski were instrumental in preparing 440 this work. Additionally, we'd like to thank Rob Austein, Roque 441 Gagliano, Richard Hansen, Geoff Huston, David Mandelberg, Sandra 442 Murphy, and Sam Weiller for their reviews and comments. 444 9. References 446 9.1. Normative References 448 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 449 Requirement Levels", BCP 14, RFC 2119, DOI 450 10.17487/RFC2119, March 1997, . 453 [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP 454 Addresses and AS Identifiers", RFC 3779, DOI 455 10.17487/RFC3779, June 2004, . 458 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border 459 Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 460 10.17487/RFC4271, January 2006, . 463 [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., 464 Housley, R., and W. Polk, "Internet X.509 Public Key 465 Infrastructure Certificate and Certificate Revocation List 466 (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, 467 . 469 [RFC6486] Austein, R., Huston, G., Kent, S., and M. Lepinski, 470 "Manifests for the Resource Public Key Infrastructure 471 (RPKI)", RFC 6486, DOI 10.17487/RFC6486, February 2012, 472 . 474 [RFC6487] Huston, G., Michaelson, G., and R. Loomans, "A Profile for 475 X.509 PKIX Resource Certificates", RFC 6487, DOI 476 10.17487/RFC6487, February 2012, . 479 [RFC7935] Huston, G. and G. Michaelson, Ed., "The Profile for 480 Algorithms and Key Sizes for Use in the Resource Public Key 481 Infrastructure", RFC 7935, DOI 10.17487/RFC7935, August 482 2016, . 484 [ID.sidr-bgpsec-protocol] Lepinski, M. and K. Sriram, "BGPsec 485 Protocol Specification", draft-ietf-sidr-bgpsec-protocol, 486 work-in-progress. 488 [ID.sidr-bgpsec-algs] Turner, S., "BGP Algorithms, Key Formats, & 489 Signature Formats", draft-ietf-sidr-bgpsec-algs, work-in- 490 progress. 492 9.2. Informative References 494 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 495 RFC 4272, DOI 10.17487/RFC4272, January 2006, 496 . 498 [RFC5123] White, R. and B. Akyol, "Considerations in Validating the 499 Path in BGP", RFC 5123, DOI 10.17487/RFC5123, February 500 2008, . 502 [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement 503 with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February 2009, 504 . 506 [RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support 507 Secure Internet Routing", RFC 6480, DOI 10.17487/RFC6480, 508 February 2012, . 510 [RFC6482] Lepinski, M., Kent, S., and D. Kong, "A Profile for Route 511 Origin Authorizations (ROAs)", RFC 6482, DOI 512 10.17487/RFC6482, February 2012, . 515 [RFC6484] Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 516 Policy (CP) for the Resource Public Key Infrastructure 517 (RPKI)", BCP 173, RFC 6484, DOI 10.17487/RFC6484, February 518 2012, . 520 [RFC6486] Austein, R., Huston, G., Kent, S., and M. Lepinski, 521 "Manifests for the Resource Public Key Infrastructure 522 (RPKI)", RFC 6486, DOI 10.17487/RFC6486, February 2012, 523 . 525 [RFC6916] Gagliano, R., Kent, S., and S. Turner, "Algorithm Agility 526 Procedure for the Resource Public Key Infrastructure 527 (RPKI)", BCP 182, RFC 6916, DOI 10.17487/RFC6916, April 528 2013, . 530 Appendix A. ASN.1 Module 532 BGPSECEKU { iso(1) identified-organization(3) dod(6) internet(1) 533 security(5) mechanisms(5) pkix(7) id-mod(0) id-mod-bgpsec-eku(84) } 535 DEFINITIONS EXPLICIT TAGS ::= 537 BEGIN 539 -- EXPORTS ALL -- 541 -- IMPORTS NOTHING -- 543 -- OID Arc -- 545 id-kp OBJECT IDENTIFIER ::= { 546 iso(1) identified-organization(3) dod(6) internet(1) 547 security(5) mechanisms(5) pkix(7) kp(3) } 549 -- BGPsec Router Extended Key Usage -- 551 id-kp-bgpsec-router OBJECT IDENTIFIER ::= { id-kp 30 } 553 END 555 Authors' Addresses 557 Mark Reynolds 558 Island Peak Software 559 328 Virginia Road 560 Concord, MA 01742 562 Email: mcr@islandpeaksoftware.com 564 Sean Turner 565 sn3rd 567 EMail: sean@sn3rd.com 569 Stephen Kent 570 Raytheon BBN Technologies 571 10 Moulton St. 572 Cambridge, MA 02138 574 Email: kent@bbn.com