draft-ietf-cdni-requirements-10.txt   draft-ietf-cdni-requirements-11.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: March 14, 2014 Comcast Expires: April 24, 2014 Comcast
Sept 10, 2013 Oct 21, 2013
Content Distribution Network Interconnection (CDNI) Requirements Content Distribution Network Interconnection (CDNI) Requirements
draft-ietf-cdni-requirements-10 draft-ietf-cdni-requirements-11
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 Provider (CSP) to end users, the contents from the Content Service Provider (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 March 14, 2014. This Internet-Draft will expire on April 24, 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 21, line 32 skipping to change at page 21, line 32
against Denial of Service attacks. This includes protection against Denial of Service attacks. This includes protection
against spoofed delivery requests sent by user agents directly against spoofed delivery requests sent by user agents directly
to a Downstream CDN attempting to appear as if they had been to a Downstream CDN attempting to appear as if they had been
redirected by a given Upstream CDN when they have not. redirected by a given Upstream CDN when they have not.
SEC-3 [MED] The CDNI solution should be able to ensure that for any SEC-3 [MED] The CDNI solution should be able to ensure that for any
given request redirected to a Downstream CDN, the chain of CDN given request redirected to a Downstream CDN, the chain of CDN
Delegation (leading to that request being served by that CDN) Delegation (leading to that request being served by that CDN)
can be established with non-repudiation. can be established with non-repudiation.
SEC-4 [MED] The CDNI solution should be able to ensure that the SEC-4 [MED] The CDNI solution should be able to ensure non-
Downstream CDN cannot spoof a transaction log attempting to repudiation by the Downstream CDN of transaction logs
appear as if it corresponds to a request redirected by a given generated by the Downstream CDN and communicated to an
Upstream CDN when that request has not been redirected by this Upstream CDN. This would ensure that the Downstream CDN
Upstream CDN. This ensures non-repudiation by the Upstream cannot repudiate transmitted Log records, therefore
CDN of transaction logs generated by the Downstream CDN for discouraging the Downstream CDN from spoofing a transaction
deliveries performed by the Downstream CDN on behalf of the log (attempting to appear as if it corresponds to a request
Upstream CDN. redirected by the Upstream CDN when that request has not been
redirected by this Upstream CDN).
SEC-5 [LOW] The CDNI solution may provide a mechanism allowing an SEC-5 [LOW] The CDNI solution may provide a mechanism allowing an
Upstream CDN that has credentials to acquire content from the Upstream CDN that has credentials to acquire content from the
CSP origin server (or another CDN), to allow establishment of CSP origin server (or another CDN), to allow establishment of
credentials authorizing the Downstream CDN to acquire the credentials authorizing the Downstream CDN to acquire the
content from the CSP origin server (or the other CDN) (e.g. content from the CSP origin server (or the other CDN) (e.g.
In case the content cannot be acquired from the Upstream CDN). In case the content cannot be acquired from the Upstream CDN).
10. IANA Considerations 10. IANA Considerations
skipping to change at page 22, line 46 skipping to change at page 22, line 46
gwatson@velocix.com gwatson@velocix.com
13. Acknowledgements 13. Acknowledgements
This document leverages the earlier work of the IETF CDI working This document leverages the earlier work of the IETF CDI working
group in particular as documented in [I-D.cain-request-routing-req], group in particular as documented in [I-D.cain-request-routing-req],
[I-D.amini-cdi-distribution-reqs] and [I-D.gilletti-cdnp-aaa-reqs]. [I-D.amini-cdi-distribution-reqs] and [I-D.gilletti-cdnp-aaa-reqs].
The authors would like to thank Gilles Bertrand, Christophe Caillet, The authors would like to thank Gilles Bertrand, Christophe Caillet,
Bruce Davie, Phil Eardly, Ben Niven-Jenkins, Agustin Schapira, Emile Bruce Davie, Phil Eardly, Ben Niven-Jenkins, Agustin Schapira, Emile
Stephan, Eric Burger, Susan He, Kevin Ma, and Daryl Malas for their Stephan, Eric Burger, Susan He, Kevin Ma, Daryl Malas, and Iuniana
input. Serge Manning along with Robert Streijl, Vishwa Prasad, Percy Oprescu for their input. Serge Manning along with Robert Streijl,
Tarapore, Mike Geller, and Ramki Krishnan contributed to this Vishwa Prasad, Percy Tarapore, Mike Geller, and Ramki Krishnan
document by addressing the requirements of the ATIS Cloud Services contributed to this document by addressing the requirements of the
Forum. 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.
14. References 14. References
14.1. Normative References 14.1. Normative References
[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. 
17 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/