draft-ietf-sidr-ghostbusters-14.txt   draft-ietf-sidr-ghostbusters-15.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 26, 2011 Intended status: Standards Track October 17, 2011
Expires: March 29, 2012 Expires: April 19, 2012
The RPKI Ghostbusters Record The RPKI Ghostbusters Record
draft-ietf-sidr-ghostbusters-14 draft-ietf-sidr-ghostbusters-15
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 March 29, 2012. This Internet-Draft will expire on April 19, 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 22 skipping to change at page 2, line 22
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . . . . . . 6 8.2. File Extension . . . . . . . . . . . . . . . . . . . . . . 7
8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7 8.3. Media Type . . . . . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . . 8
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
contact, human to human, the party responsible for a resource-holding contact, human to human, the party responsible for a resource-holding
CA certificate, AKA the certificate's maintainer, be it the holder of CA certificate, AKA the certificate's maintainer, be it the holder of
the certificate's private key or an administrative person in the the certificate's private key or an administrative person in the
organization, a NOC, .... An important example is when the operator organization, a NOC, etc. An important example is when the operator
of a prefix described by a Route Origin Authorization (ROA) sees a of a prefix described by a Route Origin Authorization (ROA) sees a
problem, or an impending problem, with a certificate or CRL in the problem, or an impending problem, with a certificate or CRL in the
path between the ROA and a trust anchor. E.g., a certificate along path between the ROA and a trust anchor. E.g., a certificate along
that path has expired, is soon to expire, or a CRL associated with a that path has expired, is soon to expire, or a CRL associated with a
CA along the path is stale, thus placing the quality of the routing CA along the path is stale, thus placing the quality of the routing
of the address space described by the ROA in jeopardy. of the address space described by the ROA in jeopardy.
As the names in RPKI certificates are not meaningful to humans, see As the names in RPKI certificates are not meaningful to humans, see
[I-D.ietf-sidr-cp], there is no way to use a certificate itself to [I-D.ietf-sidr-cp], there is no way to use a certificate itself to
lead to the worrisome certificate's or CRL's maintainer. So, "Who lead to the worrisome certificate's or CRL's maintainer. So, "Who
you gonna call?" you gonna call?"
This document specifies the RPKI Ghostbusters Record, an object This document specifies the RPKI Ghostbusters Record, an object
verified via an End Entity (EE) certificate, issued under a CA verified via an End Entity (EE) certificate, issued under a CA
certificate, the maintainer of which may be contacted using the certificate, the maintainer of which may be contacted using the
payload information in the Ghostbusters Record. payload information in the Ghostbusters Record.
The Ghostbusters Record conforms to the syntax defined in The Ghostbusters Record conforms to the syntax defined in
[I-D.ietf-sidr-signed-object]. [I-D.ietf-sidr-signed-object]. The payload of this signed object is
a severely profiled vCard.
Note that the Ghostbusters Record is not an identity certificate, but Note that the Ghostbusters Record is not an identity certificate, but
rather an attestation to the contact data made by the maintainer of rather an attestation to the contact data made by the maintainer of
the CA certificate issuing the EE certificate whose corresponding the CA certificate issuing the EE certificate whose corresponding
private key signs the Ghostbusters Record. private key signs the Ghostbusters Record.
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.
Given a certificate, to find the closest Ghostbuster Record, go up
until a CA certificate is reached, which may be the object itself of
course. That CA certificate will have an SIA to the publication
point where all subsidiary objects (until you hit a down-chain CA
certificate's signed objects) are published. The publication point
will contain zero or more 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,
skipping to change at page 4, line 47 skipping to change at page 5, line 10
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 or role who is responsible for the CA certificate.
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, and END properties 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, zero or more of ADR, TEL, and
EMAIL MUST be included. Other properties 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
skipping to change at page 6, line 43 skipping to change at page 7, line 7
The IANA is requested to register the OID for the Ghostbusters Record The IANA is requested to register the OID for the Ghostbusters Record
in the registry created by [I-D.ietf-sidr-signed-object] as follows: in the registry created by [I-D.ietf-sidr-signed-object] as follows:
Name OID Specification Name OID Specification
----------------------------------------------------------- -----------------------------------------------------------
Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ] Ghostbusters 1.2.840.113549.1.9.16.1.35 [ This document ]
8.2. File Extension 8.2. File Extension
The IANA is requested to add an item for the Ghostbusters Record file Realizing the deep issues raised by [RFC5513], the IANA is requested
extension to the RPKI Repository Name Scheme created by to add an item for the Ghostbusters Record file extension to the RPKI
[I-D.ietf-sidr-repos-struct] as follows: Repository Name Scheme created by [I-D.ietf-sidr-repos-struct] as
follows:
Filename Extension RPKI Object Reference Filename Extension RPKI Object Reference
----------------------------------------------------------- -----------------------------------------------------------
.gbr Ghostbusters Record [ This document ] .gbr Ghostbusters Record [ This document ]
8.3. Media Type 8.3. Media Type
The IANA is requested to register the media type application/ The IANA is requested to register the media type application/
rpki-ghostbusters as follows rpki-ghostbusters as follows
skipping to change at page 7, line 21 skipping to change at page 7, line 32
Subtype name: rpki-ghostbusters Subtype name: rpki-ghostbusters
Required parameters: None Required parameters: None
Optional parameters: None Optional parameters: None
Encoding considerations: binary Encoding considerations: binary
Security considerations: Carries an RPKI Ghostbusters Record Security considerations: Carries an RPKI Ghostbusters Record
[this document]. [this document].
Interoperability considerations: None Interoperability considerations: None
Published specification: This document. Published specification: This document.
Applications that use this media type: RPKI administrators. Applications that use this media type: RPKI administrators.
Additional information: Additional information:
Content: This media type is a signed object, as defined
in [I-D.ietf-sidr-signed-object], which contains a payload
of a profiled vCard as defined above in this document.
Magic number(s): None Magic number(s): None
File extension(s): .gbr File extension(s): .gbr
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
Restrictions on usage: None Restrictions on usage: None
Author: Randy Bush <randy@psg.com> Author: Randy Bush <randy@psg.com>
Change controller: Randy Bush <randy@psg.com> Change controller: Randy Bush <randy@psg.com>
skipping to change at page 8, line 27 skipping to change at page 8, line 42
[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",
draft-ietf-sidr-cp-17 (work in progress), April 2011. draft-ietf-sidr-cp-17 (work in progress), April 2011.
[RFC5513] Farrel, A., "IANA Considerations for Three Letter
Acronyms", RFC 5513, April 1 2009.
Author's Address Author's Address
Randy Bush Randy Bush
Internet Initiative Japan Internet Initiative Japan
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, Washington 98110 Bainbridge Island, Washington 98110
US US
Phone: +1 206 780 0431 x1 Phone: +1 206 780 0431 x1
Email: randy@psg.com Email: randy@psg.com
 End of changes. 14 change blocks. 
15 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/