IETF Logo Mail Archive

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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 05 February 2018 20:11 UTC

Return-Path: <alexandre.petrescu@gmail.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 1A6FC12D82C for <ipv6@ietfa.amsl.com>; Mon, 5 Feb 2018 12:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 uR37mMi9gSJV for <ipv6@ietfa.amsl.com>; Mon, 5 Feb 2018 12:11:29 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 CEC6312D879 for <ipv6@ietf.org>; Mon, 5 Feb 2018 12:11:28 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w15KBROi026126 for <ipv6@ietf.org>; Mon, 5 Feb 2018 21:11:27 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4DDE120453D for <ipv6@ietf.org>; Mon, 5 Feb 2018 21:11:27 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3B21D204508 for <ipv6@ietf.org>; Mon, 5 Feb 2018 21:11:27 +0100 (CET)
Received: from [132.166.84.204] ([132.166.84.204]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id w15KBQub021139 for <ipv6@ietf.org>; Mon, 5 Feb 2018 21:11:26 +0100
Subject: Re: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])
To: ipv6@ietf.org
References: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com> <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <04bbf4d5-5eeb-4944-7a71-7606fcf671aa@gmail.com>
Date: Mon, 05 Feb 2018 21:11:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5EUVKEK2swF0UOsQzf8TgslE1qo>
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, 05 Feb 2018 20:11:32 -0000


Le 02/02/2018 à 09:05, Ole Troan a écrit :
>>
>>> 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.

Alex

> 
> Ole
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email