Re: [alto] I-D Action: draft-ietf-alto-cost-calendar-06.txt

Danny Alex Lachos Perez <dlachosper@gmail.com> Tue, 03 July 2018 21:23 UTC

Return-Path: <dlachosper@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC7EA130E21 for <alto@ietfa.amsl.com>; Tue, 3 Jul 2018 14:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jo-6IsUiSvVq for <alto@ietfa.amsl.com>; Tue, 3 Jul 2018 14:23:08 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2533E130E0F for <alto@ietf.org>; Tue, 3 Jul 2018 14:23:08 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id q7-v6so490580pff.2 for <alto@ietf.org>; Tue, 03 Jul 2018 14:23:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tuC8g9MEVdb9MKgs5EJRErhWHp9ldVSPr/obRcNkfPo=; b=ZgLTTawCm11ckZKz8nMPOm6FcVP7gjhnt8X+zi+25gfvYrvsbkC06INegll4LUVHuM rJEJye6yzBAoznJqvatC7aSWAeWILbTnOI0RfkSQOsKlUJXxVHO+0yQutZDwOslL0BCr IuBG0bnddF5UpN+uVEstRX+XK4v5HYumVO81sOQyCxsFoJdfkO+i8wmSPWRfF96e/itf fYcysl73GYLPjnkgkkPL8dSvxEDxFdcwWwsLruunEuxpcOEjAbFe2Ey22TuvJPKWK0Gi 1Pk29GM10yAZAc8cs8/7CqH3ihfekBFeqfzUMFbu4T/XikdU9I5iF5KG11f3EjT2Y2Le jLQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tuC8g9MEVdb9MKgs5EJRErhWHp9ldVSPr/obRcNkfPo=; b=HYr0AUF4Z8ZnbGPs18FnVD3qafqkEA9OBdgJlB5wETTSEeD/oTOdCvGZIFaROEhZns 2LijvQmznb2RXGgwCLp+Gr7CkL7luEU3heXwTCa29uRWBvhmo6aJfg+V2F34bfVa0yO2 /Pek5VtEkXos+aiG9TxAoOudw20J97tY+aMFyVREUmCzUBakAxZI4IjuFHF7XqzM1ohs fYIVBouSjGT3dtsUIR6LJjkSRNzre19Cz5AkgaI9Yln9CPmzJ5dtpDKDzG2JBJcC40Z9 hzLo9qqG4UoPhRHcR+S5w/235qwh8H/t5qV2Ya5LT1nzppM+TRlAmzNzhAlrC3SdxUb7 l+wA==
X-Gm-Message-State: APt69E00omV3ifm1Da9acE8RmpbtgnOSKwV+P0VB3QXUE5vPvS8TqGKx VOk7lJav+fOgDrtCwM+dj32GwysD3Nc3de5hFe1qJg==
X-Google-Smtp-Source: ADUXVKIGeWRoqwhP1EM3wjoPVhFqbOK7gSCskrdvuA94/Va9M2aHm0oltbmzrKmhZaZmFf/yc0U9FVdAnLFKZgTdK5w=
X-Received: by 2002:a63:2c94:: with SMTP id s142-v6mr26302700pgs.39.1530652987581; Tue, 03 Jul 2018 14:23:07 -0700 (PDT)
MIME-Version: 1.0
References: <153054415221.16179.11095308245366639421@ietfa.amsl.com> <AM4PR07MB3236A46F286ED954257B68C595430@AM4PR07MB3236.eurprd07.prod.outlook.com> <afea2289-9443-c561-dee5-144349169ce1@nokia.com> <CAAbpuyq_BvGr7eZuc-mDBdUjAD7r1moPAvS=3EEG-JO2_ApaUw@mail.gmail.com> <BLUPR02MB12029ACDBA97639F3AA12CA3B5420@BLUPR02MB1202.namprd02.prod.outlook.com> <c2ebbeb6-451c-e310-019c-89be90167a89@nokia.com>
In-Reply-To: <c2ebbeb6-451c-e310-019c-89be90167a89@nokia.com>
From: Danny Alex Lachos Perez <dlachosper@gmail.com>
Date: Tue, 3 Jul 2018 18:22:56 -0300
Message-ID: <CAEDarXLkmGe8CR=YxmWMYCYAz8V=MtOQb76V42xdoyGWqCoFZw@mail.gmail.com>
To: "Vijay K. Gurbani" <vijay.gurbani@nokia.com>
Cc: Dawn Chan <dawn_chen_f@hotmail.com>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000996d6405701eeb85"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/T04X2nXRAUdRhfZmva9lWnYbZIQ>
Subject: Re: [alto] I-D Action: draft-ietf-alto-cost-calendar-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2018 21:23:12 -0000

