draft-ietf-v6ops-464xlat-04.txt		draft-ietf-v6ops-464xlat-05.txt
	Internet Engineering Task Force M. Mawatari		Internet Engineering Task Force M. Mawatari
	Internet-Draft Japan Internet Exchange Co.,Ltd.		Internet-Draft Japan Internet Exchange Co.,Ltd.
	Intended status: BCP M. Kawashima		Intended status: BCP M. Kawashima
	Expires: December 27, 2012 NEC AccessTechnica, Ltd.		Expires: January 4, 2013 NEC AccessTechnica, Ltd.
	C. Byrne		C. Byrne
	T-Mobile USA		T-Mobile USA
	June 25, 2012		July 3, 2012
	464XLAT: Combination of Stateful and Stateless Translation		464XLAT: Combination of Stateful and Stateless Translation
	draft-ietf-v6ops-464xlat-04		draft-ietf-v6ops-464xlat-05
	Abstract		Abstract
	This document describes an architecture (464XLAT) for providing		This document describes an architecture (464XLAT) for providing
	limited IPv4 connectivity across an IPv6-only network by combining		limited IPv4 connectivity across an IPv6-only network by combining
	existing and well-known stateful protocol translation RFC 6146 in the		existing and well-known stateful protocol translation RFC 6146 in the
	core and stateless protocol translation RFC 6145 at the edge. 464XLAT		core and stateless protocol translation RFC 6145 at the edge. 464XLAT
	is a simple and scalable technique to quickly deploy limited IPv4		is a simple and scalable technique to quickly deploy limited IPv4
	access service to IPv6-only edge networks without encapsulation.		access service to IPv6-only edge networks without encapsulation.
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	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 December 27, 2012.		This Internet-Draft will expire on January 4, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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
	skipping to change at page 2, line 40		skipping to change at page 2, line 40
	7.5. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 12		7.5. DNS Proxy Implementation . . . . . . . . . . . . . . . . . 12
	7.6. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 12		7.6. CLAT in a Gateway . . . . . . . . . . . . . . . . . . . . 12
	7.7. CLAT to CLAT communications . . . . . . . . . . . . . . . 12		7.7. CLAT to CLAT communications . . . . . . . . . . . . . . . 12
	8. Deployment Considerations . . . . . . . . . . . . . . . . . . 13		8. Deployment Considerations . . . . . . . . . . . . . . . . . . 13
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 13		9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
	12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14		12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	12.1. Normative References . . . . . . . . . . . . . . . . . . . 14		12.1. Normative References . . . . . . . . . . . . . . . . . . . 14
	12.2. Informative References . . . . . . . . . . . . . . . . . . 14		12.2. Informative References . . . . . . . . . . . . . . . . . . 14
	Appendix A. Examples of IPv4/IPv6 Address Translation . . . . . . 15		Appendix A. Examples of IPv4/IPv6 Address Translation . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
	1. Introduction		1. Introduction
	The IANA unallocated IPv4 address pool was exhausted on February 3,		The IANA unallocated IPv4 address pool was exhausted on February 3,
	2011. Each RIR's unallocated IPv4 address pool will exhaust in the		2011. Each RIR's unallocated IPv4 address pool will exhaust in the
	near future. It will be difficult for many networks to assign IPv4		near future. It will be difficult for many networks to assign IPv4
	addresses to end users, despite substantial IP connectivity growth		addresses to end users, despite substantial IP connectivity growth
	required for fast growing edge networks.		required for fast growing edge networks.
	This document describes an IPv4 over IPv6 solution as one of the		This document describes an IPv4 over IPv6 solution as one of the
	skipping to change at page 7, line 9		skipping to change at page 7, line 9
	IPv4 access networks. They can migrate their access network to a		IPv4 access networks. They can migrate their access network to a
	simple and highly scalable IPv6-only environment.		simple and highly scalable IPv6-only environment.
	Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE		Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE
	camp Spring 2012. The result is described in		camp Spring 2012. The result is described in
	[I-D.hazeyama-widecamp-ipv6-only-experience].		[I-D.hazeyama-widecamp-ipv6-only-experience].
	6.2. Wireless 3GPP Network Applicability		6.2. Wireless 3GPP Network Applicability
			The vast majority of mobile networks are compliant to Pre-Release 9
			3GPP standards. In Pre-Release 9 3GPP networks, GSM and UMTS
			networks must signal and support both IPv4 and IPv6 Packet Data
			Protocol (PDP) attachments to access IPv4 and IPv6 network
			destinations [RFC6459]. Since there are 2 PDPs required to support 2
			address families, this is double the number of PDPs required to
			support the status quo of 1 address family, which is IPv4.
	464XLAT in combination with stateful translation [RFC6146] and DNS64		464XLAT in combination with stateful translation [RFC6146] and DNS64
	[RFC6147] allows 85% of the Android applications to continue to work		[RFC6147] allows 85% of the Android applications to continue to work
	with single translation or native IPv6 access. For the remaining 15%		with single translation or native IPv6 access. For the remaining 15%
	of applications that require IPv4 connectivity, the CLAT function on		of applications that require IPv4 connectivity, the CLAT function on
	the UE provides a private IPv4 address and IPv4 default-route on the		the UE provides a private IPv4 address and IPv4 default-route on the
	host for the applications to reference and bind to. Connections		host for the applications to reference and bind to. Connections
	sourced from the IPv4 interface are immediately routed to the CLAT		sourced from the IPv4 interface are immediately routed to the CLAT
	function and passed to the IPv6-only mobile network, destine to the		function and passed to the IPv6-only mobile network, destine to the
	PLAT. In summary, the UE has the CLAT function that does a stateless		PLAT. In summary, the UE has the CLAT function that does a stateless
	translation [RFC6145], but only when required. The mobile network		translation [RFC6145], but only when required. The mobile network
	has a PLAT that does stateful translation [RFC6146].		has a PLAT that does stateful translation [RFC6146].
			464XLAT works with today's existing systems as much as possible.
			464XLAT is compatible with existing network based deep packet
			inspection solutions like 3GPP standardized Policy and Charging
			Control (PCC) [TS.23203].
	7. Implementation Considerations		7. Implementation Considerations
	7.1. IPv6 Address Format		7.1. IPv6 Address Format
	IPv6 address format in 464XLAT is defined in Section 2.2 of		IPv6 address format in 464XLAT is defined in Section 2.2 of
	[RFC6052].		[RFC6052].
	7.2. IPv4/IPv6 Address Translation Chart		7.2. IPv4/IPv6 Address Translation Chart
	7.2.1. Case of enabling only stateless XLATE on CLAT		7.2.1. Case of enabling only stateless XLATE on CLAT
	skipping to change at page 8, line 20		skipping to change at page 8, line 20
	| IPv4 | Destination IPv4 address		| IPv4 | Destination IPv4 address
	| server | +----------------------------+		| server | +----------------------------+
	+--------+ | Global IPv4 address |		+--------+ | Global IPv4 address |
	^ | assigned to IPv4 server |		^ | assigned to IPv4 server |
	| +----------------------------+		| +----------------------------+
	+--------+		+--------+
	| PLAT | Stateful XLATE(IPv4:IPv6=1:n)		| PLAT | Stateful XLATE(IPv4:IPv6=1:n)
	+--------+		+--------+
	^		^
	|		|
	Source IPv6 address (IPv6 cloud)		Source IPv6 address (IPv6 cloud)
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	| IPv4-Embedded IPv6 address |		| IPv4-Embedded IPv6 address |
	| defined in Section 2.2 of RFC6052 |		| defined in Section 2.2 of RFC6052 |
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	Destination IPv6 address		Destination IPv6 address
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	| IPv4-Embedded IPv6 address |		| IPv4-Embedded IPv6 address |
	| defined in Section 2.2 of RFC6052 |		| defined in Section 2.2 of RFC6052 |
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	(IPv6 cloud)		(IPv6 cloud)
	^		^
	|		|
	+--------+		+--------+
	| | In the case CLAT has a		| | In the case CLAT has a
	| | dedicated IPv6 prefix for		| | dedicated IPv6 prefix for
	| CLAT | translation, the CLAT behaves		| CLAT | translation, the CLAT can
	| | with only Stateless XLATE		| | perform with only Stateless
	| | (IPv4:IPv6=1:1).		| | XLATE (IPv4:IPv6=1:1).
	+--------+		+--------+
	^ Source IPv4 address		^ Source IPv4 address
	| +----------------------------+		| +----------------------------+
	+--------+ | Private IPv4 address |		+--------+ | Private IPv4 address |
	| IPv4 | | assigned to IPv4 client |		| IPv4 | | assigned to IPv4 client |
	| client | +----------------------------+		| client | +----------------------------+
	+--------+ Destination IPv4 address		+--------+ Destination IPv4 address
	+----------------------------+		+----------------------------+
	| Global IPv4 address |		| Global IPv4 address |
	| assigned to IPv4 server |		| assigned to IPv4 server |
	skipping to change at page 10, line 20		skipping to change at page 10, line 20
	| IPv4 | Destination IPv4 address		| IPv4 | Destination IPv4 address
	| server | +----------------------------+		| server | +----------------------------+
	+--------+ | Global IPv4 address |		+--------+ | Global IPv4 address |
	^ | assigned to IPv4 server |		^ | assigned to IPv4 server |
	| +----------------------------+		| +----------------------------+
	+--------+		+--------+
	| PLAT | Stateful XLATE(IPv4:IPv6=1:n)		| PLAT | Stateful XLATE(IPv4:IPv6=1:n)
	+--------+		+--------+
	^		^
	|		|
	Source IPv6 address (IPv6 cloud)		Source IPv6 address (IPv6 cloud)
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	| IPv4-Embedded IPv6 address |		| IPv4-Embedded IPv6 address |
	| defined in Section 2.2 of RFC6052 |		| defined in Section 2.2 of RFC6052 |
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	Destination IPv6 address		Destination IPv6 address
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	| IPv4-Embedded IPv6 address |		| IPv4-Embedded IPv6 address |
	| defined in Section 2.2 of RFC6052 |		| defined in Section 2.2 of RFC6052 |
	+--------------------------------------------------------------+		+--------------------------------------------------------------+
	(IPv6 cloud)		(IPv6 cloud)
	^		^
	|		|
	+--------+		+--------+
	| | In the case CLAT does not have		| | In the case CLAT does not have
	| | a dedicated IPv6 prefix for		| | a dedicated IPv6 prefix for
	| CLAT | translation, the CLAT behaves		| CLAT | translation, the CLAT can
	| | with NAT44 and Stateless XLATE		| | perform with NAT44 and
			| | Stateless XLATE
	| | (IPv4:IPv6=1:1).		| | (IPv4:IPv6=1:1).
	+--------+		+--------+
	^ Source IPv4 address		^ Source IPv4 address
	| +----------------------------+		| +----------------------------+
	+--------+ | Private IPv4 address |		+--------+ | Private IPv4 address |
	| IPv4 | | assigned to IPv4 client |		| IPv4 | | assigned to IPv4 client |
	| client | +----------------------------+		| client | +----------------------------+
	+--------+ Destination IPv4 address		+--------+ Destination IPv4 address
	+----------------------------+		+----------------------------+
	| Global IPv4 address |		| Global IPv4 address |
	skipping to change at page 11, line 21		skipping to change at page 11, line 21
	translation [RFC6145].		translation [RFC6145].
	The CLAT MAY discover the Pref64::/n of the PLAT via some method such		The CLAT MAY discover the Pref64::/n of the PLAT via some method such
	as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or		as DHCPv6 option, TR-069, DNS APL RR [RFC3123] or
	[I-D.ietf-behave-nat64-discovery-heuristic].		[I-D.ietf-behave-nat64-discovery-heuristic].
	7.3.2. Case of enabling NAT44 and stateless XLATE on CLAT		7.3.2. Case of enabling NAT44 and stateless XLATE on CLAT
	In the case that DHCPv6-PD [RFC3633] is not available, the CLAT does		In the case that DHCPv6-PD [RFC3633] is not available, the CLAT does
	not have dedicated IPv6 prefix for translation. If the CLAT does not		not have dedicated IPv6 prefix for translation. If the CLAT does not
	have a dedicated IPv6 prefix for translation, the CLAT performs with		have a dedicated IPv6 prefix for translation, the CLAT can perform
	NAT44 and stateless translation [RFC6145].		with NAT44 and stateless translation [RFC6145].
	Incoming source IPv4 packets from the LAN of [RFC1918] addresses are		Incoming source IPv4 packets from the LAN of [RFC1918] addresses are
	NAT44 to the CLAT IPv4 host address. Then, the CLAT will do a		NAT44 to the CLAT IPv4 host address. Then, the CLAT will do a
	stateless translation [RFC6145] so that the IPv4 packets from the		stateless translation [RFC6145] so that the IPv4 packets from the
	CLAT IPv4 host address are translated to the CLAT WAN IPv6 address as		CLAT IPv4 host address are translated to the CLAT WAN IPv6 address as
	described in [RFC6052].		described in [RFC6052].
	Its subnet prefix is made of the delegated prefix, completed if		Its subnet prefix is made of the delegated prefix, completed if
	needed to a /64 by a subnet ID = 0. Its interface ID is the 464XLAT		needed to a /64 by a subnet ID = 0. Its interface ID is the 464XLAT
	interface ID (Section 10).		interface ID (Section 10).
	skipping to change at page 14, line 14		skipping to change at page 14, line 14
	according to section 2.2.2 of [RFC5342]. Its suggested value is 02-		according to section 2.2.2 of [RFC5342]. Its suggested value is 02-
	00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00-		00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00-
	00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be		00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be
	taken in reserved or available values.		taken in reserved or available values.
	11. Acknowledgements		11. Acknowledgements
	The authors would like to thank JPIX NOC members, JPIX 464XLAT trial		The authors would like to thank JPIX NOC members, JPIX 464XLAT trial
	service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv		service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv
	Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo		Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo
	Colitti, Erik Kline, Ole Troan, Maoke Chen, and Gang Chen for their		Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, and
	helpful comments. Special acknowledgments go to Remi Despres for his		Jouni Korhonen for their helpful comments. Special acknowledgments
	plentiful supports and suggestions, especially about using NAT44 with		go to Remi Despres for his plentiful supports and suggestions,
	IANA's EUI-64 ID. We also would like to thank Fred Baker and Joel		especially about using NAT44 with IANA's EUI-64 ID. We also would
	Jaeggli for their support.		like to thank Fred Baker and Joel Jaeggli for their support.
	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, March 1997.
	[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.		[RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X.
	Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,		Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052,
	skipping to change at page 15, line 8		skipping to change at page 15, line 8
	[I-D.hazeyama-widecamp-ipv6-only-experience]		[I-D.hazeyama-widecamp-ipv6-only-experience]
	Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura,		Hazeyama, H., Hiromi, R., Ishihara, T., and O. Nakamura,
	"Experiences from IPv6-Only Networks with Transition		"Experiences from IPv6-Only Networks with Transition
	Technologies in the WIDE Camp Spring 2012",		Technologies in the WIDE Camp Spring 2012",
	draft-hazeyama-widecamp-ipv6-only-experience-01 (work in		draft-hazeyama-widecamp-ipv6-only-experience-01 (work in
	progress), March 2012.		progress), March 2012.
	[I-D.ietf-behave-nat64-discovery-heuristic]		[I-D.ietf-behave-nat64-discovery-heuristic]
	Savolainen, T., Korhonen, J., and D. Wing, "Discovery of		Savolainen, T., Korhonen, J., and D. Wing, "Discovery of
	IPv6 Prefix Used for IPv6 Address Synthesis",		IPv6 Prefix Used for IPv6 Address Synthesis",
	draft-ietf-behave-nat64-discovery-heuristic-09 (work in		draft-ietf-behave-nat64-discovery-heuristic-10 (work in
	progress), May 2012.		progress), June 2012.
	[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and		[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
	E. Lear, "Address Allocation for Private Internets",		E. Lear, "Address Allocation for Private Internets",
	BCP 5, RFC 1918, February 1996.		BCP 5, RFC 1918, February 1996.
	[RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes		[RFC3123] Koch, P., "A DNS RR Type for Lists of Address Prefixes
	(APL RR)", RFC 3123, June 2001.		(APL RR)", RFC 3123, June 2001.
	[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic		[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
	Host Configuration Protocol (DHCP) version 6", RFC 3633,		Host Configuration Protocol (DHCP) version 6", RFC 3633,
	skipping to change at page 15, line 47		skipping to change at page 15, line 47
	April 2011.		April 2011.
	[RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T.,		[RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T.,
	Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation		Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation
	Partnership Project (3GPP) Evolved Packet System (EPS)",		Partnership Project (3GPP) Evolved Packet System (EPS)",
	RFC 6459, January 2012.		RFC 6459, January 2012.
	[RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts		[RFC6535] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts
	Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012.		Using "Bump-in-the-Host" (BIH)", RFC 6535, February 2012.
			[TS.23203] 3GPP, "Policy and charging control architecture", 3GPP
			TS 23.203 10.7.0, June 2012.
	Appendix A. Examples of IPv4/IPv6 Address Translation		Appendix A. Examples of IPv4/IPv6 Address Translation
	The following are examples of IPv4/IPv6 Address Translation on the		The following are examples of IPv4/IPv6 Address Translation on the
	464XLAT architecture.		464XLAT architecture.
	Example 1. (Case of enabling only stateless XLATE on CLAT)		Example 1. (Case of enabling only stateless XLATE on CLAT)
	In the case that IPv6 prefix greater than /64 is assigned to end		In the case that IPv6 prefix greater than /64 is assigned to end
	users by such as DHCPv6-PD [RFC3633], only the function of Stateless		users by such as DHCPv6-PD [RFC3633], only the function of Stateless
	XLATE should be enabled on CLAT. Because the CLAT can use dedicated		XLATE should be enabled on CLAT. Because the CLAT can use dedicated
	a /64 from the assigned IPv6 prefix for Stateless XLATE.		a /64 from the assigned IPv6 prefix for Stateless XLATE.
	Host & configuration value		Host & configuration value
	+------------------------------+		+------------------------------+
	| IPv4 server |		| IPv4 server |
	| [198.51.100.1] | IP packet header		| [198.51.100.1] | IP packet header
	+------------------------------+ +--------------------------------+		+------------------------------+ +--------------------------------+
	^ | Source IP address |		^ | Source IP address |
	| | [192.0.2.1] |		| | [192.0.2.1] |
	| | Destination IP address |		| | Destination IP address |
	| | [198.51.100.1] |		| | [198.51.100.1] |
	+------------------------------+ +--------------------------------+		+------------------------------+ +--------------------------------+
	| PLAT | ^		| PLAT | ^
	skipping to change at page 16, line 49		skipping to change at page 17, line 42
	^ | Source IP address |		^ | Source IP address |
	| | [192.168.1.2] |		| | [192.168.1.2] |
	| | Destination IP address |		| | Destination IP address |
	| | [198.51.100.1] |		| | [198.51.100.1] |
	+------------------------------+ +--------------------------------+		+------------------------------+ +--------------------------------+
	| IPv4 client |		| IPv4 client |
	| [192.168.1.2/24] |		| [192.168.1.2/24] |
	+------------------------------+		+------------------------------+
	Delegated IPv6 prefix for client: 2001:db8:aaaa::/56		Delegated IPv6 prefix for client: 2001:db8:aaaa::/56
	Example 1. (Case of enabling only stateless XLATE on CLAT)
	Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT)		Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT)
	In the case that IPv6 prefix /64 is assigned to end users, the		In the case that IPv6 prefix /64 is assigned to end users, the
	function of NAT44 and Stateless XLATE should be enabled on CLAT.		function of NAT44 and Stateless XLATE should be enabled on CLAT.
	Because the CLAT does not have dedicated IPv6 prefix for translation.		Because the CLAT does not have dedicated IPv6 prefix for translation.
	Host & configuration value		Host & configuration value
	+-------------------------------+		+-------------------------------+
	| IPv4 server |		| IPv4 server |
	| [198.51.100.1] | IP packet header		| [198.51.100.1] | IP packet header
	+-------------------------------+ +-------------------------------+		+-------------------------------+ +-------------------------------+
	^ | Source IP address |		^ | Source IP address |
	| | [192.0.2.1] |		| | [192.0.2.1] |
	| | Destination IP address |		| | Destination IP address |
	| | [198.51.100.1] |		| | [198.51.100.1] |
	+-------------------------------+ +-------------------------------+		+-------------------------------+ +-------------------------------+
	| PLAT | ^		| PLAT | ^
	| IPv4 pool address | |		| IPv4 pool address | |
	| [192.0.2.1 - 192.0.2.100] | |		| [192.0.2.1 - 192.0.2.100] | |
	| PLAT-side XLATE IPv6 prefix | |		| PLAT-side XLATE IPv6 prefix | |
	| [2001:db8:1234::/96] | |		| [2001:db8:1234::/96] | |
	+-------------------------------+ +-------------------------------+		+-------------------------------+ +-------------------------------+
	^ | Source IP address |		^ | Source IP address |
	| | [2001:db8:aaaa:200:5e10:0:0] |		| | [2001:db8:aaaa:200:5e10:0:0] |
	| | Destination IP address |		| | Destination IP address |
	| | [2001:db8:1234::198.51.100.1] |		| | [2001:db8:1234::198.51.100.1] |
	| +-------------------------------+		+-------------------------------+ +-------------------------------+
	+-------------------------------+ ^		| CLAT Stateless XLATE function | ^
	| CLAT Stateless XLATE function | |
	| - - - - - - - - - - - - - - - | |		| - - - - - - - - - - - - - - - | |
	| PLAT-side XLATE IPv6 prefix | |		| PLAT-side XLATE IPv6 prefix | |
	| [2001:db8:1234::/96] | |		| [2001:db8:1234::/96] | |
	| CLAT-side XLATE IPv6 prefix | |		| CLAT-side XLATE IPv6 prefix | |
	| [2001:db8:aaaa::/64] | |		| [2001:db8:aaaa::/64] | |
	| CLAT-side XLATE IPv6 EUI-64 ID| |		| CLAT-side XLATE IPv6 EUI-64 ID| |
	| [02-00-5E-10-00-00-00-00] | |		| [02-00-5E-10-00-00-00-00] | |
	+ - - - - - - - - - - - - - - - + +-------------------------------+		+ - - - - - - - - - - - - - - - + +-------------------------------+
	| ^ | | Source IP address |		| ^ | | Source IP address |
	| | | | [10.255.255.1] |		| | | | [10.255.255.1] |
	| | | | Destination IP address |		| | | | Destination IP address |
	| | | | [198.51.100.1] |		| | | | [198.51.100.1] |
	+ - - - - - - - - - - - - - - - + +-------------------------------+		+ - - - - - - - - - - - - - - - + +-------------------------------+
	| CLAT NAT44 function | ^		| CLAT NAT44 function | ^
	| - - - - - - - - - - - - - - - | |		| - - - - - - - - - - - - - - - | |
	| NAT44 NATed address | |		| NAT44 NATed address | |
	| [10.255.255.1/32] | |		| [10.255.255.1/32] | |
	+-------------------------------+ |		+-------------------------------+ +-------------------------------+
	^ +-------------------------------+		^ | Source IP address |
	| | Source IP address |
	| | [192.168.1.2] |		| | [192.168.1.2] |
	| | Destination IP address |		| | Destination IP address |
	| | [198.51.100.1] |		| | [198.51.100.1] |
	+-------------------------------+ +-------------------------------+		+-------------------------------+ +-------------------------------+
	| IPv4 client |		| IPv4 client |
	| [192.168.1.2/24] |		| [192.168.1.2/24] |
	+-------------------------------+		+-------------------------------+
	Delegated IPv6 prefix for client: 2001:db8:aaaa::/64		Delegated IPv6 prefix for client: 2001:db8:aaaa::/64
	Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT)
	Authors' Addresses		Authors' Addresses
	Masataka Mawatari		Masataka Mawatari
	Japan Internet Exchange Co.,Ltd.		Japan Internet Exchange Co.,Ltd.
	KDDI Otemachi Building 19F, 1-8-1 Otemachi,		KDDI Otemachi Building 19F, 1-8-1 Otemachi,
	Chiyoda-ku, Tokyo 100-0004		Chiyoda-ku, Tokyo 100-0004
	JAPAN		JAPAN
	Phone: +81 3 3243 9579		Phone: +81 3 3243 9579
	Email: mawatari@jpix.ad.jp		Email: mawatari@jpix.ad.jp
End of changes. 21 change blocks.
	34 lines changed or deleted		45 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/