IETF Logo Mail Archive

Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)

Nick Hilliard <nick@foobar.org> Wed, 19 October 2016 22:01 UTC

Return-Path: <nick@foobar.org>
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 CDC52129469 for <idr@ietfa.amsl.com>; Wed, 19 Oct 2016 15:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 bQCzYg9tK1du for <idr@ietfa.amsl.com>; Wed, 19 Oct 2016 15:01:33 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E5C1295C6 for <idr@ietf.org>; Wed, 19 Oct 2016 15:01:32 -0700 (PDT)
X-Envelope-To: idr@ietf.org
Received: from cupcake.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id u9JM1TcT080846 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Oct 2016 23:01:29 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be cupcake.local
Message-ID: <5807ED30.30204@foobar.org>
Date: Wed, 19 Oct 2016 23:01:20 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.4 (Macintosh/20161007)
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
References: <01f301d228b4$e3319ef0$a994dcd0$@ndzh.com> <CAN-Dau1dx_4o4yV=ytR-mFL1noLtGLKAZE3D_9mP5xxhSM=v_Q@mail.gmail.com> <107141A7-5CD2-4E48-8F6C-C737FF370359@pfrc.org>
In-Reply-To: <107141A7-5CD2-4E48-8F6C-C737FF370359@pfrc.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KoK1uIh43a99-mfnNYA944uF0EQ>
Cc: Sue Hares <shares@ndzh.com>, IETF IDR WG <idr@ietf.org>
Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
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, 19 Oct 2016 22:01:35 -0000

Jeffrey Haas wrote:
> I had thought that a BCOP document on communities was out there for BGP
> communities in general, but "community" clutters the search engines
> quite a bit and I'm not finding such a thing.

are you thinking of rfc7454?

Dave's suggestion is definitely an operational- rather than a
protocol-level issue.  draft-ietf-idr-large-community is a protocol
definition, so it would be better to see this in a GROW document.

Nick

v2.29.0 | Report a Bug | By Email | System Status