1 / 5

AT&T AMT Multicast Update

AT&T AMT Multicast Update. IETF 84 Vancouver, BC. AT&T AMT Landscape. Production ready Relays deployed in 12 national sites Based on v9 Moving to v14 4Q12 (assuming it is finalized and approved) Total of 150 to 200 Gbps capacity by EOY 2012

zareh
Download Presentation

AT&T AMT Multicast Update

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. AT&T AMT Multicast Update IETF 84 Vancouver, BC

  2. AT&T AMT Landscape • Production ready Relays deployed in 12 national sites • Based on v9 • Moving to v14 4Q12 (assuming it is finalized and approved) • Total of 150 to 200 Gbps capacity by EOY 2012 • Soliciting large Content Providers with popular multicastable content • Engaged with Octoshape to utilize AMT capabilities to distribute their customers’ content • Octoshape’s proprietary technology ensures reliable delivery with high quality (quality metrics from Octoshape GW client) • Primary used for high-scale broadcast-quality video distribution • 24x7 broadcast: Examples: CNN live video (cnn.com), TVEverywhere • Events: Examples: Eurovision Song Contest, French Open

  3. Eurovision Song Contest • Partnered with Octoshape • Up to 10’s of thousands of simultaneous clients viewing • Supported 10’s of Gbps at peak period • Approx Domestic = 70%, International = 30% • Single Anycast address • No failures and sampling showed excellent quality • Interesting issue discovered w/respect Anycast routing • As busy peering locations quiesced the AMT tunnels burrowed deeper into BB to non-peering located Relays • Possible solution = separate Anycast address for Peering and Non-peering located Relays

  4. Anycast Issue 3 PeerRelay AT&T Peering Router 2 1 Peer Router 4 4 5 Internal Relay Peer Router 6 AT&T Peering Router PeerRelay External Network AT&T Network • External network peering router initially sends requests to nearest AT&T Relay at peering location • And receives content back from nearest AT&T Relay at peering location • AT&T Relay exceeds capacity limits for tunnels and quiesces • Requests routed (by AT&T Peering Routers) to Internal Relay • Internal Relay sends content via nearest peering router • Wasted BW as it would be better to serve out of the Peer Relay at the egress location • Short term solution is Internal and External Anycast address for Relays • Longer term: Router Based Relays with “infinite” BW

  5. Next Steps • Continue to deploy capacity as demand warrants • Working to make this a Product Offering (managed service) • Will allow CPs to use with their own external MC source • Integration with caching services • Integrate with other ISPs to support interdomain CDN Multicast • Setup Interconnection • Includes AMT and Native • Completed ATIS specification • Working IETF draft BCP

More Related