Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 08 September 2012 16:18 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 D183A21F857E for <dhcwg@ietfa.amsl.com>; Sat, 8 Sep 2012 09:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.021
X-Spam-Level:
X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJ7QPsk9yP88 for <dhcwg@ietfa.amsl.com>; Sat, 8 Sep 2012 09:18:51 -0700 (PDT)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 08D4621F849B for <dhcwg@ietf.org>; Sat, 8 Sep 2012 09:18:49 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id 1842294014C; Sat, 8 Sep 2012 18:18:43 +0200 (CEST)
Message-ID: <504B6FDE.9060901@gmail.com>
Date: Sat, 08 Sep 2012 18:18:38 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <91484F36-D059-4D90-8BFE-60434864A579@nominum.com> <6B6C7CCC-0971-4CD1-BC2F-849F6BDC1863@employees.org> <5044C350.4010403@gmail.com> <E666D4CA7557D04DB6B9B2BA6DC28F3D285C2A36F8@INBANSXCHMBSA3.in.alcatel-lucent.com> <6C1B27BB-3FBD-4046-9923-0FE6080D8AEC@nominum.com> <22044EFB-C429-4CF9-A2BB-23EFE1331A24@employees.org> <FDF07965-FE45-4A36-8563-EFD748351A39@nominum.com> <0CFEF31D-4A01-42A7-89B7-69BDBB41E9C8@employees.org> <6069AF94-1587-496D-BE15-5A9B6892E9F6@nominum.com> <BF63E815-FFCF-48E6-A146-B9C7030C9FAD@gmail.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA3C469D30@SZXEML510-MBS.china.huawei.com> <5049E744.30700@gmail.com> <9DB266A4-F0B6-43C4-BF8B-8A6C65792CAB@nominum.com>
In-Reply-To: <9DB266A4-F0B6-43C4-BF8B-8A6C65792CAB@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 120908-0, 08/09/2012), Outbound message
X-Antivirus-Status: Clean
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Sep 2012 16:18:51 -0000

Le 07/09/2012 15:20, Ted Lemon a écrit :
> On Sep 7, 2012, at 8:23 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> I mean I dont think an educated guess could be done reasonably to
>> form a common prefix and instruct the Relay about it.  Even less
>> that Relay to advertise the aggregated prefix instead of numerous
>> specific routes.
>
> I think the whole point of the prefix pool option is to avoid making
> educated guesses, by coming up with the aggregate route in the core
> of the network, as a management function.   IOW, I don't think the
> DHCP server will be following some heuristic to figure out what the
> aggregate prefix is; rather, it will be configured either to allocate
> one specifically, or will be configured by a management system with a
> predefined prefix pool.

Ok, I understand now.  It makes sense what you explain above.

On another hand, the idea of a Relay to act first as a Requesting Router 
has already been discarded somehow?

Alex