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

Jeffrey Haas <jhaas@pfrc.org> Thu, 17 July 2008 20:42 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 777A73A6898; Thu, 17 Jul 2008 13:42:27 -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 7CABA3A68BE for <idr@core3.amsl.com>; Thu, 17 Jul 2008 13:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.066, 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 1FiMC0NI-pcf for <idr@core3.amsl.com>; Thu, 17 Jul 2008 13:42:24 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id B189C3A6898 for <idr@ietf.org>; Thu, 17 Jul 2008 13:42:24 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id E0FC4244188; Thu, 17 Jul 2008 20:42:56 +0000 (UTC)
Date: Thu, 17 Jul 2008 16:42:56 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: David Ward <dward@cisco.com>
Message-ID: <20080717204256.GB31932@slice>
References: <7814BA97-5E24-400D-95FD-6B6C97F1C239@cisco.com> <0D6A70C961EC4DD9A18857956E977E36@ad.redback.com> <165BD300-DCB5-4BD9-8CF8-67177302C5FE@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <165BD300-DCB5-4BD9-8CF8-67177302C5FE@cisco.com>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: 'idr' <idr@ietf.org>, tony.li@tony.li
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

On Thu, Jul 17, 2008 at 03:25:00PM -0500, David Ward wrote:
> point 1: The only well-known communities are those specified in 1997 as 
> they are old enough and widely deployed to the point that they are 
> considered part of the foundation of BGP communities support.

Indeed.  Much like RFC 4271 defines well-known as "implementations MUST
recognize all well-known attributes" I think the same could be said of
the well-known communities.

We're not going to be seeing any new well known BGP path attributes any
time soon I think.

I think all we're really looking for is:
- An IANA community registry
  - It should list the well-known communities
  - It should also provide registration for:
    - FCFS assigned communities
    - assigned by working group conensus.

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