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:32 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 D038C12968D for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level:
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 csDTdL43REc6 for <idr@ietfa.amsl.com>; Tue, 18 Oct 2016 08:32:05 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 802681295A4 for <idr@ietf.org>; Tue, 18 Oct 2016 08:32:05 -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 A71C21E1F0; Tue, 18 Oct 2016 11:34:13 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <20161018152434.GB10221@dhcp-157.238.255.122.noc.gin.ntt.net>
Date: Tue, 18 Oct 2016 11:32:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB74A254-D50D-4ED6-824B-4989D97A1C8F@pfrc.org>
References: <01f401d22950$7f988470$7ec98d50$@ndzh.com> <3BC2E5A3-380D-4F60-A719-6FA5E19FC839@pfrc.org> <20161018152434.GB10221@dhcp-157.238.255.122.noc.gin.ntt.net>
To: Job Snijders <job@instituut.net>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dMBtok_r7CFB8hNT4nBa7viNcNE>
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 15:32:08 -0000

> On Oct 18, 2016, at 11:24 AM, Job Snijders <job@instituut.net> wrote:
> 
> On Tue, Oct 18, 2016 at 11:19:22AM -0400, Jeffrey Haas wrote:
>> If 129 is not otherwise contended for, it may be reasonable to simply
>> request early allocation for the wide communities code point.
> 
> and in doing so encourage early self-allocation? :)

Or avoid burning a code point when it may simply be asked for formally again.

> 
> At this point it is not even clear what exactly has been implemented,
> the wide communities effort might suffer from an incompatible deployment
> in the wild. I'd steer clear from this.

With regard to the feature maturity discussion, I tend to agree.  But there's still the general issue about how to pick a code point to do any sort of testing.  We have internal guidelines for such things, but once you get into early deployment scenarios, it gets complicated.

Conversation on this obviously should continue.

-- Jeff

> 
> Kind regards,
> 
> Job