Re: [dhcwg] Adoption Call for draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 08 January 2020 11:00 UTC

Return-Path: <alexandre.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 43EF21200D7 for <dhcwg@ietfa.amsl.com>; Wed, 8 Jan 2020 03:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 TSTh36ja8LcD for <dhcwg@ietfa.amsl.com>; Wed, 8 Jan 2020 03:00:50 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13AC6120018 for <dhcwg@ietf.org>; Wed, 8 Jan 2020 03:00:49 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 008B0jgB015231 for <dhcwg@ietf.org>; Wed, 8 Jan 2020 12:00:47 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CCAB02022FE for <dhcwg@ietf.org>; Wed, 8 Jan 2020 12:00:47 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C2ACA205315 for <dhcwg@ietf.org>; Wed, 8 Jan 2020 12:00:47 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 008B0llC022821 for <dhcwg@ietf.org>; Wed, 8 Jan 2020 12:00:47 +0100
To: dhcwg@ietf.org
References: <BYAPR11MB2888345B6D3728C02AE410EFCF240@BYAPR11MB2888.namprd11.prod.outlook.com> <BYAPR11MB28883154A0ECA38B4B0FB8B2CF3E0@BYAPR11MB2888.namprd11.prod.outlook.com> <AD8AF6C8-47F6-4E4F-B884-E849EF710EAA@gmx.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2b4e4f6b-0a9a-bd01-0c3a-1f3c0d37758f@gmail.com>
Date: Wed, 08 Jan 2020 12:00:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <AD8AF6C8-47F6-4E4F-B884-E849EF710EAA@gmx.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/aIyNFAEviSLtiUahwgP8hQYiGQA>
Subject: Re: [dhcwg] Adoption Call for draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Jan 2020 11:00:52 -0000

Hi,
I support it.  I am not a co-author.

In the past I did work with colleagues on an implementation for Relay 
with PD.

Since then I realized that operators offering Internet access with 
DHCPv6-PD might benefit from a server-relay seggregation to accommodate 
a larger number of users and richer applications.

There might be obstacles in achieving that, however.  These obstacles 
might not come from the DHCPv6 nor PD technology nor DHCP standards. 
They might come from the architecture of IPv6 which still imposes a 64 
limit, which effectively limits the genericity of the prefix length in 
DHCPv6-PD.

I hope these things will advance  hand in hand and wish all the best to 
the pd-relay-requirements draft.

Alex

Le 08/01/2020 à 11:05, ianfarrer@gmx.com a écrit :
> Hi Bernie,
> 
> Thanks for the reminder. I support its adoption (as a co-=author).
> 
> Thanks,
> Ian
> 
>> On 8. Jan 2020, at 02:31, Bernie Volz (volz) <volz@cisco.com 
>> <mailto:volz@cisco.com>> wrote:
>>
>> Hi:
>> A reminder – we are looking for an indication of interest in adopting 
>> this work in the DHC WG, or whether anyone is opposed to it.
>> For the record (with WG chair hat OFF), I support adopting this work. 
>> I think this document would help vendors to supply better products and 
>> improve subscriber experience for networks in which prefix delegation 
>> is used.
>>
>>   * Bernie
>>
>> *From:*dhcwg <dhcwg-bounces@ietf.org 
>> <mailto:dhcwg-bounces@ietf.org>>*On Behalf Of*Bernie Volz (volz)
>> *Sent:*Sunday, December 29, 2019 11:03 AM
>> *To:*dhcwg@ietf.org <mailto:dhcwg@ietf.org>
>> *Subject:*[dhcwg] Adoption Call for 
>> draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020
>> Hello:
>> As follow up from the IETF-106 DHC WG meeting, we are initiating the 
>> WG call for adoption 
>> onhttps://datatracker.ietf.org/doc/draft-fkhp-dhc-dhcpv6-pd-relay-requirements/ 
>> <https://datatracker.ietf...org/doc/draft-fkhp-dhc-dhcpv6-pd-relay-requirements/>(DHCPv6 
>> Prefix Delegating Relay). This document was presented at IETF-106 – 
>> seehttps://datatracker.ietf.org/meeting/106/materials/slides-106-dhc-dhcpv6-prefix-delegating-relay-00.
>> This starts the call for Adoption of this document. Please respond by 
>> January 14, 2020.
>> Thanks in advance for your consideration of whether the WG should or 
>> should not adopt this document as a work item.
>> And, Happy New Year!
>>
>>   * Tomek & Bernie
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org <mailto:dhcwg@ietf.org>
>> https://www.ietf.org/mailman/listinfo/dhcwg
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>