Anchorless mobility management through hICN (hICN-AMM): Deployment options
draft-auge-dmm-hicn-mobility-deployment-options-04

Document Type Active Internet-Draft (individual)
Authors Jordan Auge  , Giovanna Carofiglio  , Luca Muscariello  , Michele Papalini 
Last updated 2020-07-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DMM Working Group                                                J. Auge
Internet-Draft                                             G. Carofiglio
Intended status: Informational                            L. Muscariello
Expires: 9 January 2021                                      M. Papalini
                                                                   Cisco
                                                             8 July 2020

   Anchorless mobility management through hICN (hICN-AMM): Deployment
                                options
           draft-auge-dmm-hicn-mobility-deployment-options-04

Abstract

   A novel mobility management approach has been proposed, that
   leverages routable location-independent identifiers (IDs) and an
   Information-Centric Networking (ICN) communication model integrated
   in IPv6, also referred to as Hybrid ICN (hICN).  In virtue of its
   anchorless property, we denote this approach as hICN-AMM (hICN
   Anchorless Mobility Management) hereinafter.

   Such approach belongs to the category of pure ID-based mobility
   management schemes whose objective is (i) to overcome the limitations
   of traditional locator-based solutions like Mobile IP, (ii) to remove
   the need for a global mapping system as the one required by locator-
   identifier separation solutions like LISP or ILA.

   ID-based networking as proposed by ICN architectures allows to
   disentangle forwarding operations from changes of network location,
   hence removing tunnels and user plane or control plane anchors.

   This document discusses hICN-AMM deployment options and related
   tradeoffs in terms of cost/benefits.  Particular attention is devoted
   to the insertion in the recently proposed 5G Service Based
   Architecture under study at 3GPP where an hICN-AMM solution might
   present a more efficient alternative to the traditional tunnel-based
   mobility architecture through GTP-U.

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/.

Auge, et al.             Expires 9 January 2021                 [Page 1]
Internet-Draft      hICN mobility: deployment options          July 2020

   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 9 January 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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Overview of a mobile access network and the 5G
           architecture  . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Transparent integration (option #1) . . . . . . . . . . . . .   7
     3.1.  MEC deployment (option #1a) . . . . . . . . . . . . . . .   7
     3.2.  hICN deployment as a UPF (option #1b) . . . . . . . . . .  10
     3.3.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .  12
   4.  "Integrated" approaches: data-plane alternatives to GTP-U
           (option #2) . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  hICN insertion at N9 interface only (option #2a)  . . . .  13
     4.2.  hICN deployment at both N9 and N3 interfaces (option
           #2b)  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.3.  Control plane considerations  . . . . . . . . . . . . . .  16
   5.  Deployment considerations . . . . . . . . . . . . . . . . . .  16
     5.1.  hICN in a slice . . . . . . . . . . . . . . . . . . . . .  17
     5.2.  End-to-end deployment . . . . . . . . . . . . . . . . . .  17
     5.3.  Network-contained deployment  . . . . . . . . . . . . . .  18
     5.4.  Alternative data planes: joint hICN/SRv6 deployment . . .  18
   6.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
Show full document text