Problem Statement for Identity Enabled Networks
draft-padma-ideas-problem-statement-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-12
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)
Network Working Group                             P. Pillay-Esnault, Ed.
Internet-Draft                                                    Huawei
Intended status: Informational                             M.  Boucadair
Expires: September 13, 2017                                 C. Jacquenet
                                                                  Orange
                                                            M.  Fioccola
                                                          Telecom Italia
                                                             A.  Nennker
                                                        Deutsche Telekom
                                                          March 12, 2017

            Problem Statement for Identity Enabled Networks
                 draft-padma-ideas-problem-statement-01

Abstract

   The forthcoming deployment of 5G coupled with emerging applications
   such as augmented reality, virtual reality and 8k videos are likely
   to raise more stringent requirements in terms of ultra-low latency
   while ensuring session continuity.  The emergence of IoT services
   also raises new challenges (with respect to their interoperability,
   discovery, naming and addressing) which may lead to identity-based
   designs.  This problem statement examines how the existing solutions
   for networks whose forwarding scheme assumes the decoupling between
   the identifier and the locator information (called Identity Enabled
   Networks) will struggle to meet such requirements.  It advocates for
   a standardized, secured common control plane with data integrity for
   Identity Services such as identifier registration, mapping and
   resolution.  This memo also identifies several key areas to be
   further investigated for the architecture design of these services.

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 http://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 13, 2017.

Pillay-Esnault, et al. Expires September 13, 2017               [Page 1]
Internet-Draft                                                March 2017

Copyright Notice

   Copyright (c) 2017 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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   4
   3.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   4
   4.  Brief Overview of ID Enabled Networks . . . . . . . . . . . .   5
     4.1.  Identifiers Role in a Communication Session . . . . . . .   6
     4.2.  Mapping/Resolution Services in GRIDS differ from Domain
           Name Service (DNS)  . . . . . . . . . . . . . . . . . . .   7
   5.  Key Problems  . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Common Control Plane Infrastructure . . . . . . . . . . .   8
     5.2.  Identifier Lifecycle  . . . . . . . . . . . . . . . . . .   9
     5.3.  Security of Mapping Systems . . . . . . . . . . . . . . .   9
     5.4.  Distributed Denial of Service Attack Prone  . . . . . . .   9
   6.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Relationship between IDEAS and other IETF Working Groups  . .  10
     7.1.  LISP WG . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.2.  HIP WG  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.3.  NVO3 WG . . . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  11
Show full document text