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

David Ward <dward@cisco.com> Thu, 17 July 2008 19:41 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 CD93F3A6812; Thu, 17 Jul 2008 12:41:04 -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 A52B53A67F1 for <idr@core3.amsl.com>; Thu, 17 Jul 2008 12:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level:
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 n3dIxGAx8sVE for <idr@core3.amsl.com>; Thu, 17 Jul 2008 12:41:02 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 97FFC3A67CE for <idr@ietf.org>; Thu, 17 Jul 2008 12:41:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,204,1215388800"; d="scan'208";a="14604872"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 17 Jul 2008 19:41:32 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m6HJfVWG012635; Thu, 17 Jul 2008 15:41:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m6HJfVL2027208; Thu, 17 Jul 2008 19:41:31 GMT
Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 Jul 2008 15:41:31 -0400
Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 17 Jul 2008 15:40:37 -0400
In-Reply-To: <20080717024718.GB21614@slice>
References: <12433A6D-95F0-46B6-89C1-EEC6D425823C@cisco.com> <20080717024718.GB21614@slice>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <7814BA97-5E24-400D-95FD-6B6C97F1C239@cisco.com>
From: David Ward <dward@cisco.com>
Date: Thu, 17 Jul 2008 14:40:27 -0500
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.753.1)
X-OriginalArrivalTime: 17 Jul 2008 19:40:37.0128 (UTC) FILETIME=[FC793080:01C8E844]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1029; t=1216323691; x=1217187691; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dward@cisco.com; z=From:=20David=20Ward=20<dward@cisco.com> |Subject:=20Re=3A=20[Idr]=20Proposed=20IANA=20procedures=20 for=20BGP=20Well-known=20communities |Sender:=20 |To:=20Jeffrey=20Haas=20<jhaas@pfrc.org>; bh=RxKRBLbglrRrp+Ghz8W1f95F8rX7QD5cfe2J2Et1ST8=; b=mFNpikxGu/+YETDAPSQyUlhSBfzk76WgI8ha1t13TXOcG35dQvVcsA7IXO eXJXtI/H/CUxk4undqY7IZl9Z/SfjZovR7ENdshl4ugRwlt345X9DF10ee1r pSffcH7J2I;
Authentication-Results: rtp-dkim-1; header.From=dward@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: idr <idr@ietf.org>, David Ward <dward@cisco.com>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Jeff -


I brought this up during the IESG telechat today and there is  
precedence to have FCFS space in something titled "well-known." If  
others feel strongly, they should speak up.


-DWard

On Jul 16, 2008, at 9:47 PM, Jeffrey Haas wrote:

> 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

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