draft-ietf-cdni-requirements-08.txt   draft-ietf-cdni-requirements-09.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 28, 2013 Comcast Expires: January 2, 2014 Comcast
June 26, 2013 July 1, 2013
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-08 draft-ietf-cdni-requirements-09
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 28, 2013. This Internet-Draft will expire on January 2, 2014.
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 3, line 29 skipping to change at page 3, line 29
regardless of that end user's location or attachment network. This regardless of that end user's location or attachment network. This
creates a need for interconnecting (previously) standalone CDNs so creates a need for interconnecting (previously) standalone CDNs so
they can interoperate and collectively behave as a single delivery they can interoperate and collectively behave as a single delivery
infrastructure. The Content Distribution Network Interconnection infrastructure. The Content Distribution Network Interconnection
(CDNI) working group has been chartered to develop an interoperable (CDNI) working group has been chartered to develop an interoperable
and scalable solution for such CDN interconnections. and scalable solution for such CDN interconnections.
CDNI Problem Statement [RFC6707] outlines the problem area that the CDNI Problem Statement [RFC6707] outlines the problem area that the
CDNI working group is chartered to address. CDNI Problem Statement CDNI working group is chartered to address. CDNI Problem Statement
[RFC6770] discusses the use cases for CDN Interconnection. Framework [RFC6770] discusses the use cases for CDN Interconnection. Framework
for CDNI [I-D.davie-cdni-framework] discusses the technology for CDNI [I-D.ietf-cdni-framework] discusses the technology framework
framework for the CDNI solution and interfaces. for the CDNI solution and interfaces.
The goal of the present document is to document the requirements for The goal of the present document is to document the requirements for
the CDNI solution and interfaces. In order to meet the timelines the CDNI solution and interfaces. In order to meet the timelines
defined in the working group charter, the present document defined in the working group charter, the present document
categorizes the CDNI requirements as "High Priority", "Medium categorizes the CDNI requirements as "High Priority", "Medium
Priority", and "Low Priority". Priority", and "Low Priority".
1.1. Terminology 1.1. Terminology
This document uses the terminology defined in section 1.1 of This document uses the terminology defined in section 1.1 of
Framework for CDNI [I-D.davie-cdni-framework]. In addition, the key Framework for CDNI [I-D.ietf-cdni-framework]. In addition, the key
words "High Priority", "Medium Priority" and "Low Priority" in this words "High Priority", "Medium Priority" and "Low Priority" in this
document are to be interpreted in the following way: document are to be interpreted in the following way:
o "High Priority" indicates requirements that are to be supported by o "High Priority" indicates requirements that are to be supported by
the CDNI interfaces. A requirement is stated as "High Priority" the CDNI interfaces. A requirement is stated as "High Priority"
when it is established by the working group that it can be met to when it is established by the working group that it can be met to
achieve the goal of a deployable solution in a short timeframe achieve the goal of a deployable solution in a short timeframe
(18-24 months) as needed by the industry. This is tagged as (18-24 months) as needed by the industry. This is tagged as
"[HIGH]". "[HIGH]".
skipping to change at page 4, line 22 skipping to change at page 4, line 22
the CDNI interfaces provided that dedicating WG resources to this the CDNI interfaces provided that dedicating WG resources to this
work does not prevent addressing "High Priority" and "Medium work does not prevent addressing "High Priority" and "Medium
Priority" requirements and that attempting to meet this Priority" requirements and that attempting to meet this
requirement is not an obstacle to achieving the goal of a requirement is not an obstacle to achieving the goal of a
deployable solution in a short timeframe (18-24 months) as needed deployable solution in a short timeframe (18-24 months) as needed
by the industry. This is tagged as "[LOW]". by the industry. This is tagged as "[LOW]".
2. CDNI Model and CDNI Interfaces 2. CDNI Model and CDNI Interfaces
For convenience Figure 1 from Framework for CDNI For convenience Figure 1 from Framework for CDNI
[I-D.davie-cdni-framework] illustrating the CDNI problem area and the [I-D.ietf-cdni-framework] illustrating the CDNI problem area and the
CDNI protocols is replicated below. CDNI protocols is replicated below.
-------- --------
/ \ / \
| CSP | | CSP |
\ / \ /
-------- --------
* *
* *
* /\ * /\
skipping to change at page 23, line 6 skipping to change at page 23, line 6
| LOG-# | LI-# (label changed) | | LOG-# | LI-# (label changed) |
| LOG-4 | Removed | | LOG-4 | Removed |
| LOG-5 to LOG-18 | LI-4 to LI-17 | | LOG-5 to LOG-18 | LI-4 to LI-17 |
+--------------------+-------------------------------+ +--------------------+-------------------------------+
Requirement Reference Mapping Table Requirement Reference Mapping Table
15. References 15. References
15.1. Normative References 15.1. Normative References
[I-D.davie-cdni-framework]
Davie, B. and L. Peterson, "Framework for CDN
Interconnection", draft-davie-cdni-framework-01 (work in
progress), October 2011.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", RFC 6707, September 2012. Statement", RFC 6707, September 2012.
[RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma,
K., and G. Watson, "Use Cases for Content Delivery Network
Interconnection", RFC 6770, November 2012.
15.2. Informative References 15.2. Informative References
[I-D.amini-cdi-distribution-reqs] [I-D.amini-cdi-distribution-reqs]
Amini, L., "Distribution Requirements for Content Amini, L., "Distribution Requirements for Content
Internetworking", draft-amini-cdi-distribution-reqs-02 Internetworking", draft-amini-cdi-distribution-reqs-02
(work in progress), November 2001. (work in progress), November 2001.
[I-D.cain-request-routing-req] [I-D.cain-request-routing-req]
Cain, B., "Request Routing Requirements for Content Cain, B., "Request Routing Requirements for Content
Internetworking", draft-cain-request-routing-req-03 (work Internetworking", draft-cain-request-routing-req-03 (work
in progress), November 2001. in progress), November 2001.
[I-D.gilletti-cdnp-aaa-reqs] [I-D.gilletti-cdnp-aaa-reqs]
"CDI AAA Requirements, "CDI AAA Requirements,
draft-gilletti-cdnp-aaa-reqs-01.txt", June 2001. draft-gilletti-cdnp-aaa-reqs-01.txt", June 2001.
[I-D.ietf-cdni-framework]
Peterson, L. and B. Davie, "Framework for CDN
Interconnection", draft-ietf-cdni-framework-03 (work in
progress), February 2013.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma,
K., and G. Watson, "Use Cases for Content Delivery Network
Interconnection", RFC 6770, November 2012.
Authors' Addresses Authors' Addresses
Kent Leung (editor) Kent Leung (editor)
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
U.S.A. U.S.A.
Phone: +1 408 526 5030 Phone: +1 408 526 5030
Email: kleung@cisco.com Email: kleung@cisco.com
 End of changes. 9 change blocks. 
21 lines changed or deleted 21 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/