Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt

Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 28 October 2013 10:33 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE1A421E8093 for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.271
X-Spam-Level:
X-Spam-Status: No, score=-10.271 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YA0M-INRaXcH for <ipv6@ietfa.amsl.com>; Mon, 28 Oct 2013 03:32:56 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 4E10411E8147 for <ipv6@ietf.org>; Mon, 28 Oct 2013 03:32:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9SAWmCx011128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Oct 2013 11:32:48 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9SAWmeX006229; Mon, 28 Oct 2013 11:32:48 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9SAWilp009591; Mon, 28 Oct 2013 11:32:48 +0100
Message-ID: <526E3D4D.1060103@gmail.com>
Date: Mon, 28 Oct 2013 11:32:45 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
Subject: Re: I-D Action: draft-gont-6man-deprecate-eui64-based-addresses-00.txt
References: <20131021224345.32495.19727.idtracker@ietfa.amsl.com> <52697C33.7010904@gmail.com> <526AA1A3.2020009@gmail.com> <526AAC0F.8020906@si6networks.com>
In-Reply-To: <526AAC0F.8020906@si6networks.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Oct 2013 10:33:05 -0000

Le 25/10/2013 19:36, Fernando Gont a écrit :
> On 10/25/2013 01:51 PM, Alexandru Petrescu wrote:
>>
>> Not only operationally it may prove difficult to upgrade everything
>> from RFC2464, but all the IPv6-over-foo specs of future deployment
>> may need to accept it as well.
>
> Huh?
>
> Can you elaborate how this affects deployment?

If this spec draft-gont-6man-deprecate-eui64-based-addresses says that
IIDs derived from hardware identifiers are forbidden, and other specs
say that they are mandatory, then there may be a problem.

> Are you suggesting that we ignore well-known problems?

No.

> Are you suggesting that we stick to a feature that allows simple
> location tracking?

Location tracking, as well as other similar characteristics, are bad
when looked at from a prism, and are good when looked at from somewhere
else.

> Or.. maybe you're fine with people deploying IPv6 NAT and that kind
> of middle-box to mitigate this sort of thing?

Yes and no.

IPv6 NAT and NPT are there to be used, and are needed.

No, in that they are needed because more than just its indirect privacy
features.  They are needed also because DHCPv6-PD is not deployed by
cellular operators, and also because SLAAC over Ethernet works with
prefixes length smaller or equal 64.

If you make IIDs which are independent of the hardware ID you'd still
need to make cellular operators deploy DHCPv6-PD and make SLAAC/Ethernet
with longer than 64 prefixes.  Otherwise IPv6 NAT and NPT are still needed.

> An old-timer (who preferred to remain anonymous) just sent me this
> off-list:

Ok.

Alex