Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message - earlier discussions

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 13 September 2014 13:54 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74AAF1A0650 for <dhcwg@ietfa.amsl.com>; Sat, 13 Sep 2014 06:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.937
X-Spam-Level: **
X-Spam-Status: No, score=2.937 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MISSING_HEADERS=1.021, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=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 4wORcm2CJ7cA for <dhcwg@ietfa.amsl.com>; Sat, 13 Sep 2014 06:54:39 -0700 (PDT)
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA441A0648 for <dhcwg@ietf.org>; Sat, 13 Sep 2014 06:54:39 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.229.156.225]) by smtp2-g21.free.fr (Postfix) with ESMTP id ECB984B00B9 for <dhcwg@ietf.org>; Sat, 13 Sep 2014 15:54:36 +0200 (CEST)
Message-ID: <54144C9C.8060006@gmail.com>
Date: Sat, 13 Sep 2014 15:54:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
CC: dhcwg <dhcwg@ietf.org>
References: <20140519150302.3625.29866.idtracker@ietfa.amsl.com> <489D13FBFA9B3E41812EA89F188F018E1B03125B@xmb-rcd-x04.cisco.com> <53E3872A.30204@gmail.com> <53E38954.1030206@gmail.com> <AD6668B4-834A-4777-B667-006BA06A2C4F@gmail.com> <53E39157.8060708@gmail.com> <CAJE_bqcr5ytrgrUWwPLvZ=vHNPe=C4OZcah0529suOLOgM6odA@mail.gmail.com> <53E39635.60608@gmail.com> <CAJE_bqcv6PavTP_-EM-FMwD1hVrsqnfmWaCceZQshsxXNVr=4w@mail.gmail.com> <5409C1B8.3000101@gmail.com>
In-Reply-To: <5409C1B8.3000101@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 140913-0, 13/09/2014), Outbound message
X-Antivirus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/ivbG_UdHqhGuk0jsrO1haP5B3YU
Subject: Re: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message - earlier discussions
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 13 Sep 2014 13:54:40 -0000

I was pointed out in private about 2 other earlier discussions about 
this same topic:

"prefix length determination for DHCPv6" 2007
https://www.ietf.org/mail-archive/web/dhcwg/current/msg07412.html

"prefix length option for DHCPv6" 2011
https://www.ietf.org/mail-archive/web/dhcwg/current/msg11543.html

But there seems to be no draft discussing this problem, or offering 
potential solutions.

Alex

On 05/09/2014 15:59, Alexandru Petrescu wrote:
> Le 07/08/2014 18:24, 神明達哉 a écrit :
>> At Thu, 07 Aug 2014 17:07:33 +0200,
>> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>>
>>> That aside, I wonder why programmers have set that 64 in the kernel data
>>> absent a prefix length field in DHCP/RA, if not because of the fact that
>>> specifications are lacking.  Were it for DHCPv6 to have a prefix length
>>> field for assigned address A, then programmer would be clearer of what
>>> to put on that field, I think.
>>
>> I guess you're basically re-raising a long standing discussion of
>> whether to provide an on-link prefix via DHCPv6.
>>
>> My understanding is that we have never reached a consensus on this at
>> IETF (consider, for example, how
>> http://tools.ietf.org/html/draft-droms-dhc-dhcpv6-default-router-00
>> was discussed and we still don't have any published outcome), so a
>> simple rehash of it won't bring us anywhere.  At the very least it's
>> safer to discuss it outside the scope of rfc3315bis (because otherwise
>> we'll never be able to publish the bis).
>
> Jinmei, thanks for the pointer.
>
> But I wonder whether there is any draft that talks about how DHCPv6
> sends a prefix-length of the assigned IPv6 address, to the Client?  (not
> Prefix Delegation, but the equivalent of the Prefix Length field of a
> PIO of a Router Advertisement)?
>
> Alex
>
>>         } else {
>>             /* Current practice is that all subnets are /64's, but
>>              * some suspect this may not be permanent.
>>              */
>>             client_envadd(client, prefix, "ip6_prefixlen",
>>                       "%d", 64);
>                                ^ make this variable.
>
>>
>> --
>> JINMEI, Tatuya
>>
>>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
http://www.avast.com