idnits 2.17.1 draft-ietf-sidr-ghostbusters-13.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 (September 15, 2011) is 4600 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) == Outdated reference: A later version (-16) exists of draft-ietf-sidr-ghostbusters-09 Summary: 0 errors (**), 0 flaws (~~), 2 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 September 15, 2011 5 Expires: March 18, 2012 7 The RPKI Ghostbusters Record 8 draft-ietf-sidr-ghostbusters-13 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 March 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 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-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 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]. 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 [RFC6350]. 131 3. RPKI Ghostbusters Record Payload Example 133 An example of an RPKI Ghostbusters Record payload with all properties 134 populated is as follows: 136 BEGIN:VCARD 137 VERSION:4.0 138 FN:Human's Name 139 ORG:Organizational Entity 140 ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern;WA;98666;U.S.A. 141 TEL;TYPE=VOICE,TEXT,WORK;VALUE=uri:tel:+1-666-555-1212 142 TEL;TYPE=FAX,WORK;VALUE=uri:tel:+1-666-555-1213 143 EMAIL:human@example.com 144 END:VCARD 146 4. vCard Profile 148 The goal in profiling the vCard is not to include as much information 149 as possible, but rather to include as few properties as possible 150 while providing the minimal necessary data to enable one to contact 151 the maintainer of the RPKI data which threatens the ROA[s] of 152 concern. 154 The Ghostbusters vCard payload is a minimalist subset of the vCard as 155 described in [RFC6350]. 157 BEGIN - pro forma packaging which MUST be the first line in the 158 vCard and MUST have the value "BEGIN:VCARD" as described in 159 [RFC6350]. 161 VERSION - pro forma packaging which MUST be the second line in the 162 vCard and MUST have the value "VERSION:4.0" as described in 3.6.9 163 of [RFC6350]. 165 FN - the name, as described in 6.2.1 of [RFC6350], of a contactable 166 person who responsible a the CA certificate. 168 ORG - an organization as described in 6.6.4 of [RFC6350]. 170 ADR - a postal address as described in 6.3 of [RFC6350]. 172 TEL - a voice and/or fax phone as described in 6.4.1 of [RFC6350]. 174 EMAIL - an Email address as described in 6.4.2 of [RFC6350] 176 END - pro forma packaging which MUST be the last line in the vCard 177 and MUST have the value "END:VCARD" as described in [RFC6350]. 179 Per [RFC6350], the BEGIN, VERSION, FN, and END properties MUST be 180 included in a record. To be useful, one or more of ADR, TEL, and 181 EMAIL MUST be included. Other properties MUST NOT be included. 183 5. CMS Packaging 185 The Ghostbusters Record is a CMS signed-data object conforming to the 186 Signed Object Template for the Resource Public Key Infrastructure, 187 [I-D.ietf-sidr-signed-object]. 189 The ContentType of a Ghostbusters Record is defined as id-ct- 190 rpkiGhostbusters, and has the numerical value of 191 1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the 192 eContentType in the encapContentInfo object as well as the 193 ContentType signed attribute in the signerInfo object. See 194 [I-D.ietf-sidr-signed-object]. 196 eContent: The content of a Ghostbusters Record is described above in 197 Section 4 above. 199 Similarly to a ROA, a Ghostbusters Record is verified using an EE 200 certificate issued by the resource-holding CA certificate whose 201 maintainer is described in the vCard. 203 The EE certificate used to verify the Ghostbusters Record is the one 204 that appears in the CMS data structure which contains the payload 205 defined above. 207 This EE certificate MUST describe its internet number resources using 208 the "inherit" attribute, rather than explicit description of a 209 resource set, see [RFC3779]. 211 6. Validation 213 The validation procedure defined in Section 3 of 215 [I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record. 216 After this procedure has been performed, the Version number type 217 within the payload is checked, and the OCTET STRING containing the 218 vCard data is extracted. These data are checked against the profile 219 defined in Section 4 of this document. Only if all of these checks 220 pass is the Ghostbusters payload deemed valid and made available to 221 the application that requested the payload. 223 7. Security Considerations 225 Though there is no on-the-wire protocol in this specification, there 226 are attacks which could abuse the data described. As the data, to be 227 useful, need to be public, little can be done to avoid this exposure. 229 Phone Numbers: The vCards may contain real world telephone numbers 230 which could be abused for telemarketing, abusive calls, etc. 232 Email Addresses: The vCards may contain Email addresses which could 233 be abused for purposes of spam. 235 Relying parties are hereby warned that the data in a Ghostbusters 236 Record are self-asserted. These data have not been verified by the 237 CA that issued the CA certificate to the entity that issued the EE 238 certificate used to validate the Ghostbusters Record. 240 8. IANA Considerations 242 8.1. OID 244 The IANA is requested to register the OID for the Ghostbusters Record 245 in the registry created by [I-D.ietf-sidr-signed-object] as follows: 247 Name OID Specification 248 ----------------------------------------------------------- 249 Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ] 251 8.2. File Extension 253 The IANA is requested to add an item for the Ghostbusters Record file 254 extension to the RPKI Repository Name Scheme created by 255 [I-D.ietf-sidr-repos-struct] as follows: 257 Filename Extension RPKI Object Reference 258 ----------------------------------------------------------- 259 .gbr Ghostbusters Record [ This document ] 261 8.3. Media Type 263 The IANA is requested to register the media type application/ 264 rpki-ghostbusters as follows 266 MIME media type name: application 267 MIME subtype name: rpki-ghostbusters 268 Required parameters: None 269 Optional parameters: None 270 Encoding considerations: binary 271 Security considerations: Carries an RPKI Ghostbusters Record 272 [I-D.ietf-sidr-ghostbusters]. 273 Interoperability considerations: None 274 Published specification: This document 275 Applications which use this media type: Any MIME-complaint transport 276 Additional information: 277 Magic number(s): None 278 File extension(s): .gbr 279 Macintosh File Type Code(s): 280 Person & email address to contact for further information: 281 Randy Bush 282 Intended usage: COMMON 283 Author/Change controller: Randy Bush 285 9. Acknowledgments 287 The author wishes to thank Russ Housley, the authors of 288 [I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, Rob 289 Austein, Michael Elkins, and Barry Leiba for their contributions. 291 10. References 293 10.1. Normative References 295 [I-D.ietf-sidr-ghostbusters] 296 Bush, R., "The RPKI Ghostbusters Record", 297 draft-ietf-sidr-ghostbusters-09 (work in progress), 298 September 2011. 300 [I-D.ietf-sidr-repos-struct] 301 Huston, G., Loomans, R., and G. Michaelson, "A Profile for 302 Resource Certificate Repository Structure", 303 draft-ietf-sidr-repos-struct-09 (work in progress), 304 July 2011. 306 [I-D.ietf-sidr-signed-object] 307 Lepinski, M., Chi, A., and S. Kent, "Signed Object 308 Template for the Resource Public Key Infrastructure", 309 draft-ietf-sidr-signed-object-04 (work in progress), 310 May 2011. 312 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 313 Requirement Levels", BCP 14, RFC 2119, March 1997. 315 [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP 316 Addresses and AS Identifiers", RFC 3779, June 2004. 318 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 319 August 2011. 321 10.2. Informative References 323 [I-D.ietf-sidr-arch] 324 Lepinski, M. and S. Kent, "An Infrastructure to Support 325 Secure Internet Routing", draft-ietf-sidr-arch-13 (work in 326 progress), May 2011. 328 [I-D.ietf-sidr-cp] 329 Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate 330 Policy (CP) for the Resource PKI (RPKI", 331 draft-ietf-sidr-cp-17 (work in progress), April 2011. 333 Author's Address 335 Randy Bush 336 Internet Initiative Japan 337 5147 Crystal Springs 338 Bainbridge Island, Washington 98110 339 US 341 Phone: +1 206 780 0431 x1 342 Email: randy@psg.com