Re: [Idr] community of the day - common header

Sander Steffann <sander@steffann.nl> Fri, 09 September 2016 12:17 UTC

Return-Path: <sander@steffann.nl>
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 7FD3512B106 for <idr@ietfa.amsl.com>; Fri, 9 Sep 2016 05:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
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 YXcC6Vc_XtAZ for <idr@ietfa.amsl.com>; Fri, 9 Sep 2016 05:17:26 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (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 120F312B0EA for <idr@ietf.org>; Fri, 9 Sep 2016 05:17:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id E18BF3B; Fri, 9 Sep 2016 14:17:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :content-type:content-type:mime-version:subject:subject:received :received; s=mail; t=1473423441; bh=sKkxZFfKDXolebdOq5q7Z60nVryV VK9B5llfNc3x+aI=; b=aFXIdDviNIkXvXzA5O0UtFwfuvx4IssGcEPFQ5Fm+fK3 CaWg16RewmN52wJesMpwdz+JrJJnTX3I9ZpUlb9vNe702PqJ5TAc0nBGeIRkbYkW CIFR9aDR9DZdDdzZban8zMQfkPxuP9LMCIJecDSeRaPT1dN6XHmM2+NqHYhRs1M=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IKR-FzKKloyu; Fri, 9 Sep 2016 14:17:21 +0200 (CEST)
Received: from [IPv6:2001:9e0:803:feed::1001] (unknown [IPv6:2001:9e0:803:feed::1001]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id B8E9238; Fri, 9 Sep 2016 14:17:20 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_172E67BD-10F5-49A5-92CD-0937E0617FC6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <57D2A3A8.70904@foobar.org>
Date: Fri, 09 Sep 2016 14:17:20 +0200
Message-Id: <0413C57A-6D39-4FA9-808C-1ED57BD97F24@steffann.nl>
References: <20160908214031.GA23544@pfrc.org> <57D2A3A8.70904@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SASeHCGNgZb3ktsVxoy0b7xXFfE>
Cc: idr@ietf.org
Subject: Re: [Idr] community of the day - common header
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: Fri, 09 Sep 2016 12:17:28 -0000

Hi Nick,

> Our situation now is:
> 
> - the operational people who have contributed to this conversation think
> that large is going to work for their requirements, and is worth deploying.
> 
> - there is running code (xr, bird and exabgp) which implements the large
> proposal, and commitments from a bunch of other stacks, including non
> open-source vendors.

Sounds like this is close to rough consensus and running code...

> If we were having this conversation in 2008-2009, which was the first
> time that lack of >= 32b:32b communities started causing serious
> operational problems, I'd be a good deal more sanguine about things.
> But that time is over: it's 7 years later, and the entire operational
> community is now staring at a fast-approaching brick wall.

And demonstrated need...

There may be better, nicer, cooler, more flexible solutions. But the large proposal seems to be good enough for the foreseeable operational requirements. Operators need feature parity for 16 and 32 bit ASN now.

Cheers,
Sander