< draft-xu-ipsecme-esp-in-udp-lb-03.txt		draft-xu-ipsecme-esp-in-udp-lb-04.txt >
	Network Working Group X. Xu		Network Working Group X. Xu
	Internet-Draft Alibaba, Inc		Internet-Draft Alibaba, Inc
	Intended status: Standards Track S. Hegde		Intended status: Standards Track S. Hegde
	Expires: July 23, 2020 Juniper		Expires: September 12, 2020 Juniper
	D. Zhang		D. Zhang
	L. Xia		L. Xia
	Huawei		Huawei
	January 20, 2020		March 11, 2020
	Encapsulating IPsec ESP in UDP for Load-balancing		Encapsulating IPsec ESP in UDP for Load-balancing
	draft-xu-ipsecme-esp-in-udp-lb-03		draft-xu-ipsecme-esp-in-udp-lb-04
	Abstract		Abstract
	IPsec Virtual Private Network (VPN) is widely used by enterprises to		IPsec Virtual Private Network (VPN) is widely used by enterprises to
	interconnect their geographical dispersed branch office locations		interconnect their geographical dispersed branch office locations
	across the Wide Area Network (WAN) or the Internet, especially in the		across the Wide Area Network (WAN) or the Internet, especially in the
	Software-Defined-WAN (SD-WAN) era. In addition, IPsec is also		Software-Defined-WAN (SD-WAN) era. In addition, IPsec is also
	increasingly used by cloud providers to encrypt IP traffic traversing		increasingly used by cloud providers to encrypt IP traffic traversing
	data center interconnect WAN so as to meet the security and		data center interconnect WAN so as to meet the security and
	compliance requirements, especially in financial cloud and		compliance requirements, especially in financial cloud and
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 July 23, 2020.		This Internet-Draft will expire on September 12, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 28 ¶		skipping to change at page 3, line 28 ¶
	such, ESP-in-UDP encapsulation would still have a practical		such, ESP-in-UDP encapsulation would still have a practical
	application value in the IPv6 networks during this transition		application value in the IPv6 networks during this transition
	timeframe.		timeframe.
	Note that the difference between the ESP-in-UDP encapsulation as		Note that the difference between the ESP-in-UDP encapsulation as
	proposed in this document and the ESP-in-UDP encapsulation as		proposed in this document and the ESP-in-UDP encapsulation as
	described in [RFC3948] is that the former uses the UDP tunnel for		described in [RFC3948] is that the former uses the UDP tunnel for
	load-balancing improvement purpose and therefore the source port is		load-balancing improvement purpose and therefore the source port is
	used as an entropy field while the latter uses the UDP tunnel for NAT		used as an entropy field while the latter uses the UDP tunnel for NAT
	traverse purpose and therefore the source port is set to a constant		traverse purpose and therefore the source port is set to a constant
	value (i.e., 4500). In addition, this document only discusses about		value (i.e., 4500). In addition, the ESP-in-UDP encapsulation as
	the tunnel mode ESP encapsulation.		described in this document is applicable to both the tunnel mode ESP
			encapsulation and the transport mode ESP encapsulation.
	1.1. Requirements Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. Terminology		2. Terminology
	This memo makes use of the terms defined in [RFC2401]and [RFC2406].		This memo makes use of the terms defined in [RFC2401]and [RFC2406].
End of changes. 5 change blocks.
	6 lines changed or deleted		7 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/