ESSCertIDv2 Update for RFC 3161
RFC 5816
| Document | Type |
RFC - Proposed Standard
(April 2010; No errata)
Updates RFC 3161
|
|
|---|---|---|---|
| Authors | Stefan Santesson , Nick Pope | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5816 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Tim Polk | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) S. Santesson
Request for Comments: 5816 3xA Security
Updates: 3161 N. Pope
Category: Standards Track Thales
ISSN: 2070-1721 March 2010
ESSCertIDv2 Update for RFC 3161
Abstract
This document updates RFC 3161. It allows the use of ESSCertIDv2, as
defined in RFC 5035, to specify the hash of a signer certificate when
the hash is calculated with a function other than the Secure Hash
Algorithm (SHA-1).
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
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/rfc5816.
Copyright Notice
Copyright (c) 2010 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.
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
Santesson & Pope Standards Track [Page 1]
RFC 5816 ESSCertIDv2 Update for RFC 3161 March 2010
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.
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................2
2. Updates to RFC 3161 .............................................3
2.1. Changes to Section 2.4.1, Request Format ...................3
2.2. Changes to Section 2.4.2, Response Format ..................3
2.2.1. Signature of Time-Stamp Token .......................3
2.2.2. Verifying the Time-Stamp Token ......................4
3. Security Considerations .........................................4
4. References ......................................................5
4.1. Normative References .......................................5
4.2. Informative References .....................................5
1. Introduction
The time-stamping protocol defined in RFC 3161 [RFC3161] requires
that the Cryptographic Message Syntax (CMS) SignedData [RFC5652],
used to apply a digital signature on the time-stamp token, include a
signed attribute that identifies the signer's certificate.
This identifier only allows SHA-1 [SHA1] to be used as the hash
algorithm to generate the identifier value.
The mechanism used in [RFC3161] employed ESSCertID from RFC 2634
[ESS]. RFC 5035 [ESSV2] updated ESSCertID with ESSCertIDv2 to allow
the use of any hash algorithm.
The changes to RFC 3161 [RFC3161] defined in this document allow
ESSCertIDv2 to be used to include an identifier of the signing
certificate as defined in RFC 5035 [ESSV2].
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].
Santesson & Pope Standards Track [Page 2]
RFC 5816 ESSCertIDv2 Update for RFC 3161 March 2010
2. Updates to RFC 3161
2.1. Changes to Section 2.4.1, Request Format
Last paragraph on Page 5.
Old:
If the certReq field is present and set to true, the TSA's public
key certificate that is referenced by the ESSCertID identifier
Show full document text