Re: [Idr] early allocation for draft-gredler-idr-bgp-ls-segment-routing-ext

<bruno.decraene@orange.com> Thu, 03 November 2016 10:10 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A8712954F for <idr@ietfa.amsl.com>; Thu, 3 Nov 2016 03:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 DRHtMWE04ZIa for <idr@ietfa.amsl.com>; Thu, 3 Nov 2016 03:10:25 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67F22129549 for <idr@ietf.org>; Thu, 3 Nov 2016 03:10:25 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 1DF233B44BE; Thu, 3 Nov 2016 11:10:24 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.62]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 00E6227C086; Thu, 3 Nov 2016 11:10:24 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM5E.corporate.adroot.infra.ftgroup ([fe80::2912:bfa5:91d3:bf63%19]) with mapi id 14.03.0319.002; Thu, 3 Nov 2016 11:10:23 +0100
From: <bruno.decraene@orange.com>
To: "John G. Scudder" <jgs@juniper.net>
Thread-Topic: [Idr] early allocation for draft-gredler-idr-bgp-ls-segment-routing-ext
Thread-Index: AQHSNGRl/O1HlX2eMk614GzzELIlnqDHCK/g
Date: Thu, 3 Nov 2016 10:10:22 +0000
Message-ID: <28698_1478167824_581B0D10_28698_36_1_53C29892C857584299CBF5D05346208A1EC66A61@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <BB8878B2-97E1-4B9A-B2CB-2AAA670AFB7C@juniper.net> <EA079418-9FE5-4FA0-AD0C-0693E1FF324F@pfrc.org> <CF7167FB-4D7A-4621-BCFD-20199776E16B@juniper.net>
In-Reply-To: <CF7167FB-4D7A-4621-BCFD-20199776E16B@juniper.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.17.114517
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qas5V_O_oZL2FJKFhS-QEmPT0r8>
Cc: IETF IDR Working Group <idr@ietf.org>
Subject: Re: [Idr] early allocation for draft-gredler-idr-bgp-ls-segment-routing-ext
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2016 10:10:27 -0000

Hi John, Sue,

I support both WG adoption and early allocation.
This is the BGP-LS mapping of information defined in IGP documents which are WG doc for a long time. So it makes sense to me that the BGP-LS document also becomes an IDR WG doc.

Thanks,
Regards,
--Bruno


 > -----Original Message-----
 > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of John G. Scudder
 > Sent: Tuesday, November 01, 2016 6:21 PM
 > To: Jeffrey Haas
 > Cc: IETF IDR Working Group
 > Subject: [Idr] early allocation for draft-gredler-idr-bgp-ls-segment-routing-ext
 > 
 > On Nov 1, 2016, at 1:05 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
 > > there are a number of code point points in this document pertinent to BGP-LS that need
 > early allocation. The chairs should consider that as part of adoption work.
 > 
 > Yes, thanks for pointing that out.
 > 
 > Let's please consider that as part of this document adoption request, we should also
 > discuss early allocation for the code points listed in Section 4.1 of the draft. The registry
 > policy is "specification required" which follows the same RFC 7120 early allocation policy
 > as standards action. As a reminder, the requirements for early allocation can be
 > summarized as:
 > 
 > - Stable spec
 > - Sufficient interest
 > 
 > We will conclude the early allocation call at the same time as the WG adoption call, on
 > November 13.
 > 
 > Obviously if we DON'T adopt the document we would not pass the "sufficient interest"
 > bar, but otherwise I (switching to speak now as a WG member) would support proceeding
 > with early allocation.
 > 
 > Thanks,
 > 
 > --John
 > _______________________________________________
 > Idr mailing list
 > Idr@ietf.org
 > https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.