ETSI TR 123 975-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE IPv6 migration guidelines (V14 1 0 3GPP TR 23.pdf

《ETSI TR 123 975-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE IPv6 migration guidelines (V14 1 0 3GPP TR 23.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 123 975-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE IPv6 migration guidelines (V14 1 0 3GPP TR 23.pdf（43页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 123 975 V14.0.0 (2017-05) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IPv6 migration guidelines (3GPP TR 23.975 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 123 975 V14.0.0 (2017-05)13GPP TR 23.975 version

2、14.0.0 Release 14Reference RTR/TSGS-0223975ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 78

3、03/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the pri

4、or written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present

5、document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to o

6、ne of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The conte

7、nt of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Ma

8、rks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GS

9、M Association. ETSI ETSI TR 123 975 V14.0.0 (2017-05)23GPP TR 23.975 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available

10、 for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (h

11、ttps:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, es

12、sential to the present document. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted

13、as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“

14、 and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 123 975 V14.0.0 (2017-05)33GPP TR 23.975 version 14.

15、0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Baseline Architecture for IPv4 and IPv6 Co-existence 8g35

16、 IPv6 migration scenarios 10g35.1 Scenario 1: Dual-stack connectivity with Limited Public IPv4 Address Pools 10g35.2 Scenario 2: Dual Stack connectivity with Limited Private IPv4 Address Pools 10g35.3 Scenario 3: UEs with IPv6-only connection and applications using IPv6 10g35.4 Scenario 4: IPv4 appl

17、ications running on a Dual-stack host with an assigned IPv6 prefix and a shared IPv4 address and having to access IPv4 services . 11g36 High level requirements . 11g37 Solutions and functional flows description 11g37.1 Solution 1 Dual-stack deployment combined with NAPT44 11g37.1.1 Overview 11g37.1.

18、2 Description 11g37.1.2.1 Dual-stack deployment 11g37.1.2.2 NAPT44 deployment options 12g37.1.2.2.1 Basic deployments . 12g37.1.2.2.2 Deployments with overlapping RFC 1918 26 address spaces 12g37.1.2.2.3 Identity considerations when using overlapping RFC 1918 26 address spaces 13g37.1.3 Functional D

19、escription 13g37.1.4 Information flows . 14g37.1.5 Evaluation . 14g37.1.6 Applicability . 15g37.2 Transition Solution: Gateway-Initiated Dual-Stack Lite 15g37.2.1 GI-DS-lite Overview. 15g37.2.2 GI-DS-lite Evaluation . 17g37.2.3 GI-DS-lite Applicability . 19g37.3 Solution 3 - MS/UE IPv6-only deployme

20、nt with stateful NAT64 support. 19g37.3.1 Overview 19g37.3.2 Description 19g37.3.3 Functional Description 19g37.3.4 Server Flow Example 20g37.3.5 Evaluation . 21g37.3.6 Applicability . 22g38 Evaluation . 22g39 Summary 22g310 Recommendations 22g3Annex A: Reference Scenarios for NAT in the EPC . 23g3A

21、.1 UE and AF In the same Address Realm . 23g3ETSI ETSI TR 123 975 V14.0.0 (2017-05)43GPP TR 23.975 version 14.0.0 Release 14A.2 NAT between UE and AF 24g3A.2.1 Overlapping IPv4 address realms . 25g3Annex B: Overview of Solutions for IPv6 Transition . 28g3B.1 Solution 1 - Dual-Stack Lite Architecture

22、 28g3B.1.1 Solution 1 Description 28g3B.1.1.1 Plain IPv6 encapsulation in 3GPP architecture . 28g3B.1.1.2 GRE encapsulation . 29g3B.1.1.3 GTP encapsulation 29g3B.1.1.4 DSMIP6 29g3B.2 Solution 2 - A+P architecture . 30g3B.2.4 Port Range Router (PRR) function . 30g3B.2.4.1 General 30g3B.2.4.2 PRR in b

23、inding mode 30g3B.2.4.3 PRR in stateless mode 31g3B.2.6 Requirement on UEs 31g3B.2.7 Updating legacy UEs 32g3B.2.8 Co-existence with other transition techniques 32g3B.2.9 Applicability . 32g3B.2.10 Evaluation. 32g3B.3 Solution 3 - Protocol translation . 33g3B.4 Solution 4 - Per-interface NAT44 34g3B

24、.4.1 Overview 34g3B.4.2 Evaluation. 34g3B.4.3 Applicability . 35g3B.5 Void 35g3B.6 Void 35g3B.7 Solution 7 - BIH/NAT64 35g3B.7.1 Overview 35g3B.7.2 Solution Description . 36g3B.7.3 Service Flow Example 36g3B.7.4 Evaluation. 37g3B.7.5 Applicability . 37g3Annex C: Building Block: Dual-Stack EPS Bearer

25、 Contexts in EPS/GPRS 39g3C.1 Description . 39g3C.2 Functional Description . 39g3C.3 Information flows . 40g3C.4 Applicability . 40g3Annex D: Change history 41g3History 42g3ETSI ETSI TR 123 975 V14.0.0 (2017-05)53GPP TR 23.975 version 14.0.0 Release 14Foreword This Technical Report has been produced

26、 by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change

27、 of Release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substanc

28、e, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction With the depletion of IPv4 addresses and the development of data service, demands for deploying IPv6 are higher than before. Th

29、is document analyzes different IPv6 migration scenarios and applicable mechanisms as well as identifies impacts on 3GPP network elements. ETSI ETSI TR 123 975 V14.0.0 (2017-05)63GPP TR 23.975 version 14.0.0 Release 141 Scope The technical report identifies various scenarios of transition to IPv6 and

30、 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 migratio

31、n 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 recommendation

32、s on IPv6 transition and co-existence of IPv4 and IPv6 and identify if any normative work is needed. 2 References 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 p

33、ublication, 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

34、refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 http:/tools.ietf.org/html/draft-ietf-softwire-dual-stack-lite-01. 3 http:/tools.ietf.org/html/draft-ymbk-aplusp-04. 4 http:/tools.ietf.org/html/draft-b

35、oucadair-port-range-02. 5 http:/tools.ietf.org/html/draft-bajko-pripaddrassign-01. 6 http:/tools.ietf.org/html/draft-ietf-behave-v6v4-framework-00. 7 http:/www.ietf.org/id/draft-ietf-behave-v4v6-bih-00.txt. 8 http:/tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-00. 9 3GPP TS 23.401: “General Packe

36、t Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access“. 10 3GPP TS 23.402: “Architecture enhancements for non-3GPP accesses“. 11 3GPP TS 23.060: “General Packet Radio Service (GPRS) Service description; Stage 2“. 12 Durand, A., Droms, R., Haberma

37、n, 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

38、-gateway-init-ds-lite-03 (work in progress). 14 3GPP TR 23.981: “Interworking aspects and migration scenarios for IPv4 based IMS implementations“. ETSI ETSI TR 123 975 V14.0.0 (2017-05)73GPP TR 23.975 version 14.0.0 Release 1415 http:/www.ietf.org/internet-drafts/draft-huang-behave-rfc2767bis-00.txt

39、. 16 http:/www.ietf.org/internet-drafts/draft-huang-behave-rfc3338bis-00.txt. 17 IETF Internet-Draft, draft-ietf-behave-v6v4-xlate-stateful-12: “ NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers“ work in progress. 18 IETF Internet-Draft, draft-ietf-behave-dns64-05: “

40、DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers “work in progress. 19 IETF Internet-Draft, draft-arkko-dual-stack-extra-lite-05: “Scalable Operations of Address Translators with Per-Interface Bindings“, work in progress. 20 IETF RFC 4364: “BGP/MPLS IP Virtual

41、Private Networks (VPNs)“. 21 3GPP TS 23.203: “Policy and charging control architecture“. 22 IETF Internet-Draft, draft-boucadair-behave-ipv6-portrange: “Flexible IPv6 Migration Scenarios in the Context of IPv4 Address Shortage“ work in progress. 23 IETF Internet-Draft, draft-boucadair-behave-bittorr

42、ent-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“, VTC07-Spring, Dublin Ireland, 20-25 April 2007. 25 3GPP TS 24.008: “Mobile radio in

43、terface Layer 3 specification; Core network protocols; Stage 3“. 26 IETF RFC 1918: “Address Allocation for Private Internets“. 27 IETF RFC 2784: “Generic Routing Encapsulation (GRE)“. 28 IETF RFC 2890: “Key and Sequence Number Extensions to GRE“. 29 IETF RFC 3338: “Dual Stack Hosts Using “Bump-in-th

44、e-API“ (BIA)“. 30 IETF RFC 2767: “Dual Stack Hosts using the “Bump-In-the-Stack“ Technique (BIS)“. NOTE: The Italicised references are individual IETF drafts which have not yet been endorsed by IETF working groups. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the pres

45、ent document, the terms and definitions given in TR 21.905 1 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 1. NAT: A function which provides NAT44, NAPT44, NAT64, NAPT64 or combinations of these. Attachment

46、 circuit: as used by RFC 4364 20, 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

47、, IPSec tunnels, etc. An attachment circuit identifies uniquely the MPLS VPN used by all traffic using that circuit. CE: as used by RFC 4364 20, 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

48、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

49、route traffic in the VPN, then they are routing peers of the directly attached PEs. PE: as used by RFC 4364 20, stands for Provider Edge router. PEs use MPLS to tunnel traffic among each other enabling IP traffic between the CEs attached to them. ETSI ETSI TR 123 975 V14.0.0 (2017-05)83GPP TR 23.975 version 14.0.0 Release 143.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present docum