draft-ietf-cdni-requirements-07.txt   draft-ietf-cdni-requirements-08.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: December 2, 2013 Comcast Expires: December 28, 2013 Comcast
May 31, 2013 June 26, 2013
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-07 draft-ietf-cdni-requirements-08
Abstract Abstract
Content Delivery Networks (CDNs) are frequently used for content Content Delivery Networks (CDNs) are frequently used for content
delivery. As a result of significant growth in content delivered delivery. As a result of significant growth in content delivered
over IP networks, existing CDN providers are scaling up their over IP networks, existing CDN providers are scaling up their
infrastructure. Many Network Service Providers and Enterprise infrastructure. Many Network Service Providers and Enterprise
Service Providers are also deploying their own CDNs. To deliver Service Providers are also deploying their own CDNs. To deliver
contents from the Content Service Protect (CSP) to end users, the contents from the Content Service Protect (CSP) to end users, the
contents may traverse across multiple CDNs. This creates a need for contents may traverse across multiple CDNs. This creates a need for
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 December 2, 2013. This Internet-Draft will expire on December 28, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 17, line 29 skipping to change at page 17, line 29
* logging of the delivery of the content for the session * logging of the delivery of the content for the session
when at least one file in the set was delivered when at least one file in the set was delivered
MI-19 [MED] The CDNI Metadata Distribution interface should support MI-19 [MED] The CDNI Metadata Distribution interface should support
an OPTIONAL mechanism allowing the Upstream CDN to indicate to an OPTIONAL mechanism allowing the Upstream CDN to indicate to
the Downstream CDN which CDNI Log fields are to be provided the Downstream CDN which CDNI Log fields are to be provided
for all, for specific sets of, or for specific content items for all, for specific sets of, or for specific content items
delivered using HTTP. A CDNI implementation that does not delivered using HTTP. A CDNI implementation that does not
support this optional CDNI Metadata Distribution Interface support this optional CDNI Metadata Distribution Interface
mechanism MUST ignore this log format indication and generate mechanism shall ignore this log format indication and generate
CDNI logging format for HTTP Adaptive Streaming using the CDNI logging format for HTTP Adaptive Streaming using the
default set of CDNI Logging fields. (Note: this function is default set of CDNI Logging fields. (Note: this function is
not concluded to be in Metadata Interface or Control not concluded to be in Metadata Interface or Control
Interface) Interface)
MI-20 [MED] The CDNI Metadata Distribution interface should allow MI-20 [MED] The CDNI Metadata Distribution interface should allow
the Upstream CDN to signal to the Downstream CDN the Content the Upstream CDN to signal to the Downstream CDN the Content
Collection ID value for all, for specific sets of, or for Collection ID value for all, for specific sets of, or for
specific content items delivered using HTTP. Whenever the specific content items delivered using HTTP. Whenever the
Downstream CDN is instructed by the Upstream CDN to report the Downstream CDN is instructed by the Upstream CDN to report the
skipping to change at page 19, line 37 skipping to change at page 19, line 37
storage resources when content storage is performed by storage resources when content storage is performed by
cascaded CDNs on behalf of the Downstream CDN. cascaded CDNs on behalf of the Downstream CDN.
LI-13 [HIGH] The CDNI Logging interface shall support logging of LI-13 [HIGH] The CDNI Logging interface shall support logging of
deleted objects from the Downstream CDN to the Upstream CDN as deleted objects from the Downstream CDN to the Upstream CDN as
a result of explicit delete requests on via the CDNI Control a result of explicit delete requests on via the CDNI Control
interface from the Upstream CDN. interface from the Upstream CDN.
LI-14 [HIGH] The CDNI Logging interface shall support extensibility LI-14 [HIGH] The CDNI Logging interface shall support extensibility
to allow proprietary information fields to be carried. These to allow proprietary information fields to be carried. These
information fields must be agreed upon ahead of time between information fields shall be agreed upon ahead of time between
the corresponding CDNs. the corresponding CDNs.
LI-15 [HIGH] The CDNI Logging interface shall support the exchange LI-15 [HIGH] The CDNI Logging interface shall support the exchange
of extensible log file formats to support proprietary of extensible log file formats to support proprietary
information fields. These information fields must be agreed information fields. These information fields shall be agreed
upon ahead of time between the corresponding CDNs. upon ahead of time between the corresponding CDNs.
LI-16 [HIGH] The CDNI Logging interface shall allow a CDN to notify LI-16 [HIGH] The CDNI Logging interface shall allow a CDN to notify
another CDN about which CDNI logging information is available another CDN about which CDNI logging information is available
for transfer and/or no longer available (e.g. it exceeded some for transfer and/or no longer available (e.g. it exceeded some
logging retention period or some logging retention volume). logging retention period or some logging retention volume).
LI-17 [MED] The CDNI Logging interface should support the ability LI-17 [MED] The CDNI Logging interface should support the ability
for the Downstream CDN to include the Content Collection ID for the Downstream CDN to include the Content Collection ID
and Session ID fields in CDNI log entries generated for HTTP and Session ID fields in CDNI log entries generated for HTTP
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 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/