Re: [Idr] 2 week WG adoption call - draft-scudder-idr-capability-registry-change (9/20/2018 to 10/4/2018)

<bruno.decraene@orange.com> Thu, 20 September 2018 15:22 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 A92CE130E96; Thu, 20 Sep 2018 08:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 1qsL1mYCEtP4; Thu, 20 Sep 2018 08:22:20 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A233D130EBA; Thu, 20 Sep 2018 08:22:19 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 42GL7Y5P71z205y; Thu, 20 Sep 2018 17:22:17 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 42GL7Y4rK4zDq7F; Thu, 20 Sep 2018 17:22:17 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0415.000; Thu, 20 Sep 2018 17:22:17 +0200
From: <bruno.decraene@orange.com>
To: Susan Hares <shares@ndzh.com>, "draft-scudder-idr-capabilities-registry-change@ietf.org" <draft-scudder-idr-capabilities-registry-change@ietf.org>
CC: 'idr' <idr@ietf.org>
Thread-Topic: [Idr] 2 week WG adoption call - draft-scudder-idr-capability-registry-change (9/20/2018 to 10/4/2018)
Thread-Index: AdRQ6z7j3hqpGgIMTm2B29qXbEskJwAA++Aw
Date: Thu, 20 Sep 2018 15:22:16 +0000
Message-ID: <23742_1537456937_5BA3BB29_23742_227_1_53C29892C857584299CBF5D05346208A47B50897@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <00d001d450eb$d02ffed0$708ffc70$@ndzh.com>
In-Reply-To: <00d001d450eb$d02ffed0$708ffc70$@ndzh.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A47B50897OPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Za2MxB0iO-EjWmhl0cLFTCeu5-s>
Subject: Re: [Idr] 2 week WG adoption call - draft-scudder-idr-capability-registry-change (9/20/2018 to 10/4/2018)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Sep 2018 15:22:23 -0000

1) Support WG adoption.

2)

> Please include comments on operational impacts on this proposal.

The main risk seems collision between future allocation and past usage. IMHO the document adequately covers this by calling for past usages, and given the remaining unallocated space in existing FCFS range (74-127)  (i.e. before we reach the collision range).

Also, that collision risk already exists as of today if we consider that "BGP Capability Codes do not meet the criteria for "Reserved for Private Use" described in [RFC5226<https://tools.ietf.org/html/rfc5226>] S. 4.1.". In this regards, the document improves the situation, so the faster the change, the better.

3) Please find below 2 nits and 1 minor comment


:s/ [RFC5226<https://tools.ietf.org/html/rfc5226>]/ [RFC8126<https://tools.ietf.org/html/rfc8126>]

----

OLD :

   128-238: First Come First Served



NEW :

   128: Reserved

   129-238: First Come First Served


(in order to be consistent with    IANA is requested to allocate value 128 as "Reserved".


---

"   Finally, we invite implementors who have used values in the range

   128-255 to contribute to this draft, so that the values can be

   included in the registry. >

+1
Recalling another thread (from John) some years ago, about whether one could ask for any value or only the next one/the one chosen by IANA...I don't remember its conclusion.
In order to handle post RFC publication contributions, may be we could add a text to ask IANA to allow for request with specific value in the range 129-238.

Thanks,
Regards,
--Bruno

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, September 20, 2018 4:11 PM
To: 'idr'
Cc: draft-scudder-idr-capabilities-registry-change@ietf.org
Subject: [Idr] 2 week WG adoption call - draft-scudder-idr-capability-registry-change (9/20/2018 to 10/4/2018)

Greetings all:

Based on the messages on the IDR list, there seems to be interest to start a 2 week WG adoption call for  draft-scudder-idr-capabilities-registry-change-02.txt.  The WG adoption call will go from 9/20/2018 to 10/4/2018.

You can obtain the document quickly by clicking on the link below:

https://datatracker.ietf.org/doc/draft-scudder-idr-capabilities-registry-change/

Please include comments on operational impacts on this proposal.

Susan Hares
Co-chair 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.