Re: Question related to shared tree instantiation for RSVP-P2MP P-Tunnel as mentioned in draft-ietf-l3vpn-2547bis-mcast-07.txt

Rahul Aggarwal <rahul@juniper.net> Tue, 25 November 2008 19:49 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 8794A3A6ABA; Tue, 25 Nov 2008 11:49:43 -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 982C23A6ABA for <l3vpn@core3.amsl.com>; Tue, 25 Nov 2008 11:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 KuSQUa6uBw8C for <l3vpn@core3.amsl.com>; Tue, 25 Nov 2008 11:49:41 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id A8E903A6A9E for <l3vpn@ietf.org>; Tue, 25 Nov 2008 11:49:41 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKSSxW0WekBoi/vt3NS1QYp/jcMnX/RMsF@postini.com; Tue, 25 Nov 2008 11:49:39 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; Tue, 25 Nov 2008 11:49:16 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Nov 2008 11:49:16 -0800
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Nov 2008 11:49:15 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 25 Nov 2008 11:49:15 -0800
Received: from sapphire.juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id mAPJnFM34847; Tue, 25 Nov 2008 11:49:15 -0800 (PST) (envelope-from rahul@juniper.net)
Date: Tue, 25 Nov 2008 11:49:15 -0800
From: Rahul Aggarwal <rahul@juniper.net>
To: Rohan Sen <senrohan@gmail.com>
Subject: Re: Question related to shared tree instantiation for RSVP-P2MP P-Tunnel as mentioned in draft-ietf-l3vpn-2547bis-mcast-07.txt
In-Reply-To: <8320074d0811250122y6872c0ael469ba10ffe113508@mail.gmail.com>
Message-ID: <20081125114453.U27303@sapphire.juniper.net>
References: <8320074d0811250122y6872c0ael469ba10ffe113508@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-OriginalArrivalTime: 25 Nov 2008 19:49:15.0532 (UTC) FILETIME=[E5949CC0:01C94F36]
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

Hi Rohan,

On Tue, 25 Nov 2008, Rohan Sen wrote:

> Hi All,
>
> When RSVP-P2MP tunneling is used as P-Tunnel protocol, then how can a shared
> C-tree be used

Please look at section 11 and 13 of
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt

> or that shared C-tree can be used only when P-Tunnel protocol
> instantiates MI-PMSI through PIM or mLDP?

Inter site shared C-trees can be used when the P-tunnel protocol is
RSVP-TE P2MP.

> If a shared C-tree is used rooted at C-RP on some PE router for a mVPN, then
> do all PE C-PIM instances send C-Register and C-Join/Prune PIM messages
> directly to the C-RP via P-Tunnel (P2MP-RSVP tunnel) with destination
> address set to the C-RP Address? The draft does not clearly say anything
> about sending such C-PIM packets over the provider backbone.
>
> Greatly appreciate any help/hints on these topics.
>

C-Register packets are unicast packets and are sent from the C-DR to the
C-RP. For propagation of C-multicast routes when BGP is used for exchanging
C-multicast routing information please look at section 11 of
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-2547bis-mcast-bgp-05.txt.

rahul