Re: [Idr] WG adoption of draft-dhrao-idr-4octet-extcomm-generic-subtype
<bruno.decraene@orange-ftgroup.com> Tue, 25 November 2008 08:44 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 13CB43A6944; Tue, 25 Nov 2008 00:44:51 -0800 (PST)
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 4A00F3A6944 for <idr@core3.amsl.com>; Tue, 25 Nov 2008 00:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 f9kCWMXsqQt8 for <idr@core3.amsl.com>; Tue, 25 Nov 2008 00:44:48 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 1839C3A6839 for <idr@ietf.org>; Tue, 25 Nov 2008 00:44:47 -0800 (PST)
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Nov 2008 09:44:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 25 Nov 2008 09:44:42 +0100
Message-ID: <5A0FF108221C7C4E85738678804B567C06D36623@ftrdmel3>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] WG adoption of draft-dhrao-idr-4octet-extcomm-generic-subtype
Thread-Index: Ack9AUGnH9oaZlp0Swmmld0F6XbbfwR1zdnw
References: <200811021527.mA2FR0M34537@magenta.juniper.net>
From: bruno.decraene@orange-ftgroup.com
To: yakov@juniper.net, idr@ietf.org
X-OriginalArrivalTime: 25 Nov 2008 08:44:44.0125 (UTC) FILETIME=[105EB8D0:01C94EDA]
Subject: Re: [Idr] WG adoption of draft-dhrao-idr-4octet-extcomm-generic-subtype
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org
Support. In section 3 (Deployment Considerations) > A speaker with a 4-octet Autonomous System may have a customer or > peer with a 2-octet Autonomous System. If such a peer supports > 4-octet extended communities, then it will be able to tag its routes > with the 4-octet extended community defined by the speaker. If the > peer does not support 4-octet extended communities, then the speaker > may need to define an appropriate standard community value for the > same purpose. Could the document explicitly states whether the reserved AS_TRANS value (ASN 23456 defined in RFC 4893) can (or cannot) be used by a non compliant 2-octet AS peering with a 4-octet AS? Thanks, Regards, Bruno > -----Message d'origine----- > De : idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] De la part de Yakov Rekhter > Envoyé : dimanche 2 novembre 2008 16:27 > À : idr@ietf.org > Objet : [Idr] WG adoption of draft-dhrao-idr-4octet-extcomm-generic-subtype > > Folks, > > Please send your comments on the attached. The deadline for comments > is Nov 17, 2008. > > Yakov. > ------- Forwarded Message > > Date: Fri, 31 Oct 2008 18:29:47 -0400 > From: Jeffrey Haas <jhaas@pfrc.org> > To: idr@ietf.org > Subject: [Idr] WG adoption of draft-dhrao-idr-4octet-extcomm-generic-subtype > > Yakov and Sue, > > We'd like to request the working group adopt the internet-draft > draft-dhrao-idr-4octet-extcomm-generic-subtype as a working group item. > This draft adds a generic 4 octet extended community to complement the > 2-octet AS community behavior publised in RFC 1997. > > Although very similar to draft-ietf-l3vpn-as4octet-ext-community, we'd > like to request adoption of this draft in IDR since it has no l3vpn > specific semantics. > > - -- Jeff > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > ------- End of Forwarded Message > > _______________________________________________ > 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
- [Idr] WG adoption of draft-dhrao-idr-4octet-extco… Jeffrey Haas
- [Idr] WG adoption of draft-dhrao-idr-4octet-extco… Yakov Rekhter
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Danny McPherson
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Jeffrey Haas
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Enke Chen
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… John G. Scudder
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Geoff Huston
- [Idr] Support for 4-byte generic communities in B… Jeffrey Haas
- Re: [Idr] Support for 4-byte generic communities … Cayle Spandon
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Paul Jakma
- Re: [Idr] Support for 4-byte generic communities … Jeffrey Haas
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Jeffrey Haas
- Re: [Idr] Support for 4-byte generic communities … Yakov Rekhter
- Re: [Idr] Support for 4-byte generic communities … Andrew Partan
- Re: [Idr] Support for 4-byte generic communities … Pradosh Mohapatra (pmohapat)
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… bruno.decraene
- Re: [Idr] WG adoption ofdraft-dhrao-idr-4octet-ex… Dhananjaya Rao (dhrao)
- Re: [Idr] WG adoption of draft-dhrao-idr-4octet-e… Yakov Rekhter