[alto] Fwd: New Version Notification for draft-jenkins-alto-cdn-use-cases-01.txt

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Fri, 17 June 2011 13:34 UTC

From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Jun 2011 14:34:53 +0100
References: <CA211515.CAD2%ben@velocix.com>
To: alto@ietf.org
Message-Id: <6343CC44-9A6C-4739-BF1A-5DC5C70F58E6@niven-jenkins.co.uk>
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: [alto] Fwd: New Version Notification for draft-jenkins-alto-cdn-use-cases-01.txt
Precedence: list

Colleagues,

We just published a new version of draft-jenkins-alto-cdn-use-cases, which is available here:
http://tools.ietf.org/html/draft-jenkins-alto-cdn-use-cases-01

The draft is the result of working with the authors of draft-penno-alto-cdn to merge the use cases in that draft with the use cases already in draft-jenkins-alto-cdn-use-cases-00.

Some editorial changes have been made and 3 additional use cases are described:
1) Exposing NSP End User Reachability to a CDN
2) Exposing CDN End User Reachability to CSPs
3) CDN acquiring content from multiple upstream sources


Ben 

Begin forwarded message:
> On 17/06/2011 14:05, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
> 
>> A new version of I-D, draft-jenkins-alto-cdn-use-cases-01.txt has been
>> successfully submitted by Ben Niven-Jenkins and posted to the IETF
>> repository.
>> 
>> Filename:	 draft-jenkins-alto-cdn-use-cases
>> Revision:	 01
>> Title:		 Use Cases for ALTO within CDNs
>> Creation date:	 2011-06-17
>> WG ID:		 Individual Submission
>> Number of pages: 14
>> 
>> Abstract:
>>  For some time, Content Distribution Networks (CDNs) have been used in
>>  the delivery of some Internet services (e.g. delivery of websites,
>>  software updates and video delivery) as they provide numerous
>>  benefits including reduced delivery cost for cacheable content,
>>  improved quality of experience for end users and increased robustness
>>  of delivery.
>> 
>>  In order to derive the optimal benefit from a CDN it is preferable to
>>  deliver content from the servers (caches) that are &quot;closest&quot;
>> to the
>>  End User requesting the content, where &quot;closest&quot; may be as
>> simple as
>>  &quot;geographical or network distance&quot; combined with CDN server
>> load
>>  within a location, but may also consider other more complex
>>  combinations of metrics and CDN or Network Service Provider (NSP)
>>  policies.
>> 
>>  There are a number of different ways in which a CDN may obtain the
>>  necessary network topology and/or cost information to allow it to
>>  serve End Users from the most optimal servers/locations, such as
>>  static configuration, passively listening to routing protocols
>>  directly, active probing of underlying network(s), or obtaining
>>  topology and cost by querying an information service such as the ALTO
>>  map &amp; cost services.
>> 
>>  This document describes the use cases for a CDN to be able to obtain
>>  network topology and cost information from an ALTO server(s).
>> 
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>

[alto] Fwd: New Version Notification for draft-je… Ben Niven-Jenkins