Alaerte,
At the moment there's no telling whether the bandwidth savings are that significant compared to ingress replication method given our multicast application (IPTV) is currently only on limited deployment. Theoritically using the P2MP LSPs with BGP-VPLS P-Tunnel attribute, it should not be replicating the packets (a maximum of only 1 copy of packet will traverse through the same link). Hope this help. /ihsan From: alaerte vidali [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 December, 2007 7:00 AM To: Ihsan Junaidi Ibrahim Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Multicast over VPLS Hi Ibrahim, Could you tell me if that solved the problem of using same link twice or more for same flow, when PE1 to PEy goes over same link than PE1 to PEx and both PEx and PEy has multicast users? tks, Alaerte On 12/2/07, Ihsan Junaidi Ibrahim <[EMAIL PROTECTED]> wrote: I believe it's draft-ietf-l2vpn-vpls-mcast-01. We are already running P2MP LSP (template-based) for VPLS multicast delivery. We're on 8.3. -----Original Message----- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] On Behalf Of alaerte vidali Sent: Friday, 30 November, 2007 2:14 PM To: juniper-nsp@puck.nether.net Subject: [j-nsp] Multicast over VPLS Hi, Any news about what draft Juniper is considering implement to avoid waste bandwidth when sending multicast over VPLS in ring topology? tks, Alaerte _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
