draft-ietf-l3vpn-rt-constrain-01.txt

Spice Sylvia <falsesylvia@yahoo.co.uk> Wed, 06 October 2004 09:24 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 FAA05505 for <l3vpn-web-archive@ietf.org>; Wed, 6 Oct 2004 05:24:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF8C7-0003a5-So for l3vpn-web-archive@ietf.org; Wed, 06 Oct 2004 05:34:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF82C-000502-Ad; Wed, 06 Oct 2004 05:24:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF80p-0004sa-O5 for l3vpn@megatron.ietf.org; Wed, 06 Oct 2004 05:23:07 -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 FAA05482 for <l3vpn@ietf.org>; Wed, 6 Oct 2004 05:23:05 -0400 (EDT)
Received: from web60901.mail.yahoo.com ([216.155.196.77]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CF8AH-0003Pz-DS for l3vpn@ietf.org; Wed, 06 Oct 2004 05:32:55 -0400
Message-ID: <20041006092235.58729.qmail@web60901.mail.yahoo.com>
Received: from [61.16.170.194] by web60901.mail.yahoo.com via HTTP; Wed, 06 Oct 2004 10:22:35 BST
Date: Wed, 06 Oct 2004 10:22:35 +0100
From: Spice Sylvia <falsesylvia@yahoo.co.uk>
To: l3vpn@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 8bit
Subject: draft-ietf-l3vpn-rt-constrain-01.txt
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 8bit

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