Re: [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 04 July 2018 16:11 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7D2130EB9 for <5gangip@ietfa.amsl.com>; Wed, 4 Jul 2018 09:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYrquGCBSU9d for <5gangip@ietfa.amsl.com>; Wed, 4 Jul 2018 09:11:07 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE421130E79 for <5gangip@ietf.org>; Wed, 4 Jul 2018 09:11:06 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id v3-v6so3015800wmh.0 for <5gangip@ietf.org>; Wed, 04 Jul 2018 09:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Zo5aMGErW2HEZ2ZC5xIzFK0s6zS4jsoqD1kcqBnVbkA=; b=JneAmYehNQiIZ6h2DzN0/7SzvOPnH3bbzOIjvjunaiwaE475y3dwl9OzfEGKr/D3UH 6GdPXr7pBB9xdBJEGaDHtvl5l679zYOEeRNVaHOsr3Vo3uzK4KSXoKSo2+FW6lBcn6tx JkdyGB5v1y2sVVlO1zkXlI6CT6mXv8BbUvwzI8vim0DepzXqNHGAZEYNlxt8O36uuLTn fIe/njUK9fgiASOYkt4RQC3mRvYNUTnFnnuO/9gBjU7T6a0BXlqw2LJ7hLeAwMlnJ9Ex SbNSMZuyCf63R/xo1SSS9fpQXnCI/GmlWqxU8pTlHfmpaV0mf5SjHRNM9MY2Go63lMfF Qn0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=Zo5aMGErW2HEZ2ZC5xIzFK0s6zS4jsoqD1kcqBnVbkA=; b=axncvcMkqgXlQ+En+5oZcW1xScIPTiDNQsTFXn651vTp4XZEnE0g8Bu3coA7Cd3iI6 1hhoPSH+ajY0hyrQ8fxf0KNjqFRJcObAy307eXHxWEU3INf5nYJB0pSh09Ol2YUIgY3Q RG91m0O2L5/PNH3Y3k2rRhi9Rn1nLojd/gcOKGOcYMVatQpCfW0o1vcJG3FkZ18E+n8S ukRIof1GzZ9f/HAekxt80nApRWB7PbZlpWKFLreQR9U6jVhS35/5BrYBPfkF8rTBJwuC iv3ZpBtYWhZTRzAwft1a6BCUzIqeyZPZ774dujM9BzijKeD1VB4+x45iSf131fS4mgjO fvrQ==
X-Gm-Message-State: APt69E0jufkVITdFar4Xd763H7Cz5Db6LMzE/mgtnCDZ3aPp9kJGNaIC Lk/P8vt+xWYv0OooGT9klZBvCGnHqSKwfmWBJX8=
X-Google-Smtp-Source: AAOMgpfezFxXoEscgN6uNW4SYTDd4j0MzFOf6QIhKDqQnYecAu+fKLw0TpcOVOSA8puVJxfq4UIlU3CuSf5ftuBYn8k=
X-Received: by 2002:a1c:108b:: with SMTP id 133-v6mr2180449wmq.136.1530720665236; Wed, 04 Jul 2018 09:11:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a5d:4387:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 09:11:04 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org>
References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Wed, 04 Jul 2018 11:11:04 -0500
Message-ID: <CAC8QAcfE6JB8g0+CwgBbZEVK_SV+ePcQRVOis=mOkVfMEDR0zA@mail.gmail.com>
To: Erik Nordmark <nordmark@acm.org>
Cc: 5GANGIP <5gangip@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000807ab005702eadef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/23egJqkpSraocfavQv9bI28fg1E>
Subject: Re: [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2018 16:11:09 -0000

Hi Erik,

My comments on your draft:

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
   indicate a particular location of the mobile device.


Is this correct? IP address assigned by a cellular network would not
indicate a particular location?


Thus we believe that we can explore the core of the ID/locator privacy issue

   by looking at long-lived identifiers.


wholeheartedly concur.

If a third party can at any time determine the IP location of some
   identifier, then the device can at one point be IP geolocated at
   home, and later a coffee shop.


What is IP location? is it IP address?
I think that the above sentence is correct because the identifiers are
carried in the clear in packet headers which is not mentioned in the draft.

If this is the case, then the ID/locator mapping system can
   provide access control so that only those trusted devices can access
   the mappings.

The above quote from Sec. 5.1. first paragraph is a very good observation,
agreed.

Today such location sharing happens at an application layer using GPS
   coordinates.  But while such sharing is in effect, it wouldn't be
   unreasonable to also consider sharing IP locators to make it more
   efficient or more robust to e.g., route a video feed from one device
   to another.


The above helps clarify why IP level solution is needed.

5.3.  Business Assets

Sec. 5.3 gives some IoT context which was missing.


The draft has a number of typos and I am going to communicate them to the
author separately.
Also I send the mail to one list, you may forward it to your favorite list
if you wish.

Behcet

On Mon, Jul 2, 2018 at 5:42 PM, Erik Nordmark <nordmark@acm.org> wrote:

>
> This is a rough draft, but hopefully it can stimulate more discussion
> around privacy considerations.
>
> -------- Forwarded Message --------
> Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt
> Date: Mon, 02 Jul 2018 15:34:11 -0700
> From: internet-drafts@ietf.org
> To: Erik Nordmark <nordmark@sonic.net>
>
>
> A new version of I-D, draft-nordmark-id-loc-privacy-00.txt
> has been successfully submitted by Erik Nordmark and posted to the
> IETF repository.
>
> Name:           draft-nordmark-id-loc-privacy
> Revision:       00
> Title:          Privacy issues in ID/locator separation systems
> Document date:  2018-07-02
> Group:          Individual Submission
> Pages:          6
> URL: https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-p
> rivacy-00.txt
> Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/
> Htmlized:       https://tools.ietf.org/html/d
> raft-nordmark-id-loc-privacy-00
> Htmlized: https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-
> privacy
>
>
> 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.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>