Hello ALTO WG

Some grammar, spelling, and punctuation issues about this draft are as
follows:

   - Introduction
   - "Statement [RFC5693] and ALTO Requirements [RFC5693].Thus the current"
         - Consider adding a space after "[RFC5693]."
      - "locations, e.g. to reduce their costs.  ALTO intentionally avoids"
      - "e.g. due to diurnal patterns of traffic demand or planned events
      such"
         - Consider adding a comma after "e.g."
      - "In this draft an "ALTO Cost Calendar" is specified by information"
         - Consider adding a comma after "In this draft"
      - Section 2
      - "information resources capabilities, where as attributes with time"
         - where as -> whereas
      - "duration of the Calendar: e.g. the number of intervals provided"
         - Consider adding a comma after "e.g."
      - "IRD, the ALTO requests and responses for Cost calendars."
         - Consider adding a comma after "ALTO requests"
      - "historic or be a prediction for upcoming time periods."
         - historic -> historical
      - Section 3
      - "example an ALTO Server may provide a calendar for ALTO values"
         - Consider adding a comma after "example"
      - Section 4
      - "exchange: by providing it, an ALTO Server will avoid unecessary"
         - unecessary -> unnecessary
      - "When the Client gets the Calendar for "routingcost", it sees that
      the"
         - sees -> seems
      - "Monday, Tuesday, Wednesday and Thursday.  The ALTO Client thus may"
         - Consider adding a comma after "Wednesday"
         - extra space after "Thursday."
      - Section 6
   - "future in a calendar, this extension may improve availability of"
         - Consider adding the article "the" after "improve"

Ss

Danny Lachos


On Tue, Jul 3, 2018 at 12:58 PM Vijay K. Gurbani <vijay.gurbani@nokia.com>
wrote:

> Dawn: Excellent.  Thanks a lot.  Jensen has also volunteered to look at
> S6 and S7.
>
> As soon as you post your reviews of these sections by Wed, we'll move
> the work ahead, subject to what you find in your review, of course.
>
> Cheers,
>
> On 07/03/2018 10:33 AM, Dawn Chan wrote:
> > Hi Vijay,
> >
> > I can do a review of S6 and S7 too.
> >
> > Dawn
> >
> >
> > ________________________________________
> > From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
> > Sent: Tuesday, July 3, 2018 10:55:18 AM
> > To: Vijay K. Gurbani
> > Cc: 92yichenqian@tongji.edu.cn; Chan Dawn; Randriamasy, Sabine (Nokia -
> FR/Paris-Saclay); alto@ietf.org; geng.li@yale.edu
> > Subject: Re: [alto] I-D Action: draft-ietf-alto-cost-calendar-06.txt
> >
> > Hi Vijay,
> >
> > I will give a review on S6 and S7 by Wednesday.
> >
> > Best,
> > Jensen
> >
> > On Tue, Jul 3, 2018, 6:26 AM Vijay K. Gurbani <vijay.gurbani@nokia.com
> <mailto:vijay.gurbani@nokia.com>> 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:alto-bounces@ietf.org<mailto:alto-bounces@ietf.org>]
> On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> >> Sent: Monday, July 02, 2018 5:09 PM
> >> To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> >> Cc: alto@ietf.org<mailto:alto@ietf.org>
> >> 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<http://tools.ietf.org>.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> alto mailing list
> >> alto@ietf.org<mailto:alto@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/alto
> >>
> >> _______________________________________________
> >> alto mailing list
> >> alto@ietf.org<mailto:alto@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/alto
> >>
> >
> > - vijay
> > --
> > Vijay K. Gurbani / vijay.gurbani@nokia.com<mailtolto:
> vijay.gurbani@nokia.com>
> > Network Data Science, Nokia Networks
> > Calendar: http://goo.gl/x3Ogq
> >
>
> - vijay
> --
> Vijay K. Gurbani / vijay.gurbani@nokia.com
> Network Data Science, Nokia Networks
> Calendar: http://goo.gl/x3Ogq
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>