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

Philip Homburg <pch-v6ops-8@u-1.phicoh.com> Mon, 13 November 2017 15:17 UTC

Return-Path: <pch-bCE2691D2@u-1.phicoh.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 050CF129454; Mon, 13 Nov 2017 07:17:19 -0800 (PST)
X-Quarantine-ID: <Grf8iFspwgVe>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
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] 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 Grf8iFspwgVe; Mon, 13 Nov 2017 07:17:17 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1AE1129AC1; Mon, 13 Nov 2017 07:17:16 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1eEGU6-0000GEC; Mon, 13 Nov 2017 16:17:14 +0100
Message-Id: <m1eEGU6-0000GEC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: Victor Kuarsingh <victor@jvknet.com>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: [v6ops] Stateful SLAAC (draft-ietf-v6ops-unique-ipv6-prefix-per-host)
From: Philip Homburg <pch-v6ops-8@u-1.phicoh.com>
Sender: pch-bCE2691D2@u-1.phicoh.com
References: <be9724f5-2ff5-d90c-2749-ecae2c628b78@si6networks.com> <0b45890d-ea4a-47b8-a650-ceb72b066df8@gmail.com> <ea772bfd-4004-7f94-8469-b50e3aff0f29@si6networks.com> <F2330138-6842-4C38-B5A0-FB40BFACD038@employees.org> <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> <CAJc3aaMKnB8BjHHOqAA3Fj+Ue8KtoW7kPwQLOHu93vivA4Lugg@mail.gmail.com>
In-reply-to: Your message of "Mon, 13 Nov 2017 09:56:12 -0500 ." <CAJc3aaMKnB8BjHHOqAA3Fj+Ue8KtoW7kPwQLOHu93vivA4Lugg@mail.gmail.com>
Date: Mon, 13 Nov 2017 16:17:13 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/quYW2h6GsieShW3JXDtxIFcSYLs>
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 15:17:19 -0000

>I don't see how this work has any impact on what was done in DHC and
>disregards it.  We potentially conflating things here?
>
>Much in the same way RFC8106 (DNS info in RAs) does not disregard
>DHCPv6 since it too can offer DNS information.

There is an interesting dynamics in that any new feature for RA that is a 
essentially a duplicate from what already exists in DHCPv6 gets accepted,
but a simple feature like a default router option in DHCPv6 gets rejected
time and time again because that feature is already provided by RA.