Re: [v6ops] Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)

Fernando Gont <fgont@si6networks.com> Mon, 13 November 2017 14:55 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 71EB0129AB7; Mon, 13 Nov 2017 06:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 ODWeDq7lzULm; Mon, 13 Nov 2017 06:55:44 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1463F127B52; Mon, 13 Nov 2017 06:55:44 -0800 (PST)
Received: from [IPv6:2001:67c:1232:144:ed68:7911:ebe1:178e] (unknown [IPv6:2001:67c:1232:144:ed68:7911:ebe1:178e]) (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 24AE780747; Mon, 13 Nov 2017 15:55:40 +0100 (CET)
Subject: Re: [v6ops] Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)
To: Ted Lemon <mellon@fugue.com>
Cc: Victor Kuarsingh <victor@jvknet.com>, IPv6 Ops WG <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
References: <be9724f5-2ff5-d90c-2749-ecae2c628b78@si6networks.com> <e40697ca-8017-c9d2-c25d-89087046c9cf@gmail.com> <207f040a-7fe2-9434-e7a5-f546b26fdf63@strayalpha.com> <CAKD1Yr26NK2osApYZBm8Yd=0X7xcetrxojp6=JHOEAu9BB0q8A@mail.gmail.com> <8ca59610-2d25-2be4-9d2c-9b1a75fd3ace@si6networks.com> <E67105A3-396B-403C-B741-E9E01CFB5CE7@employees.org> <e7ec4633-8d45-1cff-ce37-48dafd488e13@si6networks.com> <BBAB48C0-384B-4380-9359-7965C7C61D58@employees.org> <4b7e8e53-ea7a-f84d-92cf-a9a113c200ce@si6networks.com> <CAKD1Yr1NG93Jv7E6hKY4BKApwJg6uG0wAgUL74cw1Fb5VsKnUg@mail.gmail.com> <14d489ec-0b28-8fe5-e28c-35a1f4fc15de@si6networks.com> <CAJc3aaPb8vOxfUVk-6sQNGpftegPCgb+j3OyGD55rmCado+VZw@mail.gmail.com> <a4a380b0-d69c-1c2c-fedc-0a3da2a8060a@si6networks.com> <CAJc3aaPg=qOpiwJ29Bq92m2RfZ-VDJtLWb-GgZV7bXP6iELiRA@mail.gmail.com> <d86e4678-7634-5574-3151-056fe92602aa@si6networks.com> <CAPt1N1=qM7kk_NQcm=ibnhv6gf_+JGkUyww6KCMOQ4Lsr8Ttdg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <d8c7dd2e-821c-b2ec-583f-92c42af55ae3@si6networks.com>
Date: Mon, 13 Nov 2017 22:57:24 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1=qM7kk_NQcm=ibnhv6gf_+JGkUyww6KCMOQ4Lsr8Ttdg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jw8VDYQXAbr9mt1qn4i-KTMZrhw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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, 13 Nov 2017 14:55:45 -0000

Ted,

On 11/13/2017 10:31 PM, Ted Lemon wrote:
> Fernando, the document is in AUTH48. If there is a technical problem
> with it that is sufficient to pull it out of the publication queue at
> this point, I haven't heard it yet. I think it would be nice to add a
> little advice on how to manage the state, but it's up to the authors to
> do this or not. This discussion is getting a bit old. 

The technical problem is that this is a v6ops document making SLAAC
stateful. As discussed, making SLAAC stateful brings breakage scenarios
not present in SLAAC, and that is certainly not a minor change.

And having folks noted that they have implemented this sort of behavior
without changing SLAAC, the low-level protocol details in Section 4 are
even less unwarranted.

It is not my call what's the proper action. But I do note that this is
yet another BCP that rather that essentially disregards work of other wg
(dhc), unnecessarily. Are you are pushing a BCP with a mechanism that is
so underspecified, that folks meaning to implement this are likely to
introduce breakage.

That said, it is not my call what's the proper action to follow. My
intent (noted to e.g. Suresh off-line) is not to obstruct the document,
but to avoid breakage -- particularly when it's unwarranted.

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