Dear all,

We have fixed the nits. If anyone sees any issues, please do let us know.

Thanks!

Richard


On Mon, Dec 9, 2013 at 2:30 AM, Enrico Marocco <
[email protected]> wrote:

> Thanks Richard,
>
> I understand the document is substantially ready to be sent to the IESG.
>
> While preparing the shepherd writeup, I've noticed the latest version of
> the draft does not pass the I-D-nits tool check:
>
> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-alto-protocol-22.txt
>
> The errors and warnings raised seem trivial; can we ask you a last
> effort to fix them, so that the document leaves the WG in a clear state?
>
> Enrico
>
> On 12/4/13 9:52 PM, Y. Richard Yang wrote:
> > Hi all,
> >
> > We made small edits to fix two typos and add clarification. The diff can
> > be found at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-22
> >
> > Wendy has checked the changes and is fine with the changes.
> >
> > Thanks!
> >
> > Richard
> >
> > ---------- Forwarded message ----------
> > From: ** <[email protected] <mailto:[email protected]>>
> > Date: Wed, Dec 4, 2013 at 3:50 PM
> > Subject: [alto] I-D Action: draft-ietf-alto-protocol-22.txt
> > To: [email protected] <mailto:[email protected]>
> > Cc: [email protected] <mailto:[email protected]>
> >
> >
> >
> > 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-22.txt
> >         Pages           : 87
> >         Date            : 2013-12-04
> >
> > 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-22
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-22
> >
> >
> > 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
> > <http://tools.ietf.org>.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > alto mailing list
> > [email protected] <mailto:[email protected]>
> > https://www.ietf.org/mailman/listinfo/alto
> >
> >
> >
> > --
> > --
> >  =====================================
> > | Y. Richard Yang <[email protected] <mailto:[email protected]>>   |
> > | Professor of Computer Science       |
> > | http://www.cs.yale.edu/~yry/        |
> >  =====================================
> >
> >
> > _______________________________________________
> > alto mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/alto
> >
>
>
>
> _______________________________________________
> 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

Reply via email to