Dear Sabine: idnits is reporting one error and a bunch of warnings; see
https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-alto-cost-calendar-14.txt

Would it be possible to fix this on Fri?  If so, please do.  I am working
on updating the shepherd writeup.

Thanks,

- vijay

On Thu, Oct 31, 2019 at 12:51 PM Randriamasy, Sabine (Nokia -
FR/Paris-Saclay) <sabine.randriam...@nokia-bell-labs.com> wrote:

> Dear ALTO WG and Vijay,
>
> The present revision addresses Vijay's review on which we have just
> exchanged and agreed.
> Best regards,
> Sabine
>
>
> -----Original Message-----
> From: alto <alto-boun...@ietf.org> On Behalf Of internet-dra...@ietf.org
> Sent: Thursday, October 31, 2019 6:48 PM
> To: i-d-annou...@ietf.org
> Cc: alto@ietf.org
> Subject: [alto] I-D Action: draft-ietf-alto-cost-calendar-14.txt
>
>
> 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 WG
> of the IETF.
>
>         Title           : ALTO Cost Calendar
>         Authors         : Sabine Randriamasy
>                           Richard Yang
>                           Qin Wu
>                           Lingli Deng
>                           Nico Schwan
>         Filename        : draft-ietf-alto-cost-calendar-14.txt
>         Pages           : 31
>         Date            : 2019-10-31
>
> Abstract:
>    This document is an extension to the base Application-Layer Traffic
>    Optimization (ALTO) protocol.  It extends the ALTO cost information
>    service so that applications decide not only 'where' to connect, but
>    also 'when'.  This is useful for applications that need to perform
>    bulk data transfer and would like to schedule these transfers during
>    an off-peak hour, for example.  This extension introduces ALTO Cost
>    Calendar, with which an ALTO Server exposes ALTO cost values in JSON
>    arrays where each value corresponds to a given time interval.  The
>    time intervals as well as other Calendar attributes, are specified in
>    the Information Resources Directory and ALTO Server responses.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-alto-cost-calendar/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-alto-cost-calendar-14
> https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-calendar-14
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-calendar-14
>
>
> 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
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Reply via email to