IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 and IPv6ND

Ted Lemon <mellon@fugue.com> Tue, 14 November 2017 14:53 UTC

Return-Path: <mellon@fugue.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 32F2A126C0F for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 06:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 vzfFWJa0qMoE for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 06:53:22 -0800 (PST)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83E32124C27 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 06:53:22 -0800 (PST)
Received: by mail-it0-x22e.google.com with SMTP id m191so13822906itg.2 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 06:53:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZW2vx3JNGYwXsTgPbqeYVom1Xu3vQEsTfSlC5tqFKhw=; b=J9o5BFLJOBnKU54mQKRfmrsaUImXXXDSNMM48DaJQ7GwNW0BQq70cZPJYLwfJWZ5it ZgfCyFcFuWvo+OAoly3wPsG/9IK7WC893Xcu27f0+B2XpasCtB/Bz8GMHm1eomdv4B2N Y7od2gTHiiILalRxAnWKI+hDTacNWuWkDH/VJ0qPotP6YgcpR8WuQsm9L9BKaWXxByZu L242PmNJZE/rCxZQcVa/GqicCaiQ7bbYzs0ZKIIyPqtSaeIMW2A3VjofK0QaDvzi9lQf xuUKVWKQdB2z4JJiBY3ZUfDAw4SkAWiccYU9xud2ewaDcy1GyULY18YU7epaEHbGdTdr 6xpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZW2vx3JNGYwXsTgPbqeYVom1Xu3vQEsTfSlC5tqFKhw=; b=aCvZZ3MpBjI6PgOUohJLOmQeoYcDUAoDUfddvdjzEFK/JEC22Qzf+pOy4sCYb4fsy9 /Q9JCZq2rTPQ9zuHEvXuydceX0iIaR1Ja5fgMceTU6h23aQFIBqn1x0MoeCwIww/gwEi 578o4Ue8ShuAmeKXD9aXXQOaUsOuYOJ0GwxsLSR/75zndJYYydDKYl4LXfDGQvueoZBZ RfrGLuOK3ypV6jrzrpZF1VwBgkrDI4i3CK5Snlceyp0n1zZDJBis7P1CJJDSYdGTmQSx fGM0DHouEbRC88etXgp7m531g41xcpa/MJdyfmc0X8k+rcAbu6miDD/N/FQF8lvjEngW NDcQ==
X-Gm-Message-State: AJaThX6Ep6Lly9UuwmPWGSE8semwHqImVIXFG3mQHz5S0+dFCvzNE36s yj+ZYcC1cjSMNRm3lrm1Tdgzm8OuxsTq2UUSgsMwTw==
X-Google-Smtp-Source: AGs4zMZL9+5+7avq71IhzIDltZdYF9dfzZgNavkGt3Xk3qom6yv0gff1hPPAPlt8Jl4q79utrBJBBZHaPkr3qSXGANA=
X-Received: by 10.36.203.4 with SMTP id u4mr6434655itg.138.1510671201902; Tue, 14 Nov 2017 06:53:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.15.203 with HTTP; Tue, 14 Nov 2017 06:53:21 -0800 (PST)
Received: by 10.79.15.203 with HTTP; Tue, 14 Nov 2017 06:53:21 -0800 (PST)
In-Reply-To: <38ef2544-df5c-4677-ffaa-7b084eb300fa@gmail.com>
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> <38ef2544-df5c-4677-ffaa-7b084eb300fa@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 14 Nov 2017 22:53:21 +0800
Message-ID: <CAPt1N1k7CBvTOHFFoNeS6TMq_dkvSQTJ4TXR=Yt8S-6p--eabg@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0b0aa05cb4da055df28ceb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/DgYOd0oZWXf9xWTwaIjLKQSP52s>
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:53:25 -0000

Why is it an unsolved problem?

On Nov 14, 2017 22:30, "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
wrote:

>
>
> 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
>>
>>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

v2.23.0 | Report a Bug | By Email