draft-ietf-sidr-ghostbusters-09.txt   draft-ietf-sidr-ghostbusters-10.txt 
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Internet Initiative Japan Internet-Draft Internet Initiative Japan
Intended status: Standards Track September 4, 2011 Intended status: Standards Track September 14, 2011
Expires: March 7, 2012 Expires: March 17, 2012
The RPKI Ghostbusters Record The RPKI Ghostbusters Record
draft-ietf-sidr-ghostbusters-09 draft-ietf-sidr-ghostbusters-10
Abstract Abstract
In the Resource Public Key Infrastructure (RPKI), resource In the Resource Public Key Infrastructure (RPKI), resource
certificates completely obscure names or any other information which certificates completely obscure names or any other information which
might be useful for contacting responsible parties to deal with might be useful for contacting responsible parties to deal with
issues of certificate expiration, maintenance, roll-overs, issues of certificate expiration, maintenance, roll-overs,
compromises, etc. This draft describes the RPKI Ghostbusters Record compromises, etc. This draft describes the RPKI Ghostbusters Record
containing human contact information which may be verified containing human contact information which may be verified
(indirectly) by a CA certificate. The data in the record are those (indirectly) by a CA certificate. The data in the record are those
of a severely profiled vCARD. of a severely profiled vCard.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 7, 2012. This Internet-Draft will expire on March 17, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . . 4 2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . . 4
3. RPKI Ghostbusters Record Payload Example . . . . . . . . . . . 4 3. RPKI Ghostbusters Record Payload Example . . . . . . . . . . . 4
4. vCARD Profile . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. vCard Profile . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. CMS Packaging . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. CMS Packaging . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
8.1. OID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. OID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.2. File Extension . . . . . . . . . . . . . . . . . . . . . . 6 8.2. File Extension . . . . . . . . . . . . . . . . . . . . . . 6
8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7 8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . . 8 10.2. Informative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 3, line 46 skipping to change at page 3, line 46
This record is not meant to supplant or be used as resource registry This record is not meant to supplant or be used as resource registry
whois data. It gives information about an RPKI CA certificate whois data. It gives information about an RPKI CA certificate
maintainer not a resource holder. maintainer not a resource holder.
The Ghostbusters Record is optional, CA certificates in the RPKI MAY The Ghostbusters Record is optional, CA certificates in the RPKI MAY
have zero or more associated Ghostbuster Records. have zero or more associated Ghostbuster Records.
This specification has three main sections. The first, Section 4, is This specification has three main sections. The first, Section 4, is
the format of the contact payload information, a severely profiled the format of the contact payload information, a severely profiled
vCARD. The second, Section 5, profiles the packaging of the payload vCard. The second, Section 5, profiles the packaging of the payload
as a profile of the RPKI Signed Object Template specification as a profile of the RPKI Signed Object Template specification
[I-D.ietf-sidr-signed-object]. The third, Section 6, describes the [I-D.ietf-sidr-signed-object]. The third, Section 6, describes the
proper validation of the signed Ghostbusters Record. proper validation of the signed Ghostbusters Record.
2. Suggested Reading 2. Suggested Reading
It is assumed that the reader understands the RPKI, It is assumed that the reader understands the RPKI,
[I-D.ietf-sidr-arch], the RPKI Repository Structure, [I-D.ietf-sidr-arch], the RPKI Repository Structure,
[I-D.ietf-sidr-repos-struct], Signed RPKI Objects, [I-D.ietf-sidr-repos-struct], Signed RPKI Objects,
[I-D.ietf-sidr-signed-object], and vCARDs [RFC6350]. [I-D.ietf-sidr-signed-object], and vCards [RFC6350].
3. RPKI Ghostbusters Record Payload Example 3. RPKI Ghostbusters Record Payload Example
An example of an RPKI Ghostbusters Record payload with all types An example of an RPKI Ghostbusters Record payload with all properties
populated is as follows: populated is as follows:
BEGIN:vCard BEGIN:vCard
VERSION:4.0 VERSION:4.0
FN:Human's Name FN:Human's Name
N:Name;Human's;Ms.;Dr.;OCD;ADD
ORG:Organizational Entity ORG:Organizational Entity
ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern; WA; 98666;U.S.A. ADR;TYPE=WORK:;;42 Twisty Passage;Deep Cavern; WA; 98666;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-666-555-1212 TEL;TYPE=VOICE,MSG,WORK:+1-666-555-1212
TEL;TYPE=FAX,WORK:+1-666-555-1213 TEL;TYPE=FAX,WORK:+1-666-555-1213
EMAIL;TYPE=INTERNET:human@example.com EMAIL;TYPE=INTERNET:human@example.com
END:vCard END:vCard
4. vCARD Profile 4. vCard Profile
The goal in profiling the vCARD is not to include as much information The goal in profiling the vCard is not to include as much information
as possible, but rather to include as few types as possible while as possible, but rather to include as few properties as possible
providing the minimal necessary data to enable one to contact the while providing the minimal necessary data to enable one to contact
maintainer of the RPKI data which threatens the ROA[s] of concern. the maintainer of the RPKI data which threatens the ROA[s] of
concern.
The Ghostbusters vCARD payload is a minimalist subset of the vCARD as The Ghostbusters vCard payload is a minimalist subset of the vCard as
described in [RFC6350]. described in [RFC6350].
BEGIN - pro forma packaging which MUST be the first line in the BEGIN - pro forma packaging which MUST be the first line in the
vCARD and MUST have the value "BEGIN:vCARD" as described in vCard and MUST have the value "BEGIN:vCard" as described in
[RFC6350]. [RFC6350].
VERSION - pro forma packaging which MUST be the second line in the VERSION - pro forma packaging which MUST be the second line in the
vCARD and MUST have the value "VERSION:4.0" as described in 3.6.9 vCard and MUST have the value "VERSION:4.0" as described in 3.6.9
of [RFC6350]. of [RFC6350].
FN - the name, as described in 6.2.1 of [RFC6350], of a contactable FN - the name, as described in 6.2.1 of [RFC6350], of a contactable
person who responsible a the CA certificate. person who responsible a the CA certificate.
N - the components of the name of the object the vCard represents,
as described in 6.2.2 of [RFC6350].
ORG - an organization as described in 6.6.4 of [RFC6350]. ORG - an organization as described in 6.6.4 of [RFC6350].
ADR - a postal address as described in 6.3 of [RFC6350]. ADR - a postal address as described in 6.3 of [RFC6350].
TEL - a voice and/or fax phone as described in 6.4.1 of [RFC6350]. TEL - a voice and/or fax phone as described in 6.4.1 of [RFC6350].
EMAIL - an Email address as described in 6.4.2 of [RFC6350] EMAIL - an Email address as described in 6.4.2 of [RFC6350]
END - pro forma packaging which MUST be the last line in the vCARD END - pro forma packaging which MUST be the last line in the vCard
and MUST have the value "END:vCARD" as described in [RFC6350]. and MUST have the value "END:vCard" as described in [RFC6350].
Per [RFC6350], the BEGIN, VERSION, FN, N, and END types MUST be Per [RFC6350], the BEGIN, VERSION, FN, and END properties MUST be
included in a record. To be useful, one or more of ADR, TEL, and included in a record. To be useful, one or more of ADR, TEL, and
EMAIL MUST be included. Other types MUST NOT be included. EMAIL MUST be included. Other properties MUST NOT be included.
5. CMS Packaging 5. CMS Packaging
The Ghostbusters Record is a CMS signed-data object conforming to the The Ghostbusters Record is a CMS signed-data object conforming to the
Signed Object Template for the Resource Public Key Infrastructure, Signed Object Template for the Resource Public Key Infrastructure,
[I-D.ietf-sidr-signed-object]. [I-D.ietf-sidr-signed-object].
The ContentType of a Ghostbusters Record is defined as id-ct- The ContentType of a Ghostbusters Record is defined as id-ct-
rpkiGhostbusters, and has the numerical value of rpkiGhostbusters, and has the numerical value of
1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the 1.2.840.113549.1.9.16.1.35. This OID MUST appear both within the
eContentType in the encapContentInfo object as well as the eContentType in the encapContentInfo object as well as the
ContentType signed attribute in the signerInfo object. See ContentType signed attribute in the signerInfo object. See
[I-D.ietf-sidr-signed-object]. [I-D.ietf-sidr-signed-object].
eContent: The content of a Ghostbusters Record is described above in eContent: The content of a Ghostbusters Record is described above in
Section 4 above. Section 4 above.
Similarly to a ROA, a Ghostbusters Record is verified using an EE Similarly to a ROA, a Ghostbusters Record is verified using an EE
certificate issued by the resource-holding CA certificate whose certificate issued by the resource-holding CA certificate whose
maintainer is described in the vCARD. maintainer is described in the vCard.
The EE certificate used to verify the Ghostbusters Record is the one The EE certificate used to verify the Ghostbusters Record is the one
that appears in the CMS data structure which contains the payload that appears in the CMS data structure which contains the payload
defined above. defined above.
This EE certificate MUST describe its internet number resources using This EE certificate MUST describe its internet number resources using
the "inherit" attribute, rather than explicit description of a the "inherit" attribute, rather than explicit description of a
resource set, see [RFC3779]. resource set, see [RFC3779].
6. Validation 6. Validation
skipping to change at page 6, line 8 skipping to change at page 6, line 4
that appears in the CMS data structure which contains the payload that appears in the CMS data structure which contains the payload
defined above. defined above.
This EE certificate MUST describe its internet number resources using This EE certificate MUST describe its internet number resources using
the "inherit" attribute, rather than explicit description of a the "inherit" attribute, rather than explicit description of a
resource set, see [RFC3779]. resource set, see [RFC3779].
6. Validation 6. Validation
The validation procedure defined in Section 3 of The validation procedure defined in Section 3 of
[I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record. [I-D.ietf-sidr-signed-object] is applied to a Ghostbusters Record.
After this procedure has been performed, the Version number type After this procedure has been performed, the Version number type
within the payload is checked, and the OCTET STRING containing the within the payload is checked, and the OCTET STRING containing the
vCARD data is extracted. These data are checked against the profile vCard data is extracted. These data are checked against the profile
defined in Section 4 of this document. Only if all of these checks defined in Section 4 of this document. Only if all of these checks
pass is the Ghostbusters payload deemed valid and made available to pass is the Ghostbusters payload deemed valid and made available to
the application that requested the payload. the application that requested the payload.
7. Security Considerations 7. Security Considerations
Though there is no on the wire protocol in this specification, there Though there is no on-the-wire protocol in this specification, there
are attacks which could abuse the data described. As the data, to be are attacks which could abuse the data described. As the data, to be
useful, need to be public, little can be done to avoid this exposure. useful, need to be public, little can be done to avoid this exposure.
Phone Numbers: The vCARDs may contain real world telephone numbers Phone Numbers: The vCards may contain real world telephone numbers
which could be abused for telemarketing, abusive calls, etc. which could be abused for telemarketing, abusive calls, etc.
Email Addresses: The vCARDs may contain Email addresses which could Email Addresses: The vCards may contain Email addresses which could
be abused for purposes of spam. be abused for purposes of spam.
Relying parties are hereby warned that the data in a Ghostbusters Relying parties are hereby warned that the data in a Ghostbusters
Record are self-asserted. These data have not been verified by the Record are self-asserted. These data have not been verified by the
CA that issued the CA certificate to the entity that issued the EE CA that issued the CA certificate to the entity that issued the EE
certificate used to validate the Ghostbusters Record. certificate used to validate the Ghostbusters Record.
8. IANA Considerations 8. IANA Considerations
8.1. OID 8.1. OID
skipping to change at page 7, line 37 skipping to change at page 7, line 33
Macintosh File Type Code(s): Macintosh File Type Code(s):
Person & email address to contact for further information: Person & email address to contact for further information:
Randy Bush <randy@psg.com> Randy Bush <randy@psg.com>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: Randy Bush <randy@psg.com> Author/Change controller: Randy Bush <randy@psg.com>
9. Acknowledgments 9. Acknowledgments
The author wishes to thank Russ Housley, the authors of The author wishes to thank Russ Housley, the authors of
[I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, Rob [I-D.ietf-sidr-repos-struct], Stephen Kent, Sandy Murphy, Rob
Austein, and Michael Elkins for their contributions. Austein, Michael Elkins, and Barry Leiba for their contributions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-sidr-ghostbusters] [I-D.ietf-sidr-ghostbusters]
Bush, R., "The RPKI Ghostbusters Record", Bush, R., "The RPKI Ghostbusters Record",
draft-ietf-sidr-ghostbusters-08 (work in progress), draft-ietf-sidr-ghostbusters-09 (work in progress),
August 2011. September 2011.
[I-D.ietf-sidr-repos-struct] [I-D.ietf-sidr-repos-struct]
Huston, G., Loomans, R., and G. Michaelson, "A Profile for Huston, G., Loomans, R., and G. Michaelson, "A Profile for
Resource Certificate Repository Structure", Resource Certificate Repository Structure",
draft-ietf-sidr-repos-struct-09 (work in progress), draft-ietf-sidr-repos-struct-09 (work in progress),
July 2011. July 2011.
[I-D.ietf-sidr-signed-object] [I-D.ietf-sidr-signed-object]
Lepinski, M., Chi, A., and S. Kent, "Signed Object Lepinski, M., Chi, A., and S. Kent, "Signed Object
Template for the Resource Public Key Infrastructure", Template for the Resource Public Key Infrastructure",
 End of changes. 27 change blocks. 
34 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/