From l3vpn-bounces@ietf.org Wed May 11 10:40:00 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVsNU-0007ng-0p; Wed, 11 May 2005 10:40:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DVsNS-0007nb-LY for l3vpn@megatron.ietf.org; Wed, 11 May 2005 10:39:58 -0400 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 KAA09702 for ; Wed, 11 May 2005 10:39:56 -0400 (EDT) Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DVscy-0002N4-RW for l3vpn@ietf.org; Wed, 11 May 2005 10:56:02 -0400 Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 0F633180048E for ; Wed, 11 May 2005 14:39:34 +0000 (GMT) X-OB-Received: from unknown (205.158.62.51) by wfilter.us4.outblaze.com; 11 May 2005 14:39:34 -0000 Received: by ws1-5.us4.outblaze.com (Postfix, from userid 1001) id F33536F050; Wed, 11 May 2005 14:39:33 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; A1.17; B2.12; Q2.03) Received: from [203.126.136.220] by ws1-5.us4.outblaze.com with http for arut@techie.com; Wed, 11 May 2005 09:39:33 -0500 X-Mailer: mail.com webmail From: "Arut Selvan" To: l3vpn@ietf.org Date: Wed, 11 May 2005 09:39:33 -0500 X-Originating-Ip: 203.126.136.220 X-Originating-Server: ws1-5.us4.outblaze.com Message-Id: <20050511143933.F33536F050@ws1-5.us4.outblaze.com> X-Spam-Score: 2.3 (++) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable Subject: Multiple PIM instances for mvpn X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org

Hi,

I came across "VPN-specific PIM instances" being mentioned in section 2.= 1 of

draft-rosen-vpn-mcast-08.txt. I wonder why multiple instances of PIM wou= ld

be required. Can't we have a single PIM instance managing multiple MVRFs= ?

I have come across an implementation which has a single instance of rout= ing protocols

in the case of unicast. Why is it different for multicast ?

Thanks,

Arut

2.1. Multicast VRFs

   Each VRF has its own multicast routing table.  When a = multicast data
   or control packet is received from a particu= lar CE device, multicast
   routing is done in the associated = VRF.

   Each PE router runs a number of instances of PIM-SM, as man= y as one
   per VRF.  In each instance of PIM-SM, the PE = maintains a PIM
   adjacency with each of the PIM-capable CE r= outers associated with
   that VRF.  The multicast routin= g table created by each instance is
   specific to the corresp= onding VRF.  We will refer to these PIM
   instances as "= VPN-specific PIM instances".

 


--=20

___________________________________________________________
Sign-up f= or Ads Free at Mail.com
http://www.mail.com/?sr=3Dsignup


