draft-ietf-cdni-requirements-15.txt   draft-ietf-cdni-requirements-16.txt 
Network Working Group K. Leung, Ed. Network Working Group K. Leung, Ed.
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational Y. Lee, Ed. Intended status: Informational Y. Lee, Ed.
Expires: July 18, 2014 Comcast Expires: July 21, 2014 Comcast
Jan 14, 2014 Jan 17, 2014
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-15 draft-ietf-cdni-requirements-16
Abstract Abstract
Content delivery is frequently provided by specifically architected Content delivery is frequently provided by specifically architected
and provisioned Content Delivery Networks (CDNs). As a result of and provisioned Content Delivery Networks (CDNs). As a result of
significant growth in content delivered over IP networks, existing significant growth in content delivered over IP networks, existing
CDN providers are scaling up their infrastructure. Many Network CDN providers are scaling up their infrastructure. Many Network
Service Providers and Enterprise Service Providers are also deploying Service Providers and Enterprise Service Providers are also deploying
their own CDNs. To deliver contents from the Content Service their own CDNs. To deliver contents from the Content Service
Provider (CSP) to end users, the contents may traverse across Provider (CSP) to end users, the contents may traverse across
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 18, 2014. This Internet-Draft will expire on July 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 33 skipping to change at page 7, line 33
upgrade, to the Content Service Provider delivering content upgrade, to the Content Service Provider delivering content
through a single CDN, to benefit from content delivery through a single CDN, to benefit from content delivery
through interconnected CDNs. through interconnected CDNs.
GEN-4 {HIGH} The CDNI solution shall not depend on intra-CDN GEN-4 {HIGH} The CDNI solution shall not depend on intra-CDN
information to be exposed to other CDNs for effective and information to be exposed to other CDNs for effective and
efficient delivery of the content. Examples of intra-CDN efficient delivery of the content. Examples of intra-CDN
information include surrogate topology, surrogate status, information include surrogate topology, surrogate status,
cached content, etc. cached content, etc.
GEN-5 {HIGH} The CDNI solution shall support delivery to the User GEN-5 {HIGH} The CDNI solution shall support CDN interconnection
Agent based on HTTP [RFC2616]. (Note that while delivery and when delivery to the User Agent is based on HTTP [RFC2616].
acquisition "data plane" protocols are out of the CDNI (Note that while delivery and acquisition "data plane"
solution scope, the CDNI solution "control plane" protocols protocols are out of the CDNI solution scope, the CDNI
are expected to participate in enabling, selecting or solution "control plane" protocols are expected to
facilitating operations of such acquisition and delivery participate in enabling, selecting or facilitating operations
protocols. Hence it is useful to state requirements on the of such acquisition and delivery protocols. Hence it is
CDNI solution in terms of specifying which acquisition and useful to state requirements on the CDNI solution in terms of
delivery protocols are to be supported). specifying which acquisition and delivery protocols are to be
supported).
GEN-6 {HIGH} The CDNI solution shall support acquisition across GEN-6 {HIGH} The CDNI solution shall support acquisition across
CDNs based on HTTP [RFC2616]. (The note above applies to CDNs based on HTTP [RFC2616]. (The note above applies to
this requirement too) this requirement too)
GEN-7 {LOW} The CDNI solution may support delivery to the User GEN-7 {LOW} The CDNI solution may support delivery to the User
Agent based on protocols other than HTTP. Agent based on protocols other than HTTP.
GEN-8 {LOW} The CDNI solution may support acquisition across CDNs GEN-8 {LOW} The CDNI solution may support acquisition across CDNs
based on protocols other than HTTP. based on protocols other than HTTP.
skipping to change at page 23, line 19 skipping to change at page 23, line 19
Stephan, Eric Burger, Susan He, Kevin Ma, Daryl Malas, Iuniana Stephan, Eric Burger, Susan He, Kevin Ma, Daryl Malas, Iuniana
Oprescu, and Spencer Dawkins for their input. Serge Manning along Oprescu, and Spencer Dawkins for their input. Serge Manning along
with Robert Streijl, Vishwa Prasad, Percy Tarapore, Mike Geller, and with Robert Streijl, Vishwa Prasad, Percy Tarapore, Mike Geller, and
Ramki Krishnan contributed to this document by addressing the Ramki Krishnan contributed to this document by addressing the
requirements of the ATIS Cloud Services Forum. requirements of the ATIS Cloud Services Forum.
Ray Brandenburg, Matt Caufield, and Gilles Bertrand provided valuable Ray Brandenburg, Matt Caufield, and Gilles Bertrand provided valuable
inputs for HTTP Adaptive Streaming, CDNI Metadata interface, and CDNI inputs for HTTP Adaptive Streaming, CDNI Metadata interface, and CDNI
Logging interface, respectively. Logging interface, respectively.
Stephen Farrell, Adrian Farrel, Benoit Claise, Sean Turner, Daryl
Malas, Christer Holmberg, and Carlos Pignataro provided review
comments that helped improve the document.
14. References 14. References
14.1. Normative References 14.1. Normative References
[I-D.ietf-cdni-framework] [I-D.ietf-cdni-framework]
Peterson, L. and B. Davie, "Framework for CDN Peterson, L. and B. Davie, "Framework for CDN
Interconnection", draft-ietf-cdni-framework-07 (work in Interconnection", draft-ietf-cdni-framework-07 (work in
progress), November 2013. progress), November 2013.
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
 End of changes. 5 change blocks. 
13 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/