Re: [Idr] Proposed IANA procedures for BGP Well-known communities

Jeffrey Haas <jhaas@pfrc.org> Thu, 17 July 2008 02:46 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 920E63A69B1; Wed, 16 Jul 2008 19:46:50 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 319873A69B1 for <idr@core3.amsl.com>; Wed, 16 Jul 2008 19:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6JtGZ21YqQV for <idr@core3.amsl.com>; Wed, 16 Jul 2008 19:46:48 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 7581F3A690E for <idr@ietf.org>; Wed, 16 Jul 2008 19:46:48 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 1C9F0244181; Thu, 17 Jul 2008 02:47:19 +0000 (UTC)
Date: Wed, 16 Jul 2008 22:47:19 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: David Ward <dward@cisco.com>
Message-ID: <20080717024718.GB21614@slice>
References: <12433A6D-95F0-46B6-89C1-EEC6D425823C@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <12433A6D-95F0-46B6-89C1-EEC6D425823C@cisco.com>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] Proposed IANA procedures for BGP Well-known communities
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Dave,

On Wed, Jul 16, 2008 at 09:37:33PM -0500, David Ward wrote:
> This registry exists;
>
> http://www.iana.org/assignments/bgp-well-known-communities

[...]

> Well-known Communities
>
>    The following communities have global significance and their
>    operations shall be implemented in any community-attribute-aware  BGP
>    speaker.

I'd suggest taking the FCFS communities and putting them in a registry
other than the "well known" one.  Well known implies that an
implementation should be aware of them and implement their semantics.

Beyond that, go for it.

-- Jeff
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr