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

David Farmer <farmer@umn.edu> Tue, 06 September 2016 22:37 UTC

Return-Path: <farmer@umn.edu>
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 4CDDE12B0D7 for <idr@ietfa.amsl.com>; Tue, 6 Sep 2016 15:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.808
X-Spam-Level:
X-Spam-Status: No, score=-5.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=umn.edu
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 ul3Ik7F5nunw for <idr@ietfa.amsl.com>; Tue, 6 Sep 2016 15:37:34 -0700 (PDT)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 15C3912B411 for <idr@ietf.org>; Tue, 6 Sep 2016 15:37:34 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 7ECE893C for <idr@ietf.org>; Tue, 6 Sep 2016 22:37:33 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWUlHlvicTnP for <idr@ietf.org>; Tue, 6 Sep 2016 17:37:33 -0500 (CDT)
Received: from mail-qk0-f200.google.com (mail-qk0-f200.google.com [209.85.220.200]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 43514851 for <idr@ietf.org>; Tue, 6 Sep 2016 17:37:33 -0500 (CDT)
Received: by mail-qk0-f200.google.com with SMTP id f128so503809972qkd.1 for <idr@ietf.org>; Tue, 06 Sep 2016 15:37:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GSxTq5ItLQCpTQmEZi9r1PlzKRQNj8cAaMqU1IVa3xM=; b=P45gI8tjq80eGC6x8s5kWi+fbJpOXMx8c2tgd+Kou36PE/j/k7BOsbKirLlkiEHfwj lsCqcXWt7M7fJkpWU8hbnO/3F4baH/auoQ2UkmyRuHRfYGkSG8+M0WpdIL23LOW8ObTQ oKlL+7omC4KlX5NkfufY/7ERpRc1Y5vFrBq24=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GSxTq5ItLQCpTQmEZi9r1PlzKRQNj8cAaMqU1IVa3xM=; b=BX2k/9O/U5+f/8TzyNUL0YC5SIo8ysND/4K7IL4NmpC4H0PPiXt52dPpZqHUZpcvEI O/P00psPNPsA5hyG8fcvpl7VbpACnW94OOg+6NKM0Ts0P9dHtZH0RQbx1HZFqCxMbbMa 3bF1Bsvh+C0/CzYdkpp8WXDMDXaAO26dho0a1s2eafqfDt5mQA1JAZuBBxHMQzcf7ox/ zzRBlABunhrL4GCaNWfHPAQFr/UmJe4jn+AA22WtGOY2AZhFwgCcE9Vl7GIioa6uCeqO uWoX+clILQJP4FJmdZkMv+fsLotk6ZfIIKVhF9l31EDhG9h0v7HbErHxGe8pZ9A/kC4o hICg==
X-Gm-Message-State: AE9vXwME+cLv2xsZQgJVnoOdAzyORubH4uu0KBt9XvOWFE+CR2kBrmvxV8iiKY6q6MmFhBaIPpzjcZ9ywokNPQzq1ZGvIUop/ZgwY/WiJAkMsLeW40dIas7MGi+s2xycWrxzLwb0AKFrhXRROQ==
X-Received: by 10.55.212.10 with SMTP id l10mr19953564qki.268.1473201452641; Tue, 06 Sep 2016 15:37:32 -0700 (PDT)
X-Received: by 10.55.212.10 with SMTP id l10mr19953541qki.268.1473201452444; Tue, 06 Sep 2016 15:37:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.33.78 with HTTP; Tue, 6 Sep 2016 15:37:31 -0700 (PDT)
In-Reply-To: <20160906113919.GC17613@vurt.meerval.net>
References: <20160906113919.GC17613@vurt.meerval.net>
From: David Farmer <farmer@umn.edu>
Date: Tue, 06 Sep 2016 17:37:31 -0500
Message-ID: <CAN-Dau35HCB1H7sUyt4RKS-FhqH0XqjV6yaRE67jCdhikGcocQ@mail.gmail.com>
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary="001a1149a1bc418993053bde71e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/SkmdXVHy9GjCyy3rdL5zmcbTgP8>
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:37:36 -0000

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.

So, my question before we get too invested in another solution to this
problem, are BGP implementers, both open source and commercial, willing to
implement something along the lines of this proposal?  If they are, then
full-speed ahead PLEASE!  But, if not, them I not sure how effective yet
another communities for 4-byte ASNs proposal will be.

Thanks

On Tue, Sep 6, 2016 at 6:39 AM, Job Snijders <job@ntt.net> wrote:

> 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.
>
> Background
> ----------
> RFC1997 BGP communities are the most common method to signal
> meta-information between autonomous systems. RFC1997 communities are a
> 32 bit entity. The convention is that the first 16 bits are the ASN in
> which the last 16 bits have a meaning. RFC1997 is so popular because of
> its elegant simplicity and ubiquitous support.
>
> The operator community (no pun intended!) is suffering from a fatal
> flaw. One in five ASNs in the Default-free zone are a 4-byte ASN (RFC
> 4893). One cannot fit a 32-bit value into a 16-bit field.
>
> 4-byte ASN Operators work around this issue by either resorting to
> kludges such as using private 16-bit ASNs as in the "Global
> Administrator" field, or by returning the ASN to their respective RIR
> and requesting a 16-bit ASN. However, both the RIRs and the IANA have
> depleted their supply of 16-bit ASNs.
>
> Work to address the issue of BGP communities has been ongoing for years.
> Notable examples are 'flexible communities' (12 years ago) and 'wide
> communities' (6 years ago). The WG so far has been unable to produce an
> internet standard which enjoys a status similar to RFC1997. Now that the
> RIRs are running out, the issue has become a matter of extreme urgency.
>
> The Large BGP Community specification gives every network operator
> (regardless of whether they have a 2-byte ASN or a 4-byte ASN) 8 bytes
> to signal meta-information in an opaque fashion. This will align with
> current, well-established practices deployed by network operators.
>
> The Large BGP Community has purposefully been specified to be narrow and
> as simple as possible to meet the operator community immediate needs,
> without dissuading from existing community extensions that are in the
> standards process pipeline.
>
> The Large Community, by design, is not extendable, because extensibility
> comes at a cost. Knowing that the amount of noise generated by an idea
> is inversely proportional to the complexity of the idea, I urge the WG
> to consider the Large Community's simplicity not a disadvantage, but a
> virtue.
>
> We ask for your support in this narrow focus to re-imagine the RFC1997
> communities in this way as it should have been done when RFC4893 was
> published.
>
> Kind regards,
>
> Job Snijders
> (co-author draft-heitz-idr-large-community)
>
> [1]: https://tools.ietf.org/html/draft-heitz-idr-large-community
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================