< draft-kumar-sfc-nsh-udp-transport-02.txt		draft-kumar-sfc-nsh-udp-transport-03.txt >
	Service Function Chaining S. Kumar, Ed.		Service Function Chaining S. Kumar, Ed.
	Internet-Draft L. Kreeger, Ed.		Internet-Draft L. Kreeger, Ed.
	Intended status: Standards Track Cisco Systems, Inc.		Intended status: Standards Track Cisco Systems, Inc.
	Expires: August 14, 2016 S. Majee		Expires: August 26, 2017 S. Majee
	F5 Networks		F5 Networks
	W. Haeffner		W. Haeffner
	Vodafone		Vodafone
	R. Manur		R. Manur
	Broadcom		Broadcom
	D. Melman		D. Melman
	Marvell		Marvell
	February 11, 2016		February 22, 2017
	UDP Transport for Network Service Header		UDP Transport for Network Service Header
	draft-kumar-sfc-nsh-udp-transport-02		draft-kumar-sfc-nsh-udp-transport-03
	Abstract		Abstract
	This draft describes the transport encapsulation to carry Network		This draft describes the transport encapsulation to carry Network
	Service Header (NSH) over UDP transport protocol. This enables		Service Header (NSH) over UDP transport protocol. This enables
	applications and services using NSH to communicate over a simple		applications and services using NSH to communicate over a simple
	layer-3 network without topological constraints. It brings down the		layer-3 network without topological constraints. It brings down the
	barrier to deploy NSH by not requiring additional overhead as is		barrier to deploy NSH by not requiring additional overhead as is
	typical of overlay encapsulation mechanisms designed on top of UDP.		typical of overlay encapsulation mechanisms designed on top of UDP.
	skipping to change at page 1, line 49 ¶		skipping to change at page 1, line 49 ¶
	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 14, 2016.		This Internet-Draft will expire on August 26, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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 13, line 41 ¶		skipping to change at page 13, line 41 ¶
	techniques. However, where source port computation for entropy is		techniques. However, where source port computation for entropy is
	disabled a random port SHOULD be selected to mitigate exposure to		disabled a random port SHOULD be selected to mitigate exposure to
	off-path attacks as described in [RFC6056].		off-path attacks as described in [RFC6056].
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-sfc-nsh]		[I-D.ietf-sfc-nsh]
	Quinn, P. and U. Elzur, "Network Service Header", draft-		Quinn, P. and U. Elzur, "Network Service Header", draft-
	ietf-sfc-nsh-02 (work in progress), January 2016.		ietf-sfc-nsh-11 (work in progress), February 2017.
	[I-D.ietf-tsvwg-rfc5405bis]		[I-D.ietf-tsvwg-rfc5405bis]
	Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage		Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage
	Guidelines", draft-ietf-tsvwg-rfc5405bis-07 (work in		Guidelines", draft-ietf-tsvwg-rfc5405bis-19 (work in
	progress), November 2015.		progress), October 2016.
	[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,		[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
	DOI 10.17487/RFC0768, August 1980,		DOI 10.17487/RFC0768, August 1980,
	<http://www.rfc-editor.org/info/rfc768>.		<http://www.rfc-editor.org/info/rfc768>.
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<http://www.rfc-editor.org/info/rfc2119>.
End of changes. 7 change blocks.
	8 lines changed or deleted		8 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/