Content for TR 23.975 Word version: 17.0.0
0 Introduction p. 5
With the depletion of IPv4 addresses and the development of data service, demands for deploying IPv6 are higher than before. This document analyzes different IPv6 migration scenarios and applicable mechanisms as well as identifies impacts on 3GPP network elements.
1 Scope p. 6
The technical report identifies various scenarios of transition to IPv6 and co-existence of IPv4 and IPv6, deployment options and impacts on 3GPP network elements. In particular:
- Identify the transition and co-existence scenarios of interest for operators and the respective assumptions and requirements.
- Analyze existing IP address allocation mechanism for IPv6 migration if necessary.
- Investigate IPv6 transition mechanisms for the scenarios identified during the study and investigate their applicability for 3GPP network, and identify the compatibility among applicable transition mechanisms.
- Identify any impact on 3GPP network elements.
- Provide recommendations on IPv6 transition and co-existence of IPv4 and IPv6 and identify if any normative work is needed.
2 References p. 6
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
RFC 6333: "Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion".
[3]
RFC 6346: "The Address plus Port (A+P) Approach to the IPv4 Address Shortage".
[4]
[5]
[6]
RFC 6144: "Framework for IPv4/IPv6 Translation".
[7]
RFC 6535: "Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)".
[8]
RFC 6145: "IP/ICMP Translation Algorithm".
[9]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[10]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[11]
TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
[12]
Durand, A., Droms, R., Haberman, B., Woodyatt, J., Lee, Y., and R. Bush: "Dual-stack Lite broadband deployments post IPv4 exhaustion", IETF draft, draft-ietf-softwire-dual-stack-lite-07 (work in progress).
[13]
Brockners, F., Gundavelli, S., Speicher, S., Ward, D: "Gateway Initiated Dual-Stack Lite Deployment", draft-ietf-softwire-gateway-init-ds-lite-03 (work in progress).
[14]
TR 23.981: "Interworking aspects and migration scenarios for IPv4 based IMS implementations".
[15] Void.
[16] Void.
[17]
RFC 6146: "Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers".
[18]
RFC 6147: "DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers".
[19]
RFC 6619: "Scalable Operation of Address Translators with Per-Interface Bindings".
[20]
RFC 4364: "BGP/MPLS IP Virtual Private Networks (VPNs)".
[21]
TS 23.203: "Policy and charging control architecture".
[22] Void.
[23]
draft-boucadair-behave-bittorrent-portrange-02 "Behaviour of Bit Torrent service in an IP Shared Address Environment" work in progress.
[24]
Haverinen, H., Siren, J., and P. Eronen: "Energy Consumption of Always-On Applications in WCDMA Networks", VTC'07-Spring, Dublin Ireland, 20-25 April 2007.
[25]
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[26]
RFC 1918: "Address Allocation for Private Internets".
[27]
RFC 2784: "Generic Routing Encapsulation (GRE)".
[28]
RFC 2890: "Key and Sequence Number Extensions to GRE".
[29]
RFC 3338: "Dual Stack Hosts Using "Bump-in-the-API" (BIA)".
[30]
RFC 2767: "Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)".
3 Definitions, symbols and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
NAT:
A function which provides NAT44, NAPT44, NAT64, NAPT64 or combinations of these.
Attachment circuit:
as used by RFC 4364, term to refer generally to means of attaching to a router, such as: PPP connections, ATM Virtual Circuits (VCs), Frame Relay VCs, Ethernet interfaces, Virtual Local Area Networks (VLANs) on Ethernet interfaces, GRE tunnels, Layer 2 Tunnelling Protocol (L2TP) tunnels, IPSec tunnels, etc. An attachment circuit identifies uniquely the MPLS VPN used by all traffic using that circuit.
CE:
as used by RFC 4364, stands for Customer Edge router or Customer Edge device. It represents an IP device using a BGP/MPLS IP Virtual Private Networks (VPN) to communicate with other CE devices using the same VPN, without the need to be routing peers of each other and without visibility of MPLS or the MPLS backbone providing connectivity between CEs in different sites. CEs are connected to PEs using attachment circuits. If CEs use dynamic routing protocols (CE routers) to route traffic in the VPN, then they are routing peers of the directly attached PEs.
PE:
as used by RFC 4364, stands for Provider Edge router. PEs use MPLS to tunnel traffic among each other enabling IP traffic between the CEs attached to them.
3.2 Abbreviations p. 8
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
NAPT44
Network Address and Port Translation IPv4 to IPv4
NAT44
Network Address Translation IPv4 to IPv4
NAPT64
Network Address and Port Translation IPv6 to IPv4
NAT64
Network Address Translation IPv6 to IPv4
PCC
Policy and Charging Control
