< draft-farinacci-lisp-simple-nat-03.txt		draft-farinacci-lisp-simple-nat-04.txt >
	Network Working Group D. Farinacci		Network Working Group D. Farinacci
	Internet-Draft lispers.net		Internet-Draft lispers.net
	Intended status: Informational November 7, 2021		Intended status: Informational May 1, 2022
	Expires: May 11, 2022		Expires: November 2, 2022
	A Simple LISP NAT-Traversal Implementation		A Simple LISP NAT-Traversal Implementation
	draft-farinacci-lisp-simple-nat-03		draft-farinacci-lisp-simple-nat-04
	Abstract		Abstract
	This informational draft documents the lispers.net LISP NAT-Traversal		This informational draft documents the lispers.net LISP NAT-Traversal
	implementation.		implementation.
	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 31 ¶
	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 May 11, 2022.		This Internet-Draft will expire on November 2, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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
	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 2, line 21 ¶		skipping to change at page 2, line 21 ¶
	5. xTR Map-Registering and Map-Server Proxy Map-Replying . . . . 10		5. xTR Map-Registering and Map-Server Proxy Map-Replying . . . . 10
	6. Packet Flow from ITR-behind-NAT to RTR . . . . . . . . . . . 11		6. Packet Flow from ITR-behind-NAT to RTR . . . . . . . . . . . 11
	7. Packet Flow from Remote ITR to RTR . . . . . . . . . . . . . 11		7. Packet Flow from Remote ITR to RTR . . . . . . . . . . . . . 11
	8. Packet Flow from RTR to ETR-behind-NAT . . . . . . . . . . . 11		8. Packet Flow from RTR to ETR-behind-NAT . . . . . . . . . . . 11
	9. Design Observations . . . . . . . . . . . . . . . . . . . . . 13		9. Design Observations . . . . . . . . . . . . . . . . . . . . . 13
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 14		10. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	12. Normative References . . . . . . . . . . . . . . . . . . . . 14		12. Normative References . . . . . . . . . . . . . . . . . . . . 14
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 15		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 15
	Appendix B. Document Change Log . . . . . . . . . . . . . . . . 15		Appendix B. Document Change Log . . . . . . . . . . . . . . . . 15
	B.1. Changes to draft-farinacci-lisp-simple-nat-03 . . . . . . 15		B.1. Changes to draft-farinacci-lisp-simple-nat-04 . . . . . . 15
	B.2. Changes to draft-farinacci-lisp-simple-nat-02 . . . . . . 15		B.2. Changes to draft-farinacci-lisp-simple-nat-03 . . . . . . 15
	B.3. Changes to draft-farinacci-lisp-simple-nat-01 . . . . . . 15		B.3. Changes to draft-farinacci-lisp-simple-nat-02 . . . . . . 15
	B.4. Changes to draft-farinacci-lisp-simple-nat-00 . . . . . . 16		B.4. Changes to draft-farinacci-lisp-simple-nat-01 . . . . . . 16
			B.5. Changes to draft-farinacci-lisp-simple-nat-00 . . . . . . 16
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Introduction		1. Introduction
	This draft documents the LISP messages and protocol procedures for a		This draft documents the LISP messages and protocol procedures for a
	simple mechanism for the NAT Traversal problem. A subset of message		simple mechanism for the NAT Traversal problem. A subset of message
	definitions and protocol procedures are taken from		definitions and protocol procedures are taken from
	[I-D.ermagan-lisp-nat-traversal]. This design was first implemented		[I-D.ermagan-lisp-nat-traversal]. This design was first implemented
	in the lispers.net LISP implementation dating back to January 2014.		in the lispers.net LISP implementation dating back to January 2014.
	skipping to change at page 14, line 37 ¶		skipping to change at page 14, line 37 ¶
	NUMBERS http://www.iana.org/numbers.html, Febuary 2007.		NUMBERS http://www.iana.org/numbers.html, Febuary 2007.
	[I-D.ermagan-lisp-nat-traversal]		[I-D.ermagan-lisp-nat-traversal]
	Ermagan, V., Farinacci, D., Lewis, D., Maino, F., Comeras,		Ermagan, V., Farinacci, D., Lewis, D., Maino, F., Comeras,
	M. P., Skriver, J., White, C., Lopez, A., and A. Cabellos,		M. P., Skriver, J., White, C., Lopez, A., and A. Cabellos,
	"NAT traversal for LISP", draft-ermagan-lisp-nat-		"NAT traversal for LISP", draft-ermagan-lisp-nat-
	traversal-19 (work in progress), May 2021.		traversal-19 (work in progress), May 2021.
	[I-D.farinacci-lisp-name-encoding]		[I-D.farinacci-lisp-name-encoding]
	Farinacci, D., "LISP Distinguished Name Encoding", draft-		Farinacci, D., "LISP Distinguished Name Encoding", draft-
	farinacci-lisp-name-encoding-12 (work in progress), May		farinacci-lisp-name-encoding-14 (work in progress), May
	2021.		2022.
	[I-D.ietf-lisp-rfc6830bis]		[I-D.ietf-lisp-rfc6830bis]
	Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.		Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
	Cabellos, "The Locator/ID Separation Protocol (LISP)",		Cabellos, "The Locator/ID Separation Protocol (LISP)",
	draft-ietf-lisp-rfc6830bis-36 (work in progress), November		draft-ietf-lisp-rfc6830bis-36 (work in progress), November
	2020.		2020.
	[I-D.ietf-lisp-rfc6833bis]		[I-D.ietf-lisp-rfc6833bis]
	Farinacci, D., Maino, F., Fuller, V., and A. Cabellos,		Farinacci, D., Maino, F., Fuller, V., and A. Cabellos,
	"Locator/ID Separation Protocol (LISP) Control-Plane",		"Locator/ID Separation Protocol (LISP) Control-Plane",
	skipping to change at page 15, line 32 ¶		skipping to change at page 15, line 32 ¶
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
	The author would like to thank the authors of the LISP NAT-Traversal		The author would like to thank the authors of the LISP NAT-Traversal
	specification [I-D.ermagan-lisp-nat-traversal] for their initial		specification [I-D.ermagan-lisp-nat-traversal] for their initial
	ideas and prototyping to allow a simpler form of NAT-Traversal to be		ideas and prototyping to allow a simpler form of NAT-Traversal to be
	designed.		designed.
	Appendix B. Document Change Log		Appendix B. Document Change Log
	B.1. Changes to draft-farinacci-lisp-simple-nat-03		B.1. Changes to draft-farinacci-lisp-simple-nat-04
			o Posted May 2022.
			o Update document timer.
			B.2. Changes to draft-farinacci-lisp-simple-nat-03
	o Posted November 2021.		o Posted November 2021.
	o Update document timer.		o Update document timer.
	B.2. Changes to draft-farinacci-lisp-simple-nat-02		B.3. Changes to draft-farinacci-lisp-simple-nat-02
	o Posted May 2021.		o Posted May 2021.
	o Update document timer.		o Update document timer.
	B.3. Changes to draft-farinacci-lisp-simple-nat-01		B.4. Changes to draft-farinacci-lisp-simple-nat-01
	o Posted November 2020.		o Posted November 2020.
	o Update document timer.		o Update document timer.
	B.4. Changes to draft-farinacci-lisp-simple-nat-00		B.5. Changes to draft-farinacci-lisp-simple-nat-00
	o Posted May 2020.		o Posted May 2020.
	o Initial posting.		o Initial posting.
	Author's Address		Author's Address
	Dino Farinacci		Dino Farinacci
	lispers.net		lispers.net
	San Jose, CA		San Jose, CA
End of changes. 10 change blocks.
	15 lines changed or deleted		22 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/