Re: I-D Action: draft-ietf-6man-default-iids-04.txt

Fernando Gont <fgont@si6networks.com> Mon, 06 July 2015 22:03 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8C81A1A9E for <ipv6@ietfa.amsl.com>; Mon, 6 Jul 2015 15:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 gRhG6gnjJQa8 for <ipv6@ietfa.amsl.com>; Mon, 6 Jul 2015 15:03:01 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 4F3C61A1A56 for <ipv6@ietf.org>; Mon, 6 Jul 2015 15:03:01 -0700 (PDT)
Received: from [186.137.82.224] (helo=[192.168.3.107]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1ZCETS-0000lR-8J; Tue, 07 Jul 2015 00:02:51 +0200
Message-ID: <559AF8D0.405@si6networks.com>
Date: Mon, 06 Jul 2015 18:53:20 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>, Kerry Lynn <kerlyn@ieee.org>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-04.txt
References: <20150626053554.16572.72663.idtracker@ietfa.amsl.com> <926657903.827241.1435374995889.JavaMail.yahoo@mail.yahoo.com> <5591BF9C.8080307@si6networks.com> <CAO42Z2zf5-g1aOAWfaDxX47H9w9Kyc0QEX+0oKyzL9nwzCb_DQ@mail.gmail.com> <5592370E.6070705@si6networks.com> <CAO42Z2xacdABghT5W269V9y3aucmh2QQd6AHNLK+MpsaLzeB8g@mail.gmail.com> <55931DAE.8000701@si6networks.com> <CAO42Z2ywMEfXKSSFeSd5DNvEW4URfmTKvaWgxNw6odXRHWW=Jw@mail.gmail.com> <559378AE.70506@si6networks.com> <CABOxzu0WkrFv9a-jjc7Txzg_ronsMucKXsu_7X+mfHyoVFZz0Q@mail.gmail.com> <559AB1CD.6000605@si6networks.com> <CABOxzu2iy8XBbCDv33ZKoA9VcfFj1f9FfVTv88=fSsM7krxguw@mail.gmail.com> <DM2PR0301MB0655C36E42E9EA90BCB1548DA8930@DM2PR0301MB0655.namprd03.prod.outlook.com>
In-Reply-To: <DM2PR0301MB0655C36E42E9EA90BCB1548DA8930@DM2PR0301MB0655.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/klpGCUyPnJN2wdXJi3KjFAE_5_o>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Jul 2015 22:03:03 -0000

Hi, Christian,

On 07/06/2015 06:15 PM, Christian Huitema wrote:
> 
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Kerry Lynn 
> Sent: Monday, July 6, 2015 10:16 AM To: Fernando Gont Cc:
> ipv6@ietf.org; Dave Thaler; Ralph Droms;
> draft-ietf-6man-default-iids@tools.ietf.org
>>> As the lead author of 
>>> https://tools.ietf.org/html/draft-ietf-6man-6lobac, I'm strongly
>>> in favor of retaining the option to specify IIDs based on
>>> locally assigned link-layer addresses, particularly for
>>> link-local addresses.
>> 
>> FWIW, this has never been under question. That is, the question is 
>> regarding the wording, not about the intent. Based on past wg
>> discussion and consensus, we all agree that there must be room to
>> go against this advice if design/engineering tradeoffs warrant
>> this.
> 
> Part of the problem is that "link layer address," as a category, is
> no well-defined.
> 
> I would prefer something stronger, like " Future specifications
> SHOULD NOT specify IPv6 address generation schemes that embed the
> underlying link-layer address in the IID. In some cases, where
> engineering constants dictate, identifiers MAY include a short
> dynamically assigned link-layer address. Notwithstanding that,
> specification MUST NOT embed a globally unique identifier such as an
> IEEE802 address or a E.164 phone number."

Two comments:

1) Getting into the underlying details can be tricky: short and
temporary identifiers might be "good enough" wrt host-tracking, but
certinaly not god when it comes to network reconnaissance. So I'd keep
things the discussion as is.. otherwise one would need to get into a
discussion ov every sort of identifier that might be employed in the
future... and we might even fail to envision them.

2) I'm myself in the camp of "MUST NOT use IEEE802 addresses or the
like"... but given that the requirements in this document have been kind
of wordsmithed among a number of groups and people, the more we tweak
the text, the more ths might take forever. I'd say that the current text
(if anything, modulo some minor edits) is good enough...

Just my 2 cents.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492