[dhcwg] Prefix-length of an assigned address, in a DHCPv6 message (was: draft-dhcwg-dhc-rfc3315bis-02.txt)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 05 September 2014 13:59 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 B65381A06EC for <dhcwg@ietfa.amsl.com>; Fri, 5 Sep 2014 06:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.683
X-Spam-Level:
X-Spam-Status: No, score=-4.683 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 SPGR-_bMVGvi for <dhcwg@ietfa.amsl.com>; Fri, 5 Sep 2014 06:59:23 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABB9F1A06F5 for <dhcwg@ietf.org>; Fri, 5 Sep 2014 06:59:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s85DxKRJ009124; Fri, 5 Sep 2014 15:59:20 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 62DE62035B7; Fri, 5 Sep 2014 15:59:36 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 54F532035A2; Fri, 5 Sep 2014 15:59:36 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s85DxJEL010712; Fri, 5 Sep 2014 15:59:20 +0200
Message-ID: <5409C1B8.3000101@gmail.com>
Date: Fri, 05 Sep 2014 15:59:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: 神明達哉 <jinmei@wide.ad.jp>
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>
In-Reply-To: <CAJE_bqcv6PavTP_-EM-FMwD1hVrsqnfmWaCceZQshsxXNVr=4w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/T691pVcdULJzZN0ABAvMZt_9pW8
Cc: dhcwg <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: [dhcwg] Prefix-length of an assigned address, in a DHCPv6 message (was: draft-dhcwg-dhc-rfc3315bis-02.txt)
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: Fri, 05 Sep 2014 13:59:26 -0000

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
>
>