ID Locator Split Based Solution for 5G Network
draft-chen-id-locator-split-5g-solution-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
INTERNET-DRAFT                                                    C.Chen
Intended Status: Proposed Standard                                 X.Wei
Expires: May 4, 2017                        Huawei Technologies Co., Ltd
                                                        October 31, 2016

             ID Locator Split Based Solution for 5G Network
               draft-chen-id-locator-split-5g-solution-00

Abstract

   In this memo, a generic network scheme based on ID / Locator
   separation architecture is proposed to satisfy the emerging new
   requirements of future networks.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2016 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
   (http://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
 

<Author>                  Expires May 4, 2017                   [Page 1]
INTERNET DRAFT              <Document Title>            October 31, 2016

   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
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Current Solution Analysis  . . . . . . . . . . . . . . . . . .  4
     2.1  GTP . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2  MIPv4/MIPv6 . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.3  PMIPv6  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.4  HIP . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.5  LISP  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.6  ILNP  . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3 Design Principle . . . . . . . . . . . . . . . . . . . . . . . .  5
   4  Architecture Design . . . . . . . . . . . . . . . . . . . . . .  6
     4.1  Architecture Overview . . . . . . . . . . . . . . . . . . .  6
     4.2  Reference Point Definition  . . . . . . . . . . . . . . . .  8
     4.3  Signaling and Data Flow Overview  . . . . . . . . . . . . .  8
       4.3.1  Packet Forwarding Procedure . . . . . . . . . . . . . .  8
       4.3.2  Handover Procedures . . . . . . . . . . . . . . . . . . 10
         4.3.2.1 Handover without routing optimization  . . . . . . . 10
         4.3.2.2 Handover with routing optimization . . . . . . . . . 11
       4.3.3  Interconnection between ID Network and IP Network . . . 13
   5 Message Definition . . . . . . . . . . . . . . . . . . . . . . . 15
   6  Security Considerations . . . . . . . . . . . . . . . . . . . . 16
   7  Privacy Considerations  . . . . . . . . . . . . . . . . . . . . 16
   8  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 16
   9  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 16
   10  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     10.1  Normative References . . . . . . . . . . . . . . . . . . . 16
     10.2  Informative References . . . . . . . . . . . . . . . . . . 16
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

 

<Author>                  Expires May 4, 2017                   [Page 2]
INTERNET DRAFT              <Document Title>            October 31, 2016

1  Introduction

   With the emergence of various new communication services, there have
   been many new network communication needs, and also more and more new
   demands for network capability. For example, there are high mobility
   requirements, such as high-speed railway communications; low latency
Show full document text