Re: draft-ietf-l3vpn-rt-constrain-01.txt
Robert Raszuk <raszuk@cisco.com> Wed, 06 October 2004 09:44 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06783 for <l3vpn-web-archive@ietf.org>; Wed, 6 Oct 2004 05:44:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF8Uy-0004jn-5O for l3vpn-web-archive@ietf.org; Wed, 06 Oct 2004 05:54:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF8I6-00078B-2m; Wed, 06 Oct 2004 05:40:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF8FP-0006n3-SH for l3vpn@megatron.ietf.org; Wed, 06 Oct 2004 05:38:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06440 for <l3vpn@ietf.org>; Wed, 6 Oct 2004 05:38:09 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF8Os-0004Lc-2J for l3vpn@ietf.org; Wed, 06 Oct 2004 05:47:59 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 06 Oct 2004 02:42:36 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i969bZdX007144; Wed, 6 Oct 2004 02:37:37 -0700 (PDT)
Received: from [10.10.10.78] (sjc-rraszuk-vpn1.cisco.com [10.25.90.226]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with SMTP id AXT44873; Wed, 6 Oct 2004 02:39:53 -0700 (PDT)
Message-ID: <4163BCD9.6090908@cisco.com>
Date: Wed, 06 Oct 2004 02:37:29 -0700
From: Robert Raszuk <raszuk@cisco.com>
Organization: Signature: http://www.employees.org/~raszuk/sig/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Spice Sylvia <falsesylvia@yahoo.co.uk>
References: <20041006092235.58729.qmail@web60901.mail.yahoo.com>
In-Reply-To: <20041006092235.58729.qmail@web60901.mail.yahoo.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: l3vpn@ietf.org
Subject: Re: draft-ietf-l3vpn-rt-constrain-01.txt
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Hi Sylvia, If I am interpreting your quiestion right - yes A is possible. In fact stay tuned for more details on A alone. I have work in progress trying to document A a bit in more detail. Thx, R. > Spice Sylvia wrote: > > Hello folks > > in the draft, given that AS#RT# froms a NLRI, > > a. Is it possible to have only the AS#RT#s avaliable > on a node and based on the fact that someone does an > import of that RT#, the prefixes should be fetched? > (that is we only send AS#RT# to peers via BGP and when > group membership/VPN membership is signaled, the > prefixes are imported) > > b. If (a) is not feasable for whatever reasons (like > time to fetch prefixes etc), and assuming that > AS#RT#prefix# are all present on the peer, can we > assume that only when a peer of the node imports a > particular AS#RT#, will the corresponding forwarding > element/label be inserted in the FIB? > > In other words, other than the benefits of TE from > RSVP-TE, can a or b be used to setup signaled LSPs? > > -brgds > Sylvia > > > > > > ___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com > >
- draft-ietf-l3vpn-rt-constrain-01.txt Spice Sylvia
- Re: draft-ietf-l3vpn-rt-constrain-01.txt Robert Raszuk
- Re: draft-ietf-l3vpn-rt-constrain-01.txt Spice Sylvia
- draft-ietf-l3vpn-rt-constrain-01.txt Ross Callon
- Re: draft-ietf-l3vpn-rt-constrain-01.txt Ross Callon