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> Wed, 07 February 2018 14:23 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 41D1312D778 for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 06:23:22 -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 qlm66TRtPZWt for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 06:23:20 -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 7C89E129C6E for <ipv6@ietf.org>; Wed, 7 Feb 2018 06:23:20 -0800 (PST)
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (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 5A81B2D508A; Wed, 7 Feb 2018 14:23:19 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id A1ED2201B87F52; Wed, 7 Feb 2018 15:23:16 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Message-Id: <3DBDC8F8-DCE0-412E-884A-9AD701A921B6@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_988B414B-DC1B-45BF-BA27-8FB2CEEDC3B1"; 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: Wed, 07 Feb 2018 15:23:15 +0100
In-Reply-To: <04bbf4d5-5eeb-4944-7a71-7606fcf671aa@gmail.com>
Cc: 6man WG <ipv6@ietf.org>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com> <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org> <04bbf4d5-5eeb-4944-7a71-7606fcf671aa@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SI5q2pkYBVRNU7Q20m5gEqoXtSE>
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: Wed, 07 Feb 2018 14:23:22 -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?
> 
> Err, yes.
> 
> Like the new transport protocol QUIC is transported in the old transport protocol UDP, or so I am told.

And just like QUIC this would be a new protocol.

Ole

v2.23.0 | Report a Bug | By Email