Hi, We made some changes per suggestion from Enrico, our shepherd. The changes are in the IANA section, where (1) we changed from Expert Review to IETF Review; and (2) We add some more details on IANA for Error Codes.
Cheers, Richard On Wed, Dec 11, 2013 at 12:39 PM, <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Application-Layer Traffic Optimization > Working Group of the IETF. > > Title : ALTO Protocol > Author(s) : Richard Alimi > Reinaldo Penno > Y. Richard Yang > Filename : draft-ietf-alto-protocol-24.txt > Pages : 88 > Date : 2013-12-11 > > Abstract: > Applications using the Internet already have access to some topology > information of Internet Service Provider (ISP) networks. For > example, views to Internet routing tables at looking glass servers > are available and can be practically downloaded to many network > application clients. What is missing is knowledge of the underlying > network topologies from the point of view of ISPs. In other words, > what an ISP prefers in terms of traffic optimization -- and a way to > distribute it. > > The Application-Layer Traffic Optimization (ALTO) Service provides > network information (e.g., basic network location structure and > preferences of network paths) with the goal of modifying network > resource consumption patterns while maintaining or improving > application performance. The basic information of ALTO is based on > abstract maps of a network. These maps provide a simplified view, > yet enough information about a network for applications to > effectively utilize them. Additional services are built on top of > the maps. > > This document describes a protocol implementing the ALTO Service. > Although the ALTO Service would primarily be provided by ISPs, other > entities such as content service providers could also operate an ALTO > Service. Applications that could use this service are those that > have a choice to which end points to connect. Examples of such > applications are peer-to-peer (P2P) and content delivery networks. > > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-alto-protocol > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-alto-protocol-24 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-24 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > -- -- ===================================== | Y. Richard Yang <[email protected]> | | Professor of Computer Science | | http://www.cs.yale.edu/~yry/ | =====================================
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
