IETF Logo Mail Archive

Re: [Idr] Request to adopt draft-heitz-idr-large-community

niels@bakker.net Mon, 19 September 2016 15:01 UTC

Return-Path: <niels@bakker.net>
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 82CAB12B3F5 for <idr@ietfa.amsl.com>; Mon, 19 Sep 2016 08:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Level:
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.316] 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 4fYI3qyTNehq for <idr@ietfa.amsl.com>; Mon, 19 Sep 2016 08:01:03 -0700 (PDT)
Received: from excession.bakker.net (home.bakker.net [82.94.16.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46CF512B3EE for <idr@ietf.org>; Mon, 19 Sep 2016 08:01:03 -0700 (PDT)
Received: by excession.bakker.net (Postfix, from userid 910) id ADA851DBA; Mon, 19 Sep 2016 17:01:00 +0200 (CEST)
Date: Mon, 19 Sep 2016 17:01:00 +0200
From: niels@bakker.net
To: idr@ietf.org
Message-ID: <20160919150100.GA70044@excession.tpb.net>
References: <20160906113919.GC17613@vurt.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20160906113919.GC17613@vurt.meerval.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/I4ey4K7LFbz7ymjufOAZ1s-7yjQ>
Subject: Re: [Idr] Request to adopt draft-heitz-idr-large-community
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: Mon, 19 Sep 2016 15:01:07 -0000

Hi,

I represent AS32787.  We use communities to steer inbound traffic 
between ports / locations.  Longer communities would allow us to use 
communities on a per peer (or per category of peer) per peering 
session basis whilst retaining a human friendly format.

32-bit commmunities can’t do that at scale without turning the 
community into an opaque number that needs tooling to interpret / 
operate.  If we retain 32787 as 16 of those bits we have 16 bits with 
which to express a set of actions on peering sessions which only 
scales to a few thousand sessions.

Considering this, I'd like to voice my approval for adoption of this 
draft.

Regards,


	-- Niels.

* job@ntt.net (Job Snijders) [Tue 06 Sep 2016, 18:30 CEST]:
>Dear IDR, fellow network operators,
>
>I would like to request that the IDR Working Group adopts 
>draft-heitz-idr-large-community [1] as a working group document.
>
[...]


--

v2.23.0 | Report a Bug | By Email