P4P meeting Eitan Efron, VP BD eitane@oversi.com

1. P4P meetingEitan Efron, VP BDeitane@oversi.com January 2008

2. The Bandwidth Explosion Demand for P2P and Video Creates Pressure • And the network just can’t cope… Existing Infrastructure P2P Downloads (BitTorrent etc.) P2PTV (Joost etc.) HTTP Video (YouTube etc.) POOR user experience Bandwidth Demand P4P targets: max delivery, minimize ISP pain

3. New Technologies are Required % of traffic Un-Monetized P2P Internet video Can not be throttled Throttled using DPI Monetized P2P Time

4. Cache = Network Optimization Engine Core / POP Backbone Router DPI Out of main traffic path Cache Saves on bandwidth Ensures & accelerates QoS Reduces pressure on the network Complements DPI install base Defers infrastructure upgrades

5. Caching = Up to 95% Savings ! X 20 value (95% BHR) Cache Out 3Gbps In 250Mbps (80Mbps international)

6. Caching = Accelerated Performance BitTorrent Cache acceleration example 680MB, Maple Story Update Peers onlyWith serverWith Cache DWLD speed 65Kb/s 375Kb/s 9.2Mb/s DWLD time 23 hours 4 hours 9 minutes X 150 faster performance High Definition (HD) Delivery Opportunity

7. Cache = Monetization through Service Differentiation Charge Users for performance Charge Content owners for delivery GOLD 5 Mbps SILVER 500 Kbps BRONZE 50 Kbps 500 GB 50 GB 10 GB HD 5 Mbps SD 500 Kbps basic best effort SLA / Acceleration Users Over the top content Cache ISP content

8. P4P Modes A iTracker AppTracker 2 • Peer query Tracker • AppTracker quarries iTracker (3) • iTracker sends peering suggestions (2) • Tracker updates peers’ list 3 Internet 1 4 ISP Peer B C AppTracker AppTracker iTracker 2 2 iTracker Internet 3 3 Internet 1 1 4 4 ISP ISP Peer Peer

9. iTracker May Increase Load on ISP Network AppTrackers INTERNET iTracker internal Peers list CORE ISP Domain Increase load on limited & expensive Uplinks ACCESS DSLAM CMTS DSLAM DSLAM CMTS CMTS DSLAM CMTS

10. iTracker auto Cache Discovery Optimizes Network Performance AppTrackers INTERNET Single Cache can be located at core No Uplink reciprocity iTracker internal Peers + cache CORE Cache ISP Domain Relieve load on limited Uplinks ACCESS DSLAM CMTS DSLAM DSLAM CMTS CMTS DSLAM CMTS

11. iTracker Implementing Cache Discovery • iTracker/AppTracker provide users with a list of Good Peers & Cache Servers • Good Peers = • Users in same POP range • Users with higher Uplink capacities • Users with lower infrastructure cost metrics • Caches in ISP cloud • POP • NOC • Enables full control by ISP to optimize to ISP infrastructure constraints • E.g. MSO/WiMAX operators with limited uplinks capacity will want to reduce load on peer uplinks and increase use of Caching

12. iTracker + Cache Field Experience 200% increase in performance iTracker + cache discovery Introduced

13. AppTracker iTracker A 2 3 Internet 1 4 ISP Peer Suggested iTracker Cache Discovery Format P4P iTracker • Map • IP range -> POP, “cost” metrics, Good Peers • IP range -> Cache servers + • Vendor Specific Data (VSD) iTracker query (Get Map) ISP/Vendor DB update AppTracker Additional compilation A. Get Map (iTracker query) B. Get vendor specific cache location GetServers(IP,hash,VSD, protocol) Vendor Specific plug-ins Vendor A Vendor B

14. Summary • Cache = relives the load on the network + sustains/improves QoE + new monetization opportunities, over existing ISP infrastructure • iTrackers cache discovery = improves savings and user experience by additional 200% • Further network optimization can occur through • Additional caching levels (e.g. aggregation, Access) • Automatic Cache discovery embedded at Client level (e.g. where P4P is not implemented), e.g. BitTorrent CDP • Cache + iTracker + DPI • DPI throttles only traffic in local caching devices and local peers

15. Energize Your Network • Meeting Customers’ Demands in • the New Digital Media Age • www.oversi.com Thank you for listening.