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

Ted Lemon <Ted.Lemon@nominum.com> Sat, 08 September 2012 16:43 UTC

Return-Path: <Ted.Lemon@nominum.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 94A7521F851C for <dhcwg@ietfa.amsl.com>; Sat, 8 Sep 2012 09:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.535
X-Spam-Level:
X-Spam-Status: No, score=-106.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 q8fym39+ltFI for <dhcwg@ietfa.amsl.com>; Sat, 8 Sep 2012 09:43:11 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id E836221F8467 for <dhcwg@ietf.org>; Sat, 8 Sep 2012 09:43:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUEt1nsPvsv+3Q7iQ2EpjGLP2gmqDXb2f@postini.com; Sat, 08 Sep 2012 09:43:11 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 171541B831D for <dhcwg@ietf.org>; Sat, 8 Sep 2012 09:43:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0A9D419005C; Sat, 8 Sep 2012 09:43:10 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Sat, 8 Sep 2012 09:43:09 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
Thread-Index: AQHNjd2jjF/7xAgSiEuAh53a0ICeZpeBG6uA
Date: Sat, 08 Sep 2012 16:43:09 +0000
Message-ID: <66943696-4C9F-4A83-A419-C049EE756691@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> <504B6FDE.9060901@gmail.com>
In-Reply-To: <504B6FDE.9060901@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BEA7BF1EC31AAC4BA7D5EF8DE1E3872E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:43:12 -0000

On Sep 8, 2012, at 12:18 PM, Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
> On another hand, the idea of a Relay to act first as a Requesting Router has already been discarded somehow?

That may well be a valid configuration in some settings, but for an ISP, particularly with legal record-keeping mandates, doing CPE prefix allocation in the core of the network makes more sense.   Also, by doing it this way, the PE router can be simpler and cheaper.