IETF Logo Mail Archive

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

<Dirk.von-Hugo@telekom.de> Wed, 11 July 2018 13:06 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
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 9C165130E1E for <5gangip@ietfa.amsl.com>; Wed, 11 Jul 2018 06:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level:
X-Spam-Status: No, score=-4.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=6KFEoUaV; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=FqH0x5Oe
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 ZWjLKDhzieRb for <5gangip@ietfa.amsl.com>; Wed, 11 Jul 2018 06:06:44 -0700 (PDT)
Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 801DC130DF3 for <5gangip@ietf.org>; Wed, 11 Jul 2018 06:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1531314403; x=1562850403; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HToPLtr9z39XKG8zrDURE5H9/3WsuW2kvgTSQIjFJIE=; b=6KFEoUaVRPho1HLRsOi4ad7ZNvQphtmp7P6NTUJMDxFqcD0lbjkBLM+A Y1V6vkDCt1WvS7G2f/Qvca1OwS2F4Nwbc2BC1v8GQkpNENYZzZGutnMZA warjzu+qd3vHbT3GJFtVqP7ipWUDwOSwgg8Kz2VL2aIYajJNmSwHrQpri ZyEfuxaqQ7t9ysRWjEBjJh0ztDvDGvb6bNAVDakyEgsXbYekjdxZSE9G0 UgxPUYsYENefL+dTZcJdVCNjCOIApXeryRMSZQRMC+8YhiSzw1O7FPJL3 ygMfPNYBtRexLzpYDfxWJecGgYYKHepBEpJb3bc/uhPcGKa3HdCZfVC8I Q==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jul 2018 15:05:39 +0200
X-IronPort-AV: E=Sophos;i="5.51,338,1526335200"; d="scan'208,217";a="844533986"
Received: from he105870.emea1.cds.t-internal.com ([10.169.118.67]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 11 Jul 2018 15:05:39 +0200
Received: from HE105870.EMEA1.cds.t-internal.com (10.169.118.67) by HE105870.emea1.cds.t-internal.com (10.169.118.67) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 11 Jul 2018 15:05:39 +0200
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105870.EMEA1.cds.t-internal.com (10.169.118.67) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Wed, 11 Jul 2018 15:05:39 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.16) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 11 Jul 2018 15:03:52 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HToPLtr9z39XKG8zrDURE5H9/3WsuW2kvgTSQIjFJIE=; b=FqH0x5OeeqMT8Dh+L+d/BVlkcM7yjGgXgNEFkxg7P2rSysxS0rOxn8uYN3GZzQT9bxwMl0e9K0rcYGm/iO2c0+WKxfHInSTojpSdXaRtZ1NQWuGnsT9n/j38zDP7K/Bq+uYCqm7yweiUrsvsZMZtlFOgmjqGxSH6bIcsXZMik7A=
Received: from LEJPR01MB0602.DEUPRD01.PROD.OUTLOOK.DE (10.158.143.148) by LEJPR01MB0603.DEUPRD01.PROD.OUTLOOK.DE (10.158.143.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.17; Wed, 11 Jul 2018 13:05:38 +0000
Received: from LEJPR01MB0602.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d431:6f17:1397:697c]) by LEJPR01MB0602.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d431:6f17:1397:697c%3]) with mapi id 15.20.0952.017; Wed, 11 Jul 2018 13:05:38 +0000
From: Dirk.von-Hugo@telekom.de
To: sarikaya@ieee.org, nordmark@acm.org
CC: 5gangip@ietf.org
Thread-Topic: [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt
Thread-Index: AQHUElYLootsYblmyUqIO8Mjev4V9aR/PooAgArKjGA=
Date: Wed, 11 Jul 2018 13:05:38 +0000
Message-ID: <LEJPR01MB0602F1995699A4BDC68689C1D15A0@LEJPR01MB0602.DEUPRD01.PROD.OUTLOOK.DE>
References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> <CAC8QAcfE6JB8g0+CwgBbZEVK_SV+ePcQRVOis=mOkVfMEDR0zA@mail.gmail.com>
In-Reply-To: <CAC8QAcfE6JB8g0+CwgBbZEVK_SV+ePcQRVOis=mOkVfMEDR0zA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.von-Hugo@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; LEJPR01MB0603; 7:WRTJcVT3MRigm7r8j95nA2kjgEEYQh2J+PVho1yZaSXPPl0x6rmb0ia1msB3YhMNZ9oF9MSA+yIZ16cJcZ0B3hirouTeEHMIZyjZYQN4jLhOX3y8r0xAL5hGJDnvxoN7Y9YGU3rIw9mlcf+uorot5T+Nu02O0XIftd2N3na+QV1UEEgEzm5e+9tB/2IRVKNqw0tZfGOjtaPv2GsYxtrECrAYtpjmsrZVzfXDIE16M4xi4Ff+hWgLocLPRkUHeR1k
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 515be21a-7cb4-413e-c11a-08d5e72eff80
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:LEJPR01MB0603;
x-ms-traffictypediagnostic: LEJPR01MB0603:
x-microsoft-antispam-prvs: <LEJPR01MB06036CDE78CA653A7C1FE525D15A0@LEJPR01MB0603.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(213716511872227)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231311)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:LEJPR01MB0603; BCL:0; PCL:0; RULEID:; SRVR:LEJPR01MB0603;
x-forefront-prvs: 0730093765
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(136003)(376002)(366004)(346002)(199004)(189003)(51444003)(476003)(6116002)(790700001)(3846002)(2501003)(11346002)(7696005)(966005)(14454004)(72206003)(229853002)(74482002)(75402003)(2900100001)(15650500001)(446003)(52396003)(5660300001)(14444005)(256004)(102836004)(76176011)(5250100002)(53546011)(86362001)(486006)(26005)(33656002)(316002)(478600001)(105586002)(66066001)(14971765001)(2420400007)(7736002)(6246003)(4326008)(53386004)(53936002)(81156014)(81166006)(8676002)(186003)(97736004)(55016002)(6306002)(54896002)(8936002)(606006)(10710500007)(2906002)(236005)(9686003)(110136005)(7110500001)(106356001)(68736007); DIR:OUT; SFP:1101; SCL:1; SRVR:LEJPR01MB0603; H:LEJPR01MB0602.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 0aUGqsGxc/BBlK8Q9sBWwOh1aNhMwelUCCsbviODfchWO0nek+0zCwfNpCxje12dIk5g+zTy7N3rGaNKYnKc+gO0tyuYG27G02sie57v40Xw0XmOv7t/fC86g9OkLd/pgJcjkKiA3WkBLdYLiA+GVrXCi+w1BTYynnZHS+qHOO16y7HI6Zm9n7g1JhX27RHrpm/uJSl0pnUGDttC6lGpx+uBWvA6xX9I5lY1AjzqRRO7YuJ0c0ZghGOXPa0Z2kldRngQt3tF2EdyrY9EF2ngugMqKBBVh48mTBpaphgyLGlSYsfGHtKO/aHM9cnCaU5aV/2MnO5KMS6iLYqvnwwaInrqfydG8bWcUE+b2kENo9k=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_LEJPR01MB0602F1995699A4BDC68689C1D15A0LEJPR01MB0602DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 515be21a-7cb4-413e-c11a-08d5e72eff80
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2018 13:05:38.3102 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB0603
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/cuYgcSjf_al46ESU3YRvsALwkZc>
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.27
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, 11 Jul 2018 13:06:48 -0000

Hi Behcet, Erik,
see my comment inline.
Thanks!
Best Regards
Dirk

From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Mittwoch, 4. Juli 2018 18:11
To: Erik Nordmark <nordmark@acm.org>
Cc: 5GANGIP <5gangip@ietf.org>
Subject: Re: [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt

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?

DH> AFAIK for the time being (3G/4G) the device receives the IP address from the GGSN/P-GW with typically only some handful of locations per dozens of millions subscribers … that will change with 5G and foreseen distributed UPFs and is also different with WiFi APs


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<mailto: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<mailto:internet-drafts@ietf.org>
To: Erik Nordmark <nordmark@sonic.net<mailto: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-privacy-00.txt
Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/
Htmlized:       https://tools.ietf.org/html/draft-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<http://tools.ietf.org>.

The IETF Secretariat

_______________________________________________
5gangip mailing list
5gangip@ietf.org<mailto:5gangip@ietf.org>
https://www.ietf.org/mailman/listinfo/5gangip

v2.23.0 | Report a Bug | By Email