IETF Logo Mail Archive

Re: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])

Ole Troan <otroan@employees.org> Fri, 02 February 2018 08:05 UTC

Return-Path: <otroan@employees.org>
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 1CD9B12F4E2 for <ipv6@ietfa.amsl.com>; Fri, 2 Feb 2018 00:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 deIQs2Ocgn4G for <ipv6@ietfa.amsl.com>; Fri, 2 Feb 2018 00:05:32 -0800 (PST)
Received: from accordion.employees.org (accordion.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35ADC12EC18 for <ipv6@ietf.org>; Fri, 2 Feb 2018 00:05:32 -0800 (PST)
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id 7D6ED2D51A3; Fri, 2 Feb 2018 08:05:31 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 55B95201A52C1D; Fri, 2 Feb 2018 09:05:29 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Message-Id: <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_1ECF85F0-8709-4FC7-B5C4-BF1B58C3B20C"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Subject: Re: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])
Date: Fri, 02 Feb 2018 09:05:28 +0100
In-Reply-To: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, 6man WG <ipv6@ietf.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6D4OUT-phfGFd_4OaCbCmi1xcWk>
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: Fri, 02 Feb 2018 08:05:34 -0000

> 
>> I'd prefer if we took some of DHCPv6 option space, some of the state
>> machines, and ditched the rest, and explained how this was done using
>> something else, for instance ND.
>> 
>> But short of that yes, there should be operational documents (in v6ops
>> perhaps) that tells implementors how SLAAC and DHCPv6 works together, and
>> what certain SLAAC messages means for DHCPv6 based resources.
> 
> Let's start with embedding DHCPv6 PD messages in IPv6 ND RS/RA options
> and see where that takes us.

If you were going to design a new configuration protocol in 2018, is that really where you would start?

Ole

v2.23.0 | Report a Bug | By Email