1 / 5

Interdomain Multicast BCP Draft

Interdomain Multicast BCP Draft. IETF 84 Vancouver, BC Robert Sayko sayko@att.com. Purpose and Goals.

isabel
Download Presentation

Interdomain Multicast BCP Draft

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. Interdomain Multicast BCP Draft IETF 84 Vancouver, BC Robert Sayko sayko@att.com

  2. Purpose and Goals • Create document to describe use of multicast to support content distribution in an environment involving multiple Service Providers in a Content Distribution Network Interconnection (CDN-i) Federation. • CDNi WG working on interdomain (i.e. Federation) CDN, but only with respect to caching • Mboned should/can support CDNi with respect to MC • Effort endorsed by mboned chair • CDNi WG has no immediate plans to address MC • Document will/should be a BCP

  3. Scope • Focus on Use cases specified in ATIS Standard: • Native Multicast: • With Multicast Enabled CDN  CDN Interconnection • With CDN  CDN Interconnection via a GRE Tunnel • AMT: • CDN  CDN Interconnection via AMT • Supporting CDN  End User Interconnection via AMT • Primary CDN  End User Interconnection via AMT • Identify and detail multicast capabilities to supportthe recommended interfaces and data exchanges between ISPs to support inter-ISP multicast • Describe provisioning processes for recommended interfaces (e.g. AMT tunnels, GRE tunnels, native) • Describemulticast-based inter-ISP data exchanges and processes for supporting: • Provisioning of: network infrastructure to support protocols, tunnels, DNS etc. • General routing and request routing • Billing and reporting • Life cycle support (customer care)

  4. Activity to Date • ATIS specification completed and published • Available for reference • Multi-vendor, ISP contributors • Initial IETF BCP draft completed and to be distributed around IETF 84 • Current co-authors from: • AT&T • Cisco • Juniper • Brocade

  5. Next Steps • Seeking additional authors/help expertise • Develop required text in following sections: • Section 4: Content Types Suitable for Multicast Delivery & Include Specific Requirements as Needed • Section 5: Evaluation of Native Multicast capabilities to Support CDN-I • Section 6: Evaluation of AMT Capabilities to Support CDN-I • Initiate Discussions with CDNi WG: • Highlight MBONED Work on Topic • Explore potential for Joint Work as Appropriate

More Related