Re: default-iids: dropping requirement 1 in Section 3

Fernando Gont <fgont@si6networks.com> Sun, 22 May 2016 19:41 UTC

Return-Path: <fgont@si6networks.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 7D81912D592 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zfbYdMrjU1u5 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41:08 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4591D12D583 for <ipv6@ietf.org>; Sun, 22 May 2016 12:41:08 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B4FAD80A53; Sun, 22 May 2016 21:41:03 +0200 (CEST)
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Alissa Cooper <alissa@cooperw.in>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57420B44.6080209@si6networks.com>
Date: Sun, 22 May 2016 15:40:52 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EPDUeCfhD8y0ZIKrKTcNH_1yHbs>
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: Sun, 22 May 2016 19:41:13 -0000

On 05/20/2016 05:06 PM, Alissa Cooper wrote:
> 
>> On May 18, 2016, at 1:26 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>> What if we dropped requirement #1 in Section 3, but left the rest the same? This would open the door such that people who wanted to comply with the SHOULD-level recommendation in this spec in the presence of randomized MAC addresses still could (e.g., by implementing 7217 and using the randomized MAC as the Net_Iface parameter), but directly embedding a MAC address in the IID would still go against the SHOULD NOT recommendation here.
> 
> I don’t think I saw anyone respond to this suggestion, so I’d like to ask again for people’s opinions about this.
> 
> To my eye this is a nice compromise.

That's a bad idea.

The reason why is  draft-gont-predictable-numeric-ids-00, RFC4941, and
even some RFC (?) by the IAB.

The root of this whole problem is embedding a layer-2 id in a layer-3
field in the first place.

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