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

Job Snijders <job@ntt.net> Tue, 06 September 2016 22:46 UTC

Return-Path: <job@ntt.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 DDA7812B232 for <idr@ietfa.amsl.com>; Tue, 6 Sep 2016 15:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level:
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.508, SPF_SOFTFAIL=0.665, URIBL_RHS_DOB=1.514] 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 RAoq4J5VTvfZ for <idr@ietfa.amsl.com>; Tue, 6 Sep 2016 15:46:53 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 7468412B03A for <idr@ietf.org>; Tue, 6 Sep 2016 15:46:53 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <job@ntt.net>) id 1bhP8l-000FEZ-Vm (job@us.ntt.net); Tue, 06 Sep 2016 22:46:52 +0000
Date: Wed, 07 Sep 2016 00:46:48 +0200
From: Job Snijders <job@ntt.net>
To: David Farmer <farmer@umn.edu>
Message-ID: <20160906224648.GG17613@vurt.meerval.net>
References: <20160906113919.GC17613@vurt.meerval.net> <CAN-Dau35HCB1H7sUyt4RKS-FhqH0XqjV6yaRE67jCdhikGcocQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAN-Dau35HCB1H7sUyt4RKS-FhqH0XqjV6yaRE67jCdhikGcocQ@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/A0AJreiArMF9XhDkY6psbHSJ4ao>
Cc: idr wg <idr@ietf.org>
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: Tue, 06 Sep 2016 22:46:55 -0000

Hi David,

On Tue, Sep 06, 2016 at 05:37:31PM -0500, David Farmer wrote:
> As an operator and someone involved in RIR policy, I support this and
> most any solution that provides usable communities for 4-byte ASNs.
> 
> However, communities for 4-byte ASNs are not a new issue and there
> have been several solutions proposed over the past couple years.  The
> blocking issue seems to have been implementations, or the lack of
> them.

You make a valid point. Without implementations this thread is worthless.

I have hope that this time around it'll be different: the specification
is so simple it is almost in-excusable to not implement it. Having no
extendability is also a feature: there will be no suprises, what is
written down is what it is.

I'm tracking implementations here: http://largebgpcommunities.net/implementations/ 
(and ofcourse in the RFC7942 section of the draft). I rely on what
people tell me, but you are probably best off to engage with your
vendors directly.

I encourage implementors to state whether this is on the roadmap and
what the ETAs will be for GM releases (if they are known yet).

Kind regards,

Job