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)

Zhuangshunwan <zhuangshunwan@huawei.com> Tue, 01 November 2016 07:00 UTC

Return-Path: <zhuangshunwan@huawei.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 E3340129537 for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 00:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.717
X-Spam-Level:
X-Spam-Status: No, score=-5.717 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 eVcTj3c6Qbvt for <idr@ietfa.amsl.com>; Tue, 1 Nov 2016 00:00:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEE2312942F for <idr@ietf.org>; Tue, 1 Nov 2016 00:00:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CZL57543; Tue, 01 Nov 2016 07:00:12 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 1 Nov 2016 07:00:12 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 1 Nov 2016 15:00:04 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.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+uRgusubexAa1gwgKvM6Eg
Date: Tue, 1 Nov 2016 07:00:03 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858C87A93D0@NKGEML515-MBX.china.huawei.com>
References: <01f401d22950$7f988470$7ec98d50$@ndzh.com>
In-Reply-To: <01f401d22950$7f988470$7ec98d50$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.86.254]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858C87A93D0NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.58183D7D.012C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2c441df91473e474f5de860bf8a6db6f
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/XbxloClNyaPnVzQGQJv5oRp3C18>
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, 01 Nov 2016 07:00:17 -0000

WG:

We have done a thorough analysis about the attribute squatting issue on Huawei router. Attribute 30 was used for an implementation of draft-vandevelde-idr-remote-next-hop, and attribute 129 was used for an implementation of draft-ietf-idr-wide-bgp-communities.

For attribute 30, we have created patches for this issue, and will completely fix the problem in the new release version. In future we will replace this feature with the mechanism defined in draft-ietf-idr-tunnel-encaps.

For attribute 129, we request deprecation of attribute code 129. We will wait for the Early Allocation value for draft-ietf-idr-wide-bgp-communities, Once it is assigned by IANA, we will update our implementation and use the assigned code for POC test.

I sincerely apologize on behalf of Huawei for our oversight.

Thanks,
Shunwan

发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares
发送时间: 2016年10月18日 23:01
收件人: 'IETF IDR WG'
抄送: 'Kristian Larsson'
主题: [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