draft-ietf-tls-padding-01.txt   draft-ietf-tls-padding-02.txt 
Network Working Group A. Langley Network Working Group A. Langley
Internet-Draft Google Inc Internet-Draft Google Inc
Expires: August 21, 2015 February 17, 2015 Intended status: Standards Track August 24, 2015
Expires: February 25, 2016
A TLS ClientHello padding extension A TLS ClientHello padding extension
draft-ietf-tls-padding-01 draft-ietf-tls-padding-02
Abstract Abstract
This memo describes a TLS extension that can be used to pad This memo describes a TLS extension that can be used to pad
ClientHello messages to a desired size. ClientHello messages to a desired size.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 30 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on August 21, 2015. This Internet-Draft will expire on February 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 45 skipping to change at page 2, line 45
3. Padding Extension 3. Padding Extension
A new extension type ("padding(21)") is defined and MAY be included A new extension type ("padding(21)") is defined and MAY be included
by the client in its ClientHello message. by the client in its ClientHello message.
enum { enum {
padding(21), (65535) padding(21), (65535)
} ExtensionType; } ExtensionType;
The "extension_data" for the extension consists of an arbitary number The "extension_data" for the extension consists of an arbitrary
of zero bytes. For example, the smallest "padding" extension is four number of zero bytes. For example, the smallest "padding" extension
bytes long and is encoded as 0x00 0x15 0x00 0x00. A ten byte is four bytes long and is encoded as 0x00 0x15 0x00 0x00. A ten byte
extension would include 6 bytes of "extension_data" and would be extension would include 6 bytes of "extension_data" and would be
encoded as: encoded as:
00 15 00 06 00 00 00 00 00 00 00 15 00 06 00 00 00 00 00 00
|---| |---| |---------------| |---| |---| |---------------|
| | | | | |
| | \- extension_data: 6 zero bytes | | \- extension_data: 6 zero bytes
| | | |
| \------------- 16-bit, extension_data length | \------------- 16-bit, extension_data length
| |
skipping to change at page 4, line 18 skipping to change at page 4, line 18
padding extension in its ExtensionType registry. padding extension in its ExtensionType registry.
7. Acknowledgements 7. Acknowledgements
The author gratefully acknowledges the contributions of Wan-Teh Chang The author gratefully acknowledges the contributions of Wan-Teh Chang
and the suggestions of Eric Rescorla. and the suggestions of Eric Rescorla.
8. Normative References 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>.
Author's Address Author's Address
Adam Langley Adam Langley
Google Inc Google Inc
Email: agl@google.com Email: agl@google.com
 End of changes. 6 change blocks. 
8 lines changed or deleted 13 lines changed or added

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