Privacy issues in ID/locator separation systems
draft-nordmark-id-loc-privacy-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                        E. Nordmark
Internet-Draft                                                    Zededa
Intended status: Standards Track                            July 2, 2018
Expires: January 3, 2019

            Privacy issues in ID/locator separation systems
                    draft-nordmark-id-loc-privacy-00

Abstract

   There exists several protocols and proposals for identifier/locator
   split which have some form of control plane by which participating
   nodes can use to share their current id to locator information with
   their peers.  This document explores some of the privacy
   considerations for such a system.

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 January 3, 2019.

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
   (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.

Nordmark                 Expires January 3, 2019                [Page 1]
Internet-Draft                idloc privacy                    July 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Keywords and Terminology  . . . . . . . . . . . . . . . . . .   3
   3.  Assumptions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Threats against Privacy . . . . . . . . . . . . . . . . . . .   4
     4.1.  Location Privacy  . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Movement Privacy  . . . . . . . . . . . . . . . . . . . .   4
   5.  Not everybody all the time  . . . . . . . . . . . . . . . . .   4
     5.1.  Optimized routing . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Family and Friends  . . . . . . . . . . . . . . . . . . .   5
     5.3.  Business Assets . . . . . . . . . . . . . . . . . . . . .   5
   6.  Boundary between ID/locator part and rest of Internet . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   When the IP address is separated, one way or another, into an
   identifier and a locator there is typically a need to be able to look
   up an identifier to find possible locators which can be used to reach
   the identified endpoint.  If such a system (think distributed
   database) was publicly available while identifiers are assigned to
   devices such as mobile phones which have a strong binding with an
   individual, then this would introduce additional privacy
   considerations which do not exist in the absence of the ID/locator
   split.

   Without an ID/locator split a device is already providing its IP
   address (in the form of a source address) to any network device along
   the path, and also to the remote endpoint.  That endpoint in
   particular might use IP geolocation databases to get a pretty good
   idea of where its peer is located, for instance to offer information
   and/or advertising relevant to that location.

   However, such such a device (e.g., a laptop or smartphone connected
   over WiFi) move e.g., from home to a coffee shop, the IP address
   changes.  This makes it harder for network devices along the paths to
   realize that the its is the same mobile device.  And if the mobile
   device is not retaining cookies or logged into websites, those remote
   peers would also have some difficulty determining it is the same
   mobile device.  Furthermore, a mobile device which is using typical
   cellular network technologies end up with an IP address, at least as
   seen by remote peers outside of the cellular network, which is
   associated with the cellular operator but does not necessarily
Show full document text