draft-ietf-cdni-problem-statement-07.txt   draft-ietf-cdni-problem-statement-08.txt 
Network Working Group B. Niven-Jenkins Network Working Group B. Niven-Jenkins
Internet-Draft Velocix (Alcatel-Lucent) Internet-Draft Velocix (Alcatel-Lucent)
Intended status: Informational F. Le Faucheur Intended status: Informational F. Le Faucheur
Expires: December 25, 2012 Cisco Expires: December 27, 2012 Cisco
N. Bitar N. Bitar
Verizon Verizon
June 23, 2012 June 25, 2012
Content Distribution Network Interconnection (CDNI) Problem Statement Content Distribution Network Interconnection (CDNI) Problem Statement
draft-ietf-cdni-problem-statement-07 draft-ietf-cdni-problem-statement-08
Abstract Abstract
Content Delivery Networks (CDNs) provide numerous benefits: reduced Content Delivery Networks (CDNs) provide numerous benefits: reduced
delivery cost for cacheable content, improved quality of experience delivery cost for cacheable content, improved quality of experience
for End Users and increased robustness of delivery. For these for End Users and increased robustness of delivery. For these
reasons they are frequently used for large-scale content delivery. reasons they are frequently used for large-scale content delivery.
As a result, existing CDN Providers are scaling up their As a result, existing CDN Providers are scaling up their
infrastructure and many Network Service Providers (NSPs) are infrastructure and many Network Service Providers (NSPs) are
deploying their own CDNs. It is generally desirable that a given deploying their own CDNs. It is generally desirable that a given
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 25, 2012. This Internet-Draft will expire on December 27, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 3, line 33 skipping to change at page 3, line 33
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . . 20 8.1. Normative References . . . . . . . . . . . . . . . . . . . 20
8.2. Informative References . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . . 20
Appendix A. Design considerations for realizing the CDNI Appendix A. Design considerations for realizing the CDNI
Interfaces . . . . . . . . . . . . . . . . . . . . . 23 Interfaces . . . . . . . . . . . . . . . . . . . . . 23
A.1. CDNI Request Routing Interface . . . . . . . . . . . . . . 23 A.1. CDNI Request Routing Interface . . . . . . . . . . . . . . 23
A.2. CDNI Metadata Interface . . . . . . . . . . . . . . . . . 25 A.2. CDNI Metadata Interface . . . . . . . . . . . . . . . . . 25
A.3. CDNI Logging Interface . . . . . . . . . . . . . . . . . . 26 A.3. CDNI Logging Interface . . . . . . . . . . . . . . . . . . 26
A.4. CDNI Control Interface . . . . . . . . . . . . . . . . . . 27 A.4. CDNI Control Interface . . . . . . . . . . . . . . . . . . 27
Appendix B. Additional Material . . . . . . . . . . . . . . . . . 28 Appendix B. Additional Material . . . . . . . . . . . . . . . . . 27
B.1. Non-Goals for IETF . . . . . . . . . . . . . . . . . . . . 28 B.1. Non-Goals for IETF . . . . . . . . . . . . . . . . . . . . 28
B.2. Relationship to relevant IETF Working Groups & IRTF B.2. Relationship to relevant IETF Working Groups & IRTF
Reserach Groups . . . . . . . . . . . . . . . . . . . . . 29 Reserach Groups . . . . . . . . . . . . . . . . . . . . . 29
B.2.1. ALTO WG . . . . . . . . . . . . . . . . . . . . . . . 29 B.2.1. ALTO WG . . . . . . . . . . . . . . . . . . . . . . . 29
B.2.2. DECADE WG . . . . . . . . . . . . . . . . . . . . . . 30 B.2.2. DECADE WG . . . . . . . . . . . . . . . . . . . . . . 30
B.2.3. PPSP WG . . . . . . . . . . . . . . . . . . . . . . . 31 B.2.3. PPSP WG . . . . . . . . . . . . . . . . . . . . . . . 31
B.2.4. IRTF P2P Research Group . . . . . . . . . . . . . . . 32 B.2.4. IRTF P2P Research Group . . . . . . . . . . . . . . . 31
Appendix C. Additional Material . . . . . . . . . . . . . . . . . 32 Appendix C. Additional Material . . . . . . . . . . . . . . . . . 32
C.1. Related standardization activites . . . . . . . . . . . . 32 C.1. Related standardization activites . . . . . . . . . . . . 32
C.1.1. IETF CDI Working Group (Concluded) . . . . . . . . . . 33 C.1.1. IETF CDI Working Group (Concluded) . . . . . . . . . . 33
C.1.2. 3GPP . . . . . . . . . . . . . . . . . . . . . . . . . 34 C.1.2. 3GPP . . . . . . . . . . . . . . . . . . . . . . . . . 33
C.1.3. ISO MPEG . . . . . . . . . . . . . . . . . . . . . . . 34 C.1.3. ISO MPEG . . . . . . . . . . . . . . . . . . . . . . . 34
C.1.4. ATIS IIF . . . . . . . . . . . . . . . . . . . . . . . 35 C.1.4. ATIS IIF . . . . . . . . . . . . . . . . . . . . . . . 35
C.1.5. CableLabs . . . . . . . . . . . . . . . . . . . . . . 35 C.1.5. CableLabs . . . . . . . . . . . . . . . . . . . . . . 35
C.1.6. ETSI MCD . . . . . . . . . . . . . . . . . . . . . . . 35 C.1.6. ETSI MCD . . . . . . . . . . . . . . . . . . . . . . . 35
C.1.7. ETSI TISPAN . . . . . . . . . . . . . . . . . . . . . 36 C.1.7. ETSI TISPAN . . . . . . . . . . . . . . . . . . . . . 35
C.1.8. ITU-T . . . . . . . . . . . . . . . . . . . . . . . . 36 C.1.8. ITU-T . . . . . . . . . . . . . . . . . . . . . . . . 36
C.1.9. Open IPTV Forum (OIPF) . . . . . . . . . . . . . . . . 36 C.1.9. Open IPTV Forum (OIPF) . . . . . . . . . . . . . . . . 36
C.1.10. TV-Anytime Forum . . . . . . . . . . . . . . . . . . . 37 C.1.10. TV-Anytime Forum . . . . . . . . . . . . . . . . . . . 36
C.1.11. SNIA . . . . . . . . . . . . . . . . . . . . . . . . . 37 C.1.11. SNIA . . . . . . . . . . . . . . . . . . . . . . . . . 37
C.1.12. Summary of existing standardization work . . . . . . . 37 C.1.12. Summary of existing standardization work . . . . . . . 37
C.2. Related Research Projects . . . . . . . . . . . . . . . . 39 C.2. Related Research Projects . . . . . . . . . . . . . . . . 39
C.2.1. OCEAN . . . . . . . . . . . . . . . . . . . . . . . . 39 C.2.1. OCEAN . . . . . . . . . . . . . . . . . . . . . . . . 39
C.2.2. Eurescom P1955 . . . . . . . . . . . . . . . . . . . . 39 C.2.2. Eurescom P1955 . . . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
The volume of video and multimedia content delivered over the The volume of video and multimedia content delivered over the
skipping to change at page 26, line 30 skipping to change at page 26, line 30
interface (e.g. handling of malformed requests/responses). interface (e.g. handling of malformed requests/responses).
o The syntax (i.e representation/encoding) of the CDNI Metadata o The syntax (i.e representation/encoding) of the CDNI Metadata
objects that will be exchanged over the interface. objects that will be exchanged over the interface.
o The semantics (i.e. meaning and expected contents) of the o The semantics (i.e. meaning and expected contents) of the
individual properties of a Metadata object. individual properties of a Metadata object.
o How the relationships between different CDNI Metadata objects are o How the relationships between different CDNI Metadata objects are
represented. represented.
A.3. CDNI Logging Interface A.3. CDNI Logging Interface
The CDNI Logging interface enables details of logs or events to be The CDNI Logging interface enables details of content distribution
exchanged between interconnected CDNs, where events could be: and delivery activities to be exchanged between interconnected CDNs,
such as log records related to the delivery of content (similar to
o Log records related to the delivery of content (similar to the log the log records recorded in a web server's access log).
records recorded in a web server's access log).
o Real-time or near-real time events before, during or after content
delivery, e.g. content delivery interruption
o Operations and diagnostic messages.
Within CDNs today, logs and events are used for a variety of purposes Within CDNs today, log records are used for a variety of purposes.
in addition to real-time and non real-time diagnostics and auditing Specifically CDNs use logs to generate Call Data Records (CDRs) for
by the CDN Provider and its customers. Specifically CDNs use logs to passing to billing and payment systems and to real-time (and near
generate Call Data Records (CDRs) for passing to billing and payment real-time) analytics systems. Such applications place requirements
systems and to real-time (and near real-time) analytics systems. on the CDNI Logging interface to support guaranteed and timely
Such applications place requirements on the CDNI Logging interface to delivery of log messages between interconnected CDNs. It may also be
support guaranteed and timely delivery of log messages between necessary to be able to prove the integrity of received log messages.
interconnected CDNs. It may also be necessary to be able to prove
the integrity of received log messages.
Several protocols already exist that could potentially be used to Several protocols already exist that could potentially be used to
exchange CDNI logs between interconnected CDNs including SNMP Traps, exchange CDNI logs between interconnected CDNs including SNMP Traps,
syslog, ftp, HTTP POST, etc. although it is likely that some of the syslog, ftp, HTTP POST, etc. although it is likely that some of the
candidate protocols may not be well suited to meet all the candidate protocols may not be well suited to meet all the
requirements of CDNI. For example SNMP traps pose scalability requirements of CDNI. For example SNMP traps pose scalability
concerns and SNMP does not support guaranteed delivery of Traps and concerns and SNMP does not support guaranteed delivery of Traps and
therefore could result in log records being lost and the consequent therefore could result in log records being lost and the consequent
CDRs and billing records for that content delivery not being produced CDRs and billing records for that content delivery not being produced
as well as that content delivery being invisible to any analytics as well as that content delivery being invisible to any analytics
skipping to change at page 27, line 22 skipping to change at page 27, line 16
Although it is not necessary to define a new protocol for exchanging Although it is not necessary to define a new protocol for exchanging
logs across the CDNI Logging interface, the CDNI working group would logs across the CDNI Logging interface, the CDNI working group would
still need to specify: still need to specify:
o The recommended protocol to use. o The recommended protocol to use.
o A default set of log fields and their syntax & semantics. Today o A default set of log fields and their syntax & semantics. Today
there is no standard set of common log fields across different there is no standard set of common log fields across different
content delivery protocols and in some cases there is not even a content delivery protocols and in some cases there is not even a
standard set of log field names and values for different standard set of log field names and values for different
implementations of the same delivery protocol. implementations of the same delivery protocol.
o A default set of events that trigger logs to be generated. o A default set of conditions that trigger log records to be
generated.
A.4. CDNI Control Interface A.4. CDNI Control Interface
The CDNI Control interface allows the Control System in The CDNI Control interface allows the Control System in
interconnected CDNs to communicate. The exact inter-CDN control interconnected CDNs to communicate. The exact inter-CDN control
functionality required to be supported by the CDNI Control interface functionality required to be supported by the CDNI Control interface
is less well defined than the other three CDNI interfaces at this is less well defined than the other three CDNI interfaces at this
time. time.
However, as discussed in Section 3, the CDNI Control interface may be However, as discussed in Section 3, the CDNI Control interface may be
 End of changes. 12 change blocks. 
27 lines changed or deleted 22 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/