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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 11 July 2017 10:09 UTC

Return-Path: <alexandre.petrescu@gmail.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 B3EF8127866 for <v6ops@ietfa.amsl.com>; Tue, 11 Jul 2017 03:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 oYXTVWe4R7as for <v6ops@ietfa.amsl.com>; Tue, 11 Jul 2017 03:09:30 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 C40ED127180 for <v6ops@ietf.org>; Tue, 11 Jul 2017 03:09:29 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v6BA9RHL017000; Tue, 11 Jul 2017 12:09:27 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F3580204B64; Tue, 11 Jul 2017 12:09:26 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E3EC1201587; Tue, 11 Jul 2017 12:09:26 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v6BA9Q2d013223; Tue, 11 Jul 2017 12:09:26 +0200
To: Erik Kline <ek@google.com>
Cc: mohamed.boucadair@orange.com, "v6ops@ietf.org" <v6ops@ietf.org>
References: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002E21@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <a67eb7d0-be6a-f158-b05c-fda0f38e09d6@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002EF9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <1be23f5b-f449-9924-8322-f21c4ccbd09e@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002F95@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <2c325097-651e-501c-747a-e7a322c3d844@gmail.com> <787AE7BB302AE849A7480A190F8B93300A0032B6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <cf949edc-a041-3dee-48ff-3a7bed854279@gmail.com> <CAAedzxr_juRWS+AT1gCfjobpHMvUped4gS7uFCbUcPP7qFgLxQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b6148d1e-6df3-dddb-f632-388ee1d5ba6d@gmail.com>
Date: Tue, 11 Jul 2017 12:09:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAAedzxr_juRWS+AT1gCfjobpHMvUped4gS7uFCbUcPP7qFgLxQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MvA1x_-nQkos4vcTv-ZB7CI9JSs>
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: Tue, 11 Jul 2017 10:09:32 -0000

What do you mean by 'not very common'?  Is it little common in some 
small place?

PD from ll src: I think the DHCP spec does not tell whether it could be 
an LL or a GUA.  I asked on the DHC WG email list.  The operator seems 
to prefer to hear the DHCP Solicit to be issued from a GUA.

Le 11/07/2017 à 11:49, Erik Kline a écrit :
> Is your carrier known to support PD?  I don't think it's very common
> yet.  Also, shouldn't you be sending your PD request from a link-local
> source address?
> 
> On 11 July 2017 at 18:28, Alexandre Petrescu
> <alexandre.petrescu@gmail.com> wrote:
>>
>>
>> Le 11/07/2017 à 08:51, mohamed.boucadair@orange.com a écrit :
>>>
>>> Hi Alex,
>>>
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>>
>>>> -----Message d'origine-----
>>>> De : Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
>>>> Envoyé : lundi 10 juillet 2017 18:28
>>>> À : BOUCADAIR Mohamed IMT/OLN; v6ops@ietf.org
>>>> Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
>>>>
>>>>
>>>>
>>>> Le 10/07/2017 à 16:58, mohamed.boucadair@orange.com a écrit :
>>>>>
>>>>> Re-,
>>>>>
>>>>> Please see inline.
>>>>>
>>>>> Cheers,
>>>>> Med
>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
>>>>>> Envoyé : lundi 10 juillet 2017 16:46
>>>>>> À : BOUCADAIR Mohamed IMT/OLN; v6ops@ietf.org
>>>>>> Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
>>>>>>
>>>>>>
>>>>>>
>>>>>> Le 10/07/2017 à 16:16, mohamed.boucadair@orange.com a écrit :
>>>>>>>
>>>>>>> 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!
>>>>>>
>>>>>>
>>>>>> YEs, and I thought that is a device-specific identifier like the IMEI,
>>>>>> not the link-local address.
>>>>>>
>>>>>>> At the IP level, an UE is identified by the bits of the IPv6 prefix,
>>>>>>>     not IID bits.
>>>>>>
>>>>>>
>>>>>> Well - by the IP address.
>>>>>
>>>>>
>>>>> [Med] No. I reiterate my answer: it is identified by the prefix not the
>>>>
>>>> full IPv6 address.  Policies at the network are enforced based on the
>>>> prefix, not the full IPv6 address.
>>>>>
>>>>>
>>>>>>
>>>>>>> Further, a network does not need IP-related information to identify
>>>>>>> an UE.
>>>>>>
>>>>>>
>>>>>> I agree, so why does it want to impose an IID to the UE?
>>>>>
>>>>>
>>>>> [Med] This is an optimization to avoid DAD.
>>>>
>>>>
>>>> Ok about LL, but how about the GUA?
>>>
>>>
>>> [Med] No problem at that front either (reading from the 3GPP spec):
>>>
>>> ==
>>> Since the GGSN guarantees that the Prefix is unique, the MS does not need
>>> to perform any Duplicate Address Detection on addresses it creates.
>>> ==
>>>
>>>     If the network uses a GUA same as
>>>>
>>>> the UE then there should be DAD for that GUA.
>>>
>>>
>>> [Med] Idem as above, the spec is clear:
>>>
>>> ==
>>> The GGSN shall not generate any globally unique IPv6 addresses for itself
>>> using the Prefix assigned to the MS in the Router Advertisement.
>>> ==
>>>
>>>>
>>>> I dont think there is any spec that tells that the network MUST NOT
>>>> assign a GUA on its interface towards the UE.
>>>
>>>
>>> [Med] See for example, 3GPP TS. 29.061
>>>
>>>>
>>>>
>>>>
>>>>>>> I still don't see any privacy concern in supplying an IID to an UE
>>>>>>> to be used for forming its link-local address.
>>>>>>
>>>>>>
>>>>>> Err...
>>>>>>
>>>>>> It's because the supplied IID is very much like an IEEE MAC 48bit
>>>>>> address.
>>>>>
>>>>>
>>>>> [Med] This is a link-local address not a GUA. So, not sure to understand
>>>>
>>>> your point.
>>>>
>>>> I can understand your point about GUA privacy vs LL privacy.
>>>
>>>
>>> [Med] OK.
>>
>>
>> Med - why there is no answer to my DHCPv6 PD Solicit?  I am using a GUA
>> without the IID from the operator.
>>
>> Alex
>>
>>
>>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops