< draft-ietf-tls-padding-02.txt		draft-ietf-tls-padding-03.txt >
	Network Working Group A. Langley		Network Working Group A. Langley
	Internet-Draft Google Inc		Internet-Draft Google Inc
	Intended status: Standards Track August 24, 2015		Updates: 5246 (if approved) Sept 2015
	Expires: February 25, 2016		Intended status: Standards Track
			Expires: March 4, 2016
	A TLS ClientHello padding extension		A TLS ClientHello padding extension
	draft-ietf-tls-padding-02		draft-ietf-tls-padding-03
	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 31 ¶		skipping to change at page 1, line 32 ¶
	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 February 25, 2016.		This Internet-Draft will expire on March 4, 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 3, line 15 ¶		skipping to change at page 3, line 15 ¶
	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
	|		|
	\------------------- extension_type for padding extension		\------------------- extension_type for padding extension
	The client MUST fill the padding extension completely with zero		The client MUST fill the padding extension completely with zero
	bytes, although the padding extension may be empty.		bytes, although the padding extension_data field may be empty.
	The server MUST NOT echo the extension.		The server MUST NOT echo the extension.
	4. Example usage		4. Example usage
	As an example, consider a client that wishes to avoid sending a		As an example, consider a client that wishes to avoid sending a
	ClientHello with a record size between 256 and 511 bytes (inclusive).		ClientHello with a record size between 256 and 511 bytes (inclusive).
	This case is considered because at least one TLS implementation is		This case is considered because at least one TLS implementation is
	known to hang the connection when such a ClientHello record is		known to hang the connection when such a ClientHello record is
	received.		received.
End of changes. 4 change blocks.
	5 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/