Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA
<mohamed.boucadair@orange.com> Wed, 12 July 2017 12:02 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 458BC12EB99 for <v6ops@ietfa.amsl.com>; Wed, 12 Jul 2017 05:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.62
X-Spam-Level:
X-Spam-Status: No, score=-1.62 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ZAyAYh5r5ERW for <v6ops@ietfa.amsl.com>; Wed, 12 Jul 2017 05:02:18 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24838131562 for <v6ops@ietf.org>; Wed, 12 Jul 2017 05:02:18 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id C852A160317; Wed, 12 Jul 2017 14:02:16 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id A8B9F600DF; Wed, 12 Jul 2017 14:02:16 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0352.000; Wed, 12 Jul 2017 14:02: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 and GUA
Thread-Index: AQHS+wPV7ER1Db9IiEeiglihfmhZ7KJQFg7A
Date: Wed, 12 Jul 2017 12:02:16 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93300A003E4C@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> <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> <6c43cf08-0bd6-daf4-ea9d-d52c34db2a8c@gmail.com>
In-Reply-To: <6c43cf08-0bd6-daf4-ea9d-d52c34db2a8c@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.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/u1jd-xKifd4eURNxrIYcYPJGoj0>
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 12:02:19 -0000
Alex, The key part is not to use (or not) a GUA, but ... The GGSN shall not generate any globally unique IPv6 addresses for itself using the Prefix assigned to the MS in the Router ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Advertisement. Cheers, Med > -----Message d'origine----- > De : Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com] > Envoyé : mercredi 12 juillet 2017 13:42 > À : BOUCADAIR Mohamed IMT/OLN; v6ops@ietf.org > Objet : Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and > GUA > > 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. > >
- [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the L… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Erik Kline
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Mark Smith
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Erik Kline
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Gert Doering
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Gert Doering
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Erik Kline
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Lorenzo Colitti
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… 神明達哉
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Lorenzo Colitti
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… 神明達哉
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split … Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - TE/MS split … mohamed.boucadair
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… holger.metschulat
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… holger.metschulat
- Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in t… Alexandre Petrescu