Re: [dhcwg] DHCPv6 and IPv6ND

Alexandre Petrescu <alexandru.petrescu@gmail.com> Wed, 15 November 2017 02:26 UTC

Return-Path: <alexandru.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 40F881201F2 for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 18:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AVsZY55mLB_I for <dhcwg@ietfa.amsl.com>; Tue, 14 Nov 2017 18:26:12 -0800 (PST)
Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (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 ED5DD127077 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 18:26:11 -0800 (PST)
Received: by mail-pg0-x22b.google.com with SMTP id z184so11490110pgd.13 for <dhcwg@ietf.org>; Tue, 14 Nov 2017 18:26:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=JFksKT1GjIoCXwoipn40DOXR8Glp8/DoTL9Bo3sQAVw=; b=rAVpGEh9yZ8MWBNX8aRmN8OFI75N5hTkk7ci4BPhNYFDMcFXyO7gEgyx2DHyfFGY/t C/kGm6T2NwwF/3DSxhtq7PRAZ+lfENVk6gNNopSxJeMCOC/ki6NP9URByV3VZ+mnHeM8 igyUFoqX/HLuiU96i6DgJSVWsyZ2bK8nb5hGu6rDV0EvcEKW6bcTO7GklQAxk16Y3Riu Iezc0Cr6R1dvZYDztUGn/QyMPGjhTL4RIxE7qvcdKul+Ua8SDNwZ/puJtxJEq02W5VmO mE9+bcfuiyMpO46J/GAtlvUOhkSM7iY42bkhCVb1iaCbVRkQVKHQTdCm7w7AcaHTI3S7 SF1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=JFksKT1GjIoCXwoipn40DOXR8Glp8/DoTL9Bo3sQAVw=; b=eGui/WBDmwr+VZJGwgPH9EC0GxALVpqYav0DzH7uBCGbLKuDuUpPgq56DGg+ISCxTZ 0mtauvsV8YHmIr7C1hx1PgkmnWMGHocWZF3ki2TmuQn0otJFgluaxpU/J8E616e+uAyJ PRwfNuQRc10B+3fc8n3aGrn9A9/NqevmSawR2fWA3ZYE1bCkxI65Oq04momzAugqnvS1 OFau0Ae1/6VJmZSAvZ+W+IpDXY9R7+P/z10RRWULl6O/yRGkrnwb1z22gAgwHiV+k9Gu 7pfBAI3gGYZiuGMq1Z5RwqirAG8fLaWqMb6Hs5Z7uTWQrZZ07kTAra8VlU3zEQO8TvgL vALA==
X-Gm-Message-State: AJaThX73F0lkBnZbeHzpVyeZv/ZDJwsfEIClRmRyoJ2M9JFFxhMFs0oE pjXycWLJMB+oJcMubFXnbfWgow==
X-Google-Smtp-Source: AGs4zMaF6p67jySjnqb2k6qROQErK5S3fedwwDH7aUP6GwvrAs2H9SVH8nfBg3VhBltHKkiyHYd5ng==
X-Received: by 10.84.131.6 with SMTP id 6mr14592320pld.100.1510712771360; Tue, 14 Nov 2017 18:26:11 -0800 (PST)
Received: from ?IPv6:2001:67c:370:1999:d989:d486:9e79:b286? ([2001:67c:370:1999:d989:d486:9e79:b286]) by smtp.gmail.com with ESMTPSA id b23sm41506860pfm.148.2017.11.14.18.26.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 18:26:10 -0800 (PST)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: dhcwg <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> <38ef2544-df5c-4677-ffaa-7b084eb300fa@gmail.com> <CAPt1N1k7CBvTOHFFoNeS6TMq_dkvSQTJ4TXR=Yt8S-6p--eabg@mail.gmail.com>
Message-ID: <e4df5049-2548-6762-994d-a12c8f663e59@gmail.com>
Date: Wed, 15 Nov 2017 03:26:07 +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: <CAPt1N1k7CBvTOHFFoNeS6TMq_dkvSQTJ4TXR=Yt8S-6p--eabg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/GjOHSDiDYIhRjCHBMu48t-Z5Ooo>
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: Wed, 15 Nov 2017 02:26:13 -0000

Because of many reasons.  The most recent popped up in mail box this 
morning - again has to do with modem and lack of DHCPv6.

But at IETF, do you know whether there is a DHCPv6 Server up?  I would 
like to test Prefix Delegation on "ietf-v6ONLY".

The RA on "ietf-v6ONLY" has bit "Managed address configuration" not set; 
and I can not see any DHCPv6 traffic there.

Alex


Le 14/11/2017 à 15:53, Ted Lemon a écrit :
> Why is it an unsolved problem?
> 
> On Nov 14, 2017 22:30, "Alexandre Petrescu" 
> <alexandre.petrescu@gmail.com <mailto: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>
>         <mailto: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 <mailto:dhcwg@ietf.org>
>         https://www.ietf.org/mailman/listinfo/dhcwg
>         <https://www.ietf.org/mailman/listinfo/dhcwg>
> 
> 
>     _______________________________________________
>     dhcwg mailing list
>     dhcwg@ietf.org <mailto:dhcwg@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dhcwg
>     <https://www.ietf.org/mailman/listinfo/dhcwg>
>