IETF Logo Mail Archive

Re: [Idr] Request to adopt draft-heitz-idr-large-community - Working Group Adoption call (9/6 to 9/20)

Jared Mauch <jared@puck.nether.net> Wed, 21 September 2016 14:11 UTC

Return-Path: <jared@puck.nether.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 88D0212B2F8 for <idr@ietfa.amsl.com>; Wed, 21 Sep 2016 07:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level:
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, 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 tMv5gn_3fTQN for <idr@ietfa.amsl.com>; Wed, 21 Sep 2016 07:11:37 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id A61EE12B30E for <idr@ietf.org>; Wed, 21 Sep 2016 07:10:14 -0700 (PDT)
Received: from [IPv6:2601:401:4:3000:497:6da:f4fc:de37] (unknown [IPv6:2601:401:4:3000:497:6da:f4fc:de37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id A3B11540F02; Wed, 21 Sep 2016 10:10:11 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CA+b+ERmu0RnWFe+eDRARZJi9qMAqhWdAB3HhxcpReUa41TZrGw@mail.gmail.com>
Date: Wed, 21 Sep 2016 10:10:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C630FEA-4713-4E76-AB00-086811DB12F7@puck.nether.net>
References: <E7A5509A-4B20-44A9-9FBE-284734B5E2FD@cisco.com> <20160909155047.GD8370@pfrc.org> <CA+b+ERnyFi_0_rfW6F2uV8AGuBXm=zpRLuWAiyrmEMmXnrY6CA@mail.gmail.com> <A0FF8539-2868-46A8-995D-7D57705D8AA3@alcatel-lucent.com> <CA+b+ERk9vOdzacXjjmhK2uWFM+Aad8gK3KLJQBeFVb2XwbW3fA@mail.gmail.com> <6190874E-0CC8-4437-9117-F7429242064B@puck.nether.net> <CA+b+ERm82jJPzHJGgmwKWY-T+q97D8tRUWW3rh6hYr3iV4BKag@mail.gmail.com> <D0E1DDA5-2C26-46A2-95BC-C7A7B19F2F8B@steffann.nl> <20160914161526.GA19429@puck.nether.net> <20160914162702.GC80448@shrubbery.net> <20160914162919.GD19429@puck.nether.net> <123D938E-E345-4572-84A4-377669A8F6FD@alcatel-lucent.com> <D56CA059-56AC-48A6-B832-177A637F0CC4@puck.nether.net> <CA+b+ERm4gm9FctgaAYyC=rr51EX=Pzsd-4+gef1v=VpkqXYwQg@mail.gmail.com> <1BC163F0-3D87-41D2-99F8-03B3F9FFD756@puck.nether.net> <CA+b+ER=wz=8EMrOusBT+EZjHECA_spER8=JQP3oUWWF65n6n5w@mail.gmail.com> <09D3713A-3DE4-4B87-8D18-79DE8D5B6B7A@puck.nether.net> <CA+b+ERmu0RnWFe+eDRARZJi9qMAqhWdAB3HhxcpReUa41TZrGw@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TDOTp7GZtvkP1RBgbjJ_N53jSXU>
Cc: John Heasley <heas@shrubbery.net>, "idr@ietf.org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] Request to adopt draft-heitz-idr-large-community - Working Group Adoption call (9/6 to 9/20)
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, 21 Sep 2016 14:11:42 -0000

> On Sep 21, 2016, at 10:01 AM, Robert Raszuk <robert@raszuk.net> wrote:
> 
> Jared, 
> 
> Yes we could/should agree on list of common communities. In fact the registered list I documented was an input from many operators providing real input: 
> 
> https://tools.ietf.org/html/draft-ietf-idr-registered-wide-bgp-communities-02
> 
> But the problem is they do not nicely fit into 32:32:32 fixed space we are cooking here. 

I don’t think that if -large- progresses that IDR has completed, will close and BGP4+ will
be complete.

We should continue to document these cases, it may end up being a venue issue though.

- Jared

v2.23.0 | Report a Bug | By Email