Re: RRs
Yakov Rekhter <yakov@juniper.net> Mon, 21 March 2005 15:21 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 KAA15341 for <l3vpn-web-archive@ietf.org>; Mon, 21 Mar 2005 10:21:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDOoE-0003lu-DX for l3vpn-web-archive@ietf.org; Mon, 21 Mar 2005 10:27:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDOft-0005gg-2K; Mon, 21 Mar 2005 10:18:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDOfq-0005gY-Np for l3vpn@megatron.ietf.org; Mon, 21 Mar 2005 10:18:35 -0500
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 KAA15017 for <l3vpn@ietf.org>; Mon, 21 Mar 2005 10:18:32 -0500 (EST)
Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDOku-0003hy-SX for l3vpn@ietf.org; Mon, 21 Mar 2005 10:23:50 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j2LFINBm066256; Mon, 21 Mar 2005 07:18:24 -0800 (PST) (envelope-from yakov@juniper.net)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j2LFINe15826; Mon, 21 Mar 2005 07:18:23 -0800 (PST) (envelope-from yakov@juniper.net)
Message-Id: <200503211518.j2LFINe15826@merlot.juniper.net>
To: venkat.dabbara@wipro.com
In-Reply-To: Your message of "Wed, 16 Mar 2005 10:43:19 +0530." <E7E0E9AD7DC3F548ACE3AAD6D2A02CBD04F13614@blr-ec-msg05.wipro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37099.1111418303.1@juniper.net>
Date: Mon, 21 Mar 2005 07:18:23 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: jsmith4112003@yahoo.co.uk, l3vpn@ietf.org
Subject: Re: RRs
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: c1c65599517f9ac32519d043c37c5336
Venkat, > Answers Inline... see in-line... > ________________________________ > > From: l3vpn-bounces@ietf.org on behalf of John Smith > Sent: Tue 3/15/2005 8:28 PM > To: l3vpn@ietf.org > Subject: RRs > > > > Hi, > > Are the following statements true about BGP Route Reflectors in BGP/MPLS = > VPNs: > > [1] We are not required to configure any RDs since most of the times = > there would not be > any customers attached to the RRs. > > > This is not always TRUE. > > BGP RR can have customers attached when it is acting as a PE router.=20 > > > [2] The RR would be peered up with a couple of BGP PE routers. The RR is likely to peer with more than just "a couple of BGP PE routers". > It would reflect (following the rules laid out for RRs) all the BGP > VPN routes it learns from one PE router to the other PE router without > modifying the NEXT_HOP. It does not even need to > look at the extended communities for doing that, unless some ORF has > been advertised by a PE router. > > It is true. RR may use Route Target Constrain (draft-ietf-l3vpn-rt-constrain-01.txt) instead of ORF. Yakov.