idnits 2.17.1 draft-ietf-sidr-ghostbusters-16.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 29, 2011) is 4473 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Bush 3 Internet-Draft Internet Initiative Japan 4 Intended status: Standards Track December 29, 2011 5 Expires: July 1, 2012 7 The RPKI Ghostbusters Record 8 draft-ietf-sidr-ghostbusters-16 10 Abstract 12 In the Resource Public Key Infrastructure (RPKI), resource 13 certificates completely obscure names or any other information which 14 might be useful for contacting responsible parties to deal with 15 issues of certificate expiration, maintenance, roll-overs, 16 compromises, etc. This draft describes the RPKI Ghostbusters Record 17 containing human contact information which may be verified 18 (indirectly) by a CA certificate. The data in the record are those 19 of a severely profiled vCard. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in [RFC2119]. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on July 1, 2012. 44 Copyright Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . . 4 63 3. RPKI Ghostbusters Record Payload Example . . . . . . . . . . . 4 64 4. vCard Profile . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 5. CMS Packaging . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 6. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 69 8.1. OID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 8.2. File Extension . . . . . . . . . . . . . . . . . . . . . . 7 71 8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7 72 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 73 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 10.1. Normative References . . . . . . . . . . . . . . . . . . . 8 75 10.2. Informative References . . . . . . . . . . . . . . . . . . 8 76 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 78 1. Introduction 80 In the operational use of the RPKI it can become necessary to 81 contact, human to human, the party responsible for a resource-holding 82 CA certificate, AKA the certificate's maintainer, be it the holder of 83 the certificate's private key or an administrative person in the 84 organization, a NOC, etc. An important example is when the operator 85 of a prefix described by a Route Origin Authorization (ROA) sees a 86 problem, or an impending problem, with a certificate or CRL in the 87 path between the ROA and a trust anchor. E.g., a certificate along 88 that path has expired, is soon to expire, or a CRL associated with a 89 CA along the path is stale, thus placing the quality of the routing 90 of the address space described by the ROA in jeopardy. 92 As the names in RPKI certificates are not meaningful to humans, see 93 [I-D.ietf-sidr-cp], there is no way to use a certificate itself to 94 lead to the worrisome certificate's or CRL's maintainer. So, "Who 95 you gonna call?" 97 This document specifies the RPKI Ghostbusters Record, an object 98 verified via an End Entity (EE) certificate, issued under a CA 99 certificate, the maintainer of which may be contacted using the 100 payload information in the Ghostbusters Record. 102 The Ghostbusters Record conforms to the syntax defined in 103 [I-D.ietf-sidr-signed-object]. The payload of this signed object is 104 a severely profiled vCard. 106 Note that the Ghostbusters Record is not an identity certificate, but 107 rather an attestation to the contact data made by the maintainer of 108 the CA certificate issuing the EE certificate whose corresponding 109 private key signs the Ghostbusters Record. 111 This record is not meant to supplant or be used as resource registry 112 whois data. It gives information about an RPKI CA certificate 113 maintainer not a resource holder. 115 The Ghostbusters Record is optional, CA certificates in the RPKI may 116 have zero or more associated Ghostbuster Records. 118 Given a certificate, to find the closest Ghostbuster Record, go up 119 until a CA certificate is reached, which may be the object itself of 120 course. That CA certificate will have an SIA to the publication 121 point where all subsidiary objects (until you hit a down-chain CA 122 certificate's signed objects) are published. The publication point 123 will contain zero or more Ghostbuster Records. 125 This specification has three main sections. The first, Section 4, is 126 the format of the contact payload information, a severely profiled 127 vCard. The second, Section 5, profiles the packaging of the payload 128 as a profile of the RPKI Signed Object Template specification 129 [I-D.ietf-sidr-signed-object]. The third, Section 6, describes the 130 proper validation of the signed Ghostbusters Record. 132 2. Suggested Reading 134 It is assumed that the reader understands the RPKI, 135 [I-D.ietf-sidr-arch], the RPKI Repository Structure, 136 [I-D.ietf-sidr-repos-struct], Signed RPKI Objects, 137 [I-D.ietf-sidr-signed-object], and vCards [RFC6350]. 139 3. RPKI Ghostbusters Record Payload Example 141 An example of an RPKI Ghostbusters Record payload with all properties 142 populated is as follows: 144 BEGIN:VCARD 145 VERSION:4.0 146 FN:Human's Name 147 ORG:Organizational Entity 148 ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern;WA;98666;U.S.A. 149 TEL;TYPE=VOICE,TEXT,WORK;VALUE=uri:tel:+1-666-555-1212 150 TEL;TYPE=FAX,WORK;VALUE=uri:tel:+1-666-555-1213 151 EMAIL:human@example.com 152 END:VCARD 154 4. vCard Profile 156 The goal in profiling the vCard is not to include as much information 157 as possible, but rather to include as few properties as possible 158 while providing the minimal necessary data to enable one to contact 159 the maintainer of the RPKI data which threatens the ROA[s] of 160 concern. 162 The Ghostbusters vCard payload is a minimalist subset of the vCard as 163 described in [RFC6350]. 165 BEGIN - pro forma packaging which MUST be the first line in the 166 vCard and MUST have the value "BEGIN:VCARD" as described in 167 [RFC6350]. 169 VERSION - pro forma packaging which MUST be the second line in the 170 vCard and MUST have the value "VERSION:4.0" as described in 3.7.9 171 of [RFC6350]. 173 FN - the name, as described in 6.2.1 of [RFC6350], of a contactable 174 person or role who is responsible for the CA certificate. 176 ORG - an organization as described in 6.6.4 of [RFC6350]. 178 ADR - a postal address as described in 6.3 of [RFC6350]. 180 TEL - a voice and/or fax phone as described in 6.4.1 of [RFC6350]. 182 EMAIL - an Email address as described in 6.4.2 of [RFC6350] 184 END - pro forma packaging which MUST be the last line in the vCard 185 and MUST have the value "END:VCARD" as described in [RFC6350]. 187 Per [RFC6350], the BEGIN, VERSION, FN, and END properties MUST be 188 included in a record. To be useful, zero or more of ADR, TEL, and 189 EMAIL MUST be included. Other properties MUST NOT be included. 191 5. CMS Packaging 193 The Ghostbusters Record is a CMS signed-data object conforming to the 194 Signed Object Template for the Resource Public Key Infrastructure, 195 [I-D.ietf-sidr-signed-object]. 197 The ContentType of a Ghostbusters Record is defined as id-ct- 198 rpkiGhostbusters, and has the numerical value of 199 1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the 200 eContentType in the encapContentInfo object as well as the 201 ContentType signed attribute in the signerInfo object. See 202 [I-D.ietf-sidr-signed-object]. 204 eContent: The content of a Ghostbusters Record is described above in 205 Section 4 above. 207 Similarly to a ROA, a Ghostbusters Record is verified using an EE 208 certificate issued by the resource-holding CA certificate whose 209 maintainer is described in the vCard. 211 The EE certificate used to verify the Ghostbusters Record is the one 212 that appears in the CMS data structure which contains the payload 213 defined above. 215 This EE certificate MUST describe its internet number resources using 216 the "inherit" attribute, rather than explicit description of a 217 resource set, see [RFC3779]. 219 6. Validation 221 The validation procedure defined in Section 3 of 222 [I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record. 223 After this procedure has been performed, the Version number type 224 within the payload is checked, and the OCTET STRING containing the 225 vCard data is extracted. These data are checked against the profile 226 defined in Section 4 of this document. Only if all of these checks 227 pass is the Ghostbusters payload deemed valid and made available to 228 the application that requested the payload. 230 7. Security Considerations 232 Though there is no on-the-wire protocol in this specification, there 233 are attacks which could abuse the data described. As the data, to be 234 useful, need to be public, little can be done to avoid this exposure. 236 Phone Numbers: The vCards may contain real world telephone numbers 237 which could be abused for telemarketing, abusive calls, etc. 239 Email Addresses: The vCards may contain Email addresses which could 240 be abused for purposes of spam. 242 Relying parties are hereby warned that the data in a Ghostbusters 243 Record are self-asserted. These data have not been verified by the 244 CA that issued the CA certificate to the entity that issued the EE 245 certificate used to validate the Ghostbusters Record. 247 8. IANA Considerations 249 8.1. OID 251 The IANA is requested to register the OID for the Ghostbusters Record 252 in the registry created by [I-D.ietf-sidr-signed-object] as follows: 254 Name OID Specification 255 ----------------------------------------------------------- 256 Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ] 258 8.2. File Extension 260 Realizing the deep issues raised by [RFC5513], the IANA is requested 261 to add an item for the Ghostbusters Record file extension to the RPKI 262 Repository Name Scheme created by [I-D.ietf-sidr-repos-struct] as 263 follows: 265 Filename Extension RPKI Object Reference 266 ----------------------------------------------------------- 267 .gbr Ghostbusters Record [ This document ] 269 8.3. Media Type 271 The IANA is requested to register the media type application/ 272 rpki-ghostbusters as follows 274 Type name: application 275 Subtype name: rpki-ghostbusters 276 Required parameters: None 277 Optional parameters: None 278 Encoding considerations: binary 279 Security considerations: Carries an RPKI Ghostbusters Record 280 [this document]. 281 Interoperability considerations: None 282 Published specification: This document. 283 Applications that use this media type: RPKI administrators. 284 Additional information: 285 Content: This media type is a signed object, as defined 286 in [I-D.ietf-sidr-signed-object], which contains a payload 287 of a profiled vCard as defined above in this document. 288 Magic number(s): None 289 File extension(s): .gbr 290 Macintosh file type code(s): 291 Person & email address to contact for further information: 292 Randy Bush 293 Intended usage: COMMON 294 Restrictions on usage: None 295 Author: Randy Bush 296 Change controller: Randy Bush 298 9. Acknowledgments 300 The author wishes to thank Russ Housley, the authors of 301 [I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, Rob 302 Austein, Michael Elkins, and Barry Leiba for their contributions. 304 10. References 306 10.1. Normative References 308 [I-D.ietf-sidr-repos-struct] 309 Huston, G., Loomans, R., and G. Michaelson, "A Profile for 310 Resource Certificate Repository Structure", 311 draft-ietf-sidr-repos-struct-09 (work in progress), 312 July 2011. 314 [I-D.ietf-sidr-signed-object] 315 Lepinski, M., Chi, A., and S. Kent, "Signed Object 316 Template for the Resource Public Key Infrastructure", 317 draft-ietf-sidr-signed-object-04 (work in progress), 318 May 2011. 320 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 321 Requirement Levels", BCP 14, RFC 2119, March 1997. 323 [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP 324 Addresses and AS Identifiers", RFC 3779, June 2004. 326 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 327 August 2011. 329 10.2. Informative References 331 [I-D.ietf-sidr-arch] 332 Lepinski, M. and S. Kent, "An Infrastructure to Support 333 Secure Internet Routing", draft-ietf-sidr-arch-13 (work in 334 progress), May 2011. 336 [I-D.ietf-sidr-cp] 337 Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 338 Policy (CP) for the Resource PKI (RPKI", 339 draft-ietf-sidr-cp-17 (work in progress), April 2011. 341 [RFC5513] Farrel, A., "IANA Considerations for Three Letter 342 Acronyms", RFC 5513, April 1 2009. 344 Author's Address 346 Randy Bush 347 Internet Initiative Japan 348 5147 Crystal Springs 349 Bainbridge Island, Washington 98110 350 US 352 Phone: +1 206 780 0431 x1 353 Email: randy@psg.com