Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?

<mohamed.boucadair@orange.com> Wed, 21 August 2013 14:41 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 A1EA121F9BEF for <dhcwg@ietfa.amsl.com>; Wed, 21 Aug 2013 07:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BRjL3hm762V for <dhcwg@ietfa.amsl.com>; Wed, 21 Aug 2013 07:41:42 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5F021F9BBF for <dhcwg@ietf.org>; Wed, 21 Aug 2013 07:41:42 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 23C473B4489; Wed, 21 Aug 2013 16:41:41 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id F202A15805B; Wed, 21 Aug 2013 16:41:40 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Wed, 21 Aug 2013 16:41:40 +0200
From: <mohamed.boucadair@orange.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Date: Wed, 21 Aug 2013 16:41:39 +0200
Thread-Topic: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?
Thread-Index: Ac6eebcGVQi3urIrRBu+CosjAtFFEQAAThgA
Message-ID: <94C682931C08B048B7A8645303FDC9F36EEDD8B472@PUEXCB1B.nanterre.francetelecom.fr>
References: <52123110.10205@gmail.com> <94C682931C08B048B7A8645303FDC9F36EEDD8B410@PUEXCB1B.nanterre.francetelecom.fr> <5214CCDC.3090308@gmail.com>
In-Reply-To: <5214CCDC.3090308@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.21.133617
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-prefix-pool-opt?
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: Wed, 21 Aug 2013 14:41:54 -0000

Hi Tomek,

Yes, you are right. Forget about my proposal to change the intended status.

Cheers,
Med

>-----Message d'origine-----
>De : Tomek Mrugalski [mailto:tomasz.mrugalski@gmail.com]
>Envoyé : mercredi 21 août 2013 16:21
>À : BOUCADAIR Mohamed IMT/OLN
>Cc : dhcwg
>Objet : Re: [dhcwg] Anyone interested in continuing draft-ietf-dhc-dhcpv6-
>prefix-pool-opt?
>
>On 21.08.2013 14:41, mohamed.boucadair@orange.com wrote:
>> Hi Tomek,
>>
>> I do still think draft-ietf-dhc-dhcpv6-prefix-pool-opt documents a
>> useful feature in order to have more automation and also control
>> routes aggregation instead of relying on proprietary behaviors of
>> each implementation. Of course, part of these objectives can be
>> achieved if routes are installed manually or use an out of band
>> mechanism to enforce routing aggregation policies. Still, the
>> proposal in draft-ietf-dhc-dhcpv6-prefix-pool-opt is superior because
>> the DHCP server has the knowledge of the prefix assignments; and
>> therefore routes can be triggered with dhcpv6 .
>>
>> A way to progress with this document is to target the Experimental
>> track. Based on the experience that will be gained in real
>> deployments, the status can be revisited if required.
>No, sorry. That won't work. At least not as you'd like it to. Take a
>look at IANA registry for DHCPv6 options:
>http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xhtml.
>It clearly states that assigning option codes require experts review
>*and* standards action. Experimental drafts are not standards. You are
>certainly welcome to proceed with this as experimental, but my
>understanding of the process is that it would be published without
>options assigned. And the draft (or experimental RFC) without option
>code is really useless, because it is unlikely that any verndor would
>implement it.
>
>As a side comment, currently assigning the option code for DHCPv6
>requires experts review. Let me cite the complete list: Ted Lemon. While
>Ted Lemon is certainly a DHCPv6 expert, the standardization process
>should not rely on a single person. If Ted becomes unavailable for
>whatever reason (e.g. wins a lottery and decides to retire tomorrow on
>his private island), we wouldn't get new DHCPv6 options any more.
>
>I suppose that is something that should be corrected one day, probably
>together with the registry name.
>
>Tomek