< draft-ietf-pkix-rfc4055-update-01.txt   draft-ietf-pkix-rfc4055-update-02.txt >
PKIX WG Sean Turner, IECA IETF PKIX WG Sean Turner, IECA
Internet Draft Daniel Brown, Certicom Internet Draft Daniel Brown, Certicom
Intended Status: Standard Track Kelvin Yiu, Microsoft Intended Status: Standard Track Kelvin Yiu, Microsoft
Updates: 4055 (once approved) Russ Housley, Vigil Security Updates: 4055 (once approved) Russ Housley, Vigil Security
Expires: November 1, 2008 Tim Polk, NIST Expires: September 9, 2009 Tim Polk, NIST
May 1, 2008 March 9, 2009
Update for RSAES-OAEP Algorithm Parameters Update for RSAES-OAEP Algorithm Parameters
draft-ietf-pkix-rfc4055-update-01.txt draft-ietf-pkix-rfc4055-update-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on November 1, 2008. This Internet-Draft will expire on September 9, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract Abstract
This document updates RFC 4055. It updates the conventions for using This document updates RFC 4055. It updates the conventions for using
the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding
(RSAES-OAEP) key transport algorithm with the Public-Key Cryptography (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key
Standards (PKCS) #1 version 1.5 signature algorithm in the Internet Infrastructure (PKI). Specifically, it updates the conventions for
X.509 Public Key Infrastructure (PKI). Specifically, it updates the algorithm parameters in an X.509 certificate's subjectPublicKeyInfo
conventions for algorithm parameters in an X.509 certificate's field.
subjectPublicKeyInfo field.
Conventions used in this document Conventions used in this document
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].
Discussion Discussion
This draft is being discussed on the 'ietf-pkix' mailing list. To This draft is being discussed on the 'ietf-pkix' mailing list. To
subscribe, send a message to ietf-pkix-request@imc.org with the subscribe, send a message to ietf-pkix-request@imc.org with the
single word subscribe in the body of the message. There is a Web site single word subscribe in the body of the message. There is a Web site
for the mailing list at <http://www.imc.org/ietf-pkix/>. for the mailing list at <http://www.imc.org/ietf-pkix/>.
1. Introduction 1. Introduction
RFC 4055 specifies conventions for using the RSA Encryption Scheme - RFC 4055 specifies conventions for using the RSA Encryption Scheme -
Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport
algorithm with the Public-Key Cryptography Standards (PKCS) #1 algorithm in the Internet X.509 Public Key Infrastructure (PKI). It
version 1.5 signature algorithm in the Internet X.509 Public Key provides algorithm identifiers and parameters for RSAES-OAEP.
Infrastructure (PKI). It provides algorithm identifiers and
parameters for RSAES-OAEP.
This document updates the conventions for RSAES-OAEP parameters in This document updates the conventions for RSAES-OAEP parameters in
the subjectPublicKeyInfo field of an X.509 certificate. The PKIX WG the subjectPublicKeyInfo field of an X.509 certificate. The PKIX WG
Elliptic Curve Cryptography (ECC) design team recommended that Key Elliptic Curve Cryptography (ECC) design team recommended that Key
Derivation Functions (KDFs) should not be constrained within a Derivation Functions (KDFs) should not be constrained within a
certificate; rather, KDF constraints should be negotiated in certificate; rather, KDF constraints should be negotiated in
protocols that need to employ certificates. protocols that need to employ certificates.
Only two paragraphs in [RFC4055] discuss RSAES-OAEP parameters in Only two paragraphs in [RFC4055] discuss RSAES-OAEP parameters in
X.509 certificates: the second paragraph of section 4 and the first X.509 certificates: the second paragraph of section 4 and the first
skipping to change at page 3, line 5 skipping to change at page 3, line 14
paragraphs. Section 3 updates the second paragraph in section 4 paragraphs. Section 3 updates the second paragraph in section 4
while section 3 updates the second paragraph in section 4.1. "Old:" while section 3 updates the second paragraph in section 4.1. "Old:"
prefaces the text to be replaced and "New:" prefaces the replacement prefaces the text to be replaced and "New:" prefaces the replacement
text. text.
This document also replaces incorrect references to the This document also replaces incorrect references to the
publicKeyAlgorithms field in Section 3 with references to the publicKeyAlgorithms field in Section 3 with references to the
parameters field in the subjectPublicKeyInfo algorithm field. No parameters field in the subjectPublicKeyInfo algorithm field. No
other changes are made to the RSASSA-PSS sections. other changes are made to the RSASSA-PSS sections.
2. Changes to Section 3 2nd Paragraph 2. Changes to Section 3 2nd and 3rd Paragraph
This change clarifies the placement of RSASSA-PSS-params in the
signature, signatureAlgorithm, and subjectPublicKeyInfo fields for CA
and EE certificates. It also clarifies the placement of RSASSA-PSS-
params in the signatureAlgorithm field in CRLs.
Old: Old:
CAs that issue certificates with the id-RSASSA-PSS algorithm CAs that issue certificates with the id-RSASSA-PSS algorithm
identifier SHOULD require the presence of parameters in the identifier SHOULD require the presence of parameters in the
publicKeyAlgorithms field if the cA boolean flag is set in the basic publicKeyAlgorithms field if the cA boolean flag is set in the basic
constraints certificate extension. CAs MAY require that the constraints certificate extension. CAs MAY require that the
parameters be present in the publicKeyAlgorithms field for end-entity parameters be present in the publicKeyAlgorithms field for end-entity
certificates. certificates.
CAs that use the RSASSA-PSS algorithm for signing certificates SHOULD
include RSASSA-PSS-params in the subjectPublicKeyInfo algorithm
parameters in their own certificates. CAs that use the RSASSA-PSS
algorithm for signing certificates or CRLs MUST include RSASSA-PSS-
params in the signatureAlgorithm parameters in the TBSCertificate or
TBSCertList structures.
New: New:
CAs that issue certificates with the id-RSASSA-PSS algorithm When the id-RSASSA-PSS object identifier appears in the
identifier SHOULD require the presence of parameters in the TBSCertificate or TBSCertList signature algorithm field, then the
subjectPublicKeyInfo algorithm field if the cA boolean flag is set in RSASSA-PSS-params structure MUST be included in the TBSCertificate or
the basic constraints certificate extension. CAs MAY require that TBSCertList signature parameters field.
the parameters be present in the subjectPublicKeyInfo algorithm field
for end-entity certificates. When the id-RSASSA-PSS object identifier appears in the
TBSCertificate subjectPublicKeyInfo algorithm field of CA
certificates, then the parameters field SHOULD include the RSASSA-
PSS-params structure. When the id-RSASSA-PSS object identifier
appears in the TBSCertificate subjectPublicKeyInfo algorithm field of
EE certificates, then the parameters field MAY include the RSASSA-
PSS-params structure.
All certificates and CRLs signed by a CA that supports the id-RSASSA-
PSS algorithm MUST include the RSASSA-PSS-params in the
signatureAlgorithm parameters in Certificate and CertList structures,
respectively.
3. Changes to Section 4 2nd Paragraph 3. Changes to Section 4 2nd Paragraph
This change prohibits the inclusion of RSAES-OAEP-params in the
subjectPublicKeyInfo field. This was done because a) it does not
affect interoperability b) aligns with PKIX practice to not include
limitations on how the public key can be used in
subjectPublicKeyInfo. A poll of implementers was taken and there
were no objections to this change as it did not affect current
implmentations.
Old: Old:
CAs that issue certificates with the id-RSAES-OAEP algorithm CAs that issue certificates with the id-RSAES-OAEP algorithm
identifier SHOULD require the presence of parameters in the identifier SHOULD require the presence of parameters in the
publicKeyAlgorithms field for all certificates. Entities that use a publicKeyAlgorithms field for all certificates. Entities that use a
certificate with a publicKeyAlgorithm value of id-RSA-OAEP where the certificate with a publicKeyAlgorithm value of id-RSA-OAEP where the
parameters are absent SHOULD use the default set of parameters for parameters are absent SHOULD use the default set of parameters for
RSAES-OAEP-params. Entities that use a certificate with a RSAES-OAEP-params. Entities that use a certificate with a
publicKeyAlgorithm value of rsaEncryption SHOULD use the default set publicKeyAlgorithm value of rsaEncryption SHOULD use the default set
of parameters for RSAES-OAEP-params. of parameters for RSAES-OAEP-params.
New: New:
CAs that issue certificates with the id-RSAES-OAEP algorithm CAs that issue certificates with the id-RSAES-OAEP algorithm
identifier MUST NOT include parameters in the subjectPublicKeyInfo identifier MUST NOT include parameters in the subjectPublicKeyInfo
algorithm field. algorithm field.
4. Changes to Section 4.1 1st Paragraph 4. Changes to Section 4.1 1st Paragraph
This change prohibits the inclusion of parameters in the
subjectPublicKeyInfo field. This was done because a) it does not
affect interoperability b) aligns with PKIX practice to not include
limitations on how the public key can be used in
subjectPublicKeyInfo. A poll of implementers was taken and there
were no objections to this change as it did not affect current
implmentations.
Old: Old:
When id-RSAES-OAEP is used in an AlgorithmIdentifier, the parameters When id-RSAES-OAEP is used in an AlgorithmIdentifier, the parameters
MUST employ the RSAES-OAEP-params syntax. The parameters may be MUST employ the RSAES-OAEP-params syntax. The parameters may be
either absent or present when used as subject public key information. either absent or present when used as subject public key information.
The parameters MUST be present when used in the algorithm identifier The parameters MUST be present when used in the algorithm identifier
associated with an encrypted value. associated with an encrypted value.
New: New:
When id-RSAES-OAEP is used in an AlgorithmIdentifier, the parameters When id-RSAES-OAEP is used in an AlgorithmIdentifier, the parameters
MUST employ the RSAES-OAEP-params syntax. The parameters MUST be MUST employ the RSAES-OAEP-params syntax. The parameters MUST be
absent when used in the subjectPublicKeyInfo field. The parameters absent when used in the subjectPublicKeyInfo field. The parameters
MUST be present when used in the algorithm identifier associated with MUST be present when used in the algorithm identifier associated with
an encrypted value. an encrypted value.
5. Security Considerations 5. Security Considerations
The security considerations from [RFC4055] apply. No new security The security considerations from [RFC4055] apply.
considerations are introduced.
If the RSAES-OAEP-params are negotiated, then the negotiation
mechanism needs to provide integrity for these parameters. For
example, an S/MIME Agent can advertise their capabilities in the
SMIMECapabilities attribute, which is either signed attribute
[RFC3851bis] or a certificate extension [RFC4262].
6. IANA Considerations 6. IANA Considerations
None None
{{Please remove this section prior to publication as an RFC.}} {{Please remove this section prior to publication as an RFC.}}
7. References 7. References
7.1. Normative References 7.1. Normative References
skipping to change at page 4, line 42 skipping to change at page 6, line 7
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional [RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional
Algorithms and Identifiers for RSA Cryptography for Algorithms and Identifiers for RSA Cryptography for
use in the Internet X.509 Public Key Infrastructure use in the Internet X.509 Public Key Infrastructure
Certificate and Certificate Revocation List (CRL) Certificate and Certificate Revocation List (CRL)
Profile", RFC 4055, June 2005. Profile", RFC 4055, June 2005.
7.2. Informative References 7.2. Informative References
None [RFC4262] S. Santesson, "X.509 Certificate Extension for
Secure/Multipurpose Internet Mail Extensions (S/MIME)
Capabilities", RFC 4262, December 2005.
[RFC3851bis] Turner, S., Farrell, S., and R. Housley, "An Internet
Attribute Certificate Profile for Authorization",
draft-ietf-pkix-3281update-04.txt, work-in-progress.
/*** RFC EDITOR: Please replace RFC3851bis with RFCXYAZ when draft-
ietf-pkix-3281update is published.
Author's Addresses Author's Addresses
Sean Turner Sean Turner
IECA, Inc. IECA, Inc.
3057 Nutley Street, Suite 106 3057 Nutley Street, Suite 106
Fairfax, VA 22031 Fairfax, VA 22031
USA USA
skipping to change at page 6, line 4 skipping to change at line 291
EMail: housley@vigilsec.com EMail: housley@vigilsec.com
Tim Polk Tim Polk
NIST NIST
Building 820, Room 426 Building 820, Room 426
Gaithersburg, MD 20899 Gaithersburg, MD 20899
USA USA
EMail: wpolk@nist.gov EMail: wpolk@nist.gov
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 16 change blocks. 
29 lines changed or deleted 96 lines changed or added

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