IETF Logo Mail Archive

Re: [Ideas] [5gangip] FW: New Version Notification for draft-xyx-5gip-ps-00.txt

Christian Huitema <huitema@huitema.net> Thu, 11 May 2017 03:20 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 300CD12950A for <ideas@ietfa.amsl.com>; Wed, 10 May 2017 20:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 x7V9uL66P1Y8 for <ideas@ietfa.amsl.com>; Wed, 10 May 2017 20:20:56 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 79F65128BB7 for <ideas@ietf.org>; Wed, 10 May 2017 20:20:56 -0700 (PDT)
Received: from xsmtp12.mail2web.com ([168.144.250.177]) by mx43.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1d8ees-0007iF-8o for ideas@ietf.org; Thu, 11 May 2017 05:20:54 +0200
Received: from internal.xmail04.myhosting.com ([10.5.2.14] helo=xmail04.myhosting.com) by xsmtp12.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <huitema@huitema.net>) id 1d8eeq-0005SO-Ab for ideas@ietf.org; Wed, 10 May 2017 23:20:52 -0400
Received: (qmail 11615 invoked from network); 11 May 2017 03:20:51 -0000
Received: from unknown (HELO [192.168.200.68]) (Authenticated-user:_huitema@huitema.net@[72.235.151.78]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <lorenzo@google.com>; 11 May 2017 03:20:51 -0000
To: Tom Herbert <tom@herbertland.com>, Uma Chunduri <uma.chunduri@huawei.com>
References: <149376035152.21552.16267155218438524059.idtracker@ietfa.amsl.com> <25B4902B1192E84696414485F5726854018A27B7@SJCEML701-CHM.china.huawei.com> <CALx6S34fqe5cO_Vzi=pT1CELX_Ewbe7RcjpHn3-gNouCZKSZXQ@mail.gmail.com> <CAC8QAcfZTO0ZB_9MSMVUCgFd5Jr0iByaArXnVxnsKVgTj6Hudg@mail.gmail.com> <CALx6S34QK8vrtYgrQzTgqDi+LGkd5P2SNDuRtqTyEBPj+VXmYg@mail.gmail.com> <25B4902B1192E84696414485F5726854018A2ACC@SJCEML701-CHM.china.huawei.com> <CALx6S37g+f4tB2343vNh1Eje7tCGtHMtNPdxRpK_-RbNSHURFg@mail.gmail.com> <25B4902B1192E84696414485F5726854018A2AF3@SJCEML701-CHM.china.huawei.com> <CALx6S34_Aibh5HQ01jpZPHE6dXVyk5tsxeSCzy4FRcGcXLj0Zw@mail.gmail.com> <25B4902B1192E84696414485F5726854018A2B11@SJCEML701-CHM.china.huawei.com> <CALx6S34srTgJ-hyKZWRwMZnaaem_gr+04a-d015AcSc-kX4dMA@mail.gmail.com> <25B4902B1192E84696414485F5726854018A2B5D@SJCEML701-CHM.china.huawei.com> <CALx6S36gazGd56nDs2W7afCbmnmNC49Xx2t5vPvgZvMSzf=NbQ@mail.gmail.com>
Cc: "5gangip@ietf.org" <5gangip@ietf.org>, Behcet Sarikaya <sarikaya@ieee.org>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, "ideas@ietf.org" <ideas@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <00dfb61c-c7a8-937c-13c7-49be5eb95016@huitema.net>
Date: Wed, 10 May 2017 20:20:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CALx6S36gazGd56nDs2W7afCbmnmNC49Xx2t5vPvgZvMSzf=NbQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 168.144.250.177
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.23)
X-Recommended-Action: accept
X-Filter-ID: s0sct1PQhAABKnZB5plbIVbU93hg6Kq00BjAzYBqWlVTHAar8Je/lORhy3PZJU8LERWeKKG4PAQY Nyavp7c49L/N1imVzxQGuMdyq1ILpVFTugiLDom8V25hond3K4RsO76XSTAwtV4mg4i2ouCDa4AU hvIWAV5xUW/+gAh4vXqIuuGbTutqzx29YiMrlFybRcOb18WfxGyg6Om6u4YYm0kTIEHsEw9hckUT vZQDFRE5hjoyEb9Oq0NWpyO3vrfYNrJwCbVSZviV1vzVlxiUlT3dKxLhoxcmaInYbR5vlqGudzLe k2TYFBStSOMccbr5Uz0sPgnpAk2KA2vJwMd1uWhCmLzOxTAcQmFWVARhgNqBNFD3an3wiMp49rVr ybSBe34TY+s3lj/RgDQoaICKQ3TFgIfDMShmlQFqCr5hA8xAXSGwpLGc/Znuh3MoIpK0hW7LlxPu vmfFp+vapGvwW7bRF0J+AL6gRRwFcty0/RGJ+cv73CChOPjKA0/DVd83mzKXD5o/Ia+BqyQ7Q0nt IZ2PVtMHd8bHCmdzlxzVIEgwyGTHIAoNFX+jcW7DGmdE6eBVl9/A6GtGi+mfMSANmgQ9/T0zHbtC pLbhgZ6Z/Qhqxiuap5uKiBpffUsHYsfmrbtbs8GJuRKR6hnrta1usy6F/SOWlhnS7qkS/mOkSgD5 8bDUIriOSOQTK7vaz2jBsjp0rjSY76LAIHA6cW4Oa33MXDoedmhl3qqejWLNmYd/R6/ammP7shp5 resthocSxdwDV/LdQk4Dnvnv/o4ZpIN8Tfe43vaXKX/yihCEqxIlRZaHuAWSnHeK3PdSA6Q+2n/k rhIYlNMbfS0wdTtG+y0nBWqy6iuzP6LY3AueKIqKe72V7y3QDXL8JTpxprEN
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/aGueE52wBJ8ela9hYHgkWhjP1Q4>
Subject: Re: [Ideas] [5gangip] FW: New Version Notification for draft-xyx-5gip-ps-00.txt
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2017 03:20:58 -0000


On 5/10/2017 5:58 PM, Tom Herbert wrote:
> So it's really the locator address for a node that changes, not the
> the identifier. The system needs to ensure that packets delivered to
> the application always get the identifier address and that keeps
> source address persistent.
And this stable identifier has horrendous privacy issues. Or can have,
especially if you were to have a design in which a mobile device has
just one such identifier and keeps it all the time. It becomes a
beautiful tracking beacon.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email