Re: [v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem

Fernando Gont <fgont@si6networks.com> Thu, 12 January 2017 09:52 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C935312955A for <v6ops@ietfa.amsl.com>; Thu, 12 Jan 2017 01:52:10 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 UquJgaHhMoeX for <v6ops@ietfa.amsl.com>; Thu, 12 Jan 2017 01:52:09 -0800 (PST)
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 83F8E12953E for <v6ops@ietf.org>; Thu, 12 Jan 2017 01:52:09 -0800 (PST)
Received: from [192.168.3.88] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 C07B882C32; Thu, 12 Jan 2017 10:52:06 +0100 (CET)
To: otroan@employees.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <SN1PR0501MB20626C57C61FA1E9EB9DFA92AE660@SN1PR0501MB2062.namprd05.prod.outlook.com> <89c6a9a4-e561-dee3-8899-17ae50ae4c2a@gmail.com> <44FCCC34-7995-4E10-85E9-58C08C371416@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <0453eb8d-757a-38c5-6e7e-40bda416acba@si6networks.com>
Date: Thu, 12 Jan 2017 06:51:36 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <44FCCC34-7995-4E10-85E9-58C08C371416@employees.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/c8RHRCCmkghrvqQLwdyHPwcQCLE>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-dhcpv6-slaac-problem
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2017 09:52:11 -0000

Hi, Ole,

On 01/12/2017 05:45 AM, otroan@employees.org wrote:
>> This draft describes real issues but the information is a bit out
>> of date. Can we ask the authors to confirm that things are still
>> the same for current o/s releases? Then publish quickly so that we
>> can start the *real* discussion: how to fix?
> 
> This draft shouldn't be gating any real discussion. If there are
> solutions please offer them now.

Noting the problem, and providing datapoints is useful, IMO.



> I have read through the draft again. While the draft has some points,
> these are issues that has been discussed extensively. I struggle to
> see how this will lead to and "fixes".
> 
> I have a suggestion. Given that we have beaten on this particular
> horse a lot over the last 15 years. Could we redo this draft into a
> "Why?" draft in the style of RFC7421? Explain the issues, explain the
> design choices and why the mechanisms function as they do, but don't
> phrase it as a problem that needs to be fixed.

The fact that you get different outcomes for different systems, setups,
etc., does not seem nice to me.

As to the why...I wonder if a "well, there's the slaac folks, and the
dhcpv6 folks..." document would be "publishable"..

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