Dear Vijay, WG,

We have fixed the nits:
https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-ietf-alto-cost-calendar-07.txt

If there are still issues, we will be happy to fix as soon as we can.

Thanks!
Richard


On Mon, Jul 2, 2018 at 6:37 PM Y. Richard Yang <[email protected]> wrote:

> Hi Vijay,
>
> I am taking a pass to fix the nites. Hope that we can make the 8 pm ET cut
> off...
>
> Richard
>
> On Mon, Jul 2, 2018 at 6:26 PM Vijay K. Gurbani <[email protected]>
> wrote:
>
>> Sabine: Thank you for getting this out.  I was hoping that all nits
>> identified by IDNits tool will be taken care in this revision.
>> Unfortunately, IDNits reports three warnings for -06.  These need to be
>> eventually fixed, perhaps as part of Auth-48, etc.
>>
>> But before I can send the draft to IESG, I need key members of the WG
>> who have reviewed previous versions of this draft to review the newly
>> added Security Considerations section.  You only need to review this
>> section, as previous versions of the draft were reviewed in their
>> entirety.  The new addition here is S6 (Security Considerations) and S7
>> (Operations Considerations).
>>
>> Can I please request a subset of the following people to review S6 and S7:
>>
>>    Yichen Qian, Li Geng, Dawn Chen, and Jensen Zhang
>>
>> I will like at least two people from the above set to read S6 and S7 and
>> let the WG know whether the draft is ready to be moved out of the WG.
>>
>> Please do so soon, preferably by Wed midnight (US Eastern).  The
>> sections are short, but your reading and feedback to the WG will be
>> invaluable.
>>
>> Thank you,
>>
>> On 07/02/2018 10:23 AM, Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
>> wrote:
>> > Hello,
>> >
>> > In this version 06:
>> >
>> > - Section 6 Security Considerations has been revised for a more
>> complete threat model,
>> > - A new Section 7 "Operations Considerations" has been added and now
>> contains the initial text on Security Considerations of version
>> draft-ietf-alto-cost-calendar-05.
>> >
>> > Thanks,
>> > Sabine
>> >
>> > -----Original Message-----
>> > From: alto [mailto:[email protected]] On Behalf Of
>> [email protected]
>> > Sent: Monday, July 02, 2018 5:09 PM
>> > To: [email protected]
>> > Cc: [email protected]
>> > Subject: [alto] I-D Action: draft-ietf-alto-cost-calendar-06.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-06.txt
>> >       Pages           : 27
>> >       Date            : 2018-07-02
>> >
>> > Abstract:
>> >    The goal of Application-Layer Traffic Optimization (ALTO) is to
>> >    bridge the gap between network and applications by provisioning
>> >    network related information in order to allow applications to make
>> >    network informed decisions.  The present draft extends the ALTO cost
>> >    information so as to broaden the decision possibilities of
>> >    applications to not only decide 'where' to connect to, but also
>> >    'when'.  This is useful to applications that need to schedule their
>> >    data transfers and connections and have a degree of freedom to do so.
>> >    ALTO guidance to schedule application traffic can also efficiently
>> >    help for load balancing and resources efficiency.  Besides, the ALTO
>> >    Cost Calendar allows to schedule the ALTO requests themselves and
>> >    thus to save a number of ALTO transactions.
>> >
>> >    This draft proposes new capabilities and attributes on filtered cost
>> >    maps and endpoint cost maps enabling an ALTO Server to provide "Cost
>> >    Calendars".  These capabilities are applicable to ALTO metrics with
>> >    time-varying values.  With ALTO Cost Calendars, 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 IRD 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-06
>> > https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-calendar-06
>> >
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-calendar-06
>> >
>> >
>> > 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
>> >
>>
>> - vijay
>> --
>> Vijay K. Gurbani / [email protected]
>> Network Data Science, Nokia Networks
>> Calendar: http://goo.gl/x3Ogq
>>
>> _______________________________________________
>> 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/        |
>  =====================================
>


-- 
-- 
 =====================================
| 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