IETF Logo Mail Archive

[Idr] draft-ietf-idr-reserved-extended-communities

<bruno.decraene@orange-ftgroup.com> Thu, 10 March 2011 09:58 UTC

Return-Path: <bruno.decraene@orange-ftgroup.com>
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 6B35F3A68FA for <idr@core3.amsl.com>; Thu, 10 Mar 2011 01:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 La694tKzvC0q for <idr@core3.amsl.com>; Thu, 10 Mar 2011 01:58:15 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 8D29B3A68C4 for <idr@ietf.org>; Thu, 10 Mar 2011 01:58:15 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 7CA88FC4010; Thu, 10 Mar 2011 10:59:38 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 6B068FC400F; Thu, 10 Mar 2011 10:59:38 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Thu, 10 Mar 2011 10:59:32 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 10 Mar 2011 10:59:31 +0100
Message-ID: <FE8F6A65A433A744964C65B6EDFDC240020291A9@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-ietf-idr-reserved-extended-communities
Thread-Index: AcuE6ZZddKRGLZzeQ1KDF5bzoq8eoAAAPT+gFoZvILA=
References: Your message of Sat, 13 Nov 2010 07:36:31 -0800.<D1EDF6F2-230D-4194-B78F-A5C7F2671ADC@juniper.net> <7807.1289841699@erosen-linux>
From: bruno.decraene@orange-ftgroup.com
To: erosen@cisco.com, idr@ietf.org
X-OriginalArrivalTime: 10 Mar 2011 09:59:32.0245 (UTC) FILETIME=[DA6CBC50:01CBDF09]
Cc: draft-decraene-idr-reserved-extended-communities@tools.ietf.org
Subject: [Idr] draft-ietf-idr-reserved-extended-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/mail-archive/web/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: Thu, 10 Mar 2011 09:58:16 -0000

Eric, all,

> From: DECRAENE Bruno 
> Sent: Monday, November 15, 2010 7:05 PM
> Subject: RE: [Idr] draft-decraene-idr-reserved-extended-communities-00
[...] 


> > I also think it's confusing to call these extended communities
"reserved",
> > as RFC 5226 ("Guidelines for Writing IANA Considerations") defines
the term
> > "reserved" as meaning "not to be assigned".
> 
> We can use a different name. Would you have any proposition?
> 

We could propose to use the name "Assigned extended communities". This
seems valid according to RFC 5226 (Guidelines for Writing an IANA
Considerations Section in RFCs point of view): "The binding or
association of a specific value with a particular purpose within a
namespace is called an assigned number (or assigned value, or sometimes
a "code point", "protocol constant", or "protocol parameter").  Each
assignment of a value in a namespace is called a registration"

Would this be fine for you? / Any comment on this proposition?

In the absence of any objections within the next two weeks I'll issue a
revised version which reflects the above proposition.

Thanks,
Regards,
Bruno

v2.23.0 | Report a Bug | By Email