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

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

1、 ETSI TR 123 975 V15.0.0 (2018-06) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IPv6 migration guidelines (3GPP TR 23.975 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 123 975 V15.0.0 (2018-06)13GPP TR 23.975 version

2、15.0.0 Release 15Reference RTR/TSGS-0223975vf00 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of it

8、s Members. 3GPPTM and LTETMare trademarks 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. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 123 975 V15.0.0 (

9、2018-06)23GPP TR 23.975 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non

10、-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 (https:/ipr.etsi.org/). Pur

11、suant 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, essential to the present do

12、cument. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tra

13、dename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present documen

14、t may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.e

15、tsi.org/key/queryform.asp. Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ 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 n

16、ot“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 123 975 V15.0.0 (2018-06)33GPP TR 23.975 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 De

17、finitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Baseline Architecture for IPv4 and IPv6 Co-existence 8g35 IPv6 migration scenarios 9g35.1 Scenario 1: Dual-stack connectivity with Limited Public IPv4 Address Pools 9g35.2 Scenario 2: Dual Stack connectivity with L

18、imited Private IPv4 Address Pools 10g35.3 Scenario 3: UEs with IPv6-only connection and applications using IPv6 10g35.4 Scenario 4: IPv4 applications running on a Dual-stack host with an assigned IPv6 prefix and a shared IPv4 address and having to access IPv4 services . 10g36 High level requirements

19、 . 11g37 Solutions and functional flows description 11g37.1 Solution 1 Dual-stack deployment combined with NAPT44 11g37.1.1 Overview 11g37.1.2 Description 11g37.1.2.1 Dual-stack deployment 11g37.1.2.2 NAPT44 deployment options 11g37.1.2.2.1 Basic deployments . 11g37.1.2.2.2 Deployments with overlapp

20、ing RFC 1918 26 address spaces 12g37.1.2.2.3 Identity considerations when using overlapping RFC 1918 26 address spaces 13g37.1.3 Functional Description 13g37.1.4 Information flows . 13g37.1.5 Evaluation . 13g37.1.6 Applicability . 14g37.2 Transition Solution: Gateway-Initiated Dual-Stack Lite 14g37.

21、2.1 GI-DS-lite Overview. 14g37.2.2 GI-DS-lite Evaluation . 16g37.2.3 GI-DS-lite Applicability . 18g37.3 Solution 3 - MS/UE IPv6-only deployment with stateful NAT64 support. 18g37.3.1 Overview 18g37.3.2 Description 19g37.3.3 Functional Description 19g37.3.4 Server Flow Example 20g37.3.5 Evaluation .

22、20g37.3.6 Applicability . 21g38 Evaluation . 21g39 Summary 21g310 Recommendations 21g3Annex A: Reference Scenarios for NAT in the EPC . 23g3A.1 UE and AF In the same Address Realm . 23g3A.2 NAT between UE and AF 24g3ETSI ETSI TR 123 975 V15.0.0 (2018-06)43GPP TR 23.975 version 15.0.0 Release 15A.2.1

23、 Overlapping IPv4 address realms . 25g3Annex B: Overview of Solutions for IPv6 Transition . 28g3B.1 Solution 1 - Dual-Stack Lite Architecture 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 29g

24、3B.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 binding 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 techniqu

25、es 32g3B.2.9 Applicability . 32g3B.2.10 Evaluation. 32g3B.3 Solution 3 - Protocol translation . 33g3B.4 Solution 4 - Per-interface NAT44 34g3B.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 D

26、escription . 35g3B.7.3 Service Flow Example 36g3B.7.4 Evaluation. 37g3B.7.5 Applicability . 37g3Annex C: Building Block: Dual-Stack EPS Bearer Contexts in EPS/GPRS 38g3C.1 Description . 38g3C.2 Functional Description . 38g3C.3 Information flows . 38g3C.4 Applicability . 39g3Annex D: Change history 4

27、0g3History 41g3ETSI ETSI TR 123 975 V15.0.0 (2018-06)53GPP TR 23.975 version 15.0.0 Release 15Foreword This Technical Report has been produced 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

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

29、for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document

30、. Introduction 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. ETSI ETSI TR 123 975

31、 V15.0.0 (2018-06)63GPP TR 23.975 version 15.0.0 Release 151 Scope 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 o

32、f 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, a

33、nd 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 The following documents contain provisions w

34、hich, 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 referen

35、ce, 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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC

36、6333: “Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion“. 3 IETF RFC 6346: “The Address plus Port (A+P) Approach to the IPv4 Address Shortage“. 4 http:/tools.ietf.org/html/draft-boucadair-port-range-02. 5 http:/tools.ietf.org/html/draft-bajko-pripaddrassign-01. 6 IETF RFC 6144: “Frame

37、work for IPv4/IPv6 Translation“. 7 IETF RFC 6535: “Dual-Stack Hosts Using “Bump-in-the-Host“ (BIH)“. 8 IETF RFC 6145: “IP/ICMP Translation Algorithm“. 9 3GPP TS 23.401: “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access“. 10 3GPP

38、 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., Haberman, B., Woodyatt, J., Lee, Y., and R. Bush: “Dual-stack Lite broadband deployments post IPv4 exhaustion“, IETF draft,

39、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 3GPP TR 23.981: “Interworking aspects and migration scenarios for IPv

40、4 based IMS implementations“. ETSI ETSI TR 123 975 V15.0.0 (2018-06)73GPP TR 23.975 version 15.0.0 Release 1515 Void. 16 Void. 17 IETF RFC 6146: “Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers“. 18 IETF RFC 6147: “DNS64: DNS Extensions for Network Address

41、Translation from IPv6 Clients to IPv4 Servers“. 19 IETF RFC 6619: “Scalable Operation of Address Translators with Per-Interface Bindings“. 20 IETF RFC 4364: “BGP/MPLS IP Virtual Private Networks (VPNs)“. 21 3GPP TS 23.203: “Policy and charging control architecture“. 22 Void. 23 IETF Internet-Draft,

42、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“, VTC07-Spring, Dublin Ireland, 20-25 April 2007. 25 3G

43、PP TS 24.008: “Mobile radio interface 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

44、 Stack Hosts Using “Bump-in-the-API“ (BIA)“. 30 IETF RFC 2767: “Dual Stack Hosts using the “Bump-In-the-Stack“ Technique (BIS)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply.

45、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 circuit: as used by RFC 4364 20, term to refer generally to means of attaching to a r

46、outer, 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 a

47、ll 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 other CE devices using the same VPN, without the need to be routing peers of each othe

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

49、: 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 V15.0.0 (2018-06)83GPP TR 23.975 version 15.0.0 Release 153.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 document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. N