< draft-jenkins-alto-cdn-use-cases-01.txt		draft-jenkins-alto-cdn-use-cases-02.txt >
	Network Working Group B. Niven-Jenkins, Ed.		Network Working Group B. Niven-Jenkins, Ed.
	Internet-Draft Velocix (Alcatel-Lucent)		Internet-Draft Velocix (Alcatel-Lucent)
	Intended status: Informational G. Watson		Intended status: Informational G. Watson
	Expires: December 19, 2011 BT		Expires: June 9, 2012 BT
	N. Bitar		N. Bitar
	Verizon		Verizon
	J. Medved		J. Medved
	Juniper Networks		Juniper Networks
	S. Previdi		S. Previdi
	Cisco Systems		Cisco Systems
	June 17, 2011		December 7, 2011
	Use Cases for ALTO within CDNs		Use Cases for ALTO within CDNs
	draft-jenkins-alto-cdn-use-cases-01		draft-jenkins-alto-cdn-use-cases-02
	Abstract		Abstract
	For some time, Content Distribution Networks (CDNs) have been used in		For some time, Content Distribution Networks (CDNs) have been used in
	the delivery of some Internet services (e.g. delivery of websites,		the delivery of some Internet services (e.g. delivery of websites,
	software updates and video delivery) as they provide numerous		software updates and video delivery) as they provide numerous
	benefits including reduced delivery cost for cacheable content,		benefits including reduced delivery cost for cacheable content,
	improved quality of experience for end users and increased robustness		improved quality of experience for end users and increased robustness
	of delivery.		of delivery.
	skipping to change at page 2, line 15 ¶		skipping to change at page 2, line 15 ¶
	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 19, 2011.		This Internet-Draft will expire on June 9, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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 5, line 12 ¶		skipping to change at page 5, line 12 ¶
	directly, active probing of underlying network(s), or obtaining		directly, active probing of underlying network(s), or obtaining
	topology and cost by querying an information service such as the ALTO		topology and cost by querying an information service such as the ALTO
	map & cost services.		map & cost services.
	The rest of this document describes the use cases for a CDN to be		The rest of this document describes the use cases for a CDN to be
	able to obtain network topology and cost information from an ALTO		able to obtain network topology and cost information from an ALTO
	server(s).		server(s).
	1.1. Terminology		1.1. Terminology
	The following terms are taken from		The following terms are taken from [I-D.ietf-cdni-problem-statement]
	[I-D.jenkins-cdni-problem-statement] and repeated here for		and repeated here for completeness.
	completeness.
	Content Distribution Network (CDN) / Content Delivery Network (CDN):		Content Distribution Network (CDN) / Content Delivery Network (CDN):
	Network infrastructure in which the network elements cooperate at		Network infrastructure in which the network elements cooperate at
	layers 4 through layer 7 for more effective delivery of Content to		layers 4 through layer 7 for more effective delivery of Content to
	User Agents. Typically a CDN consists of a Request Routing system, a		User Agents. Typically a CDN consists of a Request Routing system, a
	Distribution System (that includes a set of Surrogates), a Logging		Distribution System (that includes a set of Surrogates), a Logging
	System and a CDN control system.		System and a CDN control system.
	Content Service Provider (CSP): Provides a Content Service to End		Content Service Provider (CSP): Provides a Content Service to End
	Users (which the End Users access via a User Agent). A CSP may own		Users (which the End Users access via a User Agent). A CSP may own
	skipping to change at page 13, line 39 ¶		skipping to change at page 13, line 39 ¶
	Yale University		Yale University
	Email: ryr@yale.edu		Email: ryr@yale.edu
	7. Acknowledgements		7. Acknowledgements
	The authors would like to thank Vijay Gurbani and Volker Hilt for		The authors would like to thank Vijay Gurbani and Volker Hilt for
	their review comments and contributions to the text.		their review comments and contributions to the text.
	8. Normative References		8. Normative References
	[I-D.jenkins-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-jenkins-cdni-problem-statement-02 (work		Statement", draft-ietf-cdni-problem-statement-01 (work in
	in progress), March 2011.		progress), October 2011.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	Authors' Addresses		Authors' Addresses
	Ben Niven-Jenkins (editor)		Ben Niven-Jenkins (editor)
	Velocix (Alcatel-Lucent)		Velocix (Alcatel-Lucent)
	326 Cambridge Science Park		326 Cambridge Science Park
	Milton Road, Cambridge CB4 0WG		Milton Road, Cambridge CB4 0WG
End of changes. 7 change blocks.
	10 lines changed or deleted		9 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/