Re: [dhcwg] DHCPv6 and IPv6ND

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 14 November 2017 14:30 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18345126C89 for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 06:30:37 -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 SsW7X8wtbn-8 for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 06:30:34 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 28724124B0A for <dhcwg@ietf.org>; Tue, 14 Nov 2017 06:30:34 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAEEUWLY004692 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 15:30:32 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5FA4520556D for <dhcwg@ietf.org>; Tue, 14 Nov 2017 15:30:32 +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 56850202807 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 15:30:32 +0100 (CET)
Received: from [132.166.85.172] ([132.166.85.172]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAEEUU1h027601 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 15:30:31 +0100
To: dhcwg@ietf.org
References: <cf2e41a05fd742a3b576ee317c5392f6@XCH15-06-08.nw.nos.boeing.com> <E94F8CD6-EC4E-4B61-92B6-99FBD1D494A4@fugue.com> <8d935331012947aa942e8dc2a48d889f@XCH15-06-08.nw.nos.boeing.com> <54D1B686-A5FA-42A0-8A57-067562313488@fugue.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <38ef2544-df5c-4677-ffaa-7b084eb300fa@gmail.com>
Date: Tue, 14 Nov 2017 15:30:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <54D1B686-A5FA-42A0-8A57-067562313488@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/EfxwtLPiZr7MDWkUREXKSQU7O-Q>
Subject: Re: [dhcwg] DHCPv6 and IPv6ND
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2017 14:30:37 -0000


Le 14/11/2017 à 08:38, Ted Lemon a écrit :
> On Nov 14, 2017, at 2:20 PM, Templin, Fred L <Fred.L.Templin@boeing.com 
> <mailto:Fred.L.Templin@boeing.com>> wrote:
>> I
>> think I have a fair question. How can we get the functionality of IPv6ND
>> RA and DHCPv6 PD in a single request/response message exchange?
> 
> Right now, you can't.   The question is, why is this a problem?
> 
> We've been around on this a lot of times.   I don't see any reason to do 
> it again.   But if you want to do it, you need to say why it's a problem 
> that you have to do router discovery, why it's better to configure the 
> DHCP server with router topology information, how you're going to get 
> the right router link-local address to send, and why all of this 
> complexity is somehow a better solution than router advertisements.

Ted,

The combined use of DHCPv6 and SLAAC is an unsolved problem in cellular 
networks.  Add to that the implications of the use of an undocumented 
link-layer setup protocol ("PDP") in the address formation.

A second aspect is that for full configuration one must use both 
DHCPv6-PD and SLAAC.

If we agree to those two points then it's easy to see the consequences 
which go along the lines that Fred proposes.

But if people dont agree DHCPv6 is needed, then it's a waste of time to 
explain.

One could as well go to 3GPP and tell them to offer not only address 
setup in PDP but also prefix delegation.  That may be less time to spend 
than do it at IETF.

Alex

> 
> It's not good enough to just say "I'd really rather use DHCPv6 for this, 
> can't we specify that?"
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>