< draft-knutsen-tcpm-middlebox-discovery-03.txt		draft-knutsen-tcpm-middlebox-discovery-04.txt >
	TCP Maintenance and Minor A. Knutsen		TCP Maintenance and Minor A. Knutsen
	Extensions (tcpm) R. Frederick		Extensions (tcpm) R. Frederick
	Internet Draft J. Mahdavi		Internet Draft J. Mahdavi
	Intended Category: Informational Q. Li		Intended Category: Informational Q. Li
	Expires: May 2010 W.J. Yeh		Expires: November 2010 W.J. Yeh
	Blue Coat Systems		Blue Coat Systems
	November 9, 2009		May 3, 2010
	TCP Option for Transparent Middlebox Discovery		TCP Option for Transparent Middlebox Discovery
	<draft-knutsen-tcpm-middlebox-discovery-03.txt>		<draft-knutsen-tcpm-middlebox-discovery-04.txt>
	Status of this Memo		Status of this Memo
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	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
	skipping to change at page 1, line 45 ¶		skipping to change at page 1, line 45 ¶
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire February, 2010.		This Internet-Draft will expire February, 2010.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 Provisions		This document is subject to BCP 78 and the IETF Trust's Legal Provisions
	Relating to IETF Documents in effect on the date of publication of		Relating to IETF Documents (http://trustee.ietf.org/license-info)
	this document (http://trustee.ietf.org/license-info). Please		in effect on the date of publication of this document. Please
	review these documents carefully, as they describe your rights and		review these documents carefully, as they describe your rights and
	restrictions with respect to this document.		restrictions with respect to this document.
	Abstract		Abstract
	This document describes a TCP option intended to facilitate		This document describes a TCP option intended to facilitate
	transparent detection of middleboxes (or services playing that role)		transparent detection of middleboxes (or services playing that role)
	along the path of a TCP connection as the connection is made. The		along the path of a TCP connection as the connection is made. The
	option has no effect if an appropriate middlebox is not on the path.		option has no effect if an appropriate middlebox is not on the path.
	skipping to change at page 6, line 34 ¶		skipping to change at page 6, line 34 ¶
	The request MUST have the "R" bit to 0.		The request MUST have the "R" bit to 0.
	The device capability specifies what target data MUST be present in		The device capability specifies what target data MUST be present in
	the option, if any.		the option, if any.
	Requests are only valid in SYN packets. They MUST NOT appear in other		Requests are only valid in SYN packets. They MUST NOT appear in other
	segments and MUST be ignored when found outside of a SYN.		segments and MUST be ignored when found outside of a SYN.
	5.3. Responding to Discovery Request		5.3. Responding to Discovery Request
	Requests received in any state except SYN-SENT MUST be ignored.
	Devices MUST NOT respond to requests which have not been validated		Devices MUST NOT respond to requests which have not been validated
	using the target data, if required by the device capability.		using the target data, if required by the device capability.
	Responses MUST have the "R" bit set to 1.		Responses MUST have the "R" bit set to 1.
	The device capability specifies what target data MUST be present in		The device capability specifies what target data MUST be present in
	the option, if any.		the option, if any.
	Responses are only valid in valid SYN-ACK packets. They MUST NOT		Responses are only valid in valid SYN-ACK packets. They MUST NOT
	appear in other segments and MUST be ignored when found outside of a		appear in other segments and MUST be ignored when found outside of a
End of changes. 5 change blocks.
	7 lines changed or deleted		5 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/