1 / 6

Context

Requirements for multicast in PP L3 VPNs draft-morin-l3vpn-ppvpn-mcast-reqts-00 Elodie Hémon Thomas Morin Renaud Moignard Jean-Louis Le Roux. Context. Many solutions proposed for multicast in VPNs Existing requirements for PP VPN only address unicast services

quincy-morrow
Download Presentation

Context

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements for multicast in PP L3 VPNsdraft-morin-l3vpn-ppvpn-mcast-reqts-00Elodie HémonThomas MorinRenaud MoignardJean-Louis Le Roux

  2. Context • Many solutions proposed for multicast in VPNs • Existing requirements for PP VPN only address unicast services • Multicast VPN deployment needs specific requirements • Operator feedback may help to guide multicast VPN solution design 2

  3. Overview 1/2 • Goals • Document functional requirements for solutions enabling provider provisioned IP VPNs to carry customers multicast traffic • Be solution agnostic • Hopefully serve as a guideline for solution drafts • Draft structure • Problem statement • Customer standpoint • Service provider standpoint • Use cases 3

  4. Overview 2/2 • Statement : Bandwidth vs. State Multicast in VPNs problem is "how to make the trade-off ?" • Some key points • Scalability • Tunability : tuning knobs letting the SP choose how to do the trade-off • Traffic engineering • Resource optimization • QoS • Versatility : not bound to a particular tunneling mode • Inter-{AS,provider} support • Monitoring and troubleshooting • Robustness and infrastructure security 4

  5. Open questions • Issues developed are open for discussion • In particular • Extranet support • Fragmentation issues • Control mechanisms • Use cases and corresponding concerns • Carrier's carrier • … 5

  6. Next steps • We already received feedback from some operators • Next revision will integrate those contributions • More feedback wanted • Do you feel this work makes sense ? • What are your requirements ? • Contribute use cases • General comments about the draft • Please send your comments on L3VPN WG mailing list 6

More Related