IETF Logo Mail Archive

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

Subinoy Das <subinoy_das_82@yahoo.com> Thu, 20 November 2008 14:53 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 827073A6836; Thu, 20 Nov 2008 06:53:29 -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 4B8023A6836 for <l3vpn@core3.amsl.com>; Thu, 20 Nov 2008 06:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level:
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=-0.508, BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
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 TwS7JTFh0Me4 for <l3vpn@core3.amsl.com>; Thu, 20 Nov 2008 06:53:27 -0800 (PST)
Received: from n1a.bullet.in.yahoo.com (n1a.bullet.in.yahoo.com [202.43.219.18]) by core3.amsl.com (Postfix) with SMTP id A22D63A681D for <l3vpn@ietf.org>; Thu, 20 Nov 2008 06:53:26 -0800 (PST)
Received: from [202.86.4.171] by n1.bullet.in.yahoo.com with NNFMP; 20 Nov 2008 14:53:24 -0000
Received: from [203.104.18.55] by t2.bullet.in.yahoo.com with NNFMP; 20 Nov 2008 14:53:24 -0000
Received: from [127.0.0.1] by omp107.mail.in2.yahoo.com with NNFMP; 20 Nov 2008 14:53:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 744018.27944.bm@omp107.mail.in2.yahoo.com
Received: (qmail 19002 invoked by uid 60001); 20 Nov 2008 14:53:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=Np81ErM+UjV5sz9CmFSzPBlKa89jONLTRFz+KMELrFN+HfU4XrzBq30CClhBZ8FKfi7mzNIn3Kzzjj2ZCRgIkdtJ+wL+Lw+TC0SG9awRpl+zfk6I+OTbwXrpW2/jybe1D5JXSvTcOegnZ/vOqpwfswg0Fq/Ngi7eJSN30q6+dt4=;
X-YMail-OSG: V_NyLOoVM1krMDFK.9UUkECjLWAvOtI_t73mPqlTf5ez3fLUm94o2U7dwH.twbsTYNBV_cmKKvafYuEzry3fDq_NciRNQMFx2efPFRe1XCs.WtaQiKeESpEat9HYvSUYbjjHpK5zgOFslN.nwQXJtkvZVcK1nz3J62UQkuADiqMIKYm4Q_HKgLlHDtz49xe9TnrSPi4F5qiCtdk-
Received: from [125.20.3.101] by web94910.mail.in2.yahoo.com via HTTP; Thu, 20 Nov 2008 20:23:21 IST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
Date: Thu, 20 Nov 2008 20:23:21 +0530
From: Subinoy Das <subinoy_das_82@yahoo.com>
Subject: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Register packet is sent through MPLS provider network
To: L3VPN MAIL <l3vpn@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1038468350-1227192801=:18257"
Message-ID: <673423.18257.qm@web94910.mail.in2.yahoo.com>
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,

I have one confusion from draft-ietf-l3vpn-2547bis-mcast-07.txt.

Suppose 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?

Regards,
Subinoy



      Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/

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