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)

Jeffrey Haas <jhaas@pfrc.org> Tue, 18 October 2016 15:19 UTC

Return-Path: <jhaas@pfrc.org>
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 BF9291294ED for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level:
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, 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 GXEPFePYdh4l for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:19:24 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0839A127A91 for <idr@ietf.org>; Tue, 18 Oct 2016 08:19:24 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 331CB1E1F0; Tue, 18 Oct 2016 11:21:32 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B0D07F51-C9E2-4365-A762-40674381D90F"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <01f401d22950$7f988470$7ec98d50$@ndzh.com>
Date: Tue, 18 Oct 2016 11:19:22 -0400
Message-Id: <3BC2E5A3-380D-4F60-A719-6FA5E19FC839@pfrc.org>
References: <01f401d22950$7f988470$7ec98d50$@ndzh.com>
To: Sue Hares <shares@ndzh.com>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UazFCd020HwuWCQtM7qzD4QwL7o>
Cc: IETF IDR WG <idr@ietf.org>, 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:19:27 -0000

Sue,

If 129 is not otherwise contended for, it may be reasonable to simply request early allocation for the wide communities code point.

-- Jeff

> On Oct 18, 2016, at 11:01 AM, Susan Hares <shares@ndzh.com>; wrote:
> 
> 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 
>  
>  
> _______________________________________________
> Idr mailing list
> Idr@ietf.org <mailto:Idr@ietf.org>
> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr>