idnits 2.17.1 draft-ietf-sidr-ghostbusters-05.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 (July 10, 2011) is 4667 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: 'I-D.ietf-sidr-ghostbusters' is mentioned on line 274, but not defined == Outdated reference: A later version (-09) exists of draft-ietf-sidr-repos-struct-08 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 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 July 10, 2011 5 Expires: January 11, 2012 7 The RPKI Ghostbusters Record 8 draft-ietf-sidr-ghostbusters-05 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 to be signed (indirectly) by a 18 resource-owning certificate. The data in the record are those of a 19 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 RFC 2119 [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 January 11, 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 . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. RPKI Ghostbusters Record Payload Example . . . . . . . . . . . 4 64 4. vCARD Profile . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 5. CMS Packaging . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 6. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 69 8.1. OID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 8.2. File Extension . . . . . . . . . . . . . . . . . . . . . . 6 71 8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7 72 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 73 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 74 10.1. Normative References . . . . . . . . . . . . . . . . . . . 7 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-owning 82 certificate. An important example is when the owner of a Route 83 Origin Authorization (ROA) sees a problem, or an impending problem, 84 with a certificate or CRL in the path between the ROA and a trust 85 anchor. E.g., a certificate along that path has expired, is soon to 86 expire, or a CRL associated with a CA along the path is stale, thus 87 placing the quality of the routing of the address space described by 88 the ROA in jeopardy. 90 As the names in RPKI certificates are intentionally hashes which are 91 not meaningful to humans, see [I-D.ietf-sidr-cp], there is no way to 92 use a certificate itself to lead to the worrisome certificate's or 93 CRL's maintainer. So, "Who do you call?" 95 This document specifies the RPKI Ghostbusters Record, an object 96 signed, indirectly via an End Entity (EE) certificate, by the 97 certificate whose maintainer may be contacted using the human usable 98 payload information in the Ghostbusters Record. 100 The Ghostbusters Record conforms to the syntax defined in 101 [I-D.ietf-sidr-signed-object]. 103 Note that the Ghostbusters Record is not an identity certificate, but 104 rather an attestation to the contact data made by the issuer of the 105 certificate signing the Ghostbusters Record. 107 This record is not meant to supplant or be used as resource registry 108 whois data. It gives information about an RPKI certificate 109 maintainer not a resource holder. 111 This specification has three main sections. The first, Section 4, is 112 the format of the contact payload information, a severely profiled 113 vCARD. The second, Section 5, profiles the packaging of the payload 114 as a profile of the RPKI Signed Object Template specification 115 [I-D.ietf-sidr-signed-object]. The third, Section 6, describes the 116 proper validation of the signed Ghostbusters Record. 118 2. Suggested Reading 120 It is assumed that the reader understands the RPKI, 121 [I-D.ietf-sidr-arch], the RPKI Repository Structure, 122 [I-D.ietf-sidr-repos-struct], Signed RPKI Objects, 123 [I-D.ietf-sidr-signed-object], and vCARDs 124 [I-D.ietf-vcarddav-vcardrev]. 126 3. RPKI Ghostbusters Record Payload Example 128 An example of an RPKI Ghostbusters Record payload with all types 129 populated is as follows: 131 BEGIN:vCard 132 VERSION:4.0 133 FN:Human's Name 134 N:Name;Human's;Ms.;Dr.;OCD;ADD 135 ORG:Organizational Entity 136 ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern; WA; 98666;U.S.A. 137 TEL;TYPE=VOICE,MSG,WORK:+1-666-555-1212 138 TEL;TYPE=FAX,WORK:+1-666-555-1213 139 EMAIL;TYPE=INTERNET:human@example.com 140 END:vCard 142 4. vCARD Profile 144 The goal in profiling the vCARD is not to include as much information 145 as possible, but rather to include as few types as possible while 146 providing the minimal necessary data to enable one to contact the 147 maintainer of the RPKI data which threatens the ROA[s] of concern. 149 The Ghostbusters vCARD payload is a minimalist subset of the vCARD as 150 described in [I-D.ietf-vcarddav-vcardrev]. 152 BEGIN - pro forma packaging which MUST be the first line in the 153 vCARD and MUST have the value "BEGIN:vCARD" as described in 154 [I-D.ietf-vcarddav-vcardrev]. 156 VERSION - pro forma packaging which MUST be the second line in the 157 vCARD and MUST have the value "VERSION:4.0" as described in 3.6.9 158 of [I-D.ietf-vcarddav-vcardrev]. 160 FN - the name, as described in 6.2.1 of 161 [I-D.ietf-vcarddav-vcardrev], of a contactable person who 162 responsible for the certificate. 164 N - the components of the name of the object the vCard represents, 165 as described in 6.2.2 of [I-D.ietf-vcarddav-vcardrev]. 167 ORG - an organization as described in 6.6.4 of 168 [I-D.ietf-vcarddav-vcardrev]. 170 ADR - a postal address as described in 6.3 of 171 [I-D.ietf-vcarddav-vcardrev]. 173 TEL - a voice and/or fax phone as described in 6.4.1 of 174 [I-D.ietf-vcarddav-vcardrev]. 176 EMAIL - an Email address as described in 6.4.2 of 177 [I-D.ietf-vcarddav-vcardrev] 179 END - pro forma packaging which MUST be the last line in the vCARD 180 and MUST have the value "END:vCARD" as described in 181 [I-D.ietf-vcarddav-vcardrev]. 183 Per [I-D.ietf-vcarddav-vcardrev], the BEGIN, VERSION, FN, N, and END 184 types MUST be included in a record. To be useful, one or more of 185 ADR, TEL, and EMAIL MUST be included. Other types MUST NOT be 186 included. 188 5. CMS Packaging 190 The Ghostbusters Record is a CMS signed-data object conforming to the 191 Signed Object Template for the Resource Public Key Infrastructure, 192 [I-D.ietf-sidr-signed-object]. 194 The ContentType of a Ghostbusters Record is defined as id-ct- 195 rpkiGhostbusters, and has the numerical value of 196 1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the 197 eContentType in the encapContentInfo object as well as the 198 ContentType signed attribute in the signerInfo object. See 199 [I-D.ietf-sidr-signed-object]. 201 eContent: The content of a Ghostbusters Record is described above in 202 Section 4 above. 204 Similarly to a ROA, the Ghostbusters Record is verified using an EE 205 certificate issued under the CA certificate associated with the 206 resource-holding certificate whose maintainer is described in the 207 vCARD. 209 The EE certificate used to verify the Ghostbusters Record is the one 210 that appears in the CMS data structure that contains the payload 211 defined above. 213 6. Validation 215 The validation procedure defined in Section 3 of 217 [I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record. 218 After this procedure has been performed, the Version number type 219 within the payload is checked, and the OCTET STRING containing the 220 vCARD data is extracted. These data are checked against the profile 221 defined in Section 4 of this document. Only if all of these checks 222 pass is the Ghostbusters payload deemed valid and made available to 223 the application that requested the payload. 225 7. Security Considerations 227 Though there is no on the wire protocol in this specification, there 228 are attacks which could abuse the data described. As the data, to be 229 useful, need to be public, little can be done to avoid this exposure. 231 Phone Numbers: The vCARDs may contain real world telephone numbers 232 which could be abused for telemarketing, abusive calls, etc. 234 Email Addresses: The vCARDs may contain Email addresses which could 235 be abused for purposes of spam. 237 Relying parties are warned that the data in a Ghostbusters Record are 238 self-asserted. These data have not been verified by the CA that 239 issued a (CA) certificate to the entity that issued the EE 240 certificate used to validate the Ghostbusters Record. 242 8. IANA Considerations 244 8.1. OID 246 The IANA is requested to register the OID for the Ghostbusters Record 247 in the registry created by [I-D.ietf-sidr-signed-object] as follows: 249 Name OID Specification 250 ----------------------------------------------------------- 251 Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ] 253 8.2. File Extension 255 The IANA is requested to add an item for the Ghostbusters Record file 256 extension to the RPKI Repository Name Scheme created by 257 [I-D.ietf-sidr-repos-struct] as follows: 259 Filename Extension RPKI Object Reference 260 ----------------------------------------------------------- 261 .gbr Ghostbusters Record [ This document ] 263 8.3. Media Type 265 The IANA is requested to register the media type application/ 266 rpki-ghostbusters as follows 268 MIME media type name: application 269 MIME subtype name: rpki-ghostbusters 270 Required parameters: None 271 Optional parameters: None 272 Encoding considerations: binary 273 Security considerations: Carries an RPKI Ghostbusters Record 274 [I-D.ietf-sidr-ghostbusters]. 275 Interoperability considerations: None 276 Published specification: This document 277 Applications which use this media type: Any MIME-complaint transport 278 Additional information: 279 Magic number(s): None 280 File extension(s): .gbr 281 Macintosh File Type Code(s): 282 Person & email address to contact for further information: 283 Randy Bush 284 Intended usage: COMMON 285 Author/Change controller: Randy Bush 287 9. Acknowledgments 289 The author wishes to thank Russ Housley, the authors of 290 [I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, and Michael 291 Elkins for their contributions. 293 10. References 295 10.1. Normative References 297 [I-D.ietf-sidr-repos-struct] 298 Huston, G., Loomans, R., and G. Michaelson, "A Profile for 299 Resource Certificate Repository Structure", 300 draft-ietf-sidr-repos-struct-08 (work in progress), 301 June 2011. 303 [I-D.ietf-sidr-signed-object] 304 Lepinski, M., Chi, A., and S. Kent, "Signed Object 305 Template for the Resource Public Key Infrastructure", 306 draft-ietf-sidr-signed-object-04 (work in progress), 307 May 2011. 309 [I-D.ietf-vcarddav-vcardrev] 310 Perreault, S., "vCard Format Specification", 311 draft-ietf-vcarddav-vcardrev-22 (work in progress), 312 May 2011. 314 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 315 Requirement Levels", BCP 14, RFC 2119, March 1997. 317 10.2. Informative References 319 [I-D.ietf-sidr-arch] 320 Lepinski, M. and S. Kent, "An Infrastructure to Support 321 Secure Internet Routing", draft-ietf-sidr-arch-13 (work in 322 progress), May 2011. 324 [I-D.ietf-sidr-cp] 325 Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 326 Policy (CP) for the Resource PKI (RPKI", 327 draft-ietf-sidr-cp-17 (work in progress), April 2011. 329 Author's Address 331 Randy Bush 332 Internet Initiative Japan 333 5147 Crystal Springs 334 Bainbridge Island, Washington 98110 335 US 337 Phone: +1 206 780 0431 x1 338 Email: randy@psg.com