From l3vpn-bounces@ietf.org Wed May 11 21:50:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DW2q6-0006IV-Um; Wed, 11 May 2005 21:50:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DW2q5-0006IP-NN for l3vpn@megatron.ietf.org; Wed, 11 May 2005 21:50:13 -0400 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 VAA18601 for ; Wed, 11 May 2005 21:50:11 -0400 (EDT) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DW35h-0008FH-Ko for l3vpn@ietf.org; Wed, 11 May 2005 22:06:23 -0400 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 11 May 2005 18:50:02 -0700 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j4C1nxnC011909; Wed, 11 May 2005 18:49:59 -0700 (PDT) Received: (from ycai@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id SAA28906; Wed, 11 May 2005 18:49:59 -0700 (PDT) Date: Wed, 11 May 2005 18:49:59 -0700 (PDT) Message-Id: <200505120149.SAA28906@cisco.com> X-Authentication-Warning: cypher.cisco.com: ycai set sender to ycai@cypher.cisco.com using -f From: Yiqun Cai To: arut@techie.com In-reply-to: <20050511143933.F33536F050@ws1-5.us4.outblaze.com> (arut@techie.com) References: <20050511143933.F33536F050@ws1-5.us4.outblaze.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: l3vpn@ietf.org Subject: Re: Multiple PIM instances for mvpn X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ycai@cisco.com List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org > > Hi, > I came across "VPN-specific PIM instances" being mentioned in section 2.1 of > draft-rosen-vpn-mcast-08.txt. I wonder why multiple instances of PIM would > be required. Can't we have a single PIM instance managing multiple MVRFs? > I have come across an implementation which has a single instance of routing protocols > in the case of unicast. Why is it different for multicast ? > Thanks, > Arut "A VPN-specific PIM instance" refers to the PIM protocol machinery executed in the context of that VPN/VRF on the PE router. It doesn't imply or mandate how one should implement it, especially how many OS specific processes or taskes that should be created. -- Yiqun From l3vpn-bounces@ietf.org Mon May 16 17:48:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXnS3-0004L9-EV; Mon, 16 May 2005 17:48:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXnRy-0004Jz-Bo; Mon, 16 May 2005 17:48:34 -0400 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 RAA26978; Mon, 16 May 2005 17:48:31 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXnib-0004k0-1V; Mon, 16 May 2005 18:05:45 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1DXnRv-0001nu-7K; Mon, 16 May 2005 17:48:31 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 16 May 2005 17:48:31 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: Internet Architecture Board , l3vpn mailing list , l3vpn chair , l3vpn chair , RFC Editor Subject: Protocol Action: 'MPLS/BGP Layer 3 Virtual Private Network Management Information Base' to Proposed Standard X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org The IESG has approved the following document: - 'MPLS/BGP Layer 3 Virtual Private Network Management Information Base ' as a Proposed Standard This document is the product of the Layer 3 Virtual Private Networks Working Group. The IESG contact persons are Mark Townsley and Margaret Wasserman. Technical Summary This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor Multi-protocol Label Switching Layer-3 Virtual Private Networks on a Multi-Protocol Label Switching (MPLS) Label Switching Router (LSR) supporting this feature. Working Group Summary (From Ron Bonica) Around this time last year (April 2004) there was significant contraversy regarding one particular item in the VPN MIB. See the thread "draft-ietf-l3vpn-mpls-vpn-mib drop counter" in the (l3vpn mailing list) archive. This issue was resolved in early summer (2004) and there has been general consensus since then. Protocol Quality This document was reviewed by (MIB Doctor) Bert Wijnen and Mark Townsley. RFC Editor Note: There are 3 items that the IESG requests the RFC Editor to correct before publication of this document. 1. In section 18, please change: 'Each of the following "IANA Considerations" subsections requests' to: 'The following subsection requests' 2. Note that the "9999" in the text below is not an the actual number, it is a number that needs to be assigned by IANA. It would have been much better to have"xxxx" or "nnnn" here, but that is not case this time. > MIB OID assignment of: > ::= { mplsStdMIB 9999 } -- assigned by IANA, see section > 18.1 for details 3. Please make the various references consistent with respect to hyphen usage as in the example below: > The MODULE is named: MPLS-L3VPN-STD-MIB > And then in the one MODULE-COMPLIANCE he speaks of "L3 MPLS VPN MIB" > and in the 2nd MODULE-COMPLIANCE he speaks of "L3-MPLS-VPN-STD-MIB" > which is inconsistent and confusing. From l3vpn-bounces@ietf.org Mon May 16 17:50:04 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXnTQ-0004lU-I9; Mon, 16 May 2005 17:50:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DXnTK-0004iy-TJ; Mon, 16 May 2005 17:49:59 -0400 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 RAA27171; Mon, 16 May 2005 17:49:56 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DXnjx-0004my-BY; Mon, 16 May 2005 18:07:09 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1DXnTK-0006by-0v; Mon, 16 May 2005 17:49:58 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 16 May 2005 17:49:58 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: Internet Architecture Board , l3vpn mailing list , l3vpn chair , l3vpn chair , RFC Editor Subject: Protocol Action: 'Definition of Textual Conventions for Virtual Private Network (VPN) Management' to Proposed Standard X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org The IESG has approved the following document: - 'Definition of Textual Conventions for Virtual Private Network (VPN) Management ' as a Proposed Standard This document is the product of the Layer 3 Virtual Private Networks Working Group. The IESG contact persons are Mark Townsley and Margaret Wasserman. Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines Textual Conventions used in VPNs and IETF VPN-related MIBs. Working Group Summary Chairs reported no controversy in WG at all. Protocol Quality This document has been reviewed by Bert Wijnen (MIB Doctor) and Mark Townsley. RFC Editor Note: 1. Please make the reference to RFC 2685 normative rather than informative. 2. There are no page numbers in the ToC 3. Please use the following text for Section 4, Security Considerations: > This module does not define any management objects. Instead, it > defines a set of textual conventions which may be used by other > MIB modules to define management objects. > > Meaningful security considerations can only be written in the MIB > modules that define management objects. This document has > therefore no impact on the security of the Internet. From l3vpn-bounces@ietf.org Tue May 17 15:48:19 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DY838-0007j4-VF; Tue, 17 May 2005 15:48:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DY835-0007i9-6O; Tue, 17 May 2005 15:48:15 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02066; Tue, 17 May 2005 15:48:12 -0400 (EDT) Message-Id: <200505171948.PAA02066@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 17 May 2005 15:48:12 -0400 Cc: l3vpn@ietf.org Subject: I-D ACTION:draft-ietf-l3vpn-ospf-2547-04.txt X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF. Title : OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP VPNs Author(s) : E. Rosen, et al. Filename : draft-ietf-l3vpn-ospf-2547-04.txt Pages : 28 Date : 2005-5-17 Many Service Providers offer Virtual Private Network ("VPN") services to their customers, using a technique in which customer edge routers ("CE routers") are routing peers of provider edge routers ("PE routers"). The Border Gateway Protocol ("BGP") is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching ("MPLS") is used to tunnel customer packets across the provider's backbone. This is known as a "BGP/MPLS IP VPN". The base specification for BGP/MPLS IP VPNs presumes that the routing protocol on the interface between a PE router and a CE router is BGP. This document extends that specification by allowing the routing protocol on the PE/CE interface to be the Open Shortest Path First ("OSPF") protocol. This document updates draft-ietf-l3vpn-rfc2547bis-03.txt. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospf-2547-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-l3vpn-ospf-2547-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-l3vpn-ospf-2547-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-5-17154141.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-l3vpn-ospf-2547-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-l3vpn-ospf-2547-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-5-17154141.I-D@ietf.org> --OtherAccess-- --NextPart-- From l3vpn-bounces@ietf.org Wed May 25 04:14:17 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dar1s-0004x6-Us; Wed, 25 May 2005 04:14:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dar1o-0004v3-8v for l3vpn@megatron.ietf.org; Wed, 25 May 2005 04:14:12 -0400 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 EAA17512 for ; Wed, 25 May 2005 04:14:10 -0400 (EDT) Received: from webmail-outgoing.us4.outblaze.com ([205.158.62.67]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DarK8-0005WH-N5 for l3vpn@ietf.org; Wed, 25 May 2005 04:33:10 -0400 Received: from unknown (unknown [192.168.9.180]) by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id CC8561800226 for ; Wed, 25 May 2005 08:13:57 +0000 (GMT) X-OB-Received: from unknown (205.158.62.55) by wfilter.us4.outblaze.com; 25 May 2005 08:13:57 -0000 Received: by ws1-3.us4.outblaze.com (Postfix, from userid 1001) id C2C7B101D8; Wed, 25 May 2005 08:13:57 +0000 (GMT) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; A1.17; B2.12; Q2.03) Received: from [203.126.136.220] by ws1-3.us4.outblaze.com with http for arut@techie.com; Wed, 25 May 2005 03:13:57 -0500 X-Mailer: mail.com webmail From: "Arut Selvan" To: l3vpn@ietf.org Date: Wed, 25 May 2005 03:13:57 -0500 X-Originating-Ip: 203.126.136.220 X-Originating-Server: ws1-3.us4.outblaze.com Message-Id: <20050525081357.C2C7B101D8@ws1-3.us4.outblaze.com> X-Spam-Score: 2.6 (++) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: quoted-printable Subject: igmp modifications for mVPN solution X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org

Hi All,

I would like to know if any modifications to IGMP would be required to s= upport a multicast VPN solution.

Thanks,

Arut


--=20

___________________________________________________________
Sign-up f= or Ads Free at Mail.com
http://www.mail.com/?sr=3Dsignup


From l3vpn-bounces@ietf.org Wed May 25 04:57:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DarhH-0003qo-JG; Wed, 25 May 2005 04:57:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DarhG-0003qj-EB for l3vpn@megatron.ietf.org; Wed, 25 May 2005 04:57:02 -0400 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 EAA20065 for ; Wed, 25 May 2005 04:57:00 -0400 (EDT) Received: from omr5.netsolmail.com ([216.168.230.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Darzb-0006iW-JB for l3vpn@ietf.org; Wed, 25 May 2005 05:16:00 -0400 Received: from ms9.netsolmail.com (IDENT:mirapoint@[216.168.230.183]) by omr5.netsolmail.com (8.12.10/8.12.10) with ESMTP id j4P8uwqp019348; Wed, 25 May 2005 04:56:58 -0400 (EDT) Received: from ms9.netsolmail.com (localhost.netsolmail.com [127.0.0.1]) by ms9.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id DGU17607; Wed, 25 May 2005 04:56:57 -0400 (EDT) Message-Id: <200505250856.DGU17607@ms9.netsolmail.com> Received: from 81.178.20.174 by ms9.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with HTTP/1.1; Wed, 25 May 2005 09:56:57 +0100 Date: Wed, 25 May 2005 09:56:57 +0100 From: Mark Lewis To: Arut Selvan X-Mailer: Webmail Mirapoint Direct 3.2.2-GA MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.8 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Cc: l3vpn@ietf.org Subject: Re: igmp modifications for mVPN solution X-BeenThere: l3vpn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mark@mjlnet.com List-Id: l3vpn.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: l3vpn-bounces@ietf.org Errors-To: l3vpn-bounces@ietf.org Assuming that you are refering to a solution based on: http://www.ietf.org/internet-drafts/draft-rosen-vpn-mcast- 08.txt Because the solution described in the draft is transparent to customers, and IGMP is a protocol is deployed at customer sites for host membership reporting/etc, this implies no requirement for modifications. Rgds, Mark ---- Original message ---- >Date: Wed, 25 May 2005 03:13:57 -0500 >From: "Arut Selvan" >Subject: igmp modifications for mVPN solution >To: l3vpn@ietf.org > > Hi All, > > I would like to know if any modifications to IGMP > would be required to support a multicast VPN > solution. > > Thanks, > > Arut > > -- > > ___________________________________________________________ > Sign-up for Ads Free at Mail.com > http://www.mail.com/?sr=signup