idnits 2.17.1 draft-ietf-pkix-rfc3161-update-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([ESSV2], [RFC3161], [SHA1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3161, updated by this document, for RFC5378 checks: 1998-09-23) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 26, 2009) is 5289 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3852 (Obsoleted by RFC 5652) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF PKIX WG Stefan Santesson 3 Internet Draft (3xA Security) 4 Intended Status: Proposed Standard Nick Pope 5 Updates: 3161 (once approved) (Thales) 6 Expires: April 29, 2010 October 26, 2009 8 ESSCertIDv2 update for RFC 3161 9 draft-ietf-pkix-rfc3161-update-09 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.html 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 Copyright and License Notice 34 Copyright (c) 2009 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the BSD License. 47 Abstract 49 This document updates RFC 3161 [RFC3161]. It allows the use of 50 ESSCertIDv2 defined in RFC 5035 [ESSV2] to specify the hash of a 51 signer certificate when the hash is calculated with a function other 52 than SHA-1 [SHA1]. 54 Table of Contents 56 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 57 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2 Updates to RFC 3161 . . . . . . . . . . . . . . . . . . . . . . 3 59 2.1 Changes to section 2.4.1 Request Format . . . . . . . . . . 3 60 2.2 Changes to Section 2.4.2 Response Format . . . . . . . . . 4 61 2.2.1 signature of time stamp token . . . . . . . . . . . . 4 62 2.2.2 verifying the time stamp token . . . . . . . . . . . . 5 63 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 6 64 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 65 5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 5.1 Normative References . . . . . . . . . . . . . . . . . . . 7 67 5.2 Informative References . . . . . . . . . . . . . . . . . . 7 68 Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 70 1 Introduction 72 The time stamping protocol defined in RFC 3161 [RFC3161] requires 73 that the CMS SignedData [RFC3852], used to apply a digital signature 74 on the time-stamp token, include a signed attribute that identifies 75 the signer's certificate. 77 This identifier only allows SHA-1 to be used as hash algorithm to 78 generate the identifier value. 80 The mechanism used in [RFC3161] employed ESSCertID from RFC 2634 81 [ESS]. RFC 5035 [ESSV2] updated ESSCertID with ESSCertIDv2 to allow 82 the use of any hash algorithm. 84 The changes to RFC 3161 [RFC3161] defined in this document allows 85 ESSCertIDv2 to be used to include an identifier of the signing 86 certificate as defined in RFC 5035 [ESSV2]. 88 1.1 Terminology 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC 2119 [RFC2119]. 94 2 Updates to RFC 3161 96 2.1 Changes to section 2.4.1 Request Format 98 Last paragraph on page 5. 100 Old: 102 If the certReq field is present and set to true, the TSA's public 103 key certificate that is referenced by the ESSCertID identifier 104 inside a SigningCertificate attribute in the response MUST be 105 provided by the TSA in the certificates field from the SignedData 106 structure in that response. That field may also contain other 107 certificates. 109 New: 111 If the certReq field is present and set to true, the TSA's public 112 key certificate that is referenced by the ESSCertID [ESS] field 113 inside a SigningCertificate attribute or by the ESSCertIDv2 114 [ESSV2] field inside a SigningCertificateV2 attribute in the 115 response MUST be provided by the TSA in the certificates field 116 from the SignedData structure in that response. That field may 117 also contain other certificates. 119 2.2 Changes to Section 2.4.2 Response Format 121 2.2.1 signature of time stamp token 123 5th paragraph on page 8, just before the definition of TSTInfo. 125 Old: 127 The time-stamp token MUST NOT contain any signatures other than 128 the signature of the TSA. The certificate identifier (ESSCertID) 129 of the TSA certificate MUST be included as a signerInfo attribute 130 inside a SigningCertificate attribute. 132 New: 134 The time-stamp token MUST NOT contain any signatures other than 135 the signature of the TSA. The certificate identifier (either 136 ESSCertID [ESS] or ESSCertIDv2 [ESSV2]) of the TSA certificate 137 MUST be included as a signerInfo attribute inside a 138 SigningCertificate attribute. 140 Note: As mentioned in RFC 5035 [ESSV2], the SigningCertificateV2 141 attribute MUST be used if any algorithm other than SHA-1 is 142 used and SHOULD NOT be used for SHA-1. 144 Note: For backwards compatibility, in line with RFC 5035, both 145 ESSCertID and ESSCertIDv2 MAY be present. Systems MAY ignore 146 ESSCertIDv2 if RFC 5035 has not been implemented. 148 2.2.2 verifying the time stamp token 150 3rd paragraph on page 11. 152 Old: 154 The purpose of the tsa field is to give a hint in identifying the 155 name of the TSA. If present, it MUST correspond to one of the 156 subject names included in the certificate that is to be used to 157 verify the token. However, the actual identification of the 158 entity that signed the response will always occur through the use 159 of the certificate identifier (ESSCertID Attribute) inside a 160 SigningCertificate attribute which is part of the signerInfo (See 161 Section 5 of [ESS]). 163 New: 165 The purpose of the tsa field is to give a hint in identifying the 166 name of the TSA. If present, it MUST correspond to one of the 167 subject names included in the certificate that is to be used to 168 verify the token. However, the actual identification of the 169 entity that signed the response will always occur through the use 170 of the certificate identifier (ESSCertID inside a 171 SigningCertificate attribute or ESSCertIDv2 inside a 172 SigningCertificateV2 attribute) which is part of the signerInfo 173 (See Section 5 of [ESS] and Section 3 of [ESSV2]). 175 3 Security Considerations 177 This draft incorporates the security considerations of RFC 5035 178 [ESSV2] with further explanations in this section. 180 ESSCertID provides a means based on the SHA-1 hash algorithm for 181 identifying the certificate used to verify the signature on a time 182 stamp. The use of ESSCertIDv2 aims to enable implementers to comply 183 with policies that require phasing out all uses of the SHA-1 184 algorithm. 186 The update provided by this draft is motivated by reasons of 187 interoperability and migration to other hash algorithms rather than 188 mitigating new security issues. 190 4 IANA Considerations 192 This draft requires no actions by IANA. 194 5 References 196 5.1 Normative References 198 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 199 Requirement Levels", BCP 14, RFC 2119, March 1997. 201 [ESS] Hoffman, P., "Enhanced Security Services for S/MIME", RFC 202 2634, June 1999. 204 [ESSV2] Schaad, J., "Enhanced Security Services (ESS) Update: 205 Adding CertID Algorithm Agility", RFC 5035. August 2007. 207 [RFC3161] Adams, C., Cain, P., Pinkas, D. and Zuccherato, R. "Time- 208 Stamp Protocol (TSP)", RFC 3161. August 2001. 210 [RFC3852] R. Housley, "Cryptographic Message Syntax (CMS)", RFC 211 3852, July 2004. 213 5.2 Informative References 215 [SHA1] Secure Hash Standard. FIPS Pub 180-1. National Institute 216 of Standards and Technology. 17 April 1995. 218 Author's Addresses 220 Stefan Santesson 221 3xA Security AB 222 Sweden 224 Email: sts@aaa-sec.com 226 Nick Pope 227 Thales Information Systems Security 228 Long Crendon, Aylesbury 229 United Kingdom 231 Email: nick.pope@thales-esecurity.com