INTERNET-DRAFT P. Yee
Intended Status: Proposed Standard AKAYLA
Updates: 5280 (if approved) August 16, 2012
Expires: February 17, 2013
Updates to the Internet X.509 Public Key InfrastructureCertificate and Certificate Revocation List (CRL) Profile<draft-ietf-pkix-rfc5280-clarifications-08.txt>
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2012 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Yee Expires February 17, 2013 [Page 1]

INTERNET-DRAFT RFC 5280 Clarifications August 16, 2012
as providing guidance in that regard.
The Section 7.3 rules for ASCII encoding of Internationalized Domain
Names (IDN) as Distinguished Names are aligned with the rules in
Section 7.2 which govern IDN encoding as GeneralNames.
In light of some observed attacks, the Security Considerations now
give added depth to the consequences of CA key compromise. This
section additionally notes that collision resistance is not a
required property of one-way hash functions when used to generate key
identifiers.
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Update to RFC 5280, Section 3.2: Certification Paths and Trust
Add the following paragraph to the end of RFC 5280, Section 3.2:
| Consistent with Section 3.4.61 of X.509 (11/2008) [X.509] we note
| that use of self-issued certificates and self-signed certificates
| issued by other than CAs are outside the scope of this specification.
| Thus, for example, a web server or client might generate a self-
| signed certificate to identify itself. These certificates, and how a
| relying party uses them to authenticate asserted identities, are
| both outside the scope of RFC 5280.
3. Update to RFC 5280, Section 4.2.1.4: Certificate PoliciesRFC 5280, Section 4.2.1.4, the tenth paragraph says:
| An explicitText field includes the textual statement directly in
| the certificate. The explicitText field is a string with a
| maximum size of 200 characters. Conforming CAs SHOULD use the
| UTF8String encoding for explicitText, but MAY use IA5String.
| Conforming CAs MUST NOT encode explicitText as VisibleString or
| BMPString. The explicitText string SHOULD NOT include any control
| characters (e.g., U+0000 to U+001F and U+007F to U+009F). When
| the UTF8String encoding is used, all character sequences SHOULD be
| normalized according to Unicode normalization form C (NFC) [NFC].
This paragraph is replaced with:
| An explicitText field includes the textual statement directly in
| the certificate. The explicitText field is a string with a
Yee Expires February 17, 2013 [Page 3]

INTERNET-DRAFT RFC 5280 Clarifications August 16, 2012
| maximum size of 200 characters. Conforming CAs SHOULD use the
| UTF8String encoding for explicitText, but MAY use VisibleString or
| BMPString. Conforming CAs MUST NOT encode explicitText as
| IA5String. The explicitText string SHOULD NOT include any control
| characters (e.g., U+0000 to U+001F and U+007F to U+009F). When
| the UTF8String or BMPString encoding is used, all character
| sequences SHOULD be normalized according to Unicode normalization
| form C (NFC) [NFC].
4. Update to RFC 5280, Section 6.2: Using the Path Validation AlgorithmRFC 5280, Section 6.2, the third paragraph says:
| Where a CA distributes self-signed certificates to specify trust
| anchor information, certificate extensions can be used to specify
| recommended inputs to path validation. For example, a policy
| constraints extension could be included in the self-signed
| certificate to indicate that paths beginning with this trust anchor
| should be trusted only for the specified policies. Similarly, a name
| constraints extension could be included to indicate that paths
| beginning with this trust anchor should be trusted only for the
| specified name spaces. The path validation algorithm presented in
| Section 6.1 does not assume that trust anchor information is provided
| in self-signed certificates and does not specify processing rules for
| additional information included in such certificates.
| Implementations that use self-signed certificates to specify trust
| anchor information are free to process or ignore such information.
This paragraph is replaced with:
| Where a CA distributes self-signed certificates to specify trust
| anchor information, certificate extensions can be used to specify
| recommended inputs to path validation. For example, a policy
| constraints extension could be included in the self-signed
| certificate to indicate that paths beginning with this trust anchor
| should be trusted only for the specified policies. Similarly, a name
| constraints extension could be included to indicate that paths
| beginning with this trust anchor should be trusted only for the
| specified name spaces. The path validation algorithm presented
| in Section 6.1 does not assume that trust anchor information is
| provided in self-signed certificates and does not specify processing
| rules for additional information included in such certificates.
| However, [RFC5914] defines several formats for representing trust
| anchor information, including self-signed certificates, and [RFC5937]
| provides an example of how such information may be used to initialize
| the path validation inputs. Implementations are free to make use of
| any additional information that is included in a trust anchor
| representation, or to ignore such information.
Yee Expires February 17, 2013 [Page 4]

