idnits 2.17.1 draft-ietf-sidr-ghostbusters-08.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 (August 17, 2011) is 4636 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 282, 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 August 17, 2011 5 Expires: February 18, 2012 7 The RPKI Ghostbusters Record 8 draft-ietf-sidr-ghostbusters-08 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 February 18, 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 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-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, .... 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 do 95 you 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]. 105 Note that the Ghostbusters Record is not an identity certificate, but 106 rather an attestation to the contact data made by the maintainer of 107 the CA certificate issuing the EE certificate whose corresponding 108 private key signs the Ghostbusters Record. 110 This record is not meant to supplant or be used as resource registry 111 whois data. It gives information about an RPKI CA certificate 112 maintainer not a resource holder. 114 The Ghostbusters Record is optional, CA certificates in the RPKI MAY 115 have zero or more associated Ghostbuster Records. 117 This specification has three main sections. The first, Section 4, is 118 the format of the contact payload information, a severely profiled 119 vCARD. The second, Section 5, profiles the packaging of the payload 120 as a profile of the RPKI Signed Object Template specification 121 [I-D.ietf-sidr-signed-object]. The third, Section 6, describes the 122 proper validation of the signed Ghostbusters Record. 124 2. Suggested Reading 126 It is assumed that the reader understands the RPKI, 127 [I-D.ietf-sidr-arch], the RPKI Repository Structure, 128 [I-D.ietf-sidr-repos-struct], Signed RPKI Objects, 129 [I-D.ietf-sidr-signed-object], and vCARDs 130 [I-D.ietf-vcarddav-vcardrev]. 132 3. RPKI Ghostbusters Record Payload Example 134 An example of an RPKI Ghostbusters Record payload with all types 135 populated is as follows: 137 BEGIN:vCard 138 VERSION:4.0 139 FN:Human's Name 140 N:Name;Human's;Ms.;Dr.;OCD;ADD 141 ORG:Organizational Entity 142 ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern; WA; 98666;U.S.A. 143 TEL;TYPE=VOICE,MSG,WORK:+1-666-555-1212 144 TEL;TYPE=FAX,WORK:+1-666-555-1213 145 EMAIL;TYPE=INTERNET:human@example.com 146 END:vCard 148 4. vCARD Profile 150 The goal in profiling the vCARD is not to include as much information 151 as possible, but rather to include as few types as possible while 152 providing the minimal necessary data to enable one to contact the 153 maintainer of the RPKI data which threatens the ROA[s] of concern. 155 The Ghostbusters vCARD payload is a minimalist subset of the vCARD as 156 described in [I-D.ietf-vcarddav-vcardrev]. 158 BEGIN - pro forma packaging which MUST be the first line in the 159 vCARD and MUST have the value "BEGIN:vCARD" as described in 160 [I-D.ietf-vcarddav-vcardrev]. 162 VERSION - pro forma packaging which MUST be the second line in the 163 vCARD and MUST have the value "VERSION:4.0" as described in 3.6.9 164 of [I-D.ietf-vcarddav-vcardrev]. 166 FN - the name, as described in 6.2.1 of 167 [I-D.ietf-vcarddav-vcardrev], of a contactable person who 168 responsible a the CA certificate. 170 N - the components of the name of the object the vCard represents, 171 as described in 6.2.2 of [I-D.ietf-vcarddav-vcardrev]. 173 ORG - an organization as described in 6.6.4 of 174 [I-D.ietf-vcarddav-vcardrev]. 176 ADR - a postal address as described in 6.3 of 177 [I-D.ietf-vcarddav-vcardrev]. 179 TEL - a voice and/or fax phone as described in 6.4.1 of 180 [I-D.ietf-vcarddav-vcardrev]. 182 EMAIL - an Email address as described in 6.4.2 of 183 [I-D.ietf-vcarddav-vcardrev] 185 END - pro forma packaging which MUST be the last line in the vCARD 186 and MUST have the value "END:vCARD" as described in 187 [I-D.ietf-vcarddav-vcardrev]. 189 Per [I-D.ietf-vcarddav-vcardrev], the BEGIN, VERSION, FN, N, and END 190 types MUST be included in a record. To be useful, one or more of 191 ADR, TEL, and EMAIL MUST be included. Other types MUST NOT be 192 included. 194 5. CMS Packaging 196 The Ghostbusters Record is a CMS signed-data object conforming to the 197 Signed Object Template for the Resource Public Key Infrastructure, 198 [I-D.ietf-sidr-signed-object]. 200 The ContentType of a Ghostbusters Record is defined as id-ct- 201 rpkiGhostbusters, and has the numerical value of 202 1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the 203 eContentType in the encapContentInfo object as well as the 204 ContentType signed attribute in the signerInfo object. See 205 [I-D.ietf-sidr-signed-object]. 207 eContent: The content of a Ghostbusters Record is described above in 208 Section 4 above. 210 Similarly to a ROA, a Ghostbusters Record is verified using an EE 211 certificate issued by the resource-holding CA certificate whose 212 maintainer is described in the vCARD. 214 The EE certificate used to verify the Ghostbusters Record is the one 215 that appears in the CMS data structure which contains the payload 216 defined above. 218 This EE certificate MUST describe its internet number resources using 219 the "inherit" attribute, rather than explicit description of a 220 resource set, see [RFC3779]. 222 6. Validation 224 The validation procedure defined in Section 3 of 225 [I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record. 226 After this procedure has been performed, the Version number type 227 within the payload is checked, and the OCTET STRING containing the 228 vCARD data is extracted. These data are checked against the profile 229 defined in Section 4 of this document. Only if all of these checks 230 pass is the Ghostbusters payload deemed valid and made available to 231 the application that requested the payload. 233 7. Security Considerations 235 Though there is no on the wire protocol in this specification, there 236 are attacks which could abuse the data described. As the data, to be 237 useful, need to be public, little can be done to avoid this exposure. 239 Phone Numbers: The vCARDs may contain real world telephone numbers 240 which could be abused for telemarketing, abusive calls, etc. 242 Email Addresses: The vCARDs may contain Email addresses which could 243 be abused for purposes of spam. 245 Relying parties are hereby warned that the data in a Ghostbusters 246 Record are self-asserted. These data have not been verified by the 247 CA that issued the CA certificate to the entity that issued the EE 248 certificate used to validate the Ghostbusters Record. 250 8. IANA Considerations 252 8.1. OID 254 The IANA is requested to register the OID for the Ghostbusters Record 255 in the registry created by [I-D.ietf-sidr-signed-object] as follows: 257 Name OID Specification 258 ----------------------------------------------------------- 259 Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ] 261 8.2. File Extension 263 The IANA is requested to add an item for the Ghostbusters Record file 264 extension to the RPKI Repository Name Scheme created by 265 [I-D.ietf-sidr-repos-struct] as follows: 267 Filename Extension RPKI Object Reference 268 ----------------------------------------------------------- 269 .gbr Ghostbusters Record [ This document ] 271 8.3. Media Type 273 The IANA is requested to register the media type application/ 274 rpki-ghostbusters as follows 276 MIME media type name: application 277 MIME subtype name: rpki-ghostbusters 278 Required parameters: None 279 Optional parameters: None 280 Encoding considerations: binary 281 Security considerations: Carries an RPKI Ghostbusters Record 282 [I-D.ietf-sidr-ghostbusters]. 283 Interoperability considerations: None 284 Published specification: This document 285 Applications which use this media type: Any MIME-complaint transport 286 Additional information: 287 Magic number(s): None 288 File extension(s): .gbr 289 Macintosh File Type Code(s): 290 Person & email address to contact for further information: 291 Randy Bush 292 Intended usage: COMMON 293 Author/Change controller: Randy Bush 295 9. Acknowledgments 297 The author wishes to thank Russ Housley, the authors of 298 [I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, Rob 299 Austein, and Michael Elkins for their contributions. 301 10. References 303 10.1. Normative References 305 [I-D.ietf-sidr-repos-struct] 306 Huston, G., Loomans, R., and G. Michaelson, "A Profile for 307 Resource Certificate Repository Structure", 308 draft-ietf-sidr-repos-struct-08 (work in progress), 309 June 2011. 311 [I-D.ietf-sidr-signed-object] 312 Lepinski, M., Chi, A., and S. Kent, "Signed Object 313 Template for the Resource Public Key Infrastructure", 314 draft-ietf-sidr-signed-object-04 (work in progress), 315 May 2011. 317 [I-D.ietf-vcarddav-vcardrev] 318 Perreault, S., "vCard Format Specification", 319 draft-ietf-vcarddav-vcardrev-22 (work in progress), 320 May 2011. 322 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 323 Requirement Levels", BCP 14, RFC 2119, March 1997. 325 [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP 326 Addresses and AS Identifiers", RFC 3779, June 2004. 328 10.2. Informative References 330 [I-D.ietf-sidr-arch] 331 Lepinski, M. and S. Kent, "An Infrastructure to Support 332 Secure Internet Routing", draft-ietf-sidr-arch-13 (work in 333 progress), May 2011. 335 [I-D.ietf-sidr-cp] 336 Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 337 Policy (CP) for the Resource PKI (RPKI", 338 draft-ietf-sidr-cp-17 (work in progress), April 2011. 340 Author's Address 342 Randy Bush 343 Internet Initiative Japan 344 5147 Crystal Springs 345 Bainbridge Island, Washington 98110 346 US 348 Phone: +1 206 780 0431 x1 349 Email: randy@psg.com