LISP for the Mobile Network
draft-farinacci-lisp-mobile-network-09
Network Working Group D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental P. Pillay-Esnault
Expires: March 12, 2021 Independent
U. Chunduri
Futurewei Technologies
September 8, 2020
LISP for the Mobile Network
draft-farinacci-lisp-mobile-network-09
Abstract
This specification describes how the LISP architecture and protocols
can be used in a LTE/5G mobile network to support session survivable
EID mobility. A recommendation is provided to SDOs on how to
integrate LISP into the mobile network.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 12, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Farinacci, et al. Expires March 12, 2021 [Page 1]
Internet-Draft LISP for the Mobile Network September 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 6
4. Addressing and Routing . . . . . . . . . . . . . . . . . . . 13
5. gNB/eNodeB LISP Functionality . . . . . . . . . . . . . . . . 13
6. UPF/pGW LISP Functionality . . . . . . . . . . . . . . . . . 14
7. Compatible Data-Plane using GTP . . . . . . . . . . . . . . . 14
8. Roaming and Packet Loss . . . . . . . . . . . . . . . . . . . 15
9. Mobile Network LISP Mapping System . . . . . . . . . . . . . 15
10. LISP Over the 5G N3/N6/N9 Interfaces . . . . . . . . . . . . 15
11. Multicast Considerations . . . . . . . . . . . . . . . . . . 17
12. Security Considerations . . . . . . . . . . . . . . . . . . . 18
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
14. SDO Recommendations . . . . . . . . . . . . . . . . . . . . . 18
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
15.1. Normative References . . . . . . . . . . . . . . . . . . 18
15.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 22
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 23
B.1. Changes to draft-farinacci-lisp-mobile-network-09 . . . . 23
B.2. Changes to draft-farinacci-lisp-mobile-network-08 . . . . 23
B.3. Changes to draft-farinacci-lisp-mobile-network-07 . . . . 23
B.4. Changes to draft-farinacci-lisp-mobile-network-06 . . . . 23
B.5. Changes to draft-farinacci-lisp-mobile-network-05 . . . . 23
B.6. Changes to draft-farinacci-lisp-mobile-network-04 . . . . 23
B.7. Changes to draft-farinacci-lisp-mobile-network-03 . . . . 23
B.8. Changes to draft-farinacci-lisp-mobile-network-02 . . . . 24
B.9. Changes to draft-farinacci-lisp-mobile-network-01 . . . . 24
B.10. Changes to draft-farinacci-lisp-mobile-network-00 . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which provide an architecture to build overlays on top of the
underlying Internet. Mapping EIDs to RLOC-sets is accomplished with
a Mapping Database System. By using a level of indirection for
Show full document text