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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 12 July 2017 11:41 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 778BE12ECC1 for <v6ops@ietfa.amsl.com>; Wed, 12 Jul 2017 04:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 qQe4jbH72o20 for <v6ops@ietfa.amsl.com>; Wed, 12 Jul 2017 04:41:42 -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 C8554127342 for <v6ops@ietf.org>; Wed, 12 Jul 2017 04:41:41 -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 v6CBfe3N018967; Wed, 12 Jul 2017 13:41:40 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 023DE2081BF; Wed, 12 Jul 2017 13:41:40 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E94062055A4; Wed, 12 Jul 2017 13:41:39 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v6CBfdwo010710; Wed, 12 Jul 2017 13:41:39 +0200
To: 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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6c43cf08-0bd6-daf4-ea9d-d52c34db2a8c@gmail.com>
Date: Wed, 12 Jul 2017 13:41:39 +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: <787AE7BB302AE849A7480A190F8B93300A0032B6@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ymn0CGVcEZngg_hk0vE8bf3Emys>
Subject: Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA
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: Wed, 12 Jul 2017 11:41:43 -0000

Med,

[...]
>>>>> 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 think that spec is wrong (3GPP TS. 29.061?).

Because, in practice some operator on some APN puts a GUA (not an LLA) 
on its router's interface towards the UE.  It uses that GUA in the src 
of the RA sent to the UE.  Packet dump available upon request.

Alex

> 
>> 
>> 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.
>