Dear all, The editors have made the changes to the error codes, suggested by the excellent work of Sebastian (who should become a co-editor, I feel), and feel confident on the technical content of the document. Hence, we would like to request the working group to review the document soon so that we can finish a short WGLC soon and start extension working items, as we discussed at last IETF.
Thanks a lot! Richard On Wed, Oct 2, 2013 at 9:41 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-20.txt > Pages : 85 > Date : 2013-10-02 > > 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-20 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-20 > > > 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 >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
