draft-ietf-cdni-use-cases-05.txt		draft-ietf-cdni-use-cases-06.txt
	Internet Engineering Task Force G. Bertrand, Ed.		Internet Engineering Task Force G. Bertrand, Ed.
	Internet-Draft E. Stephan		Internet-Draft E. Stephan
	Intended status: Informational France Telecom - Orange		Intended status: Informational France Telecom - Orange
	Expires: November 24, 2012 T. Burbridge		Expires: November 25, 2012 T. Burbridge
	P. Eardley		P. Eardley
	BT		BT
	K. Ma		K. Ma
	Azuki Systems, Inc.		Azuki Systems, Inc.
	G. Watson		G. Watson
	Alcatel-Lucent (Velocix)		Alcatel-Lucent (Velocix)
	May 23, 2012		May 24, 2012
	Use Cases for Content Delivery Network Interconnection		Use Cases for Content Delivery Network Interconnection
	draft-ietf-cdni-use-cases-05		draft-ietf-cdni-use-cases-06
	Abstract		Abstract
	Content Delivery Networks (CDNs) are commonly used for improving the		Content Delivery Networks (CDNs) are commonly used for improving the
	End User experience of a content delivery service, at a reasonable		End User experience of a content delivery service, at a reasonable
	cost. This document focuses on use cases that correspond to		cost. This document focuses on use cases that correspond to
	identified industry needs and that are expected to be realized once		identified industry needs and that are expected to be realized once
	open interfaces and protocols supporting interconnection of CDNs are		open interfaces and protocols supporting interconnection of CDNs are
	specified and implemented. The document can be used to guide the		specified and implemented. The document can be used to guide the
	definition of the requirements to be supported by CDN Interconnection		definition of the requirements to be supported by CDN Interconnection
	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 November 24, 2012.		This Internet-Draft will expire on November 25, 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 2, line 27		skipping to change at page 2, line 27
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	1.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3		1.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
	1.3. Rationale for Multi-CDN Systems . . . . . . . . . . . . . 4		1.3. Rationale for Multi-CDN Systems . . . . . . . . . . . . . 4
	2. Footprint Extension Use Cases . . . . . . . . . . . . . . . . 6		2. Footprint Extension Use Cases . . . . . . . . . . . . . . . . 6
	2.1. Geographic Extension . . . . . . . . . . . . . . . . . . . 6		2.1. Geographic Extension . . . . . . . . . . . . . . . . . . . 6
	2.2. Inter-Affiliates Interconnection . . . . . . . . . . . . . 6		2.2. Inter-Affiliates Interconnection . . . . . . . . . . . . . 6
	2.3. ISP Handling of Third-Party Content . . . . . . . . . . . 7		2.3. ISP Handling of Third-Party Content . . . . . . . . . . . 7
	2.4. Nomadic Users . . . . . . . . . . . . . . . . . . . . . . 7		2.4. Nomadic Users . . . . . . . . . . . . . . . . . . . . . . 7
	3. Offload Use Cases . . . . . . . . . . . . . . . . . . . . . . 8		3. Offload Use Cases . . . . . . . . . . . . . . . . . . . . . . 8
	3.1. Overload Handling and Dimensioning . . . . . . . . . . . . 9		3.1. Overload Handling and Dimensioning . . . . . . . . . . . . 8
	3.2. Resiliency . . . . . . . . . . . . . . . . . . . . . . . . 9		3.2. Resiliency . . . . . . . . . . . . . . . . . . . . . . . . 9
	3.2.1. Failure of Content Delivery Resources . . . . . . . . 9		3.2.1. Failure of Content Delivery Resources . . . . . . . . 9
	3.2.2. Content Acquisition Resiliency . . . . . . . . . . . . 10		3.2.2. Content Acquisition Resiliency . . . . . . . . . . . . 9
	4. CDN Capability Use Cases . . . . . . . . . . . . . . . . . . . 10		4. CDN Capability Use Cases . . . . . . . . . . . . . . . . . . . 10
	4.1. Device and Network Technology Extension . . . . . . . . . 10		4.1. Device and Network Technology Extension . . . . . . . . . 10
	4.2. Technology and Vendor Interoperability . . . . . . . . . . 11		4.2. Technology and Vendor Interoperability . . . . . . . . . . 11
	4.3. QoE and QoS Improvement . . . . . . . . . . . . . . . . . 11		4.3. QoE and QoS Improvement . . . . . . . . . . . . . . . . . 11
	5. Enforcement of Content Delivery Policy . . . . . . . . . . . . 12		5. Enforcement of Content Delivery Policy . . . . . . . . . . . . 12
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 12		8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12		9. Informative References . . . . . . . . . . . . . . . . . . . . 12
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 12
	9.2. Informative References . . . . . . . . . . . . . . . . . . 13
	Appendix A. Content Service Providers' Delivery Policies . . . . 13		Appendix A. Content Service Providers' Delivery Policies . . . . 13
	A.1. Content Delivery Policy Enforcement . . . . . . . . . . . 13		A.1. Content Delivery Policy Enforcement . . . . . . . . . . . 13
	A.2. Secure Access . . . . . . . . . . . . . . . . . . . . . . 15		A.2. Secure Access . . . . . . . . . . . . . . . . . . . . . . 14
	A.3. Branding . . . . . . . . . . . . . . . . . . . . . . . . . 15		A.3. Branding . . . . . . . . . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
	1. Introduction		1. Introduction
	Content Delivery Networks (CDNs) are commonly used for improving the		Content Delivery Networks (CDNs) are commonly used for improving the
	End User experience of a content delivery service, at a reasonable		End User experience of a content delivery service, at a reasonable
	cost. This document focuses on use cases that correspond to		cost. This document focuses on use cases that correspond to
	identified industry needs and that are expected to be realized once		identified industry needs and that are expected to be realized once
	open interfaces and protocols supporting interconnection of CDNs are		open interfaces and protocols supporting interconnection of CDNs are
	specified and implemented. The document can be used to guide the		specified and implemented. The document can be used to guide the
	skipping to change at page 3, line 33		skipping to change at page 3, line 33
	o CDN Offload Use Cases (Section 3)		o CDN Offload Use Cases (Section 3)
	o CDN Capability Use Cases (Section 4)		o CDN Capability Use Cases (Section 4)
	Then, the document highlights the need for interoperability in order		Then, the document highlights the need for interoperability in order
	to exchange and enforce content delivery policies (Section 5).		to exchange and enforce content delivery policies (Section 5).
	1.1. Terminology		1.1. Terminology
	We adopt the terminology described in		We adopt the terminology described in
	[I-D.ietf-cdni-problem-statement], [I-D.davie-cdni-framework],		[I-D.ietf-cdni-problem-statement], and [I-D.davie-cdni-framework].
	[RFC3466], and [RFC3568].
	We extend this terminology with the following terms.		We extend this terminology with the following terms.
	Access CDN:		Access CDN:
	A CDN that includes Surrogates in the same administrative network as		A CDN that includes Surrogates in the same administrative network as
	the end-user. Such CDN can use accurate information on the End		the end-user. Such CDN can use accurate information on the End
	User's network context to provide valued-added Content Delivery		User's network context to provide valued-added Content Delivery
	Services to Content Service Providers.		Services to Content Service Providers.
	1.2. Abbreviations		1.2. Abbreviations
	o CDN: Content Delivery Network also known as Content Distribution		o CDN: Content Delivery Network also known as Content Distribution
	Network		Network
	o CSP: Content Service Provider		o CSP: Content Service Provider
	o dCDN: downstream CDN
			o dCDN: downstream CDN
	o DNS: Domain Name System		o DNS: Domain Name System
	o DRM: Digital Rights Management		o DRM: Digital Rights Management
	o EU: End User		o EU: End User
	o ISP: Internet Service Provider		o ISP: Internet Service Provider
	o NSP: Network Service Provider		o NSP: Network Service Provider
	skipping to change at page 12, line 40		skipping to change at page 12, line 36
	7. IANA Considerations		7. IANA Considerations
	This memo includes no request to IANA.		This memo includes no request to IANA.
	8. Security Considerations		8. Security Considerations
	This document focuses on the motivational use cases for CDN		This document focuses on the motivational use cases for CDN
	Interconnection, and does not analyze the associated threats. Those		Interconnection, and does not analyze the associated threats. Those
	are discussed in [I-D.ietf-cdni-problem-statement].		are discussed in [I-D.ietf-cdni-problem-statement].
	9. References		9. Informative References
	9.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.
	9.2. Informative References
	[I-D.davie-cdni-framework]		[I-D.davie-cdni-framework]
	Davie, B. and L. Peterson, "Framework for CDN		Davie, B. and L. Peterson, "Framework for CDN
	Interconnection", draft-davie-cdni-framework-01 (work in		Interconnection", draft-davie-cdni-framework-01 (work in
	progress), October 2011.		progress), October 2011.
	[I-D.ietf-cdni-problem-statement]		[I-D.ietf-cdni-problem-statement]
	Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content		Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content
	Distribution Network Interconnection (CDNI) Problem		Distribution Network Interconnection (CDNI) Problem
	Statement", draft-ietf-cdni-problem-statement-06 (work in		Statement", draft-ietf-cdni-problem-statement-06 (work in
	progress), May 2012.		progress), May 2012.
	[I-D.ietf-cdni-requirements]		[I-D.ietf-cdni-requirements]
	Leung, K. and Y. Lee, "Content Distribution Network		Leung, K. and Y. Lee, "Content Distribution Network
	Interconnection (CDNI) Requirements",		Interconnection (CDNI) Requirements",
	draft-ietf-cdni-requirements-02 (work in progress),		draft-ietf-cdni-requirements-02 (work in progress),
	December 2011.		December 2011.
	[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.		[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
	[RFC3466] Day, M., Cain, B., Tomlinson, G., and P. Rzewski, "A Model
	for Content Internetworking (CDI)", RFC 3466,
	February 2003.
	[RFC3568] Barbir, A., Cain, B., Nair, R., and O. Spatscheck, "Known
	Content Network (CN) Request-Routing Mechanisms",
	RFC 3568, July 2003.
	Appendix A. Content Service Providers' Delivery Policies		Appendix A. Content Service Providers' Delivery Policies
	CSPs commonly apply different delivery policies to given sets of		CSPs commonly apply different delivery policies to given sets of
	content assets delivered through CDNs. Interconnected CDNs need to		content assets delivered through CDNs. Interconnected CDNs need to
	support these policies. This annex presents examples of CSPs'		support these policies. This annex presents examples of CSPs'
	delivery policies and their consequences on CDNI operations.		delivery policies and their consequences on CDNI operations.
	A.1. Content Delivery Policy Enforcement		A.1. Content Delivery Policy Enforcement
	The content distribution policies that a CSP attaches to a content		The content distribution policies that a CSP attaches to a content
End of changes. 13 change blocks.
	30 lines changed or deleted		12 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/