Problem Statement for Secure End to End Privacy in IdLoc Systems
draft-xyz-pidloc-ps-00

Document Type Active Internet-Draft (individual)
Last updated 2019-05-14
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                                        D. von Hugo
Internet-Draft                                          Deutsche Telekom
Intended status: Standards Track                             B. Sarikaya
Expires: November 15, 2019                           Denpel Informatique
                                                              L. Iannone
                                                       Telecom ParisTech
                                                             A. Petrescu
                                                               CEA, LIST
                                                                  K. Sun
                                                     Soongsil University
                                                              U. Fattore
                                                                     NEC
                                                            May 14, 2019

    Problem Statement for Secure End to End Privacy in IdLoc Systems
                       draft-xyz-pidloc-ps-00.txt

Abstract

   Efficient and service aware flexible end-to-end routing in future
   communication networks is achieved by routing protocol approaches
   making use of Identifier Locator separation systems.  Since these
   systems require a correlation between identifiers and location which
   might allow tracking and misusage of individuals' identities and
   locations such operation demands for highly secure measures to
   preserve privacy of users and devices.  This document tries to
   identify and describe typical use cases and derive thereof
   requirements to be fulfilled by privacy preserving Identifier-Locator
   split (PidLoc) approaches.

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 November 15, 2019.

von Hugo, et al.        Expires November 15, 2019               [Page 1]
Internet-Draft          Pidloc Problem Statement                May 2019

Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   3
   3.  Identifier Locator Separation Protocols . . . . . . . . . . .   3
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Industrial IoT  . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  5G Use Case . . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Cloud Use Case  . . . . . . . . . . . . . . . . . . . . .   5
     4.4.  Vehicular Networks  . . . . . . . . . . . . . . . . . . .   5
   5.  PIdLoc Requirements . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Forthcoming future communication systems which are currently under
   specification by standardization organizations try to achieve higher
   resource efficiency and flexibility as compared to currently deployed
   and operated networks.  Independent of specific access technologies
   multiple applications shall be served with different levels of
   policy- driven mobility support and quality of service in terms of
   bandwidth, latency, error probability etc.  Current practice of IP
   address usage includes semantics as session identification as well as
Show full document text