draft-ietf-sidr-ghostbusters-08.txt   draft-ietf-sidr-ghostbusters-09.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 August 17, 2011 Intended status: Standards Track September 4, 2011
Expires: February 18, 2012 Expires: March 7, 2012
The RPKI Ghostbusters Record The RPKI Ghostbusters Record
draft-ietf-sidr-ghostbusters-08 draft-ietf-sidr-ghostbusters-09
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
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 February 18, 2012. This Internet-Draft will expire on March 7, 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 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . . . . 7 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
1. Introduction 1. Introduction
In the operational use of the RPKI it can become necessary to In the operational use of the RPKI it can become necessary to
skipping to change at page 4, line 10 skipping to change at page 4, line 10
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 [I-D.ietf-sidr-signed-object], and vCARDs [RFC6350].
[I-D.ietf-vcarddav-vcardrev].
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 types
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 N:Name;Human's;Ms.;Dr.;OCD;ADD
skipping to change at page 4, line 37 skipping to change at page 4, line 36
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 types as possible while
providing the minimal necessary data to enable one to contact the providing the minimal necessary data to enable one to contact the
maintainer of the RPKI data which threatens the ROA[s] of concern. 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 [I-D.ietf-vcarddav-vcardrev]. 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
[I-D.ietf-vcarddav-vcardrev]. [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 [I-D.ietf-vcarddav-vcardrev]. of [RFC6350].
FN - the name, as described in 6.2.1 of FN - the name, as described in 6.2.1 of [RFC6350], of a contactable
[I-D.ietf-vcarddav-vcardrev], of a contactable person who person who responsible a the CA certificate.
responsible a the CA certificate.
N - the components of the name of the object the vCard represents, N - the components of the name of the object the vCard represents,
as described in 6.2.2 of [I-D.ietf-vcarddav-vcardrev]. as described in 6.2.2 of [RFC6350].
ORG - an organization as described in 6.6.4 of ORG - an organization as described in 6.6.4 of [RFC6350].
[I-D.ietf-vcarddav-vcardrev].
ADR - a postal address as described in 6.3 of ADR - a postal address as described in 6.3 of [RFC6350].
[I-D.ietf-vcarddav-vcardrev].
TEL - a voice and/or fax phone as described in 6.4.1 of TEL - a voice and/or fax phone as described in 6.4.1 of [RFC6350].
[I-D.ietf-vcarddav-vcardrev].
EMAIL - an Email address as described in 6.4.2 of EMAIL - an Email address as described in 6.4.2 of [RFC6350]
[I-D.ietf-vcarddav-vcardrev]
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 and MUST have the value "END:vCARD" as described in [RFC6350].
[I-D.ietf-vcarddav-vcardrev].
Per [I-D.ietf-vcarddav-vcardrev], the BEGIN, VERSION, FN, N, and END Per [RFC6350], the BEGIN, VERSION, FN, N, and END types MUST be
types MUST be included in a record. To be useful, one or more of included in a record. To be useful, one or more of ADR, TEL, and
ADR, TEL, and EMAIL MUST be included. Other types MUST NOT be EMAIL MUST be included. Other types MUST NOT be included.
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
skipping to change at page 7, line 49 skipping to change at page 7, line 43
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, and Michael Elkins for their contributions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-sidr-ghostbusters]
Bush, R., "The RPKI Ghostbusters Record",
draft-ietf-sidr-ghostbusters-08 (work in progress),
August 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-08 (work in progress), draft-ietf-sidr-repos-struct-09 (work in progress),
June 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",
draft-ietf-sidr-signed-object-04 (work in progress), draft-ietf-sidr-signed-object-04 (work in progress),
May 2011. May 2011.
[I-D.ietf-vcarddav-vcardrev]
Perreault, S., "vCard Format Specification",
draft-ietf-vcarddav-vcardrev-22 (work in progress),
May 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP [RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP
Addresses and AS Identifiers", RFC 3779, June 2004. Addresses and AS Identifiers", RFC 3779, June 2004.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011.
10.2. Informative References 10.2. Informative References
[I-D.ietf-sidr-arch] [I-D.ietf-sidr-arch]
Lepinski, M. and S. Kent, "An Infrastructure to Support Lepinski, M. and S. Kent, "An Infrastructure to Support
Secure Internet Routing", draft-ietf-sidr-arch-13 (work in Secure Internet Routing", draft-ietf-sidr-arch-13 (work in
progress), May 2011. progress), May 2011.
[I-D.ietf-sidr-cp] [I-D.ietf-sidr-cp]
Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate
Policy (CP) for the Resource PKI (RPKI", Policy (CP) for the Resource PKI (RPKI",
 End of changes. 20 change blocks. 
35 lines changed or deleted 30 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/