IETF Logo Mail Archive

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)

marco@lamehost.it Wed, 19 October 2016 07:36 UTC

Return-Path: <marco@lamehost.it>
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 D7913129532 for <idr@ietfa.amsl.com>; Wed, 19 Oct 2016 00:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.331
X-Spam-Level:
X-Spam-Status: No, score=-2.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.431, 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 ZpcaZYce8FzB for <idr@ietfa.amsl.com>; Wed, 19 Oct 2016 00:36:03 -0700 (PDT)
Received: from seele.lamehost.it (seele.lamehost.it [80.76.80.23]) by ietfa.amsl.com (Postfix) with ESMTP id 61737129547 for <idr@ietf.org>; Wed, 19 Oct 2016 00:36:02 -0700 (PDT)
Received: from www.lamehost.it (unknown [80.76.80.23]) (Authenticated sender: marco@lamehost.it) by seele.lamehost.it (Postfix) with ESMTPSA id 28638746D1; Wed, 19 Oct 2016 09:35:59 +0200 (CEST)
Mime-Version: 1.0
Date: Wed, 19 Oct 2016 07:35:59 +0000
Content-Type: multipart/alternative; boundary="--=_RainLoop_222_967948787.1476862559"
Message-ID: <483547c6b1659efd478be4d9483d724f@www.lamehost.it>
X-Mailer: RainLoop/1.10.3.151
From: marco@lamehost.it
To: Robert Raszuk <robert@raszuk.net>, Job Snijders <job@instituut.net>
In-Reply-To: <CA+b+ERmD1QZsc0Re0vBs+2i10JmdEorL=Qac6peLJnqgbRgJxA@mail.gmail.com>
References: <CA+b+ERmD1QZsc0Re0vBs+2i10JmdEorL=Qac6peLJnqgbRgJxA@mail.gmail.com> <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>
X-Originating-IP: 79.24.77.5
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (seele.lamehost.it [0.0.0.0]); Wed, 19 Oct 2016 09:35:59 +0200 (CEST)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (seele.lamehost.it [0.0.0.0]); Wed, 19 Oct 2016 09:35:59 +0200 (CEST)
X-Virus-Scanned: clamav-milter 0.99.2 at seele
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WCyL4OGMvISfhRkBHZOYf1Wvz00>
Cc: IETF IDR WG <idr@ietf.org>, Kristian Larsson <kll@dev.terastrm.net>, Susan 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: Wed, 19 Oct 2016 07:36:05 -0000

As there is strong consensus that the community should not allow to vendors to pick up codepoints on their own, i think that the best course of actions is to assign a fresh (not-squatted) number to this draft.

For what concerns 30 and 129, i suggest to mark them as deprecated with a reference to this thread.

October 18, 2016 8:14 PM, "Robert Raszuk"  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)  r.  
On Tue, Oct 18, 2016 at 7:57 PM, Job Snijders  wrote:

  On Tue, Oct 18, 2016 at 01:14:21PM -0400, Susan Hares wrote:
> Jeff:
>
> This is a good idea to just make 129 an early allocation for wide communities.

I have to disagree.

It is not known what version of the wide communities draft has been
implemented. This code is deployed in the wild, there are no guarantees
that those routers will ever be upgraded.

I think the -wide- deployment effort will shoot itself in the foot by
using 129.

Kind regards,

Job
_______________________________________________
Idr mailing list
Idr@ietf.org (mailto:Idr@ietf.org)
https://www.ietf.org/mailman/listinfo/idr (https://www.ietf.org/mailman/listinfo/idr)

v2.23.0 | Report a Bug | By Email