< draft-ietf-tsvwg-natsupp-08.txt		draft-ietf-tsvwg-natsupp-09.txt >
	Network Working Group R. Stewart		Network Working Group R. Stewart
	Internet-Draft Netflix, Inc.		Internet-Draft Netflix, Inc.
	Intended status: Standards Track M. Tuexen		Intended status: Standards Track M. Tuexen
	Expires: January 6, 2016 I. Ruengeler		Expires: November 19, 2016 I. Ruengeler
	Muenster Univ. of Appl. Sciences		Muenster Univ. of Appl. Sciences
	July 5, 2015		May 18, 2016
	Stream Control Transmission Protocol (SCTP) Network Address Translation		Stream Control Transmission Protocol (SCTP) Network Address Translation
	Support		Support
	draft-ietf-tsvwg-natsupp-08.txt		draft-ietf-tsvwg-natsupp-09.txt
	Abstract		Abstract
	The Stream Control Transmission Protocol (SCTP) provides a reliable		The Stream Control Transmission Protocol (SCTP) provides a reliable
	communications channel between two end-hosts in many ways similar to		communications channel between two end-hosts in many ways similar to
	the Transmission Control Protocol (TCP). With the widespread		the Transmission Control Protocol (TCP). With the widespread
	deployment of Network Address Translators (NAT), specialized code has		deployment of Network Address Translators (NAT), specialized code has
	been added to NAT for TCP that allows multiple hosts to reside behind		been added to NAT for TCP that allows multiple hosts to reside behind
	a NAT and yet use only a single globally unique IPv4 address, even		a NAT and yet use only a single globally unique IPv4 address, even
	when two hosts (behind a NAT) choose the same port numbers for their		when two hosts (behind a NAT) choose the same port numbers for their
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 January 6, 2016.		This Internet-Draft will expire on November 19, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 20 ¶		skipping to change at page 3, line 20 ¶
	(SCTP_NAT_FRIENDLY) . . . . . . . . . . . . . . . . . . . 40		(SCTP_NAT_FRIENDLY) . . . . . . . . . . . . . . . . . . . 40
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
	9.1. New Chunk Flags for Two Existing Chunk Types . . . . . . 40		9.1. New Chunk Flags for Two Existing Chunk Types . . . . . . 40
	9.2. Three New Error Causes . . . . . . . . . . . . . . . . . 41		9.2. Three New Error Causes . . . . . . . . . . . . . . . . . 41
	9.3. Two New Chunk Parameter Types . . . . . . . . . . . . . . 42		9.3. Two New Chunk Parameter Types . . . . . . . . . . . . . . 42
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 42		10. Security Considerations . . . . . . . . . . . . . . . . . . . 42
	11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 42		11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 42
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . 43		12. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
	12.1. Normative References . . . . . . . . . . . . . . . . . . 43		12.1. Normative References . . . . . . . . . . . . . . . . . . 43
	12.2. Informative References . . . . . . . . . . . . . . . . . 43		12.2. Informative References . . . . . . . . . . . . . . . . . 43
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
	1. Introduction		1. Introduction
	Stream Control Transmission Protocol [RFC4960] provides a reliable		Stream Control Transmission Protocol [RFC4960] provides a reliable
	communications channel between two end-hosts in many ways similar to		communications channel between two end-hosts in many ways similar to
	TCP [RFC0793]. With the widespread deployment of Network Address		TCP [RFC0793]. With the widespread deployment of Network Address
	Translators (NAT), specialized code has been added to NAT for TCP		Translators (NAT), specialized code has been added to NAT for TCP
	that allows multiple hosts to reside behind a NAT using private		that allows multiple hosts to reside behind a NAT using private
	addresses (see [RFC6890]) and yet use only a single globally unique		addresses (see [RFC6890]) and yet use only a single globally unique
	IPv4 address, even when two hosts (behind a NAT) choose the same port		IPv4 address, even when two hosts (behind a NAT) choose the same port
	skipping to change at page 43, line 10 ¶		skipping to change at page 43, line 10 ¶
	The authors wish to thank Jason But, Gorry Fairhurst, Bryan Ford,		The authors wish to thank Jason But, Gorry Fairhurst, Bryan Ford,
	David Hayes, Alfred Hines, Henning Peters, Timo Voelker, Dan Wing,		David Hayes, Alfred Hines, Henning Peters, Timo Voelker, Dan Wing,
	and Qiaobing Xie for their invaluable comments.		and Qiaobing Xie for their invaluable comments.
	12. References		12. References
	12.1. Normative References		12.1. 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>.
	[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,		[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla,
	"Authenticated Chunks for the Stream Control Transmission		"Authenticated Chunks for the Stream Control Transmission
	Protocol (SCTP)", RFC 4895, August 2007.		Protocol (SCTP)", RFC 4895, DOI 10.17487/RFC4895, August
			2007, <http://www.rfc-editor.org/info/rfc4895>.
	[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC		[RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol",
	4960, September 2007.		RFC 4960, DOI 10.17487/RFC4960, September 2007,
			<http://www.rfc-editor.org/info/rfc4960>.
	[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.		[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M.
	Kozuka, "Stream Control Transmission Protocol (SCTP)		Kozuka, "Stream Control Transmission Protocol (SCTP)
	Dynamic Address Reconfiguration", RFC 5061, September		Dynamic Address Reconfiguration", RFC 5061,
	2007.		DOI 10.17487/RFC5061, September 2007,
			<http://www.rfc-editor.org/info/rfc5061>.
	[RFC6096] Tuexen, M. and R. Stewart, "Stream Control Transmission		[RFC6096] Tuexen, M. and R. Stewart, "Stream Control Transmission
	Protocol (SCTP) Chunk Flags Registration", RFC 6096,		Protocol (SCTP) Chunk Flags Registration", RFC 6096,
	January 2011.		DOI 10.17487/RFC6096, January 2011,
			<http://www.rfc-editor.org/info/rfc6096>.
	12.2. Informative References		12.2. Informative References
	[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC		[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
	793, September 1981.		RFC 793, DOI 10.17487/RFC0793, September 1981,
			<http://www.rfc-editor.org/info/rfc793>.
	[RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V.		[RFC6458] Stewart, R., Tuexen, M., Poon, K., Lei, P., and V.
	Yasevich, "Sockets API Extensions for the Stream Control		Yasevich, "Sockets API Extensions for the Stream Control
	Transmission Protocol (SCTP)", RFC 6458, December 2011.		Transmission Protocol (SCTP)", RFC 6458,
			DOI 10.17487/RFC6458, December 2011,
			<http://www.rfc-editor.org/info/rfc6458>.
	[RFC6890] Cotton, M., Vegoda, L., Bonica, R., and B. Haberman,		[RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
	"Special-Purpose IP Address Registries", BCP 153, RFC		"Special-Purpose IP Address Registries", BCP 153,
	6890, April 2013.		RFC 6890, DOI 10.17487/RFC6890, April 2013,
			<http://www.rfc-editor.org/info/rfc6890>.
	[RFC6951] Tuexen, M. and R. Stewart, "UDP Encapsulation of Stream		[RFC6951] Tuexen, M. and R. Stewart, "UDP Encapsulation of Stream
	Control Transmission Protocol (SCTP) Packets for End-Host		Control Transmission Protocol (SCTP) Packets for End-Host
	to End-Host Communication", RFC 6951, May 2013.		to End-Host Communication", RFC 6951,
			DOI 10.17487/RFC6951, May 2013,
			<http://www.rfc-editor.org/info/rfc6951>.
	Authors' Addresses		Authors' Addresses
	Randall R. Stewart		Randall R. Stewart
	Netflix, Inc.		Netflix, Inc.
	Chapin, SC 29036		Chapin, SC 29036
	US		US
	Email: randall@lakerest.net		Email: randall@lakerest.net
	Michael Tuexen		Michael Tuexen
	Muenster University of Applied Sciences		Muenster University of Applied Sciences
	Stegerwaldstrasse 39		Stegerwaldstrasse 39
	48565 Steinfurt		48565 Steinfurt
	DE		DE
	Email: tuexen@fh-muenster.de		Email: tuexen@fh-muenster.de
	Irene Ruengeler		Irene Ruengeler
	Muenster University of Applied Sciences		Muenster University of Applied Sciences
End of changes. 16 change blocks.
	20 lines changed or deleted		33 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/