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

Fernando Gont <fgont@si6networks.com> Sun, 22 May 2016 20:24 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 E26AA12B037 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:21 -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 BvtY1-qLtCGR for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:19 -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 7870B12D1DA for <ipv6@ietf.org>; Sun, 22 May 2016 13:24:19 -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 DD8B780A53; Sun, 22 May 2016 22:24:16 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Fernando Gont <fernando@gont.com.ar>
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> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <573F947E.7020108@gont.com.ar> <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
Message-ID: <57420E50.2050007@si6networks.com>
Date: Sun, 22 May 2016 15:53: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: <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Aw15zm6IyP2MGjVKfLr7wp5_Zp0>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
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 20:24:22 -0000

On 05/22/2016 12:23 AM, Lorenzo Colitti wrote:
> On Sat, May 21, 2016 at 7:49 AM, Fernando Gont <fernando@gont.com.ar
> <mailto:fernando@gont.com.ar>> wrote:
> 
>     > Excellent! Now, if we can only make this draft stop saying that that you
>     > SHOULD NOT do that...  :-)
> 
>     This draft does not say and never say that. Please stop saying that, or
>     quote the offending text, such that we remove it, and we can make
>     progress.
> 
> 
> Let me restate it again: the draft says "hosts SHOULD use RFC7217 when
> they would otherwise have configured a stable IID". By my reading, that
> is equivalent to saying "hosts SHOULD use RFC7217 all the time", because
> currently hosts MUST configure stable IIDs all the time.
> 
> I already proposed a solution: say that generating a stable IID is OPTIONAL.

This goes beyond what this document was meant to do. BUt if the wg wants
this document to also do that, I'm fine. I guess that if we were to do
that, this document now also needs to update RFC4941, or can we keep it
otherwise "as is"?

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