OTT, IPTV, CDN + IPv6 OTT, IPTV, CDN + IPv6

Challenges of OTT video delivery in thedual-stacked world 

Berislav Todorovic,berislav.todorovic@gmail.com

DisclaimerDisclaimer

The views and opinions expressed in this presentation are those of the 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 and do not necessarily reflect the official policy or position of the

author’s employer or any other legal entity. Examples and diagrams author’s employer or any other legal entity. Examples and diagrams provided within this presentation are only generic examples, not reflecting provided within this presentation are only generic examples, not reflecting any implementation of an existing system or a network. Assumptions made any implementation of an existing system or a network. Assumptions made

within the presentation are not reflective of the position of any legal entity. within the presentation are not reflective of the position of any legal entity.

A disclaimer a day, keeps the lawyer

away

… and you’re not supposed to read it

easily!

Digital Video Ecosystem TodayDigital Video Ecosystem Today

• DVB-S, DVB-C, DVB-T …• VoD over cable networks (STB-based)• Over-the-top TV

– YouTube– Netflix– …

• TV Delivery via IP (IPTV)• Multi-screen TV

– Live streaming– VoD

Internet-basedInternet-based

The Isles of the Cyberworld …The Isles of the Cyberworld …

IPv4IPv4

IPv6IPv6

NAT64DS-Lite

4rd6rd

MAP (P+T)

The Dual-Stacked RealityThe Dual-Stacked Reality

Private IPv4(or no IPv4)

Dual-Stack ISPIPv4/IPv6

Public IPv6

IPv4Internet

IPv6Internet

Bottleneck

“NAT”

They use IPv4, so it goesvia the “NAT” gateway !!!

LiveEncode

r

VoDEncode

r

LivePackag

er

VoDPackag

er

LiveDRM

VoDDRM

CDN

PortalWebsite

Metadata Processing Systems

MUX

Live Sources

VoDLibrary

DRM Key

Server

TVchannels

On-demandcontentowners

OTT Video EcosystemOTT Video EcosystemSimplifiedSimplified Content

IngestContentDelivery

Where to start with the IPv6 migration?

Migrating the Head-EndMigrating 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?

...$this->asset[‘url’] = “http://10.193.3.21410.193.3.214/assets/” . $country . “/” $date . “/” . $filename;

get_metadata ($this->asset[‘url’], ...);...

Ever heard of DNS ???

Bad news• In a .php file, in the middle of nowhere, someone wrote:

And what about this?And what about this?

LiveEncode

r

VoDEncode

r

LivePackag

er

VoDPackag

er

LiveDRM

VoDDRM

CDN

PortalWebsite

Metadata Processing Systems

MUX

Live Sources

VoDLibrary

DRM Key

Server

TVchannels

On-demandcontentowners

OTT Video EcosystemOTT Video EcosystemSimplifiedSimplified Content

IngestContentDelivery

LiveEncode

r

VoDEncode

r

LivePackag

er

VoDPackag

er

LiveDRM

VoDDRM

CDN

PortalWebsite

Metadata Processing Systems

MUX

Live Sources

VoDLibrary

DRM Key

Server

TVchannels

On-demandcontentowners

Pragmatic ApproachPragmatic ApproachContent

IngestContentDelivery

Here youneedIPv6!

Leave thisin its IPv4

nirvana!

In other words …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 IPv4• To the customers it will use IPv6 or IPv4 (depends

on the end customer site).• We should avoid using using IPv4 for IPv6-

enabled customers!• But try to find an IPv6-capable CDN …

CDN OptionsCDN Options

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

Vendors can be funny sometimes …Vendors can be funny sometimes …(Both birds and mosquitos can fly, so …)(Both birds and mosquitos can fly, so …)

Question:• Does your product support IPv6. Please elaborate!

Answer:• Yes it does.

Our product is based on LinuxLinux kernel supports IPv6Therefore, our product supports IPv6 …

Sure?

14

CContent ontent DDelivery elivery NNetwork (CDN)etwork (CDN)

Origin

Delivery(Caches)

BackupOrigin

Content

15

CDN Intelligence - Request RoutingCDN Intelligence - Request Routing

HTTP requestHTTP request

GET / HTTP/1.1Host: www.x.com

HTTP responseHTTP responseHTTP 302 Found \n Location: http://d1.de.cdn.com/path

d1.IE.cdn.comd1.IE.cdn.com198.18.44.1198.18.44.12001:db8:cd::44:12001:db8:cd::44:1

d1.DE.cdn.comd1.DE.cdn.com198.18.33.1198.18.33.12001:db8:cd::33:12001:db8:cd::33:1

d1.DK.cdn.comd1.DK.cdn.com198.18.55.1198.18.55.12001:db8:cd::55:12001:db8:cd::55:1

RequestRequestRouterRouter

Content request(GET /path HTTP...)(GET /path HTTP...)

Content

HTTP redirector

Redirection based on

End ClientIP(v4/v6) address!

16

CDN Intelligence - Request RoutingCDN Intelligence - Request Routing

DNS queryDNS querywww.x.com

IP = ??????

DNS replyDNS replywww.x.com

IP = 198.18.33.1198.18.33.1

RequestRequestRouterRouter

Content request(GET /path HTTP...)(GET /path HTTP...)

Content

d1.IE.cdn.comd1.IE.cdn.com198.18.44.1198.18.44.12001:db8:cd::44:12001:db8:cd::44:1

d1.DE.cdn.comd1.DE.cdn.com198.18.33.1198.18.33.12001:db8:cd::33:12001:db8:cd::33:1

d1.DK.cdn.comd1.DK.cdn.com198.18.55.1198.18.55.12001:db8:cd::55:12001:db8:cd::55:1

LocalDNS

Authoritative

DNS

Redirection based on

the IP address ofEnd Client’sLocal DNS!

DNS Request Routing IssueDNS 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 EDNS0 option to include end client’s IP subnet info– Added by the ISP local DNS– Supported by Google rDNS [8.8.8.8] / [8.8.4.4]– Full dual-stack (IPv4/IPv6) support!

RequestRequestRouterRouterLocal

DNS

DNS Q

192.0.1.1/322001:db8:ec::1/128

DNS QEDNS0192.0.1.0/242001:db8:ec::/48

Global CDNs supporting Global CDNs supporting edns-client-edns-client-subnetsubnet

IPv6world

CDN as a tool for IPv6 migrations …CDN as a tool for IPv6 migrations …

IPTV Backend

IPv4CDN

IPv4 / IPv6

BE systemscan live on

IPv4 …

No FWchanges!

Issues to Take Care …Issues to Take Care …

• The CDN should FULLY support IPv6 (on all nodes!)

• Authoritative DNS infrastructure – IPv6 ready?• Resolving DNS servers – IPv6 ready?• Geo-IPv6 information to be kept accurate!• Otherwise, we may experience issues …

– Redirection of IPv6 customer to an IPv4-only node …– Redirection of IPv6 customer to a non-optimal node

• Security …