draft-ietf-sidr-policy-qualifiers-02.txt   rfc7318.txt 
Network Working Group A. Newton Internet Engineering Task Force (IETF) A. Newton
Internet-Draft ARIN Request for Comments: 7318 ARIN
Updates: 6487 (if approved) G. Huston Updates: 6487 G. Huston
Intended status: Standards Track APNIC Category: Standards Track APNIC
Expires: January 4, 2015 July 3, 2014 ISSN: 2070-1721 July 2014
Policy Qualifiers in RPKI Certificates Policy Qualifiers in Resource Public Key Infrastructure (RPKI)
draft-ietf-sidr-policy-qualifiers-02 Certificates
Abstract Abstract
This document updates RFC 6487 by clarifying the inclusion of policy This document updates RFC 6487 by clarifying the inclusion of policy
qualifiers in the certificate policies extension of RPKI resource qualifiers in the certificate policies extension of Resource Public
certificates. Key Infrastructure (RPKI) resource certificates.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on January 4, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7318.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Update to RFC 6487 . . . . . . . . . . . . . . . . . . . . . 2 2. Update to RFC 6487 . . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 5. Normative References . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Terminology 1. Introduction
This document introduces policy qualifiers in the certificate
policies extension of the RPKI resource certificates. This document
updates [RFC6487].
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].
2. Update to RFC 6487 2. Update to RFC 6487
[RFC6487] profiles certificates, certificate revocation lists, and [RFC6487] profiles certificates, certificate revocation lists, and
certificate signing requests specified in [RFC5280] for use in certificate signing requests specified in [RFC5280] for use in
routing public key infrastructure. routing public key infrastructure.
[RFC5280] defines an extension to certificates for the listing of [RFC5280] defines an extension to certificates for the listing of
policy information (See section 4.2.1.4). [RFC6487] states in policy information (see Section 4.2.1.4). [RFC6487] states in
Section 4.8.9: "This extension MUST be present and MUST be marked Section 4.8.9: "This extension MUST be present and MUST be marked
critical. It MUST include exactly one policy, as specified in the critical. It MUST include exactly one policy, as specified in the
RPKI CP [RFC6484]". This references the CertPolicyId of the sequence RPKI CP [RFC6484]". This references the CertPolicyId of the sequence
allowed in PolicyInformation as defined by [RFC5280]. allowed in PolicyInformation as defined by [RFC5280].
[RFC5280] also specifies that PolicyInformation may optionally have a [RFC5280] also specifies that PolicyInformation may optionally have a
sequence of PolicyQualifierInfo objects. [RFC6487] does not sequence of PolicyQualifierInfo objects. [RFC6487] does not
specifically allow or disallow these PolicyQualifierInfo objects specifically allow or disallow these PolicyQualifierInfo objects,
although it also states in section 4: "Unless specifically noted as although Section 4 also states: "Unless specifically noted as being
being OPTIONAL, all the fields listed here MUST be present, and any OPTIONAL, all the fields listed here MUST be present, and any other
other fields MUST NOT appear in a conforming resource certificate." fields MUST NOT appear in a conforming resource certificate."
Because there is a need for some RPKI Certificate Authorities to Because there is a need for some RPKI Certificate Authorities to
include policy qualifiers in their certificates, this document include policy qualifiers in their certificates, this document
updates [RFC6487], Section 4.8.9, as follows: updates Section 4.8.9 of [RFC6487] as follows:
OLD: OLD:
This extension MUST be present and MUST be marked critical. It This extension MUST be present and MUST be marked critical. It
MUST include exactly one policy, as specified in the RPKI MUST include exactly one policy, as specified in the RPKI
Certificate Policy (CP) [RFC6484]. Certificate Policy (CP) [RFC6484].
NEW: NEW:
This extension MUST be present and MUST be marked critical. It This extension MUST be present and MUST be marked critical. It
MUST include exactly one policy, as specified in the RPKI CP MUST include exactly one policy, as specified in the RPKI CP
[RFC6484]. Exactly one policy qualifier MAY be included. If a [RFC6484]. Exactly one policy qualifier MAY be included. If a
policy qualifier is included, the policyQualifierId MUST be the policy qualifier is included, the policyQualifierId MUST be the
Certification Practice Statement (CPS) pointer qualifier type Certification Practice Statement (CPS) pointer qualifier type
(id-qt-cps). (id-qt-cps).
As noted in [RFC5280], section 4.2.1.4: "Optional qualifiers, which As noted in [RFC5280], Section 4.2.1.4: "Optional qualifiers, which
MAY be present, are not expected to change the definition of the MAY be present, are not expected to change the definition of the
policy." In this case any optional policy qualifier that MAY be policy." In this case, any optional policy qualifier that MAY be
present in a resource certificate MUST NOT change the definition of present in a resource certificate MUST NOT change the definition of
the RPKI CP [RFC6484]. the RPKI CP [RFC6484].
3. IANA Considerations 3. Security Considerations
None.
4. Security Considerations
The Security Considerations of [RFC6487] apply to this document. The Security Considerations of [RFC6487] apply to this document.
This document updates the RPKI certificate profile to specify that This document updates the RPKI certificate profile to specify that
the certificate policies extension can include a policy qualifier, the certificate policies extension can include a policy qualifier,
which is a URI. While de-referencing the URI is not required for which is a URI. While dereferencing the URI is not required for
certificate validation, doing so could provide a denial-of-service certificate validation, doing so could provide a denial-of-service
(DoS) vector, where the target host may be subjected to bogus work (DoS) vector, where the target host may be subjected to bogus work
de-referencing the URI. However, this specification, like [RFC5280], dereferencing the URI. However, this specification, like [RFC5280],
places no processing requirements on the URI included in the places no processing requirements on the URI included in the
qualifier. qualifier.
As an update to [RFC6487], this document broadens the class of As an update to [RFC6487], this document broadens the class of
certificates that conform to the RPKI profile by explicitly including certificates that conform to the RPKI profile by explicitly including
within the profile those certificates that contain a policy qualifier within the profile those certificates that contain a policy qualifier
as described here. A relying party that performs a strict validation as described here. A relying party that performs a strict validation
based on [RFC6487] and fails to support the updates described in this based on [RFC6487] and fails to support the updates described in this
document, would incorrectly invalidate RPKI objects that include the document would incorrectly invalidate RPKI objects that include the
changes in Section 2. changes in Section 2.
5. Acknowledgments 4. Acknowledgments
Frank Hill and Adam Guyot helped define the scope of this issue and Frank Hill and Adam Guyot helped define the scope of the issue
identified and worked with RPKI validator implementers to clarify the covered by this document and identified and worked with RPKI
use of policy qualifiers in resource certificates. validator implementers to clarify the use of policy qualifiers in
resource certificates.
Sean Turner provided significant text to this document regarding the Sean Turner provided significant text to this document regarding the
processing of the CPS URI and limiting the scope of the allowable processing of the CPS URI and limiting the scope of the allowable
content of the policy qualifier. content of the policy qualifier.
6. Normative References 5. Normative References
[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.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, May 2008. (CRL) Profile", RFC 5280, May 2008.
[RFC6484] Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate [RFC6484] Kent, S., Kong, D., Seo, K., and R. Watro, "Certificate
skipping to change at page 4, line 31 skipping to change at page 5, line 13
2012. 2012.
Authors' Addresses Authors' Addresses
Andrew Lee Newton Andrew Lee Newton
American Registry for Internet Numbers American Registry for Internet Numbers
3635 Concorde Parkway 3635 Concorde Parkway
Chantilly, VA 20151 Chantilly, VA 20151
USA USA
Email: andy@arin.net EMail: andy@arin.net
URI: http://www.arin.net URI: http://www.arin.net
Geoff Huston Geoff Huston
Asia Pacific Network Information Center Asia Pacific Network Information Center
6 Cordelia Street 6 Cordelia Street
South Brisbane QLD 4101 South Brisbane QLD 4101
Australia Australia
Email: gih@apnic.net EMail: gih@apnic.net
URI: http://www.apnic.net URI: http://www.apnic.net
 End of changes. 23 change blocks. 
52 lines changed or deleted 47 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/