OTT IPTV CDN IPv 6 Challenges of OTT

OTT, IPTV, CDN + IPv 6 Challenges of OTT video delivery in the dual-stacked world Berislav Todorovic, berislav. todorovic@gmail. com

Disclaimer A disclaimer a day, keeps the lawyer away The views and opinions expressed in this presentation are those of the author and do not necessarily reflect the official policy or position of the author’s employer or any other legal entity. Examples and diagrams provided within this presentation are only generic examples, not reflecting any implementation of an existing system or a network. Assumptions made within the presentation are not reflective of the position of any legal entity. … and you’re not supposed to read it easily!

Digital Video Ecosystem Today • DVB-S, DVB-C, DVB-T … • Vo. D over cable networks (STB-based) • Over-the-top TV – You. Tube – Netflix – … • TV Delivery via IP (IPTV) • Multi-screen TV – Live streaming – Vo. D Internet-based

The Isles of the Cyberworld … IPv 6 IPv 4 NAT 64 DS-Lite 4 rd 6 rd MAP (P+T)

The Dual-Stacked Reality Bottleneck Private IPv 4 (or no IPv 4) IPv 4 Internet Dual-Stack ISP IPv 4/IPv 6 Public IPv 6 “NAT” IPv 6 Internet They use IPv 4, so it goes via the “NAT” gateway !!!

TV channels Live Sources OTT Video Ecosystem Simplified Content Ingest Delivery DRM Key Server MUX Vo. D Library On-demand content owners Live Encoder Vo. D Encoder Live Packager Vo. D Packager Live DRM C D N Vo. D DRM Portal Website Metadata Processing Systems Where to start with the IPv 6 migration?

Migrating the Head-End Good news • Majority of application flows are HTTP(S) sessions! – Exception: live encoders usually use multicast towards sources – This may be tough … true! • Apache or IIS mostly, so migration should be easy, right? Bad news • In a. php file, in the middle of nowhere, someone wrote: . . . $this->asset[‘url’] = “http: //10. 193. 3. 214/assets/”. 10. 193. 3. 214 $country. “/” $date. “/”. $filename; get_metadata ($this->asset[‘url’], . . . ); . . . Ever heard of DNS ? ? ?

And what about this?

TV channels Live Sources OTT Video Ecosystem Simplified DRM Key Server MUX Vo. D Library On-demand content owners Live Encoder Vo. D Encoder Live Packager Vo. D Packager Live DRM C D N Vo. D DRM Portal Website Metadata Processing Systems Content Ingest Delivery

TV channels Live Sources Pragmatic Approach DRM Key Server MUX Vo. D Library On-demand content owners Live Encoder Vo. D Encoder Live Packager Vo. D Packager Content Ingest Delivery Live DRM C D N Vo. D DRM Portal Website Metadata Processing Systems Leave this in its IPv 4 nirvana! Here you need IPv 6!

In other words … • • The CDN is the key component here! It requires full dual-stack support! It will talk to the back-end systems using IPv 4 To the customers it will use IPv 6 or IPv 4 (depends on the end customer site). • We should avoid using IPv 4 for IPv 6 -enabled customers! • But try to find an IPv 6 -capable CDN …

CDN Options • Lease • Buy • Build your own (e. g. using open-source etc. )

Vendors can be funny sometimes … (Both birds and mosquitos can fly, so …) Question: • Does your product support IPv 6. Please elaborate! Answer: • Yes it does. Our product is based on Linux kernel supports IPv 6 Therefore, our product supports IPv 6 … Sure?

Content Delivery Network (CDN) Content Delivery (Caches) Origin Backup Origin 14

CDN Intelligence - Request Routing d 1. IE. cdn. com 198. 18. 44. 1 2001: db 8: cd: : 44: 1 HTTP redirector d 1. DK. cdn. com 198. 18. 55. 1 2001: db 8: cd: : 55: 1 Content HTTP request GET / HTTP/1. 1 Host: www. x. com Request Router d 1. DE. cdn. com 198. 18. 33. 1 2001: db 8: cd: : 33: 1 Redirection based on End Client IP(v 4/v 6) address! HTTP response HTTP 302 Found n Location: http: //d 1. de. cdn. com/path Content request (GET /path HTTP. . . ) 15

CDN Intelligence - Request Routing d 1. IE. cdn. com 198. 18. 44. 1 2001: db 8: cd: : 44: 1 DNS query www. x. com IP = ? ? ? Authoritativ e DNS Content Request Router DNS reply www. x. com IP = 198. 18. 33. 1 d 1. DK. cdn. com 198. 18. 55. 1 2001: db 8: cd: : 55: 1 Local DNS d 1. DE. cdn. com 198. 18. 33. 1 2001: db 8: cd: : 33: 1 Redirection based on the IP address of End Client’s Local DNS! Content request (GET /path HTTP. . . ) 16

DNS Request Routing Issue • IP address of the DNS is presented to the CDN’s RR • Client IP information by default lost • Proposal - draft-vandergaast-edns-client-subnet – – Uses EDNS 0 option to include end client’s IP subnet info Added. Request by the ISP local DNS Router Supported by Google r. DNS [8. 8] / [8. 8. 4. 4] Full dual-stack (IPv 4/IPv 6) support! 192. 0. 1. 1/32 2001: db 8: ec: : 1/128 Local DNS Q EDNS 0 192. 0. 1. 0/24 2001: db 8: ec: : /48

Global CDNs supporting edns-client-subnet

CDN as a tool for IPv 6 migrations … No FW changes! IPTV Backend CDN IPv 4 / IPv 6 world IPv 4 BE systems can live on IPv 4 …

Issues to Take Care … • • • The CDN should FULLY support IPv 6 (on all nodes!) Authoritative DNS infrastructure – IPv 6 ready? Resolving DNS servers – IPv 6 ready? Geo-IPv 6 information to be kept accurate! Otherwise, we may experience issues … – Redirection of IPv 6 customer to an IPv 4 -only node … – Redirection of IPv 6 customer to a non-optimal node • Security …