draft-arkko-townsley-coexistence-06.txt		draft-arkko-townsley-coexistence.txt
	Network Working Group J. Arkko		Network Working Group J. Arkko
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Informational M. Townsley		Intended status: Informational M. Townsley
	Expires: April 25, 2011 Cisco		Expires: April 4, 2011 Cisco
	October 22, 2010		October 2010
	IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios		IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios
	draft-arkko-townsley-coexistence-06		draft-arkko-townsley-coexistence-06
	Abstract		Abstract
	When IPv6 was designed, it was expected that the transition from IPv4		When IPv6 was designed, it was expected that the transition from IPv4
	to IPv6 would occur more smoothly and expeditiously than experience		to IPv6 would occur more smoothly and expeditiously than experience
	has revealed. The growth of the IPv4 Internet and predicted		has revealed. The growth of the IPv4 Internet and predicted
	depletion of the free pool of IPv4 address blocks on a foreseeable		depletion of the free pool of IPv4 address blocks on a foreseeable
	skipping to change at page 1, line 34		skipping to change at page 1, line 34
	This document was originally created as input to the Montreal co-		This document was originally created as input to the Montreal co-
	existence interim meeting in October 2008, which led to the		existence interim meeting in October 2008, which led to the
	rechartering of the Behave and Softwire working groups to take on new		rechartering of the Behave and Softwire working groups to take on new
	IPv4 and IPv6 coexistence work. This document is published as a		IPv4 and IPv6 coexistence work. This document is published as a
	historical record of the thinking at the time, but hopefully also		historical record of the thinking at the time, but hopefully also
	helps understand the rationale behind current IETF tools for co-		helps understand the rationale behind current IETF tools for co-
	existence and transition.		existence and transition.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF 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.
	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). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		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."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on April 4, 2011.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on April 25, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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
	skipping to change at page 2, line 23		skipping to change at page 2, line 15
	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
	described in the BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2.1. Reaching the IPv4 Internet . . . . . . . . . . . . . . . . 6		2.1. Reaching the IPv4 Internet . . . . . . . . . . . . . . . . 5
	2.1.1. NAT444 . . . . . . . . . . . . . . . . . . . . . . . . 6		2.1.1. NAT444 . . . . . . . . . . . . . . . . . . . . . . . . 5
	2.1.2. Distributed NAT . . . . . . . . . . . . . . . . . . . 8		2.1.2. Distributed NAT . . . . . . . . . . . . . . . . . . . 7
	2.1.3. Recommendation . . . . . . . . . . . . . . . . . . . . 10		2.1.3. Recommendation . . . . . . . . . . . . . . . . . . . . 9
	2.2. Running out of IPv4 Private Address Space . . . . . . . . 11		2.2. Running out of IPv4 Private Address Space . . . . . . . . 10
	2.3. Enterprise IPv6 Only Networks . . . . . . . . . . . . . . 13		2.3. Enterprise IPv6 Only Networks . . . . . . . . . . . . . . 12
	2.4. Reaching Private IPv4 Only Servers . . . . . . . . . . . . 14		2.4. Reaching Private IPv4 Only Servers . . . . . . . . . . . . 13
	2.5. Reaching IPv6 Only Servers . . . . . . . . . . . . . . . . 16		2.5. Reaching IPv6 Only Servers . . . . . . . . . . . . . . . . 15
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 17		3. Security Considerations . . . . . . . . . . . . . . . . . . . 16
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 18		5. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 17
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19		6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
	6.1. Normative References . . . . . . . . . . . . . . . . . . . 19		6.1. Normative References . . . . . . . . . . . . . . . . . . . 18
	6.2. Informative References . . . . . . . . . . . . . . . . . . 19		6.2. Informative References . . . . . . . . . . . . . . . . . . 18
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 20
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
	1. Introduction		1. Introduction
	This document was originally created as input to the Montreal co-		This document was originally created as input to the Montreal co-
	existence interim meeting in October 2008, which led to the		existence interim meeting in October 2008, which led to the
	rechartering of the Behave and Softwire working groups to take on new		rechartering of the Behave and Softwire working groups to take on new
	IPv4 and IPv6 coexistence work. This document is published as a		IPv4 and IPv6 coexistence work. This document is published as a
	historical record of the thinking at the time, but hopefully also		historical record of the thinking at the time, but hopefully also
	helps understand the rationale behind current IETF tools for co-		helps understand the rationale behind current IETF tools for co-
	existence and transition.		existence and transition.
	skipping to change at page 20, line 50		skipping to change at page 19, line 50
	[Huston.IPv4]		[Huston.IPv4]
	Huston, G., "The IPv4 Internet Report", available		Huston, G., "The IPv4 Internet Report", available
	at http://ipv4.potaroo.net, August 2008.		at http://ipv4.potaroo.net, August 2008.
	[I-D.nishitani-cgn]		[I-D.nishitani-cgn]
	Nishitani, T., Miyakawa, S., Nakagawa, A., and H. Ashida,		Nishitani, T., Miyakawa, S., Nakagawa, A., and H. Ashida,
	"Common Functions of Large Scale NAT (LSN)",		"Common Functions of Large Scale NAT (LSN)",
	draft-nishitani-cgn-02 (work in progress), June 2009.		draft-nishitani-cgn-02 (work in progress), June 2009.
	[I-D.shirasaki-isp-shared-addr]		[I-D.shirasaki-isp-shared-addr]
	Shirasaki, Y., Miyakawa, S., Nakagawa, A., Yamaguchi, J.,		Yamagata, I., Miyakawa, S., Nakagawa, A., Yamaguchi, J.,
	and H. Ashida, "ISP Shared Address",		and H. Ashida, "ISP Shared Address",
	draft-shirasaki-isp-shared-addr-02 (work in progress),		draft-shirasaki-isp-shared-addr-05 (work in progress),
	March 2009.		September 2010.
	[I-D.azinger-additional-private-ipv4-space-issues]		[I-D.azinger-additional-private-ipv4-space-issues]
	Azinger, M. and L. Vegoda, "Additional Private IPv4 Space		Azinger, M. and L. Vegoda, "Additional Private IPv4 Space
	Issues",		Issues",
	draft-azinger-additional-private-ipv4-space-issues-04		draft-azinger-additional-private-ipv4-space-issues-04
	(work in progress), April 2010.		(work in progress), April 2010.
	[I-D.ietf-v6ops-tunnel-security-concerns]		[I-D.ietf-v6ops-tunnel-security-concerns]
	Krishnan, S., Thaler, D., and J. Hoagland, "Security		Krishnan, S., Thaler, D., and J. Hoagland, "Security
	Concerns With IP Tunneling",		Concerns With IP Tunneling",
End of changes. 9 change blocks.
	36 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/