IETF Logo Mail Archive

Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address

<mohamed.boucadair@orange.com> Mon, 10 July 2017 14:16 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E15812F3D6 for <v6ops@ietfa.amsl.com>; Mon, 10 Jul 2017 07:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 aWzjbfTJ0KwE for <v6ops@ietfa.amsl.com>; Mon, 10 Jul 2017 07:16:18 -0700 (PDT)
Received: from relais-inet.orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 661CC13174D for <v6ops@ietf.org>; Mon, 10 Jul 2017 07:16:18 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id C6AA94053D; Mon, 10 Jul 2017 16:16:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.61]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id A314F1A00A4; Mon, 10 Jul 2017 16:16:16 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM7E.corporate.adroot.infra.ftgroup ([fe80::b91c:ea2c:ac8a:7462%19]) with mapi id 14.03.0352.000; Mon, 10 Jul 2017 16:16:16 +0200
From: mohamed.boucadair@orange.com
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
Thread-Index: AQHS+YOPPey6jPfoA0yB3PY8fHlvUKJNGKhg
Date: Mon, 10 Jul 2017 14:16:16 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A002EF9@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002E21@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <a67eb7d0-be6a-f158-b05c-fda0f38e09d6@gmail.com>
In-Reply-To: <a67eb7d0-be6a-f158-b05c-fda0f38e09d6@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eCYdGrT7bQjsltHYpQBNCBiZ5_Y>
Subject: Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 14:16:19 -0000

Alex, 

I'm focusing on this part of your answer. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
> Envoyé : lundi 10 juillet 2017 15:51
> À : BOUCADAIR Mohamed IMT/OLN; v6ops@ietf.org
> Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
> 
> Med,
> 
> 
> >> This has consequences on privacy, and may impact interoperability
> >> when DHCPv6-PD is used later in the process.
> >
> > [Med] I don't follow you here. There is no privacy concern out
> > there. The IID used when forming a global IPv6 address will be
> > selected by the terminal; no assumption is made about those bits.
> 
> There is a privacy concern: if the operator enforces the UE to always
> use the network-assigned IID then that UE is trackable.
> 

[Med] I'm not sure what you mean by "trackable" in this context. If you mean that "a UE can be identified by the network", then an UE is always identified by the network it connects to! At the IP level, an UE is identified by the bits of the IPv6 prefix, not IID bits. Further, a network does not need IP-related information to identify an UE. 

I still don't see any privacy concern in supplying an IID to an UE to be used for forming its link-local address.

v2.23.0 | Report a Bug | By Email