Re: [Idr] BGP Attribute for Large communities (Attribute 30) was squatted on - Let's get a new attribute number (1 week WG call (10/18 to 10/25)

<bruno.decraene@orange.com> Tue, 18 October 2016 15:41 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 4DA051296B1 for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.049
X-Spam-Level:
X-Spam-Status: No, score=-3.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, 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 LQGKQlhiuIdZ for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:41:27 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor34.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 DD4A11296B0 for <idr@ietf.org>; Tue, 18 Oct 2016 08:41:26 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 29108180554; Tue, 18 Oct 2016 17:41:25 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.19]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id F04E31A0066; Tue, 18 Oct 2016 17:41:24 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM44.corporate.adroot.infra.ftgroup ([fe80::b08d:5b75:e92c:a45f%18]) with mapi id 14.03.0319.002; Tue, 18 Oct 2016 17:41:24 +0200
From: <bruno.decraene@orange.com>
To: Susan Hares <shares@ndzh.com>, 'IETF IDR WG' <idr@ietf.org>
Thread-Topic: [Idr] BGP Attribute for Large communities (Attribute 30) was squatted on - Let's get a new attribute number (1 week WG call (10/18 to 10/25)
Thread-Index: AdIpUHjFMTMxey+uRgusubexAa1gwgABMaNw
Date: Tue, 18 Oct 2016 15:41:24 +0000
Message-ID: <6259_1476805285_580642A5_6259_1295_19_53C29892C857584299CBF5D05346208A0FA04E6B@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <01f401d22950$7f988470$7ec98d50$@ndzh.com>
In-Reply-To: <01f401d22950$7f988470$7ec98d50$@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.3]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A0FA04E6BOPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UYvv-ucteztgDhRH_cmrpuvsdOY>
Cc: 'Kristian Larsson' <kll@dev.terastrm.net>
Subject: Re: [Idr] BGP Attribute for Large communities (Attribute 30) was squatted on - Let's get a new attribute number (1 week WG call (10/18 to 10/25)
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: Tue, 18 Oct 2016 15:41:29 -0000

What about assigning attribute 30 and 139 for "Experimental" use? Especially since this registry has none currently.

      Experimental: Available for experimental use as described in
            [EXPERIMENTATION<https://tools.ietf.org/html/rfc5226#ref-EXPERIMENTATION>;].  IANA does not record specific
            assignments for any particular use.

https://tools.ietf.org/html/rfc5226#section-4

[EXPERIMENTATION<https://tools.ietf.org/html/rfc5226#ref-EXPERIMENTATION>;] "Assigning Experimental and Testing Numbers Considered Useful" https://tools.ietf.org/html/rfc3692

Obviously this assumes that people do use this value for experimentation, i.e. follow the rule...

Regards,
--Bruno


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, October 18, 2016 5:01 PM
To: 'IETF IDR WG'
Cc: 'Kristian Larsson'
Subject: [Idr] BGP Attribute for Large communities (Attribute 30) was squatted on - Let's get a new attribute number (1 week WG call (10/18 to 10/25)

WG:

Early testing of the Large Communities draft (draft-ietf-idr-large-community-03.txt)  with attribute value of 30 detect that we had an implementation squatting on attribute 30 by a Huawei router.   "Squatting" on an attribute is anti-social behavior in the Internet in any release of software.

The individuals who did in Huawei have been contacted by Jie Dong, and "asked" if they had made this mistake in any other attribute.   These individuals confessed to Attribute 129 (for wide communities).  These individuals apologize to the Working group.

Now what shall we do? The large community draft is critical for several networks. After talking with the developers and operators, John and I would like to recommend we do the following:

IDR should recommend that the following attribute numbers be deprecated:

BGP Attribute 30
BGP attribute 129

IDR should ask IANA to assign BGP Large Communities (currently Attribute 30) to a new attribute number.  This is a 1 week call to determine if the IDR approves this action.   This call will allow the large communities draft to still continue with the 2 week WG LC.

John, Alvaro, and I have check the early allocation rules.  Implementations should ask for early allocation prior to releasing, and they do not need to be interoperability testing to request the early allocation for the attribute.

Sue Hares



_________________________________________________________________________________________________________________________

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.