IETF Logo Mail Archive

Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Register packet is sent through MPLS provider network

Yakov Rekhter <yakov@juniper.net> Mon, 24 November 2008 15:05 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 3D9253A6A08; Mon, 24 Nov 2008 07:05:05 -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 01B7A3A6922 for <l3vpn@core3.amsl.com>; Mon, 24 Nov 2008 07:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 cOTTmm5PPEck for <l3vpn@core3.amsl.com>; Mon, 24 Nov 2008 07:05:03 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 1264E3A67ED for <l3vpn@ietf.org>; Mon, 24 Nov 2008 07:05:03 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKSSrCnNyWtTiv8YrjxLkhJN2uxeHqM/2g@postini.com; Mon, 24 Nov 2008 07:05:01 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, 24 Nov 2008 07:03:10 -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, 24 Nov 2008 07:03:10 -0800
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Nov 2008 07:03:09 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Nov 2008 07:03:09 -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 mAOF38M88921; Mon, 24 Nov 2008 07:03:08 -0800 (PST) (envelope-from yakov@juniper.net)
Message-ID: <200811241503.mAOF38M88921@magenta.juniper.net>
To: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Register packet is sent through MPLS provider network
In-Reply-To: <673423.18257.qm@web94910.mail.in2.yahoo.com>
References: <673423.18257.qm@web94910.mail.in2.yahoo.com>
X-MH-In-Reply-To: Subinoy Das <subinoy_das_82@yahoo.com> message dated "Thu, 20 Nov 2008 20:23:21 +0530."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <29609.1227538988.1@juniper.net>
Date: Mon, 24 Nov 2008 07:03:08 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 24 Nov 2008 15:03:09.0236 (UTC) FILETIME=[C341F740:01C94E45]
Cc: L3VPN MAIL <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

Subinoy,

> 
> Hi,
> I have one confusion from draft-ietf-l3vpn-2547bis-mcast-07.txt.
> Customer is running PIM as multicast protocol, Provider network
> support l3vpn with BGP, RSVP P2MP.
> Then how customer Register packet destined to C-RP is forwarded 
> through provider network?

Customer Register messages are unicast messages, and as such
they are forwarded throught the provider network to C-RP the
same way as any customer unicast packets are forwarded through
the provider network - using 2547 VPN unicast routing.

Yakov.

v2.28.0 | Report a Bug | By Email | System Status