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 20:42 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 EF25312987C for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 13:42:59 -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 puaHeRv-OrdC for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 13:42:59 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 13B841296E3 for <idr@ietf.org>; Tue, 18 Oct 2016 13:42:59 -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 65EA81E1F0; Tue, 18 Oct 2016 16:45:07 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_41684514-25B2-4FE0-A78A-7714D202A2FF"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CA+b+ERmD1QZsc0Re0vBs+2i10JmdEorL=Qac6peLJnqgbRgJxA@mail.gmail.com>
Date: Tue, 18 Oct 2016 16:42:56 -0400
Message-Id: <76457807-16D9-4358-B618-1BDAB7EEBEF6@pfrc.org>
References: <01f401d22950$7f988470$7ec98d50$@ndzh.com> <3BC2E5A3-380D-4F60-A719-6FA5E19FC839@pfrc.org> <001801d22963$11733630$3459a290$@ndzh.com> <20161018175753.GD10221@dhcp-157.238.255.122.noc.gin.ntt.net> <CA+b+ERmD1QZsc0Re0vBs+2i10JmdEorL=Qac6peLJnqgbRgJxA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/a1YWuhkIqsq66tUAwcBgvDbcvmA>
Cc: IETF IDR WG <idr@ietf.org>, Kristian Larsson <kll@dev.terastrm.net>, Sue Hares <shares@ndzh.com>
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 20:43:00 -0000

Robert,

> On Oct 18, 2016, at 2:14 PM, Robert Raszuk <robert@raszuk.net>; wrote:
> 
> 
> I would tend to agree with Job here. 
> 
> I see no point to reserve already known to be "overloaded" code point for wide or for that matter any new BGP attribute. 
> 
> That's the price we pay for no BGP Police or BGP FBI/GBI  ... (G=global)

To clarify my original point, I think holding onto it for early allocation makes sense.

Whether or not the code Huawei is working on is ready for such an allocation is a different matter.  But if the code point is otherwise associated with the feature, incremental rollout issues aside, seems reasonable to not waste that code point.

-- Jeff (I don't feel super strong about this, but see other threads)