IETF Logo Mail Archive

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

Erik Kline <ek@google.com> Mon, 10 July 2017 10:49 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 21E80129AA0 for <v6ops@ietfa.amsl.com>; Mon, 10 Jul 2017 03:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 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_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 HweWMu3Bobra for <v6ops@ietfa.amsl.com>; Mon, 10 Jul 2017 03:49:09 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 428E8126D85 for <v6ops@ietf.org>; Mon, 10 Jul 2017 03:49:09 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id x125so33988740ywa.0 for <v6ops@ietf.org>; Mon, 10 Jul 2017 03:49:09 -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=1YRngpAMZzQW1EcK14Fo5g83ADAMTSCLJiq7WorbImA=; b=LiJ2WDCmfxsmaCZvneHNsj/yf3A4IyVgUkbFATUM7+TAXpttADWOeGTgYMwc5WzB/0 W1F8S8RNUw9Cb9tUQ17NcdnPOkemi7hXuxn3nJkcQ1RvEg6/p2b6AM/9WwFyid9HeE8u Zvf5qjBQ5n5j2efdKDdnQwvIXFvo0BCt96De0zdhKKZPEWVi+oCix/p5xfWU0tkij3bD yQJemFojpub6XoLo/CfWR0uf/z7Mt8rQMRV785Ciw3/8cT+R5IJh2c8kScLB3m42VfSJ NHmks2DEiDUGMHF5r9iHyd7/13VEkilT8uXZoOObWOwDQd4rebqdYS/ChsijLA76zoe8 jGXA==
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=1YRngpAMZzQW1EcK14Fo5g83ADAMTSCLJiq7WorbImA=; b=RoQwh26yKfH99EZT/zQBNdKhndT7QMUg6T4cwQ4raR/xZk9nsm73+urGQT2L/atb8I RT40xdE0HplJ+T2/9IjKuL2A3A9WHyzUZcRk8P+oRLisUJ8naGoDMbhcWWFtsRPni12l ma/1iKwwocW1DiBtSiFP9TfbRvuctFrmEZ4QeoU7QOF4rRbvgBUE3R65ZnA2YFfRH/+c K0sGtjTdJZAsjTZ2IN6i/G0U/9C8O95E67pTt644y8B/AfIH5Pm4GuRCfFIJNO24A8Kw 6D5GicZpzU6uO0tJ+1V/wQUHR5Ctou2kpRK0dmcbsLiS0gwGsf2I8e8MA5uOufZXHbBF n9Qw==
X-Gm-Message-State: AIVw111sd9T2VJ3x8rY/QatQqpmEzFGithC9l2eI80m59fYnt4OKjx6C yBw5o+huV/eNwBF7T5WF8MUT+QRe/IY3Zdc=
X-Received: by 10.129.50.140 with SMTP id y134mr99700ywy.312.1499683748310; Mon, 10 Jul 2017 03:49:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.217.69 with HTTP; Mon, 10 Jul 2017 03:48:47 -0700 (PDT)
In-Reply-To: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com>
References: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com>
From: Erik Kline <ek@google.com>
Date: Mon, 10 Jul 2017 19:48:47 +0900
Message-ID: <CAAedzxok0_eAng+r3WPAdh+OS5tYNSqoVTC8zRL=xoSX0-oSrA@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a1140932a1d2f710553f4550e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7UTtnwMr47qtadiCB402Y8c2xxQ>
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 10:49:11 -0000

It can form other IIDs, but (a) it uses this for link-local and (b)
it's the default used for its GUA.  But sending traffic from other
IIDs is perfectly fine (464xlat on Android does this in fact).

I'm not yet convinced there's much to worry about here.

On 10 July 2017 at 19:11, Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:
> Hi,
>
> The INFORMATIONAL RFC6459 "IPv6 in 3GPP" contains this paragraph:
>>
>> The 3GPP network allocates each default bearer a unique /64 prefix, and
>> uses layer-2 signaling to suggest to the UE an Interface Identifier that is
>> guaranteed not to conflict with the gateway's Interface Identifier.  The UE
>> must configure its link-local address using this Interface Identifier.
>
>
> I disagree that the UE must configure its LL using this IID.  Where is
> this requirement from?
>
> The UE should be allowed to form an IID at its will, if so it wishes.
>
> This has consequences on privacy, and may impact interoperability when
> DHCPv6-PD is used later in the process.
>
> Also, this being an INFORMATIONAL document, in no case a party
> implementing it could impose it on some other party.
>
> Alex
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email