INTERNET-DRAFT RFC 5280 Clarifications August 16, 20125. Update to RFC 5280, Section 7.3: Internationalized Domain Names in Distinguished NamesRFC 5280, Section 7.3, the first paragraph says:
| Domain Names may also be represented as distinguished names using
| domain components in the subject field, the issuer field, the
| subjectAltName extension, or the issuerAltName extension. As with
| the dNSName in the GeneralName type, the value of this attribute is
| defined as an IA5String. Each domainComponent attribute represents a
| single label. To represent a label from an IDN in the distinguished
| name, the implementation MUST perform the "ToASCII" label conversion
| specified in Section 4.1 of RFC 3490. The label SHALL be considered
| a "stored string". That is, the AllowUnassigned flag SHALL NOT be
| set.
This paragraph is replaced with:
| Domain Names may also be represented as distinguished names using
| domain components in the subject field, the issuer field, the
| subjectAltName extension, or the issuerAltName extension. As with
| the dNSName in the GeneralName type, the value of this attribute is
| defined as an IA5String. Each domainComponent attribute represents a
| single label. To represent a label from an IDN in the distinguished
| name, the implementation MUST perform the "ToASCII" label conversion
| specified in Section 4.1 of RFC 3490 with the UseSTD3ASCIIRules flag
| set. The label SHALL be considered a "stored string". That is, the
| AllowUnassigned flag SHALL NOT be set. The conversion process is the
| same as is performed in step 4 in Section 7.2.
6. Security Considerations
This document modifies the Security Considerations section of RFC5280 as follows. The fifth paragraph of the Security Considerations
section of RFC 5280 says:
| The protection afforded private keys is a critical security factor.
| On a small scale, failure of users to protect their private keys will
| permit an attacker to masquerade as them or decrypt their personal
| information. On a larger scale, compromise of a CA's private signing
| key may have a catastrophic effect. If an attacker obtains the
| private key unnoticed, the attacker may issue bogus certificates and
| CRLs. Existence of bogus certificates and CRLs will undermine
| confidence in the system. If such a compromise is detected, all
| certificates issued to the compromised CA MUST be revoked, preventing
| services between its users and users of other CAs. Rebuilding after
| such a compromise will be problematic, so CAs are advised to
| implement a combination of strong technical measures (e.g., tamper-
Yee Expires February 17, 2013 [Page 5]

INTERNET-DRAFT RFC 5280 Clarifications August 16, 2012
| resistant cryptographic modules) and appropriate management
| procedures (e.g., separation of duties) to avoid such an incident.
This paragraph is replaced with:
| The protection afforded private keys is a critical security factor.
| On a small scale, failure of users to protect their private keys will
| permit an attacker to masquerade as them or decrypt their personal
| information. On a larger scale, compromise of a CA's private signing
| key may have a catastrophic effect.
|
| If an attacker obtains the private key of a CA unnoticed, the
| attacker may issue bogus certificates and CRLs. Even if an attacker
| is unable to obtain a copy of a CA's private key, the attacker may be
| able to issue bogus certificates and CRLs by making unauthorized use
| of the CA's workstation or of an RA's workstation. Such an attack
| may be the result of an attacker obtaining unauthorized access to the
| workstation, either locally or remotely, or may be the result of
| inappropriate activity by an insider. Existence of bogus
| certificates and CRLs will undermine confidence in the system. Among
| many other possible attacks, the attacker may issue bogus
| certificates that have the same subject names as legitimate
| certificates in order impersonate legitimate certificate subjects.
| This could include bogus CA certificates in which the subject names
| in the bogus certificates match the names under which legitimate CAs
| issue certificates and CRLs. This would allow the attacker to issue
| bogus certificates and CRLs that have the same issuer names, and
| possibly the same serial numbers, as certificates and CRLs issued by
| legitimate CAs.
The following text is added to the end of the Security Considerations
section of 5280:
One-way hash functions are commonly used to generate key identifier
values (AKI and SKI), e.g., as described in Sections 4.1.1 and 4.1.2.
However, none of the security properties of such functions are required
for this context.
7. IANA Considerations
This document has no actions for IANA.
Yee Expires February 17, 2013 [Page 6]