MAP-Me : Managing Anchorless Mobility in Content Centric Networking
draft-irtf-icnrg-mapme-00

Document Type Active Internet-Draft (icnrg RG)
Last updated 2018-03-18
Stream IRTF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream IRTF state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICNRG                                                       J. Auge, Ed.
Internet-Draft                                        G. Carofiglio, Ed.
Intended status: Informational                       L. Muscariello, Ed.
Expires: September 18, 2018                             M. Papalini, Ed.
                                                     Cisco Systems, Inc.
                                                            mar 17, 2018

  MAP-Me : Managing Anchorless Mobility in Content Centric Networking
                       draft-irtf-icnrg-mapme-00

Abstract

   Mobility has become a basic premise of network communications,
   thereby requiring a native integration into 5G networks.  Despite
   numerous efforts to propose and standardize effective mobility-
   management models for IP, the result is a complex, poorly flexible
   set of mechanisms.  The natural support for mobility offered by ICN
   (Information Centric Networking) makes it a good candidate to define
   a radically new solution relieving limitations of the traditional
   approaches.  If consumer mobility is supported in ICN by design, in
   virtue of its connectionless pull-based communication model, producer
   mobility is still an open challenge.  In this document, we focus on
   two prominent ICN architectures, CCN (Content Centric Networking) and
   NDN (Named Data Networking) and describe MAP-Me, an anchor-less
   solution to manage micro-mobility of content producers via a name-
   based CCN/NDN data plane, with support for latency-sensitive
   applications.

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 September 18, 2018.

Auge, et al.           Expires September 18, 2018               [Page 1]
Internet-Draft     Managing Anchorless Mobility in CCN          mar 2018

Copyright Notice

   Copyright (c) 2018 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.  State-of-the-art and benefits of anchorless mobility
       solutions . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Design principles . . . . . . . . . . . . . . . . . . . . . .   6
   4.  MAP-Me description  . . . . . . . . . . . . . . . . . . . . .   7
   5.  Update protocol . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Rationale . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Update propagation  . . . . . . . . . . . . . . . . . . .   8
     5.3.  Concurrent updates  . . . . . . . . . . . . . . . . . . .  11
   6.  MAP-Me Notification/Discovery protocol  . . . . . . . . . . .  12
     6.1.  Interest Notification . . . . . . . . . . . . . . . . . .  13
     6.2.  Discovery . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.3.  Full approach . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  MAP-Me Messages . . . . . . . . . . . . . . . . . . . . .  14
     7.2.  MAP-Me additional Network Information . . . . . . . . . .  14
   8.  Algorithm description . . . . . . . . . . . . . . . . . . . .  15
     8.1.  IU/IN transmission at producer  . . . . . . . . . . . . .  15
     8.2.  IU/IN transmission at network routers . . . . . . . . . .  16
     8.3.  Hop-by-hop IU/IN acknowledgement  . . . . . . . . . . . .  16
     8.4.  Face removal at producer/network nodes  . . . . . . . . .  17
     8.5.  Consumer request forwarding in case of producer discovery  17
   9.  Security considerations . . . . . . . . . . . . . . . . . . .  19
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   11. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  19
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
Show full document text