idnits 2.17.1 draft-farinacci-lisp-mobile-network-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 21 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 28, 2021) is 941 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Unused Reference: 'RFC1700' is defined on line 774, but no explicit reference was found in the text == Unused Reference: 'RFC8060' is defined on line 794, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1700 (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 6833 (Obsoleted by RFC 9301) == Outdated reference: A later version (-16) exists of draft-ietf-lisp-eid-anonymity-11 == Outdated reference: A later version (-13) exists of draft-ietf-lisp-eid-mobility-08 == Outdated reference: A later version (-15) exists of draft-ietf-lisp-mn-10 == Outdated reference: A later version (-14) exists of draft-ietf-lisp-predictive-rlocs-08 == Outdated reference: A later version (-38) exists of draft-ietf-lisp-rfc6830bis-36 == Outdated reference: A later version (-31) exists of draft-ietf-lisp-rfc6833bis-30 == Outdated reference: A later version (-29) exists of draft-ietf-lisp-sec-23 == Outdated reference: A later version (-15) exists of draft-ietf-lisp-te-09 Summary: 3 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Farinacci 3 Internet-Draft lispers.net 4 Intended status: Experimental P. Pillay-Esnault 5 Expires: April 1, 2022 Independent 6 U. Chunduri 7 Intel Corporation 8 September 28, 2021 10 LISP for the Mobile Network 11 draft-farinacci-lisp-mobile-network-13 13 Abstract 15 This specification describes how the LISP architecture and protocols 16 can be used in a LTE/5G mobile network to support session survivable 17 EID mobility. A recommendation is provided to SDOs on how to 18 integrate LISP into the mobile network. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on April 1, 2022. 37 Copyright Notice 39 Copyright (c) 2021 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 56 3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 7 57 4. Addressing and Routing . . . . . . . . . . . . . . . . . . . 14 58 5. gNB/eNodeB LISP Functionality . . . . . . . . . . . . . . . . 14 59 6. UPF/pGW LISP Functionality . . . . . . . . . . . . . . . . . 15 60 7. Compatible Data-Plane using GTP . . . . . . . . . . . . . . . 16 61 8. Roaming and Packet Loss . . . . . . . . . . . . . . . . . . . 16 62 9. Mobile Network LISP Mapping System . . . . . . . . . . . . . 16 63 10. LISP Over the 5G N3/N6/N9 Interfaces . . . . . . . . . . . . 17 64 11. Multicast Considerations . . . . . . . . . . . . . . . . . . 18 65 12. Security Considerations . . . . . . . . . . . . . . . . . . . 19 66 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 67 14. SDO Recommendations . . . . . . . . . . . . . . . . . . . . . 19 68 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 69 15.1. Normative References . . . . . . . . . . . . . . . . . . 19 70 15.2. Informative References . . . . . . . . . . . . . . . . . 20 71 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 23 72 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 24 73 B.1. Changes to draft-farinacci-lisp-mobile-network-12 . . . . 24 74 B.2. Changes to draft-farinacci-lisp-mobile-network-12 . . . . 24 75 B.3. Changes to draft-farinacci-lisp-mobile-network-11 . . . . 24 76 B.4. Changes to draft-farinacci-lisp-mobile-network-10 . . . . 24 77 B.5. Changes to draft-farinacci-lisp-mobile-network-09 . . . . 24 78 B.6. Changes to draft-farinacci-lisp-mobile-network-08 . . . . 24 79 B.7. Changes to draft-farinacci-lisp-mobile-network-07 . . . . 25 80 B.8. Changes to draft-farinacci-lisp-mobile-network-06 . . . . 25 81 B.9. Changes to draft-farinacci-lisp-mobile-network-05 . . . . 25 82 B.10. Changes to draft-farinacci-lisp-mobile-network-04 . . . . 25 83 B.11. Changes to draft-farinacci-lisp-mobile-network-03 . . . . 25 84 B.12. Changes to draft-farinacci-lisp-mobile-network-02 . . . . 25 85 B.13. Changes to draft-farinacci-lisp-mobile-network-01 . . . . 25 86 B.14. Changes to draft-farinacci-lisp-mobile-network-00 . . . . 26 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 89 1. Introduction 91 The LISP architecture and protocols [I-D.ietf-lisp-rfc6830bis] 92 introduces two new numbering spaces, Endpoint Identifiers (EIDs) and 93 Routing Locators (RLOCs) which provide an architecture to build 94 overlays on top of the underlying Internet. Mapping EIDs to RLOC- 95 sets is accomplished with a Mapping Database System. By using a 96 level of indirection for routing and addressing, separating an 97 address identifier from its location can allow flexible and scalable 98 mobility. By assigning EIDs to mobile devices and RLOCs to the 99 network nodes that support such mobile devices, LISP can provide 100 seamless mobility. 102 For a reading audience unfamiliar with LISP, a brief tutorial level 103 document is available at [I-D.ietf-lisp-introduction]. 105 This specification will describe how LISP can be used to provide 106 layer-3 mobility within and across an LTE [LTE401-3GPP] [LTE402-3GPP] 107 and 5G [ARCH5G-3GPP] [PROC5G-3GPP] mobile network. 109 The following are the design requirements: 111 1. Layer-3 address mobility is provided within a mobile network RAN 112 supported by a UPF/pGW region (intra-UPF/pGW) as well as across 113 UPF/pGW regions (inter-UPF/pGW). 115 2. UE nodes can get layer-3 address mobility when roaming off the 116 mobile network to support Fixed Mobile Convergence [FMC]. 118 3. Transport layer session survivability exists while roaming 119 within, across, and off of the mobile network. 121 4. No address management is required when UEs roam. EID addresses 122 are assigned to UEs at subscription time. EIDs can be reassigned 123 when UE ownership changes. 125 5. The design will make efficient use of radio resources thereby not 126 adding extra headers to packets that traverse the RAN. 128 6. The design can support IPv4 unicast and multicast packet delivery 129 and will support IPv6 unicast and multicast packet delivery. 131 7. The design will allow use of both the GTP [GTPv1-3GPP] 132 [GTPv2-3GPP] and LISP [I-D.ietf-lisp-rfc6830bis] data-planes 133 while using the LISP control-plane and mapping system. 135 8. The design can be used for either 4G/LTE and 5G mobile networks 136 and may be able to support interworking between the different 137 mobile networks. 139 9. The LISP architecture provides a level of indirection for routing 140 and addressing. From a mobile operator's perspective, these 141 mechanisms provide advantages and efficiencies for the URLLC, 142 FMC, and mMTC use cases. See Section 2 for definitions and 143 references of these use cases. 145 The goal of this specification is take advantage of LISP's non- 146 disruptive incremental deployment benefits. This can be achieved by 147 changing the fewest number of components in the mobile network. The 148 proposal suggests adding LISP functionality only to gNB/eNodeB and 149 UPF/pGW nodes. There are no hardware or software changes to the UE 150 devices or the RF-based RAN to realize this architecture. The LISP 151 mapping database system is deployed as an addition to the mobile 152 network and does not require any coordination with existing 153 management and provisioning systems. 155 Similar ID Oriented Networking (ION) mechanisms for the 5G 156 [ARCH5G-3GPP] [PROC5G-3GPP] mobile network are also being considered 157 in other standards organizations such as ETSI [ETSI-NGP] and ITU 158 [ITU-IMT2020]. The NGMN Alliance describes Locator/ID separation as 159 an enabler to meet Key Performance Indicator Requirements [NGMN]. 161 2. Definition of Terms 163 xTR: Is a LISP node in the network that runs the LISP control-plane 164 and data-plane protocols according to [I-D.ietf-lisp-rfc6830bis] 165 and [I-D.ietf-lisp-rfc6833bis]. A formal definition of an xTR can 166 be found in [I-D.ietf-lisp-rfc6830bis]. In this specification, a 167 LISP xTR is a node that runs the LISP control-plane with the GTP 168 data-plane. 170 EID: Is an Endpoint Identifier. EIDs are assigned to UEs and other 171 Internet nodes in LISP sites. A formal definition of an EID can 172 be found in [I-D.ietf-lisp-rfc6830bis]. 174 UE EID: A UE can be assigned an IPv4 and/or an IPv6 address either 175 statically, or dynamically as is the procedure in the mobile 176 network today. These IP addresses are known as LISP EIDs and are 177 registered to the LISP mapping system. These EIDs are used as the 178 source address in packets that the UE originates. 180 RLOC: Is an Routing Locator. RLOCs are assigned to gNB/eNodeBs and 181 UPF/pGWs and other LISP xTRs in LISP sites. A formal definition 182 of an RLOC can be found in [I-D.ietf-lisp-rfc6830bis]. 184 Mapping System: Is the LISP mapping database system that stores EID- 185 to-RLOC mappings. The mapping system is centralized for use and 186 distributed to scale and secure deployment. LISP Map-Register 187 messages are used to publish mappings and LISP Map-Requests 188 messages are used to lookup mappings. LISP Map-Reply messages are 189 used to return mappings. EID-records are used as lookup keys, and 190 RLOC-records are returned as a result of the lookup. Details can 191 be found in [RFC6833]. 193 LISP Control-Plane: In this specification, a LISP xTR runs the LISP 194 control-plane which originates, consumes, and processes Map- 195 Request, Map-Register, Map-Reply, and Map-Notify messages. 197 RAN: Radio Access Network where UE nodes connect to gNB/eNodeB nodes 198 via radios to get access to the Internet. 200 EPC: Evolved Packet Core [EPS-3GPP] system is the part of the mobile 201 network that allows the RAN to connect to a data packet network. 202 The EPC is a term used for the 4G/LTE mobile network. 204 NGC: Next Generation Core [EPS-3GPP] system is the part of the 5G 205 mobile network that allows the RAN to connect to a data packet 206 network. The NGC is roughly equivalent to the 4G EPC. 208 GTP: GTP [GTPv1-3GPP] [GTPv2-3GPP] is the UDP tunneling mechanism 209 used in the LTE/4G and 5G mobile network. 211 UE: User Equipment as defined by [GPRS-3GPP] which is typically a 212 mobile phone. The UE is connected to the network across the RAN 213 to gNB/eNodeB nodes. 215 eNodeB: Is the device defined by [GPRS-3GPP] which borders the RAN 216 and connects UEs to the EPC in a 4G/LTE mobile network. The 217 eNodeB nodes are termination point for a GTP tunnel and are LISP 218 xTRs. The equivalent term in the 5G mobile network is "(R)AN" and 219 "5G-NR", or simply "gNB". In this document, the two terms are 220 used interchangeably. 222 pGW: Is the PDN-Gateway as defined by [GPRS-3GPP] which connects the 223 EPC in a 4G/LTE mobile network to the Internet. The pGW nodes are 224 termination point for a GTP tunnel and is a LISP xTR. The 225 equivalent user/data-plane term in the 5G mobile network is the 226 "UPF", which also has the capability to chain network functions. 227 In this document, the two terms are used interchangeably to mean 228 the border point from the EPC/NGC to the Internet. 230 URLLC: Ultra-Reliable and Low-Latency provided by the 5G mobile 231 network for the shortest path between UEs [NGMN]. 233 FMC: Fixed Mobile Convergence [FMC] is a term used that allows a UE 234 device to move to and from the mobile network. By assigning a 235 fixed EID to a UE device, LISP supports transport layer continuity 236 between the mobile network and a fixed infrastructure such as a 237 WiFi network. 239 mMTC: Massive Machine-Type Services [mMTC] is a term used to refer 240 to using the mobile network for large-scale deployment of Internet 241 of Things (IoT) applications. 243 3. Design Overview 245 LISP will provide layer-3 address mobility based on the procedures in 246 [I-D.ietf-lisp-eid-mobility] where the EID and RLOCs are not co- 247 located. In this design, the EID is assigned to the UE device and 248 the RLOC(s) are assigned to gNB/eNodeB nodes. So any packets going 249 to a UE are always encapsulated to the gNB/eNodeB that associates 250 with the UE. For data flow from the UE to any EIDs (or destinations 251 to non-LISP sites) that are outside of the NGC/EPC, use the RLOCs of 252 the UPF/pGW nodes so the UPF/pGW can send packets into the Internet 253 core (unencapsulated). 255 The following procedures are used to incorporate LISP in the NGC/EPC: 257 o UEs are assigned EIDs. They usually never change. They identify 258 the mobile device and are used for transport connections. If 259 privacy for EIDs is desired, refer to details in 260 [I-D.ietf-lisp-eid-anonymity]. 262 o gNB/eNodeB nodes are LISP xTRs. They have GTP, and optionally 263 LISP, tunnels to the UPF/pGW nodes. The gNB/eNodeB is the RLOC 264 for all EIDs assigned to UE devices that are attached to the gNB/ 265 eNodeB. 267 o UPF/pGW nodes are LISP xTRs. They have GTP, and optionally LISP, 268 tunnels to the gNB/eNodeB nodes. The UPF/pGW is the RLOC for all 269 traffic destined for the Internet. 271 o The LISP mapping system runs in the NGC/EPC. It maps EIDs to 272 RLOC-sets. 274 o Traffic from a UE to UE within a UPF/pGW region can be 275 encapsulated from gNB/eNodeB to another gNB/eNodeB or via the UPF/ 276 pGW, acting as an RTR [I-D.ietf-lisp-rfc6830bis], to provide data- 277 plane policy. 279 o Traffic from a UE to UE across a UPF/pGW region have these options 280 for data flow: 282 1. Encapsulation by a gNB/eNodeB in one region to a gNB/eNodeB in 283 another region. 285 2. Encapsulation by a gNB/eNodeB in one region to a UPF/pGW in 286 the same region and then the UPF/pGW reencapsulates to a gNB/ 287 eNodeB in another region. 289 3. Encapsulation by a gNB/eNodeB in one region to a UPF/pGW in 290 another region and then the UPF/pGW reencapsulates to a gNB/ 291 eNodeB in its same region 293 4. Encapsulation by the gNB/eNodeB to a LISP xTR outside of the 294 mobile network. An xTR outside of the mobile network could be 295 a router in a data-center, a router at the edge of a WAN at a 296 remote branch, or a WiFi access-point, and even a gNB/eNodeB 297 in another carrier's mobile network. All these deployment 298 options are to be considered for future architectures. 300 o Note when encapsulation happens between a gNB/eNodeB and a UPF/ 301 pGW, GTP is used as the data-plane and when encapsulation between 302 two gNB/eNodeBs occur, LISP can be used as the data-plane when 303 there is no X2 interface [X2-3GPP] between the gNB/eNodeB nodes. 305 o The UPF/pGW nodes register their RLOCs for a default EID-prefix to 306 the LISP mapping system. This is done so gNB/eNodeB nodes can 307 find UPF/pGW nodes to encapsulate to. 309 o The gNB/eNodeB nodes register EIDs to the mapping system for the 310 UE nodes. The registration occurs when gNB/eNodeB nodes discover 311 the layer-3 addresses of the UEs that connect to them. The gNB/ 312 eNodeB nodes register multiple RLOCs associated with the EIDs to 313 get multi-homing and path diversity benefits from the NGC/EPC 314 network. 316 o When a UE moves off a gNB/eNodeB, the gNB/eNodeB node deregisters 317 itself as an RLOC for the EID associated with the UE. 319 o Optionally, and for further study for future architectures, the 320 gNB/eNodeB or UPF/pGW could encapsulate to an xTR that is outside 321 of the NGC/EPC network. They could encapsulate to a LISP CPE 322 router at a branch office, a LISP top-of-rack router in a data 323 center, a LISP wifi access-point, LISP border routers at a hub 324 site, and even a LISP router running in a VM or container on a 325 server. 327 The following diagram illustrates the LTE mobile network topology and 328 structure [LTE401-3GPP] [LTE402-3GPP]: 330 (--------------------------------------------) 331 ( ) 332 ( Internet ) 333 ( ) 334 (--------------------------------------------) 335 | | 336 | | 337 (---------|---------) (---------|---------) 338 ( UPF-pGW ) ( UPF-pGW ) 339 ( ) ( ) 340 ( NGC/EPC ) ( NGC/EPC ) 341 ( ) ( ) 342 ( gNB-eNB gNB-eNB ) ( gNB-eNB gNB-eNB ) 343 (---/--\-----/--\---) (---/--\-----/--\---) 344 / \ / \ / \ / \ 345 / \ / \ / \ / \ 346 / \ / \ 347 / RAN \ / RAN \ 348 / \ / \ 349 ( UE UE UE ) ( UE UE UE ) 351 LTE/5G Mobile Network Architecture 353 The following diagram illustrates how LISP is used on the mobile 354 network: 356 (1) IPv6 EIDs are assigned to UEs. 357 (2) RLOCs assigned to gNB/eNodeB nodes are [a1,a2], [b1,b2], [c1,c2], [d1,d2] 358 on their uplink interfaces. 359 (3) RLOCs assigned to UPF/pGW nodes are [p1,p2], [p3,p4]. 360 (4) RLOCs can be IPv4 or IPv6 addresses or mixed RLOC-sets. 362 (--------------------------------------------) 363 ( ) 364 ( Internet ) 365 ( ) 366 (--------------------------------------------) 367 | | 368 | | 369 (---------|---------) (---------|---------) 370 ( UPF-pGW ) ( UPF-pGW ) 371 ( p1 p2 ) ( p3 p4 ) 372 ( ) ( ) 373 ( NGC/EPC ) ( NGC/EPC ) 374 ( ) ( ) 375 ( a1 a2 b1 b2 ) ( c1 c2 d1 d2 ) 376 ( gNB-eNB gNB-eNB ) ( gNB-eNB gNB-eNB ) 377 (---/--\-----/--\---) (---/--\-----/--\---) 378 / \ / \ / \ / \ 379 / \ / \ / \ / \ 380 / \ / \ 381 / RAN \ / RAN \ 382 / \ / \ 383 ( UE UE UE ) ( UE UE UE ) 384 EIDs: a::1 b::1 c::1 x::1 y::1 z::1 386 Mobile Network with EID/RLOC Assignment 388 The following table lists the EID-to-RLOC entries that reside in the LISP 389 Mapping System when the above UEs are are attached to the 4 gNB/eNodeBs: 391 EID-Record RLOC-Record Commentary Footnote 392 0::/0 [p1,p2,p3 p4] gNB/eNodeBs encap to p1-p4 for Internet (1) 393 destinations which are non-EIDs 395 a::1/128 [a1,a2] UPF/pGWs load-split traffic to [a1,a2] for (2) 396 UE a::1 and it can move to [b1,b2] 398 b::1/128 [a1,a2] gNB/eNodeB tracks both UEs a::1 and b::1, (3) 399 it can do local routing between the UEs 401 c::1/128 [b1,b2] UE c::1 can roam to [c1,c2] or [d1,d2], (4) 402 may use UPF/pGW [p1,p2] after move 404 x::1/128 [c1,c2] UE x::1 can talk directly to UE y::1, (5) 405 gNB/eNodeBs encap to each other 407 y::1/128 [d1,d2] UE can talk to Internet when [d1,d2], (6) 408 encap to UPF/pGW [p3,p4] or use backup [p1,p2] 410 z::1/128 [d1,d2] UE z::1 can talk to a::1 directly (7) 411 where [d1,d2] encaps to [a1,a2] 413 (1) For packets that flow from UE nodes to destinations that are not 414 in LISP sites, the gNB/eNodeB node uses one of the RLOCs p1, p2, p3, 415 or p4 as the destination address in the outer encapsulated header. 416 Encapsulated packets are then routed by the NGC/EPC core to the UPF/ 417 pGW nodes. In turn, the UPF/pGW nodes, then route packets into the 418 Internet core. 420 (2) Packets that arrive to UPF/pGW nodes from the Internet destined 421 to UE nodes are encapsulated to one of the gNB/eNodeB RLOCs a1, a2, 422 b1, b2. When UE, with EID a::1 is attached to the leftmost gNB/ 423 eNodeB, the EID a::1 is registered to the mapping system with RLOCs 424 a1 and a2. When UE with EID c::1 is attached to the rightmost gNB/ 425 eNodeB (in the left region), the EID c::1 is registered to the 426 mapping system with RLOCs b1 and b2. 428 (3) If UE with EID a::1 and UE with EID b::1 are attached to the same 429 gNB/eNodeB node, the gNB/eNodeB node tracks what radio interface to 430 use to route packets from one UE to the other. 432 (4) If UE with EID c::1 roams away from gNB/eNodeB with RLOCs b1 and 433 b2, to the gNB/eNodeB with RLOCs c1 and c2 (in the rightmost region), 434 packets destined toward the Internet, can use any UPF/pGW. Any 435 packets that flow back from the Internet can use any UPF/pGW. In 436 either case, the UPF/pGW is informed by the mapping system that the 437 UE with EID c::1 has new RLOCs and should now encapsulate to either 438 RLOC c1 or c2. 440 (5) When UE with EID x::1 is attached to gNB/eNodeB with RLOCs c1 and 441 c2 and UE with EID y::1 is attached to gNB/eNodeB with RLOCs d1 and 442 d2, they can talk directly, on the shortest path to each gNB/eNodeB, 443 when each encapsulates packets to each other's RLOCs. 445 (6) When packets from UE with EID y::1 are destined for the Internet, 446 the gNB/eNodeB with RLOCs d1 and d2 that the UE is attached to can 447 use any exit UPF/pGWs RLOCs p1, p2, p3, or p4. 449 (7) UE with EID z::1 can talk directory to UE with EID a::1 by each 450 gNB/eNodeB they are attached to encapsulsates to each other's RLOCs. 451 In case (5), the two gNB/eNodeB's were in the same region. In this 452 case, the gNB/eNodeBs are in different regions. 454 The following abbreviated diagram shows a topology that illustrates 455 how a UE roams with LISP across UPF/pGW regions: 457 (--------------------------------------------) 458 ( ) 459 ( Internet ) 460 ( ) 461 (--------------------------------------------) 462 | | 463 | | 464 (---------|---------) (---------|---------) 465 ( UPF-pGW ) ( UPF-pGW ) 466 ( p1 p2 ) ( p3 p4 ) 467 ( ) ( ) 468 ( NGC/EPC ) ( NGC/EPC ) 469 ( ) ( ) 470 ( a1 a2 b1 b2 ) ( c1 c2 d1 d2 ) 471 ( gNB-eNB gNB-eNB ) ( gNB-eNB gNB-eNB ) 472 (---/--\-----/--\---) (---/--\-----/--\---) 473 / \ / \ / \ / \ 474 / \ / \ / \ / \ 475 / \ / \ 476 / RAN \ / RAN \ 477 / \ / \ 478 ( UE ------------------------------> UE ) 479 a::1 a::1 481 UE EID Mobility 483 The contents of the LISP mapping database before UE moves: 485 EID-Record RLOC-Record Commentary 486 0::/0 [p1,p2,p3,p4] gNB/eNodeB [a1,a2] encaps to p1-p4 for Internet 487 destinations when a::1 on gNB/eNodeB [a1,a2] 489 a::1/128 [a1,a2] Before UE moves to other UPF/pGW region 491 The contents of the LISP mapping database after UE moves: 493 EID-Record RLOC-Record Commentary 494 0::/0 [p1,p2,p3,p4] gNB/eNodeB [d1,d2] encaps to p1-p4 for Internet 495 destinations when a::1 moves to gNB/eNodeB 496 [d1,d2] 498 a::1/128 [d1,d2] After UE moves to new UPF/pGW region 499 4. Addressing and Routing 501 UE based EID addresses will be IPv6 addresses. It will be determined 502 at a future time what length the IPv6 prefix will be to cover all UEs 503 in a mobile network. This coarse IPv6 prefix is called an EID-prefix 504 where more-specific EID-prefixes will be allocated out of it for each 505 UPF/pGW node. Each UPF/pGW node is responsible for advertising the 506 more-specific EID-prefix into the Internet routing system so they can 507 attract packets from non-EIDs nodes to UE EIDs. 509 An RLOC address will either be an IPv4 or IPv6 address depending on 510 the support for single or dual-stack address-family in the NGC/EPC 511 network. An RLOC-set in the mapping system can have a mixed address- 512 family locator set. There is no requirement for the NGC/EPC to 513 change to support one address-family or the other. And there is no 514 requirement for the NGC/EPC network to support IPv4 multicast or IPv6 515 multicast. The LISP overlay will support both. 517 The only requirement for RLOC addresses is that they are routable in 518 the NGC/EPC and the Internet. 520 The requirements of the LISP and GTP data-plane overlay is to support 521 a layer-3 overlay network only. There is no architectural 522 requirement to support layer-2 overlays. However, operators may want 523 to provide a layer-2 LAN service over their mobile network. Details 524 about how LISP supports layer-2 overlays can be found in 525 [I-D.ietf-lisp-eid-mobility]. 527 5. gNB/eNodeB LISP Functionality 529 The gNB/eNodeB node runs as a LISP xTR for control-plane 530 functionality and runs GTP for data-plane functionality. Optionally, 531 the LISP data-plane can be used to establish dynamic tunnels from one 532 gNB/eNodeB node to another gNB/eNodeB node. 534 The gNB/eNodeB LISP xTR will follow the procedures of 535 [I-D.ietf-lisp-eid-mobility] to discover UE based EIDs, track them by 536 monitoring liveness, registering them when appear, and deregistering 537 them when they move away. Since the gNB/eNodeB node is an xTR, it is 538 acting as a layer-3 router and the GTP tunnel from the gNB/eNodeB 539 node to the UPF/pGW node is realizing a layer-3 overlay. This will 540 provide scaling benefits since broadcast and link-local multicast 541 packets won't have to travel across the NGC/EPC to the UPF/pGW node. 543 A day in the life of a UE originated packet: 545 1. The UE node originates an IP packet over the RAN. 547 2. The gNB/eNodeB receives an IPv4/IPv6 packet, it extracts the 548 source address from the packet, learns the UE based EID, stores 549 its RAN location locally and registers the EID to the mapping 550 system. 552 3. The gNB/eNodeB extracts the destination address, looks up the 553 address in the mapping system. The lookup returns the RLOC of a 554 UPF/pGW node if the destination is not an EID or an RLOC gNB/ 555 eNodeB node if the destination is a UE based EID. 557 4. The gNB/eNodeB node encapsulates the packet to the RLOC using GTP 558 or optionally the LISP data-plane. 560 It is important to note that in [I-D.ietf-lisp-eid-mobility], EID 561 discovery occurs when a LISP xTR receives an IP or ARP/ND packet. 562 However, if there are other methods to discover the EID of a device, 563 like in UE call setup, the learning and registration referenced in 564 Paragraph 2 can happen before any packet is sent. 566 6. UPF/pGW LISP Functionality 568 The UPF/pGW node runs as a LISP xTR for control-plane functionality 569 and runs GTP for data-plane functionality. Optionally, the LISP 570 data-plane can be used to establish dynamic tunnels from one UPF/pGW 571 node to another UPF/pGW or gNB/eNodeB node. 573 The UPF/pGW LISP xTR does not follow the EID mobility procedures of 574 [I-D.ietf-lisp-eid-mobility] since it is not responsible for 575 discovering UE based EIDs. A UPF/pGW LISP xTR simply follows the 576 procedures of a PxTR in [I-D.ietf-lisp-rfc6830bis] and for 577 interworking to non-EID sites in [RFC6832]. 579 A day in the life of a UPF/pGW received packet: 581 1. The UPF/pGW node receives a IP packet from the Internet core. 583 2. The UPF/pGW node extracts the destination address from the packet 584 and looks it up in the LISP mapping system. The lookup returns 585 an RLOC of a gNB/eNodeB node. Optionally, the RLOC could be 586 another UPF/pGW node. 588 3. The UPF/pGW node encapsulates the packet to the RLOC using GTP or 589 optionally the LISP data-plane. 591 7. Compatible Data-Plane using GTP 593 Since GTP is a UDP based encapsulating tunnel protocol, it has the 594 same benefits as LISP encapsulation. At this time, there appears to 595 be no urgent need to not continue to use GTP for tunnels between a 596 gNB/eNodeB nodes and between a gNB/eNodeB node and a UPF/pGW node. 598 There are differences between GTP tunneling and LISP tunneling. GTP 599 tunnels are setup at call initiation time. LISP tunnels are 600 dynamically encapsulating, used on demand, and don't need setup or 601 teardown. The two tunneling mechanisms are a hard state versus soft 602 state tradeoff. 604 This specification recommends for early phases of deployment, to use 605 GTP as the data-plane so a transition for it to use the LISP control- 606 plane can be achieved more easily. At later phases, the LISP data- 607 plane may be considered so a more dynamic way of using tunnels can be 608 achieved to support URLLC. 610 This specification recommends the use of procedures from 611 [I-D.ietf-lisp-eid-mobility] and NOT the use of LISP-MN 612 [I-D.ietf-lisp-mn]. Using LISP-MN states that a LISP xTR resides on 613 the mobile UE. This is to be avoided so extra encapsulation header 614 overhead is NOT sent on the RAN. The LISP data-plane or control- 615 plane will not run on the UE. 617 8. Roaming and Packet Loss 619 Using LISP for the data-plane has some advantages in terms of 620 providing near-zero packet loss. In the current mobile network, 621 packets are queued on the gNB/eNodeB node the UE is roaming to or 622 rerouted on the gNB/eNodeB node the UE has left. In the LISP 623 architecture, packets can be sent to multiple "roamed-from" and 624 "roamed-to" nodes while the UE is moving or is off the RAN. See 625 mechanisms in [I-D.ietf-lisp-predictive-rlocs] for details. 627 9. Mobile Network LISP Mapping System 629 The LISP mapping system stores and maintains EID-to-RLOC mappings. 630 There are two mapping database transport systems that are available 631 for scale, LISP-ALT [RFC6836] and LISP-DDT [RFC8111]. The mapping 632 system will store EIDs assigned to UE nodes and the associated RLOCs 633 assigned to gNB/eNodeB nodes and UPF/pGW nodes. The RLOC addresses 634 are routable addresses by the NGC/EPC network. 636 This specification recommends the use of LISP-DDT. 638 10. LISP Over the 5G N3/N6/N9 Interfaces 640 So far in this specification we have described how LISP runs on the 641 gNB and UPF nodes in the mobile network. In the 5G architecture 642 [ARCH5G-3GPP] definition, some key components are Access and Mobility 643 Management Function (AMF) and the Session Management Function (SMF). 644 These two components provide control plane functionality to off-load 645 session anchoring by distributing state and packet flow among 646 multiple nodes in the NGC. These functions control the data-plane 647 anchors deployed in Branch Point Uplink Classifier (BP/ULCL) in UPF 648 data-plane nodes. 650 Here is an illustration where a BP/ULCL-UPF node would appear in the 651 mobile network: 653 (--------------------------------------------) 654 ( Internet ) 655 +-> (--------------------------------------------) 656 | | 657 N6 | 658 | (---------|---------) 659 +-> ( UPF ) <-+ 660 NGC ( [p1,p2] ) | 661 ( ) N9 662 +-> ( BP/ULCL ) | 663 | ( UPF [p3,p4] ) <-+ 664 N3 ( ) 665 | ( [a1] [a2] ) 666 +-> ( gNB gNB ) 667 (---/--\-----/--\---) 668 / \ / \ 669 / \ 670 / RAN \ 671 / \ 672 ( UE UE UE ) 673 a::1 a::2 a::3 675 The BP/ULCL-UPF node is configured as an LISP RTR and uses the 676 Traffic Engineering features of LISP specified in [I-D.ietf-lisp-te]. 677 In LISP-TE an Explicit Locator Path (ELP) can be stored in the RLOC- 678 record for any given EID thereby allowing packet flow from a UE to 679 the Internet to traverse through the BP/UCLC-UPF node. A UE 680 originated packet is encapsulated by the gNB to the BP/ULCL-UPF which 681 decapsulates and reencapsulates to the UPF at the Internet border. 682 This allows LISP to run over the 5G N3 and N9 interface with one 683 mapping entry. And if the ELP contained an xTR outside of the mobile 684 network, LISP could also run over the N6 interface. 686 The contents of the LISP mapping database: 688 EID-Record RLOC-Record Commentary 689 0::/0 [ELP{a1,p3,p1}, 4 RLOC-records, 2 with paths through the BP-UPF 690 ELP{a1,p4,p2}, and 2 directly to the border UPF from UEs 691 p1, p2] connected to gNB with RLOC a1 693 a::1/128 [a1,a2] The UPF or BP-UPF can encap directly for UE with 694 EID a::1 to either gNB with optimized latency 696 a::2/128 [ELP{p1,p3,a2}, The UPF can encap to either RLOC p3 or p4 to 697 ELP{p1,p4,a2}] forward traffic through the BP-UPF on its way 698 toward gNB with RLOC a1 700 a::3/128 [ELP{p1,p3,a2}, The UPF can encap to the BP-UPF or directly 701 a2] to gNB with RLOC a2 to reach UE with EID a::3 703 11. Multicast Considerations 705 Since the mobile network runs the LISP control-plane, and the mapping 706 system is available to support EIDs for unicast packet flow, it can 707 also support multicast packet flow. Support for multicast can be 708 provided by the LISP/GTP overlay with no changes to the NGC/EPC 709 network. 711 Multicast (S-EID,G) entries can be stored and maintained in the same 712 mapping database that is used to store UE based EIDs. Both Internet 713 connected nodes, as well as UE nodes, can source multicast packets. 714 The protocol procedures from [I-D.ietf-lisp-signal-free-multicast] 715 are followed to make multicast delivery available. Both multicast 716 packet flow and UE mobility can occur at the same time. 718 A day in the life of a 1-to-many multicast packet: 720 1. A UE node joins an (S,G) multicast flow by using IGMPv2 or 721 IGMPv3. 723 2. The gNB/eNodeB node records which UE on the RAN should get 724 packets sourced by S and destined for group G. 726 3. The gNB/eNodeB node registers the (S,G) entry to the mapping 727 system with its RLOC according to the receiver site procedures in 728 [I-D.ietf-lisp-signal-free-multicast]. The gNB/eNodeB does this 729 to show interest in joining the multicast flow. 731 4. When other UE nodes join the same (S,G), their associated gNB/ 732 eNodeB nodes will follow the procedures in steps 1 through 3. 734 5. The (S,G) entry stored in the mapping database has an RLOC-set 735 which contains a replication list of all the gNB/eNodeB RLOCs 736 that registered. 738 6. A multicast packet from source S to destination group G arrives 739 at the UPF/pGW. The UPF/pGW node looks up (S,G), gets returned 740 the replication list of all joined gNB/eNodeB nodes and 741 replicates the multicast packet by encapsulating the packet to 742 each of them. 744 7. Each gNB/eNodeB node decapsulates the packet and delivers the 745 multicast packet to one or more IGMP-joined UEs on the RAN. 747 12. Security Considerations 749 For control-plane authentication and authorization procedures, this 750 specification recommends the mechanisms in 751 [I-D.ietf-lisp-rfc6833bis], LISP-SEC [I-D.ietf-lisp-sec] and LISP- 752 ECDSA [I-D.farinacci-lisp-ecdsa-auth]. 754 For data-plane privacy procedures, this specification recommends the 755 mechanisms in [RFC8061] When the LISP data-plane is used. Otherwise, 756 the NGC/EPC must provide data-plane encryption support. 758 13. IANA Considerations 760 There are no specific requests for IANA. 762 14. SDO Recommendations 764 The authors request other Standards Development Organizations to 765 consider LISP as a technology for device mobility. It is recommended 766 to start with this specification as a basis for design and develop 767 more deployment details in the appropriate Standards Organizations. 768 The authors are willing to facilitate this activity. 770 15. References 772 15.1. Normative References 774 [RFC1700] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 775 DOI 10.17487/RFC1700, October 1994, 776 . 778 [RFC6832] Lewis, D., Meyer, D., Farinacci, D., and V. Fuller, 779 "Interworking between Locator/ID Separation Protocol 780 (LISP) and Non-LISP Sites", RFC 6832, 781 DOI 10.17487/RFC6832, January 2013, 782 . 784 [RFC6833] Fuller, V. and D. Farinacci, "Locator/ID Separation 785 Protocol (LISP) Map-Server Interface", RFC 6833, 786 DOI 10.17487/RFC6833, January 2013, 787 . 789 [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, 790 "Locator/ID Separation Protocol Alternative Logical 791 Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, 792 January 2013, . 794 [RFC8060] Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical 795 Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060, 796 February 2017, . 798 [RFC8061] Farinacci, D. and B. Weis, "Locator/ID Separation Protocol 799 (LISP) Data-Plane Confidentiality", RFC 8061, 800 DOI 10.17487/RFC8061, February 2017, 801 . 803 [RFC8111] Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A. 804 Smirnov, "Locator/ID Separation Protocol Delegated 805 Database Tree (LISP-DDT)", RFC 8111, DOI 10.17487/RFC8111, 806 May 2017, . 808 15.2. Informative References 810 [ARCH5G-3GPP] 811 "System Architecture for the 5G System", TS.23.501 812 https://portal.3gpp.org/desktopmodules/Specifications/ 813 SpecificationDetails.aspx?specificationId=3144, December 814 2016. 816 [EPS-3GPP] 817 "Non-Access-Stratum (NAS) Protocol for Evolved Packet 818 System (EPS); Stage 3", TS.23.501 819 https://portal.3gpp.org/desktopmodules/specifications/ 820 specificationdetails.aspx?specificationid=1072, December 821 2017. 823 [ETSI-NGP] 824 "NGP Evolved Architecture for mobility using Identity 825 Oriented Networks", NGP-004, version 1.1.1 826 https://portal.etsi.org/webapp/WorkProgram/ 827 Report_WorkItem.asp?WKI_ID=50531, January 2018. 829 [FMC] "[TS23316] 3rd Generation Partnership Project; Technical 830 Specification Group Services and System Aspects; Wireless 831 and wireline convergence access support for the 5G System 832 (5GS) (Release 16), 3GPP TS23.316", November 2018. 834 [GPRS-3GPP] 835 "General Packet Radio Service (GPRS) for Evolved Universal 836 Terrestrial Radio Access Network (E-UTRAN) Access", 837 TS23.401 Release 8 838 https://portal.3gpp.org/desktopmodules/specifications/ 839 specificationdetails.aspx?specificationid=849, January 840 2015. 842 [GTPv1-3GPP] 843 "General Packet Radio System (GPRS) Tunnelling Protocol 844 User Plane (GTPv1-U)", TS.29.281 845 https://portal.3gpp.org/desktopmodules/Specifications/ 846 SpecificationDetails.aspx?specificationId=1699, January 847 2015. 849 [GTPv2-3GPP] 850 "3GPP Evolved Packet System (EPS); Evolved General Packet 851 Radio Service (GPRS) Tunnelling Protocol for Control plane 852 (GTPv2-C); Stage 3", TS.29.274 853 https://portal.3gpp.org/desktopmodules/Specifications/ 854 SpecificationDetails.aspx?specificationId=1692, January 855 2015. 857 [I-D.farinacci-lisp-ecdsa-auth] 858 Farinacci, D. and E. Nordmark, "LISP Control-Plane ECDSA 859 Authentication and Authorization", draft-farinacci-lisp- 860 ecdsa-auth-03 (work in progress), September 2018. 862 [I-D.ietf-lisp-eid-anonymity] 863 Farinacci, D., Pillay-Esnault, P., and W. Haddad, "LISP 864 EID Anonymity", draft-ietf-lisp-eid-anonymity-11 (work in 865 progress), September 2021. 867 [I-D.ietf-lisp-eid-mobility] 868 Comeras, M. P., Ashtaputre, V., Moreno, V., Maino, F., and 869 D. Farinacci, "LISP L2/L3 EID Mobility Using a Unified 870 Control Plane", draft-ietf-lisp-eid-mobility-08 (work in 871 progress), July 2021. 873 [I-D.ietf-lisp-introduction] 874 Cabellos, A. and D. S. (Ed.), "An Architectural 875 Introduction to the Locator/ID Separation Protocol 876 (LISP)", draft-ietf-lisp-introduction-15 (work in 877 progress), September 2021. 879 [I-D.ietf-lisp-mn] 880 Farinacci, D., Lewis, D., Meyer, D., and C. White, "LISP 881 Mobile Node", draft-ietf-lisp-mn-10 (work in progress), 882 August 2021. 884 [I-D.ietf-lisp-predictive-rlocs] 885 Farinacci, D. and P. Pillay-Esnault, "LISP Predictive 886 RLOCs", draft-ietf-lisp-predictive-rlocs-08 (work in 887 progress), April 2021. 889 [I-D.ietf-lisp-rfc6830bis] 890 Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. 891 Cabellos, "The Locator/ID Separation Protocol (LISP)", 892 draft-ietf-lisp-rfc6830bis-36 (work in progress), November 893 2020. 895 [I-D.ietf-lisp-rfc6833bis] 896 Farinacci, D., Maino, F., Fuller, V., and A. Cabellos, 897 "Locator/ID Separation Protocol (LISP) Control-Plane", 898 draft-ietf-lisp-rfc6833bis-30 (work in progress), November 899 2020. 901 [I-D.ietf-lisp-sec] 902 Maino, F., Ermagan, V., Cabellos, A., and D. Saucez, 903 "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-23 (work 904 in progress), September 2021. 906 [I-D.ietf-lisp-signal-free-multicast] 907 Moreno, V. and D. Farinacci, "Signal-Free Locator/ID 908 Separation Protocol (LISP) Multicast", draft-ietf-lisp- 909 signal-free-multicast-09 (work in progress), March 2018. 911 [I-D.ietf-lisp-te] 912 Farinacci, D., Kowal, M., and P. Lahiri, "LISP Traffic 913 Engineering Use-Cases", draft-ietf-lisp-te-09 (work in 914 progress), September 2021. 916 [ITU-IMT2020] 917 "Focus Group on IMT-2020", 918 https://www.itu.int/dms_pubrec/itu-r/rec/m/R-REC- 919 M.687-2-199702-I!!PDF-E.pdf. 921 [LTE401-3GPP] 922 "General Packet Radio Service (GPRS) enhancements for 923 Evolved Universal Terrestrial Radio Access Network 924 (E-UTRAN) access", TS.23.401 925 https://portal.3gpp.org/desktopmodules/Specifications/ 926 SpecificationDetails.aspx?specificationId=849, January 927 2015. 929 [LTE402-3GPP] 930 "Architecture enhancements for non-3GPP accesses", 931 TS.23.402 932 https://portal.3gpp.org/desktopmodules/Specifications/ 933 SpecificationDetails.aspx?specificationId=850, January 934 2015. 936 [mMTC] "NGMN KPIs and Deployment Scenarios for Consideration for 937 IMT2020", https://www.ngmn.org/uploads/media/151204_NGMN_ 938 KPIs_and_Deployment_Scenarios_for_Consideration_for_IMT_20 939 20_-_LS_Annex_V1_approved.pdf, December 2015. 941 [NGMN] "5G End-to-End Architecture Framework", NGMN 942 https://www.ngmn.org/uploads/ 943 media/201117-NGMN_E2EArchFramework_v4.31.pdf, November 944 2020. 946 [PROC5G-3GPP] 947 "Procedures for the 5G System", TS.23.502 948 https://portal.3gpp.org/desktopmodules/Specifications/ 949 SpecificationDetails.aspx?specificationId=3145, December 950 2016. 952 [X2-3GPP] "Evolved Universal Terrestrial Radio Access Network 953 (E-UTRAN); X2 Application Protocol (X2AP)", TS.36.423 954 https://portal.3gpp.org/desktopmodules/Specifications/ 955 SpecificationDetails.aspx?specificationId=2452, June 2017. 957 Appendix A. Acknowledgments 959 The authors would like to thank Gerry Foster and Peter Ashwood Smith 960 for their expertise with 3GPP mobile networks and for their early 961 review and contributions. The authors would also like to thank Fabio 962 Maino, Malcolm Smith, and Marc Portoles for their expertise in both 963 5G and LISP as well as for their early review comments. 965 The authors would like to give a special thank you to Ryosuke 966 Kurebayashi from NTT Docomo and Kalyani Bogineni from Verizon for 967 their operational and practical commentary. 969 Appendix B. Document Change Log 971 B.1. Changes to draft-farinacci-lisp-mobile-network-12 973 o Posted September 2021. 975 o Updated Uma's affliation. 977 B.2. Changes to draft-farinacci-lisp-mobile-network-12 979 o Posted September 2021. 981 o Update references and document timer. 983 B.3. Changes to draft-farinacci-lisp-mobile-network-11 985 o Posted March 2021. 987 o Changes to reflect editorial comments from Dirk von-Hugo. 989 o Updated ITU and 5G references (manually). 991 B.4. Changes to draft-farinacci-lisp-mobile-network-10 993 o Posted March 2021. 995 o Update references and document timer. 997 B.5. Changes to draft-farinacci-lisp-mobile-network-09 999 o Posted September 2020. 1001 o Update references and document timer. 1003 B.6. Changes to draft-farinacci-lisp-mobile-network-08 1005 o Posted March 2020. 1007 o Change author affliations. 1009 B.7. Changes to draft-farinacci-lisp-mobile-network-07 1011 o Posted March 2020. 1013 o Update references and document timer. 1015 B.8. Changes to draft-farinacci-lisp-mobile-network-06 1017 o Posted September 2019. 1019 o Update references and document timer. 1021 B.9. Changes to draft-farinacci-lisp-mobile-network-05 1023 o Posted March 2019. 1025 o Update references and document timer. 1027 B.10. Changes to draft-farinacci-lisp-mobile-network-04 1029 o Posted September 2018. 1031 o Update document timer. 1033 B.11. Changes to draft-farinacci-lisp-mobile-network-03 1035 o Posted March 2018. 1037 o Make the spec more 5G user-friendly. That is, the design has 1038 always worked for either 4G or 5G but we make it more clear about 1039 5G by using some basic 5G node terminlogy. 1041 o Add a section how LISP can work on the N3, N6, and N9 5G spec 1042 interfaces. 1044 o Describe how LISP-TE can allow BP-UPF offload functionality. 1046 B.12. Changes to draft-farinacci-lisp-mobile-network-02 1048 o Posted mid September 2017. 1050 o Editorial fixes from draft -01. 1052 B.13. Changes to draft-farinacci-lisp-mobile-network-01 1054 o Posted September 2017. 1056 o Explain each EID case illustrated in the "Mobile Network with EID/ 1057 RLOC Assignment" diagram. 1059 o Make a reference to mMTC as a 3GPP use-case for 5G. 1061 o Add to the requirements section how mobile operators believe that 1062 using Locator/ID separation mechanisms provide for more efficient 1063 mobile netwowks. 1065 o Indicate that L2-overlays is not recommended by this specification 1066 as the LISP mobile network architeture but how operators may want 1067 to deploy a layer-2 overlay service. 1069 B.14. Changes to draft-farinacci-lisp-mobile-network-00 1071 o Initial draft posted August 2017. 1073 Authors' Addresses 1075 Dino Farinacci 1076 lispers.net 1077 San Jose, CA 1078 USA 1080 Email: farinacci@gmail.com 1082 Padma Pillay-Esnault 1083 Independent 1084 Santa Clara, CA 1085 USA 1087 Email: padma.ietf@gmail.com 1089 Uma Chunduri 1090 Intel Corporation 1091 Santa Clara, CA 1092 USA 1094 Email: umac.ietf@gmail.com