IETF Logo Mail Archive

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

Danny McPherson <danny@tcb.net> Tue, 29 July 2008 18:19 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 97B8B28C127; Tue, 29 Jul 2008 11:19:21 -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 82CF528C12B for <idr@core3.amsl.com>; Tue, 29 Jul 2008 11:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.008
X-Spam-Level:
X-Spam-Status: No, score=-1.008 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
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 n4G3c+qVMwYI for <idr@core3.amsl.com>; Tue, 29 Jul 2008 11:19:19 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id CF69A28C127 for <idr@ietf.org>; Tue, 29 Jul 2008 11:19:19 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 2D33726866F; Tue, 29 Jul 2008 12:19:32 -0600 (MDT)
Received: from [130.129.23.44] (130.129.23.44 [130.129.23.44]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Tue, 29 Jul 2008 12:19:32 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=130.129.23.44; client-port=54133; syn-fingerprint=65535:50:1:64:M1316,N,W3,N,N,T,S; data-bytes=0
Message-Id: <01029160-A376-4CE6-8DB7-8195B511947D@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: David Ward <dward@cisco.com>
In-Reply-To: <3980AE3D-A9C1-4F82-96EC-53440FA6EA3E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 29 Jul 2008 12:19:14 -0600
References: <12433A6D-95F0-46B6-89C1-EEC6D425823C@cisco.com> <3980AE3D-A9C1-4F82-96EC-53440FA6EA3E@cisco.com>
X-Mailer: Apple Mail (2.926)
Cc: idr <idr@ietf.org>, shares@ghs.com, Yakov Rekhter <yakov@juniper.net>
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

On Jul 29, 2008, at 11:45 AM, David Ward wrote:

> All -
> Please discuss as we will have no allocation of well-known or  
> reserved BGP communities until some procedures have reached WG  
> consensus. If it is felt that we must maintain "well-known  
> communities," a reliable and guaranteed algorithm as to when a  
> community is ubiquitously deployed has to be given otherwise we are  
> simply stuck w/ the notion of "reserved."

I'm fine with this proposal, I think it makes sense.

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

v2.23.0 | Report a Bug | By Email