Problem Statement for Secure End to End Privacy Enabled Mapping System
draft-xyz-atick-ps-01

Document Type Active Internet-Draft (individual)
Last updated 2018-06-07
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: December 9, 2018                            Denpel Informatique
                                                              L. Iannone
                                                       Telecom ParisTech
                                                              T. Herbert
                                                              Quantonium
                                                            June 7, 2018

 Problem Statement for Secure End to End Privacy Enabled Mapping System
                       draft-xyz-atick-ps-01.txt

Abstract

   Problem Statement for Secure End to End Privacy Enabled Mapping
   System for Identifier Locator separation systems is presented.  Since
   identifiers are often carried in packet headers in clear, and mapping
   systems are often designed to be accessible by any entity, to
   preserve identifier's privacy, lookups to the mapping system should
   be allowed only by authorized entities.  In mapping systems, in
   addition to privacy, security also requires special attention because
   of the caches introduced into the data path.  Any denial of service
   attacks on the cache should not allow the communication to come to an
   end.

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 December 9, 2018.

von Hugo, et al.        Expires December 9, 2018                [Page 1]
Internet-Draft           Atick Problem Statement               June 2018

Copyright Notice

   Copyright (c) 2018 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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Security In the Data Path . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Current 4G and the upcoming converged communication network of 5G
   core network (5GC) make use of tunneling with anchor points to handle
   mobility, policy and quality of service.  The use of IP addresses
   induces the topology and enables easy location tracking.  Elimination
   or reduction of anchor points, as well as disassociating topology
   from IP addresses to facilitate efficient mobility and user privacy
   using Identifier Locator separation systems like Identifier Locator
   Addressing, The Locator/ID Separation Protocol and others is needed.
   Many drawbacks of tunneling are discussed in
   [I-D.ietf-intarea-tunnels] and we do not repeat them here.

   This document attempts to make the case for the use of the identifier
   locator separation (Id-Loc) protocols in the data plane and
   identifies the problems for such a large scale use.  The problems
   identified mainly are privacy of the identifiers and associated
   locators and security issues.

von Hugo, et al.        Expires December 9, 2018                [Page 2]
Internet-Draft           Atick Problem Statement               June 2018

2.  Conventions and Terminology
Show full document text