Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Register packet is sent through MPLS provider network
Subinoy Das <subinoy_das_82@yahoo.com> Tue, 25 November 2008 04:50 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 054AF3A69EB; Mon, 24 Nov 2008 20:50:59 -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 6FAB13A69EB for <l3vpn@core3.amsl.com>; Mon, 24 Nov 2008 20:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.245
X-Spam-Level:
X-Spam-Status: No, score=0.245 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_50=0.001, 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 bEV5sncRFrON for <l3vpn@core3.amsl.com>; Mon, 24 Nov 2008 20:50:56 -0800 (PST)
Received: from n8a.bullet.tw1.yahoo.com (n8a.bullet.tw1.yahoo.com [119.160.244.195]) by core3.amsl.com (Postfix) with SMTP id 6C3843A691A for <l3vpn@ietf.org>; Mon, 24 Nov 2008 20:50:56 -0800 (PST)
Received: from [119.160.244.76] by n8.bullet.tw1.yahoo.com with NNFMP; 25 Nov 2008 04:50:53 -0000
Received: from [203.212.168.61] by t1.bullet.tw1.yahoo.com with NNFMP; 25 Nov 2008 04:50:53 -0000
Received: from [203.104.18.51] by t2.bullet.kr1.yahoo.com with NNFMP; 25 Nov 2008 04:50:51 -0000
Received: from [127.0.0.1] by omp112.mail.in2.yahoo.com with NNFMP; 25 Nov 2008 04:50:38 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 756968.81215.bm@omp112.mail.in2.yahoo.com
Received: (qmail 57047 invoked by uid 60001); 25 Nov 2008 04:50:38 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=oYf8p82lGUXNslQ6o5hXom9SUli0racrI+nhyTdpqFr80yCpqoWCRh/dzLDzzJ68TdTHK6akV2H77TUiUARTODgxzTRL7MKHPUPl9zWNiA+wVu18e4o2Irq4Smub81kdYxb8TIURsH/c7W8ASzTdHTPr438NzwSYwi9rlWkmCPU=;
X-YMail-OSG: onStPNgVM1l9y3zpgNW1RYpz8FXGtNHiGqieUkGtqDUUiswmQIkuxkLAWKIwDninlKypRApHkNwKye8hcjlJUNFW4LeIfyBW.q5p_NJEzziT7UV6OJ9dV150gnGNewnUQAjW1RobS3dtXpAxyDpHj1ZlTOwlPwZtSvx.L7ckkKkEzJyQfmF0j966FHX8JieCQG91UvUDX3JnbMM-
Received: from [125.20.3.101] by web94904.mail.in2.yahoo.com via HTTP; Tue, 25 Nov 2008 10:20:38 IST
X-Mailer: YahooMailRC/1155.32 YahooMailWebService/0.7.260.1
References: <673423.18257.qm@web94910.mail.in2.yahoo.com> <200811241503.mAOF38M88921@magenta.juniper.net>
Date: Tue, 25 Nov 2008 10:20:38 +0530
From: 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
To: Yakov Rekhter <yakov@juniper.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-68146013-1227588638=:35955"
Message-ID: <663103.35955.qm@web94904.mail.in2.yahoo.com>
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
Thanks - Subinoy ________________________________ From: Yakov Rekhter <yakov@juniper.net> To: Subinoy Das <subinoy_das_82@yahoo.com> Cc: L3VPN MAIL <l3vpn@ietf.org> Sent: Monday, 24 November, 2008 8:33:08 PM Subject: Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Register packet is sent through MPLS provider network 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. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
- draft-ietf-l3vpn-2547bis-mcast-07.txt -- How C-Re… Subinoy Das
- Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How … Yakov Rekhter
- Re: draft-ietf-l3vpn-2547bis-mcast-07.txt -- How … Subinoy Das