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

<mohamed.boucadair@orange.com> Thu, 09 January 2020 09:35 UTC

Return-Path: <mohamed.boucadair@orange.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 B756B1200C3 for <dhcwg@ietfa.amsl.com>; Thu, 9 Jan 2020 01:35:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 wjLu0Op7OjwH for <dhcwg@ietfa.amsl.com>; Thu, 9 Jan 2020 01:35:29 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 050F81200BA for <dhcwg@ietf.org>; Thu, 9 Jan 2020 01:35:29 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 47tgvg62PSz103P; Thu, 9 Jan 2020 10:35:27 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.107]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 47tgvg5G3czDq7C; Thu, 9 Jan 2020 10:35:27 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM8F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Thu, 9 Jan 2020 10:35:27 +0100
From: mohamed.boucadair@orange.com
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Adoption Call for draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020
Thread-Index: AdW+YPSEV8Zlj6FWRK66c+ivPe4AYgIbc3Ug
Date: Thu, 09 Jan 2020 09:35:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933031403311@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <BYAPR11MB2888345B6D3728C02AE410EFCF240@BYAPR11MB2888.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB2888345B6D3728C02AE410EFCF240@BYAPR11MB2888.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933031403311OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/JKl09JYS_RhrvdiIJ4H4HeIq2JQ>
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: Thu, 09 Jan 2020 09:35:31 -0000

Hi Bernie, all,

I support.

For the routing part, the draft may clarify that it focuses on the client-facing interface and not the one covered, e.g., in https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-prefix-pool-opt-03.

Cheers,
Med

De : dhcwg [mailto:dhcwg-bounces@ietf.org] De la part de Bernie Volz (volz)
Envoyé : dimanche 29 décembre 2019 17:03
À : dhcwg@ietf.org
Objet : [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 on https://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 - see https://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