Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address
Erik Kline <ek@google.com> Tue, 11 July 2017 09:50 UTC
Return-Path: <ek@google.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 B2C501242F7 for <v6ops@ietfa.amsl.com>; Tue, 11 Jul 2017 02:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 JcLhcAosBzkH for <v6ops@ietfa.amsl.com>; Tue, 11 Jul 2017 02:50:18 -0700 (PDT)
Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C1A112EB99 for <v6ops@ietf.org>; Tue, 11 Jul 2017 02:50:18 -0700 (PDT)
Received: by mail-yb0-x230.google.com with SMTP id p207so36199100yba.2 for <v6ops@ietf.org>; Tue, 11 Jul 2017 02:50:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wL2bjXh17Nex7jEmfVgix/0O9/ImAf/CXIrCCsmUDyg=; b=dKAspF58JfIYeISro4fo7lM/1KRcu7GAR6uSF5OcZ/rdEghCSIK0SncmOkfZfFmju6 ZY3fEJjl/jv/DioGRp1FfELqzZbTAXDm3c041lY0JVKL0zKWTJMCmUtprY5C0qQUL003 1nOS5o1z1e6mTI2d9nENjEMp6wNib0NYzYpdpqRxD7b2vBVReUKrbIR+BPD+dLcVkrMu ZsGM3OpbgCn5mXHbSCCz/oPFNO4vHJHTdhbKKvSahVJXGPyYVE0RIWcMlTHlEakQvPhk dpY3e0LXdWkJr7qbU/o+c7vHl/2WOVax9iKVUAajcNWpjrkwf6Bn2RIuvoq9cKg4TZXl 2ZCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wL2bjXh17Nex7jEmfVgix/0O9/ImAf/CXIrCCsmUDyg=; b=At6NNQo5PhVn1K0n/9tE4cGUO2lSF174WqJOLae6RNG8+uxCUzw4Hf6q5kSbIvz6R0 v+50EVAxbSs1JmXk0TSINwjIcudbF63SkPEevjQvZkvtZx2As6jjHOr75Aaykyz73Iqu EbRMEAsg9nYngA5Lf9ultOyqrPuvV7t8/qTXBmzRUpc63mYzpc24lgqnrAP62XiY6fov LUdjvrZOgaBzFLmXwmB0wbvCH2dgb7lkBCjBHx0kf4PR4Dva6vqP9p1WGxT2y654iuA8 aUB2iumZbSS2xR6x6NymTW3YLmyCp7dAUZuksqMi0gd3GDqRWxaLwysEgExgOSAl1lvL GmBw==
X-Gm-Message-State: AIVw110O/jFkABfr49I3Tv2DUls1ad4BuIM6jqaanjpLs1nVa5rFgCqg BXhIYITlp2tf/oFJDGpsjYEo6NbkrQQi
X-Received: by 10.37.11.5 with SMTP id 5mr1290123ybl.235.1499766617682; Tue, 11 Jul 2017 02:50:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.217.69 with HTTP; Tue, 11 Jul 2017 02:49:56 -0700 (PDT)
In-Reply-To: <cf949edc-a041-3dee-48ff-3a7bed854279@gmail.com>
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>
From: Erik Kline <ek@google.com>
Date: Tue, 11 Jul 2017 18:49:56 +0900
Message-ID: <CAAedzxr_juRWS+AT1gCfjobpHMvUped4gS7uFCbUcPP7qFgLxQ@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: mohamed.boucadair@orange.com, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a11c047c084e907055407a011"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/sYtJZgFpHFxf0DC3o0nc9h8oi9w>
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 09:50:21 -0000
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
- [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