Re: I-D ACTION:draft-ietf-l3vpn-as4octet-ext-community-01.txt
Yakov Rekhter <yakov@juniper.net> Mon, 01 December 2008 14:18 UTC
Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70DA23A6847; Mon, 1 Dec 2008 06:18:22 -0800 (PST)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 479993A69D9 for <l3vpn@core3.amsl.com>; Mon, 1 Dec 2008 06:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 eftH7hnJEXFo for <l3vpn@core3.amsl.com>; Mon, 1 Dec 2008 06:18:20 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id 7C3FA3A6847 for <l3vpn@ietf.org>; Mon, 1 Dec 2008 06:18:19 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKSTPyJ3EqUhai1FniPLzvSHEajGiPIo8G@postini.com; Mon, 01 Dec 2008 06:18:17 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Mon, 1 Dec 2008 06:13:26 -0800
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Dec 2008 06:13:26 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Dec 2008 06:13:25 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Dec 2008 06:13:25 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id mB1EDPM74298; Mon, 1 Dec 2008 06:13:25 -0800 (PST) (envelope-from yakov@juniper.net)
Message-ID: <200812011413.mB1EDPM74298@magenta.juniper.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: I-D ACTION:draft-ietf-l3vpn-as4octet-ext-community-01.txt
In-Reply-To: <20081126204652.GB22864@slice>
References: <200810272022.m9RKMiM75734@magenta.juniper.net> <20081126204652.GB22864@slice>
X-MH-In-Reply-To: Jeffrey Haas <jhaas@pfrc.org> message dated "Wed, 26 Nov 2008 15:46:52 -0500."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <79755.1228140805.1@juniper.net>
Date: Mon, 01 Dec 2008 06:13:25 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 01 Dec 2008 14:13:25.0606 (UTC) FILETIME=[F9C46860:01C953BE]
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org
Jeff, > Yakov, > > On Mon, Oct 27, 2008 at 01:22:44PM -0700, Yakov Rekhter wrote: > > Title : Four-octet AS Specific BGP Extended Community > > Author(s) : Y. Rekhter, S. Sangli, D. Tappan > > Filename : draft-ietf-l3vpn-as4octet-ext-community-01.txt > > In a mail exchange with Dhananjaya Rao offlist, he pointed out your IANA > considerations for this document only enumerates the transitive versions > of these communities. In section 2, the non-transitive version is > called out. > > Is this intentional? Section 2 describes 4-octet AS specific extended communities. In general, such communities could be either transitive or non-transitive. IANA considerations specified two particular instances of 4-octet AS specific extended communities - four-octet AS specific Route Target, and four-octet AS specific Route Origin. These two communities are transitive. Yakov.
- I-D ACTION:draft-ietf-l3vpn-as4octet-ext-communit… Internet-Drafts
- I-D ACTION:draft-ietf-l3vpn-as4octet-ext-communit… Yakov Rekhter
- Re: I-D ACTION:draft-ietf-l3vpn-as4octet-ext-comm… Jeffrey Haas
- Re: I-D ACTION:draft-ietf-l3vpn-as4octet-ext-comm… Yakov Rekhter