Requirements to Secure End to End Privacy in IdLoc Systems
draft-xyz-pidloc-reqs-00

Document Type Active Internet-Draft (individual)
Last updated 2019-05-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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                                         L. Iannone
Internet-Draft                                         Telecom ParisTech
Intended status: Standards Track                             D. von Hugo
Expires: November 28, 2019                              Deutsche Telekom
                                                             B. Sarikaya
                                                     Denpel Informatique
                                                            May 27, 2019

       Requirements to Secure End to End Privacy in IdLoc Systems
                      draft-xyz-pidloc-reqs-00.txt

Abstract

   Use of Identifier Locator separation systems is proposed for various
   use cases to allow for efficient and service aware flexible end-to-
   end routing.  A statement on the issue of privacy preservation of
   both users and devices identity and location describes major
   challenges identified for this problem.  This document attempts to
   derive requirements towards a potential solution space of approaches
   to preserve privacy in Identifier-Locator split (PidLoc) protocols.

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 28, 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

Iannone, et al.         Expires November 28, 2019               [Page 1]
Internet-Draft             Pidloc Requirements                  May 2019

   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 . . . . . . . . . . . . . . . . .   2
   3.  Identifier Locator Separation Protocols . . . . . . . . . . .   3
   4.  PId-Loc Requirements  . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Limited Effort  . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Flexibility . . . . . . . . . . . . . . . . . . . . . . .   3
     4.3.  Scalability . . . . . . . . . . . . . . . . . . . . . . .   3
     4.4.  Resiliency  . . . . . . . . . . . . . . . . . . . . . . .   3
     4.5.  ID to Locator Association  Protection . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [I-D.xyz-pidloc-ps] has identified and described typical use cases
   for application of privacy preserving Identifier-Locator split
   (PidLoc) approaches and derived thereof a problem statement
   describing corresponding issues and challenges.  Privacy in this
   respect includes prevention of acquisition of personal information,
   behavioral details, and location information by unauthorised parties.
   This document tries to assess that set of issues and challenges to
   come up with a set of requirements for approaches towards service
   specific and optimized packet routing based on Id-Loc principle
   providing privacy and security.

2.  Conventions and Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119] and
   [I-D.xyz-pidloc-ps].

Iannone, et al.         Expires November 28, 2019               [Page 2]
Internet-Draft             Pidloc Requirements                  May 2019

3.  Identifier Locator Separation Protocols
Show full document text