Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>

Alissa Cooper <alissa@cooperw.in> Thu, 19 May 2016 05:19 UTC

Return-Path: <alissa@cooperw.in>
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 37FD212B057 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 22:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=y6O9hvxs; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ddqEhVLe
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 EHstx-OtiQ8u for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 22:19:49 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B99F12B022 for <ipv6@ietf.org>; Wed, 18 May 2016 22:19:49 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B8831205E1 for <ipv6@ietf.org>; Thu, 19 May 2016 01:19:48 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 19 May 2016 01:19:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=FSultIOKu4M5U6Gt9WrTLyU+qIc=; b=y6O9hv xsnvf+0k54A20VCptg8tDyHsfRF7l4bn73Z2iaH8ZTxtA2uvy0d4iEdSOAwF8dOz tJAXg3E4Q34ZiBk39t1PkYDneLIsWKS0pRob3TMpMzMqvmzaFnIvyh/5Vf/atOw7 qM5pSuT4b3mVajWXoI4CDJQLz5sezToeaWUP4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=FSultIOKu4M5U6G t9WrTLyU+qIc=; b=ddqEhVLecDmGEBk9s5kBhGuxNfpJc2Yj3ocpoXX2hG8Lgsg SM202b/AKLlmP0VZOhlZBFoYJLkFsVqJK169GAO6hPE/+rkNHBckjEa6S4l2wffq BChdMxPIZbNFI/693zkTgSveQitLuZoYg42rYraCLdT30t4VqZQNeL7+ECks=
X-Sasl-enc: v3AyL4xnG4sTE5jYV3spTf6pr5LzL6ThOCvLcekTsGO5 1463635188
Received: from sjc-alcoop-8814.cisco.com (unknown [128.107.241.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 1005EC0001E; Thu, 19 May 2016 01:19:47 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
Date: Wed, 18 May 2016 22:19:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-v5wEci7WJCkqA9T_GQzLJw1BtI>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 19 May 2016 05:19:51 -0000

> On May 18, 2016, at 4:22 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:
> 
> At Tue, 17 May 2016 22:13:36 -0400,
> Fernando Gont <fgont@si6networks.com> wrote:
> 
>>> From this one, and your response to the next point, it seems you are
>>> saying the decision was to refuse to address that concern.  Am I
>>> understanding it correctly?
>> 
>> No. My take is that the concern is flawed. Please read
>> draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
>> length about security and privacy issues regarding reusing identifiers
>> in different context, for different scopes, etc.
>> 
>> Let's call a lemon a lemon: Asking to embed a layer-2 identifier/address
>> in a layer-3 address is extremely bad.
> 
> I don't have a strong position on this matter itself, but my
> understanding of the sense of the wg is that this is controversial,
> and at least far from a clear consensus.  To repeat myself, *my*
> concern on this last call is that it's not even clear, at least to me,
> if this draft tries to say embedding a link-layer address is, whether
> it's randomized or not, "extremely bad" (and must therefore be
> prohibited).  If that's the intent, it should be clearly stated

The draft makes just about a clear a statement in this vein as is possible:

"By default, nodes SHOULD NOT employ IPv6 address generation schemes
   that embed the underlying link-layer address in the IID.”

Note that this statement does not prohibit anything, nor does it make a normative (in the moral sense) judgment. It just states the recommendation, which is the point of the document.

I appreciate that not everyone on the list agrees with this recommendation. But I find the claim that this recommendation is unclear to be difficult to understand. That is, I can’t think of a way to convey the same recommendation that would be clearer. If you can, please suggest text.

Alissa


> and
> backed by a clear consensus from the wg.  Right now I don't see either
> such a clear statement or clear wg consensus.
> 
> --
> JINMEI, Tatuya