Use Cases for Identity Enabled Networks
draft-padma-ideas-use-cases-00

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                              D. Farinacci
Expires: September 13, 2017                                  lispers.net
                                                              T. Herbert
                                                                Facebook
                                                            C. Jacquenet
                                                                  Orange
                                                                 D. Lake
                                                                    Dell
                                                                M. Menth
                                                          U of Tuebingen
                                                                D. Meyer
                                                                 Brocade
                                                         D. Raychaudhuri
                                                      Rutgers University
                                                          March 12, 2017

                Use Cases for Identity Enabled Networks
                     draft-padma-ideas-use-cases-00

Abstract

   This document describes some use cases for Identity Enabled networks
   using a Generic Resilient Identity Services infrastructure.

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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   3
   3.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   3
   4.  Common Control Plane Infrastructure . . . . . . . . . . . . .   5
     4.1.  ID-Based Protocols  . . . . . . . . . . . . . . . . . . .   5
     4.2.  Need for a Generic Resilient Identity Services in IoT . .   6
     4.3.  Case 1: Smart Home  . . . . . . . . . . . . . . . . . . .   8
     4.4.  Case 2: Smart City  . . . . . . . . . . . . . . . . . . .   9
     4.5.  Case 3: Industrial IOT Services . . . . . . . . . . . . .   9
   5.  Network Simplification  . . . . . . . . . . . . . . . . . . .  10
     5.1.  Case 4: Proximity Services and Scopes . . . . . . . . . .  10
     5.2.  Case 5: Ease of troubleshooting and Management  . . . . .  11
     5.3.  Case 6: Application of Common policies  . . . . . . . . .  11
   6.  Ease of Provisioning  . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Case 7: Automatic Bootstrapping . . . . . . . . . . . . .  11
     6.2.  Case 8: Active User-Driven Provisioning . . . . . . . . .  12
   7.  Mobility  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Case 9: Mobility within a single provider network . . . .  12
     7.2.  Case 10: Roaming across Mobile Networks . . . . . . . . .  15
     7.3.  Case 11: Mobility of a Subnet . . . . . . . . . . . . . .  16
   8.  Heterogeneous Multi-Access Environments (hetnet)  . . . . . .  18
     8.1.  Case 12: Dynamic Mobility across Cellular and Wi-Fi . . .  18
     8.2.  Case 13:Ad-hoc Networks Mobility across Hetnet  . . . . .  18
     8.3.  Case 14: Multi-network Access Support . . . . . . . . . .  19
Show full document text