draft-ietf-tls-cached-info-02.txt   draft-ietf-tls-cached-info-03.txt 
INTERNET-DRAFT S. Santesson (3xA Security) INTERNET-DRAFT S. Santesson (3xA Security)
Intended Status: Proposed Standard Intended Status: Proposed Standard
Expires: March 19, 2010 September 15, 2009 Expires: August 22, 2010 February 18, 2010
Transport Layer Security (TLS) Cached Information Extension Transport Layer Security (TLS) Cached Information Extension
<draft-ietf-tls-cached-info-02.txt> <draft-ietf-tls-cached-info-03.txt>
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
Drafts. Internet-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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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
Copyright Notice Copyright and License Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. 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 BSD License.
Abstract Abstract
This document defines a Transport Layer Security (TLS) extension for This document defines a Transport Layer Security (TLS) extension for
cached information. This extension allows the TLS client to inform a cached information. This extension allows the TLS client to inform a
server of cached information from previous TLS sessions, allowing the server of cached information from previous TLS sessions, allowing the
server to omit sending cached static information to the client during server to omit sending cached static information to the client during
the TLS handshake protocol exchange. the TLS handshake protocol exchange.
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Cached Information Extension . . . . . . . . . . . . . . . . . . 3 2 Cached Information Extension . . . . . . . . . . . . . . . . . . 4
4 Message flow . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 Message flow . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5 Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5 Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
7 Normative References . . . . . . . . . . . . . . . . . . . . . . 5 7 Normative References . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Introduction 1 Introduction
TLS handshakes often include fairly static information such as server TLS handshakes often include fairly static information such as server
certificate and a list of trusted Certification Authorities (CAs). certificate and a list of trusted Certification Authorities (CAs).
Static information such as a server certificate can be of Static information such as a server certificate can be of
considerable size. This is the case in particular if the server considerable size. This is the case in particular if the server
certificate is bundled with a complete certificate path, including certificate is bundled with a complete certificate path, including
all intermediary certificates up to the trust anchor public key. all intermediary certificates up to the trust anchor public key.
skipping to change at page 3, line 34 skipping to change at page 4, line 34
HashAlgorithm hash; HashAlgorithm hash;
opaque hash_value<1..255>; opaque hash_value<1..255>;
} CachedInformationHash; } CachedInformationHash;
struct { struct {
CachedInformationType type; CachedInformationType type;
CachedInformationHash hashes<1..2^16-1>; CachedInformationHash hashes<1..2^16-1>;
} CachedObject; } CachedObject;
struct { struct {
CachedObject cached_info<1..2^24-1>;; CachedObject cached_info<1..2^16-1>;;
} CachedInformation; } CachedInformation;
Hash algorithm identifiers are provided by the RFC 5246 [RFC5246] Hash algorithm identifiers are provided by the RFC 5246 [RFC5246]
HashAlgorithm registry. Compliant implementations MUST support HashAlgorithm registry. Compliant implementations MUST support
sha1(2) as HashAlgorithm. sha1(2) as HashAlgorithm.
When CachedInformationType identifies certificate_chain, then When CachedInformationType identifies certificate_chain, then
hash_value MUST include at least one hash value calculated over the hash_value MUST include at least one hash value calculated over the
certificate_list element of a server side Certificate message. certificate_list element of a server side Certificate message.
 End of changes. 8 change blocks. 
18 lines changed or deleted 22 lines changed or added

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