CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet

Slides:

Advertisements

Similar presentations

Reinventing using REST. Anything addressable by a URI is called a resource GET, PUT, POST, DELETE WebDAV (MOVE, LOCK)

Advertisements

Deployment Considerations for Dual-stack Lite IETF 80 Prague Yiu Lee, Roberta Magione, Carl Williams, Christian Jacquenet Mohamed Boucadair.

Vice President of Facilities

B. Davie, L. Peterson et al. draft-davie-cdni-framework-00.txt.

2.1 Installing the DNS Server Role Overview of the Domain Name System Role Overview of the DNS Namespace DNS Improvements for Windows Server 2008 Considerations.

© 2010 Cisco and/or its affiliates. All rights reserved. 1 Bruce Davie

Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) IETF 67 - ANCP WG November 5-10, 2006 draft-moustafa-ancp-security-threats-00.txt.

TELECOM ITALIA GROUP Ongoing Activities Report BT London, Feb 15, 2011.

CDNI Footprint Advertisement draft-previdi-cdni-footprint-advertisement-00 Stefano Previdi Francois Le Faucheur Allan Guillou Jan Medved IETF-82 Taipei,

Multicasting Applications Across Inter-Domain Peering Points Percy S. Tarapore, AT&T Robert Sayko, AT&T Greg Shepherd, Cisco Toerless Eckert, Cisco Ram.

Building Your Own Firewall Chapter 10. Learning Objectives List and define the two categories of firewalls Explain why desktop firewalls are used Explain.

Flash Crowds And Denial of Service Attacks: Characterization and Implications for CDNs and Web Sites Aaron Beach Cs395 network security.

Introduction CS-480b Dick Steflik. X.800 – OSI Security Services Security Service – a service provided by a protocol layer of communicating open systems,

Technologies for Building Content Delivery Networks Pei Cao Cisco Systems, Inc.

CDN Interconnect (CDNI) Problem Space: Drivers and Enablers Nabil Bitar (Verizon) Francois Le Faucheur (Cisco) Benjamin Niven-Jenkins (Velocix/ALU) IETF80-Prague.

INTERCONNECTING CDNS AKA “PEERING PEER-TO-PEER” Bruce Davie & Francois le Faucheur.

© 2011 Nicira. All rights reserved.. Peering at the Content Layer Bruce Davie Chief Service Provider Architect

On the Use and Performance of Content Distribution Networks Balachander Krishnamurthy Craig Wills Yin Zhang Presenter: Wei Zhang CSE Department of Lehigh.

Content Distribution March 8, : Application Layer1.

1 Open Pluggable Edge Services OPES Abbie Barbir, Ph.D.

Cryptography and Network Security

M i SMob i S Mob i Store - Mobile i nternet File Storage Platform Chetna Kaur.

OV Copyright © 2013 Logical Operations, Inc. All rights reserved. Network Security  Network Perimeter Security  Intrusion Detection and Prevention.

Case Study: DirXML Implementation at Waste Management Rick Wagner Systems Engineer Novell, Inc.

CPSC 441: Multimedia Networking1 Outline r Scalable Streaming Techniques r Content Distribution Networks.

OV Copyright © 2011 Element K Content LLC. All rights reserved. Network Security  Network Perimeter Security  Intrusion Detection and Prevention.

Grid Resource Allocation and Management (GRAM) Execution management Execution management –Deployment, scheduling and monitoring Community Scheduler Framework.

CDN Interconnection Problem Statement draft-jenkins-cdni-problem-statement-02 Ben Niven-Jenkins Francois Le Faucheur Nabil Bitar.

Intra-CDN Provider CDNi Experiment Ge Chen Mian Li Hongfei Xia

Introduction to dCache Zhenping (Jane) Liu ATLAS Computing Facility, Physics Department Brookhaven National Lab 09/12 – 09/13, 2005 USATLAS Tier-1 & Tier-2.

1 Topic 2: Lesson 3 Intro to Firewalls Summary. 2 Basic questions What is a firewall? What is a firewall? What can a firewall do? What can a firewall.

Network Security. 2 SECURITY REQUIREMENTS Privacy (Confidentiality) Data only be accessible by authorized parties Authenticity A host or service be able.

11 SECURING NETWORK COMMUNICATION Chapter 9. Chapter 9: SECURING NETWORK COMMUNICATION2 OVERVIEW  List the major threats to network communications. 

