1 / 18

Peering at the Content Layer

Peering at the Content Layer. Bruce Davie. Chief Service Provider Architect bsd@nicira.com. Outline. Some history: “peering peer-to-peer” Motivation for interconnecting CDNs Technical challenges Current efforts Discussion. SN. SN. SN. SN. SN. SN. SN. SN. SN. Peer DHT. SN. SN.

ohio
Download Presentation

Peering at the Content Layer

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. Peering at the Content Layer Bruce Davie Chief Service Provider Architectbsd@nicira.com

  2. Outline • Some history: “peering peer-to-peer” • Motivation for interconnecting CDNs • Technical challenges • Current efforts • Discussion

  3. SN SN SN SN SN SN SN SN SN Peer DHT SN SN SN SN SN GW SN SN SN SN SN Peer DHT GW SN SN SN GW SN SN SN GW SN GW SN SN SN SN SN GW SN SN Peer DHT SN SN SN SN SN SN SN SN SN Peering Peer-to-Peer • See Walfish et al., IPTPS 2005 • Each DHT exposes a (put, get) service a la OpenDHT • Service Providers operate individual DHTs and collaborate to provide a global service

  4. Peering Providers above IP Layer • Peering among DHTs (rather than one big DHT) provides • 1. Isolation: autonomous providers can manage, troubleshoot etc without concern for state in another provider • 2. Good Incentives: in a large ring, each provider has incentive to free-load on the resources of other providers • 3. Flexible Policy: e.g. a regional provider prefers to get content from local region rather than from another region • The important thing is the interface (put, get), not the internal implementation • Analogous to BGP at the IP peering interface

  5. Peering among CDN operators • DHT-as-a-service yet to take off, but CDNs have • So let’s peer at the Content Layer • Peering at the IP layer provided a lot of benefits • Essentially took networking from the “walled garden” model of AOL (and even earlier companies) to the innovative, all-powerful, Global Internet • Hope for similar benefits if we can peer at Content layer

  6. CDN Building Blocks

  7. How CDNs work in one slide • Back-end or Origin servers hold the original content • Cache nodes or surrogates hold copies of the content, replicated and geographically distributed • Requests for content from users get redirected to surrogates • Either DNS, HTTP redirect, or both • Lots of cleverness to pick a surrogate to optimize QOE, cost, performance, etc • Surrogate may need to acquire content from origin or another surrogate

  8. CDNs Today Content Provider Content Provider Content Provider Content Provider CDN Provider CDN Provider

  9. CDNI Model Content Provider only need contractual/technical relationship with 1 (or a few) CDN Content Provider Content Provider Content Provider Content Provider CDN Provider Content Provider CDN Provider CDN Provider CDNI Gateway CDNI Gateway CDNI Gateway Content Provider CDN Provider CDN Provider CDNI Gateway CDNI Gateway Content Provider Content delivered to user by “best” downstream CDN. Where “best” reflects Content Provider and CDN Provider policies, agreements, tarrifs,..

  10. Why CDN Peering Makes Sense • There is a handful of global CDNs today, and high barrier to entry • Akamai, Limelight, Level3 • They have little incentive to interconnect with anyone • May ISPs are deploying CDN technology within their footprint because their business is increasingly about content delivery • CDN improves user experience by allocating resources to popular content • CDN saves on bandwidth costs for SP • A lack of CDN peering means that the CDN infrastructure is underutilized • Netflix over Comcast example • ISPs lose control over how content flows across their network • Bandwidth wastage for ISPs • More global-reach CDNs will be enabled by peering, fostering competition, innovation • Akamai has been described as a money-routing company – more of that must be good, right?

  11. CDNI Problem Overview • Unlike DHTs, CDNs lack a really clean interface • Partly due to the fact that they try to be “transparent” • Some mess with DNS, some use HTTP-redirects • Need to get a number of details right: • A request for content should produce the right content (naming) • A chain of CDNs deliver content – everyone wants to get paid (accounting) • The Content owner pays someone to deliver content - wants to know that content actually was delivered (logging) • Content sometimes needs to be purged in a hurry (control) • Lots of metadata (e.g. access controls, regional availability, time windows) • Routing of requests has many similarities to BGP (policy, loop-avoidance)

  12. -------- / \ | CSP | \ / -------- * /\ * / \ ---------------------- |CDNI| ---------------------- / Upstream CDN \ | | / Downstream CDN \ | +-------------+ | Control Interface| +-------------+ | |******* Control |<======|====|========>| Control *******| |* +------*----*-+ | | | | +-*----*------+ *| |* * * | | | | * * *| |* +------*------+ | Logging Interface| +------*------+ *| |* ***** Logging |<======|====|========>| Logging ***** *| |* * +-*-----------+ | | | | +-----------*-+ * *| |* * * * | Request Routing | * * * *| .....*...+-*---------*-+ | Interface | +-*---------*-+...*.*... . |* * *** Req-Routing |<======|====|========>| Req-Routing *** * *| . . |* * * +-------------+.| | | | +-------------+ * * *| . . |* * * . CDNI Metadata | * * *| . . |* * * +-------------+ |. Interface | +-------------+ * * *| . . |* * * | Distribution|<==.===|====|========>| Distribution| * * *| . . |* * * | | | . \ / | | | * * *| . . |* * * |+---------+ | | . \/ | | +---------+| * * *| . . |* * ***| +---------+| | ....Request......+---------+ |*** * *| . . |* *****+-|Surrogate|************************|Surrogate|-+***** *| . . |******* +---------+| | Acquisition | |+----------+ *******| . . | +-------------+ | | +-------*-----+ | . . \ / \ * / . . ---------------------- ---------*------------ . . * . . * Delivery . . * . . +--*---+ . ...............Request.............................| User |..Request.. | Agent| +------+ IETF CDNI Model and Interfaces <==> ifces in scope of CDNI **** ifces outside scope .... Ifces outside scope

  13. Example Content Provider Content Provider CDN Provider Log Acquire CDNI Gateway CDN Provider Redirect CDNI Gateway Request Request Content

  14. End-UserOperatorBOperator A |DNS cdn.csp.com | | |-------------------------------------------------->| | | |(1) |CNAME b.cdn.csp.com | | |NS records for b.cdn.csp.com | |<--------------------------------------------------| |DNS b.cdn.csp.com | | |------------------------>| | | |(2) | |IPaddrofB's Delivery Node | |<------------------------| | |HTTP cdn.csp.com | | |------------------------>| | | |(3) | | |DNS op-b-acq.op-a.net | | |------------------------>| | | |(4) | |IPaddrofA's Delivery Node | |<------------------------| | |HTTP op-b-acq.op-a.net | | |------------------------>| | | |(5) | |Data | | |<------------------------| |Data | | |<------------------------| |

  15. Current Work • Customer Trials • Some of these ideas tried last year with 2 operators, 2 CDN vendors, 2 countries • At least one larger trial underway • IETF • CDNI Working Group is attempting to standardize the appropriate interfaces • Quite a lot of moving parts • Reducing the amount of ad hoc agreements and manual config seems necessary

  16. Routing for Content • There have been proposals to carry content names (e.g. URIs) in BGP • Hard to see how this can scale • Not obviously needed for CDNI • Intra-CDN routing today is all proprietary • One approach to inter-CDN routing: • Let CDNs advertise “footprint” • Redirect requests to CDNs based on matching user requests to footprint info

  17. Discussion • Peering at the IP layer has been key to Internet’s success • Failure to peer at content layer is causing problems already as content dominates • Could think of this as a cheap path to Content Centric Networking • Akamai’s leading innovation, arguably, was routing money across peering boundaries – CDNI creates more money flow opportunities • Global CDNs may or may not have correct incentives to play • A lot of this will come down to economics • Technical hurdles mostly around defining clean interfaces that meet rich set of requirements, allow flexibility in implementation

  18. References • http://datatracker.ietf.org/wg/cdni/ • http://tools.ietf.org/html/draft-davie-cdni-framework-01 • http://datatracker.ietf.org/doc/draft-previdi-cdni-footprint-advertisement/

More Related