Applicability and Tradeoffs of ICN for Efficient IoT draft-lindgren-icnrg-efficientiot-00 presented by Olov Schelén IRTF ICNRG IETF 90, Toronto.

1 Chapter 1 – Background Computer Security T/ Tyseer Alsamany - Computer Security.

CDNI Requirements (draft-lefaucheur-cdni-requirements-02) CDNI Working Group IETF 81 Quebec City, Canada July 28, 2011 Kent Leung Yiu.

Draft-tarapore-mbone- multicast-cdni-06 Percy S. Tarapore, AT&T Robert Sayko, AT&T Greg Shepherd, Cisco Toerless Eckert, Cisco Ram Krishnan, Brocade.

Topic 1 – Introduction Huiqun Yu Information Security Principles & Applications.

Switch Features Most enterprise-capable switches have a number of features that make the switch attractive for large organizations. The following is a.

Models for adaptive-streaming-aware CDNI - File Management and Content Collections draft-brandenburg-cdni-has-01, section 3.1 CDNI Extended Design Team.

Applicability and Tradeoffs of ICN for Efficient IoT draft-lindgren-icnrg-efficientiot-01 presented by Adeel Malik IRTF ICNRG Interim ICNRG meeting, Paris.

Your friend, Bluestem. What is Bluestem? “Bluestem is a software system which enables one or more high-security SSL HTTP servers in a domain (entrusted.

CDNI Metadata Interface (draft-ma-cdni-metadata-01) Kevin J. Ma

Content Terminology in CDNI draft-deventer-cdni-content-terminology IETF 81 – Quebec, CDNI WG Oskar van Deventer Ray van Brandenburg.

IETF69 ANCP WG1 ANCP Multicast Handling draft-maglione-ancp-mcast-00.txt R. Maglione, A. Garofalo - Telecom Italia F. Le Faucheur, T. Eckert - cisco Systems.

26/07/2011 IETF 81 CDNI WG - draft-xiaoyan-cdni-requestrouting-01 1 CDNI WG draft-xiaoyan-cdni-requestrouting-01 IETF81 - Quebec Xiaoyan He

Content Distribution Internetworking IETF BOF December 12, 2000 Phil Rzewski Gary Tomlinson.

CDN Interconnect Metadata draft-ietf-cdni-metadata-00 Ben Niven-Jenkins David Ferguson Grant Watson.

CDNI Capabilities Interface draft-ma-cdni-capabilities-00 Kevin J. Ma 1.

MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.

INFSO-RI Enabling Grids for E-sciencE NPM Security Alistair K Phipps (NeSC) JRA4 Face To Face, CERN, Geneva.

Interdomain Multicast BCP Draft IETF 84 Vancouver, BC Robert Sayko

CDNI Video Publisher Use cases (draft-ma-cdni-publisher-use-cases-00) Kevin J. Ma

Draft-fieau-https-delivery-delegation-02 A CDNi Use case Lurk BoF Frédéric Fieau Orange Emile Stephan, Benoît Gaussen IETF 95 – Buenos Aires.

Request Interface for CDN Interconnection draft-choi-cdni-req-intf-00.txt Taesang Choi Jonggyu Sung Jongmin Lee.

DOTS Requirements Andrew Mortensen November 2015 IETF 94 1.

Multicast in Information-Centric Networking March 2012.

Windows Active Directory – What is it? Definition - Active Directory is a centralized and standardized system that automates network management of user.

Deploying Dual-Stack Lite in IPv6 Network draft-boucadair-dslite-interco-v4v6-04 Mohamed Boucadair

CDNI URI Signing (draft-leung-cdni-uri-signing-01) CDNI Working Group IETF 85 Atlanta, Georgia November 8, 2012 Kent Leung

Module 3: Enabling Access to Internet Resources

Live Global Sports Events

Models for adaptive-streaming-aware CDNI - Content Acquisition and Content Collections draft-brandenburg-cdni-has-01, section 3.2 CDNI Extended Design.

Francois Le Faucheur– CDNI Work Scope Recap Francois Le Faucheur–

CDNi Request Routing Redirection with Loop Prevention draft-choi-cdni-req-routing-redir-loop-prevention-01.txt Taesang Choi Young-IL.

Goals of soBGP Verify the origin of advertisements

Cloud Web Filtering Platform

ATIS IIF Use Cases and Relevance to CDNI

BoF CDNI IETF80 – Prague Content Distribution Network Interconnection (CDNI) Experiments Gilles Bertrand, France Telecom Francois Le Faucheur, Cisco Larry.

BoF CDNi draft-bertrand-cdni-use-cases-01 IETF80 - Prague

Presentation transcript:

CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet Dean Cheng Yiu Lee IETF77, Anaheim Francois Le Faucheur, Cisco Mahesh Viveganandhan, Cisco Grant Watson, BT Yiu Lee, Comcast IETF 80, Prague

Requirements Structure Sets of Requirements  Generic Requirements  Control Protocol Requirements  Request Routing Protocol Requirements  Metadata Distribution Protocol Requirements  Logging Protocol Requirements  Security Requirements Scopes (in each set):  Initial scope (within potential WG initial charter) MUST: strong convergence that it is required “day1” SHOULD/MAY: needs further arbitration on whether it can be supported “day1”  Future scope (outside potential WG initial charter)

Generic Requirements R1: Leverage existing protocols. R2: No change in the user agent (the client). R3: CDNI solution must not be intrusive into CDNs:  dCDN and uCDN are not required to know each other’s cache topology, cache status,… R4 & R5: HTTP is the first supported protocol for Delivery and Acquisition. R8: [should] support cascaded CDNs. R9: [should] support any kind of CDNI topology (e.g. Star, Ring, Tree etc.) R10: CDNI must prevent looping R11: CDNI must consider known issues with 3 rd party references uCDN= upstream CDN dCDN= downstream CDN

Control Protocol Requirements These requirements are defined to:  Enable CDNs to communicate for management/bootstrapping prior to the actual content delivery.  Enable uCDN to trigger actions in dCDN Some highlights:  R15: Content Purge request by uCDN (invalidate/delete an object).  R16: Content Purge Acknowledgment by dCDN.  R17: Trigger Metadata pre-positioning from the uCDN to dCDN.  R18: [should] Trigger content pre-positioning from the uCDN to dCDN

Request Routing Protocol Requirements These requirements are defined to allow the uCDN Routing- Request System (RRS) to delegate a request to the dCDN RRS. Highlights:  R27: dCDN can refuse further request delegations (“busy” tone)  R28: [should] dCDN advertises capabilities (e.g. footprint, content types), resources (e.g. streaming bandwidth) and affinities (e.g. delivery cost)  R30: [may] dCDN advertises policy/admin-info (e.g. max requests per second, max aggregate volume)  R31 & R32: efficient for small objects (aka DNS-based) and for large objects (aka HTTP-based)  R33 & R34: Support both Recursive Request Routing and Iterative Request Routing.  R37: Pass the user agent location information.  R38: Pass the content metadata location information.

Metadata Distribution Protocol Requirements These requirements are defined to allow the uCDN to communicate to dCDN the “distribution metadata” Highlights:  R45: uCDN provides metadata to dCDN  R46: Support both pre-positioning and dynamic content acquisition  R47: Support metadata “Pull”  R48: Support metadata “Push”  R49 & R50: metadata must convey where/how dCDN can acquire content  R51 & R52: Support real-time Add/Modify/Delete metadata  R53 & R54: Metadata data structure must support referencing a single object or a set of objects.  R58 & R59 : Support distribution control policies (geo-blocking, time window & authorization checks (e.g. URI signing) Distribution metadata = metadata that is relevant to, and has to be processed, by CDNs (eg where to acquire content, time window)

Logging Protocol Requirements In a distributed system such as CDNI, logging is used to track/recreate the chain of events (for accounting, monitoring, analytics, troubleshooting). Highlights:  R63: Reliable logging.  R64: dCDN provides logging to uCDN for content delivery performed by dCDN on behalf of uCDN  R67: Support offload batch upload of log files.

Security Requirements A set of requirements to secure CDNI  R74: Support secure channel to exchange data over Internet.  R75: Protect against DOS attack.  R76: [should] non-repudiation of logs.  R77: [should] Protect against spoofed log.  R78: [may] Define a mechanism to delegate credentials to downstream CDN to acquire content from the origin.

Questions?

Two New Terms Recursive CDNI Request Routing  Consult the downstream CDN to make the routing decision Iterative CDNI Request Routing  Make the routing decision without consulting downstream CDN