Re: [alto] WGLC for draft-ietf-alto-incr-update-sse-11
Kerim Gokarslan <kerim.gokarslan@yale.edu> Tue, 03 July 2018 18:21 UTC
Return-Path: <kerim.gokarslan@yale.edu>
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 60006130F66 for <alto@ietfa.amsl.com>; Tue, 3 Jul 2018 11:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=yale.edu
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 VQ7T5jMbAhkD for <alto@ietfa.amsl.com>; Tue, 3 Jul 2018 11:21:29 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 F3AA4130FED for <alto@ietf.org>; Tue, 3 Jul 2018 11:21:28 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id c12-v6so2304982ljj.1 for <alto@ietf.org>; Tue, 03 Jul 2018 11:21:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=auF6/Naat0udRABVsTuneGz5dBhixZUOYWIQ6bUcGO0=; b=2OjOQe9gSA0Tg0I0Qzt9mTMVQF7ksszlx4uk9t+9P0eE3dwcVPJtOhU3fpXZQMSwWF lJURCe+3M1Jd+Yvkz0mqow5KgLFoVuEc/mlUAO9pIQRywD9tsn7o8gYwXwVFChgAcCs4 APpiQ3cIXE0A0l4vKJ9j6ZLKXgqKWYm9M6N9s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=auF6/Naat0udRABVsTuneGz5dBhixZUOYWIQ6bUcGO0=; b=f01rW0G8GHRmpJIt1yZ4O5MhozmwK72NvdnuHVq/7X6wzlKeZSUYtJkitXwQGxi8Pt n88uLeCEfgPOJ3dSC8dgteZ6rkFVqL0aUliGRuLgcQhwcZCMtYYOxFWXKQGw/fiZWD10 1gn62/fnN3q3WoPRTCTdrQEOxIwJNJ90gqVkIrPxSWbmNPhC0H0QqViZORmRtXDH5eX4 LH5sc8nXHfi2zwk0+WBBFiI5uRwXqD1siFXqaBKkyaWb4+DU0LSr/0y8an2eOHJpFLjn DOULstQWitY5jTJbkHy47j5SDCsnTbTfZxMuuZXXDYQ7tgrh+zSLXToJnEBWgrUbRzXR giiQ==
X-Gm-Message-State: APt69E0ILB4tvol0XCSmj/VTp6l+ckOvJPe/jVQjgTThugb4aIK+2IFn me++lBDrzmWArRumyCnJdGXPfPueeOU7xIl2D7KsAg==
X-Google-Smtp-Source: AAOMgpfjqHxGkRJnJc1Jl2kZlgt13TmTzHHpQgIJGv5X7t4a4qXTyEUUR+SJ2LsFH6sRjHuSI1MgqqI/LssH5oeoXJY=
X-Received: by 2002:a2e:3313:: with SMTP id d19-v6mr2473836ljc.25.1530642087067; Tue, 03 Jul 2018 11:21:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:cd4d:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 11:21:26 -0700 (PDT)
In-Reply-To: <e5ba219e-f296-3c28-f688-a6332bb312ff@nokia.com>
References: <66e930c9-8cb8-4ef7-d3fd-721c1c85c350@nokia.com> <CANUuoLqzXzBT_NOR58Gr=6UVcGAa6B264rEPrRQ4bKjBFL=Dsg@mail.gmail.com> <800a1963-94eb-b39a-d0d4-d8ef695bdf88@nokia.com> <CANUuoLoYmS_DYvoCEmZOV40k6vFe9ebGhbNGeeQ3A_zeSi-sKA@mail.gmail.com> <8dda1824-148c-4afb-859e-1685f8f59226@nokia.com> <CANUuoLq7nN5gtQSiU1R50+EtFv+q90LbOjr=7SSMgki1PRAqmA@mail.gmail.com> <CAD3kL9+5owChW9ZpZFb5V-WG9k81atBeMMneBU-RtnMJQO09oQ@mail.gmail.com> <e5ba219e-f296-3c28-f688-a6332bb312ff@nokia.com>
From: Kerim Gokarslan <kerim.gokarslan@yale.edu>
Date: Tue, 03 Jul 2018 11:21:26 -0700
Message-ID: <CAD3kL9+-Bsn5OkycHDUskLv1fTAW-2j55chWvU3D7=D1u_RWBg@mail.gmail.com>
To: "Vijay K. Gurbani" <vijay.gurbani@nokia.com>
Cc: "Y. Richard Yang" <yry@cs.yale.edu>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e0ea9005701c6167"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/IOhfdUxPt9yXVNedy9gbJgGB7GQ>
Subject: Re: [alto] WGLC for draft-ietf-alto-incr-update-sse-11
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 18:21:40 -0000
Dear Vijay and WG, I finished reviewing the draft-ietf-alto-incr-update-ssef document (version 12). I think the language of the document and the design is clean and complete. I didn't see any major technical issue (or design errors) but I marked some small issues like spelling and punctuation errors, which can be seen as 'nits'. Page 4, Paragraph 3, Line 3: provides -> provide (noun is plural) Page 4, Paragraph 4, Line 6: satsify -> satisfy (spelling) Page 6, Paragraph 2, Line 7: sends -> send Page 6, Paragraph 2, Line 1: Update Stream Control (spelling) Page 12, Section 4.3.1, Line 1: the difference (missing the) Page 15, Paragraph 3, Line 6: An data -> a data Page 15, Paragraph 4, Line 1: A update -> an update Page 15, Paragraph 4, Line 2: life time -> lifetime Page 17, Last Paragraph, Line 3: an URI -> a URI Page 26, Section 9.1 Paragraph 3, Line 1: Also note -> Also, note (missing comma) Page 28, Section 9.2 Paragraph 1, Line 10: Thus server -> Thus, server (missing comma) Page 30, Paragraph 2, Line 2: a ipv4 -> an ipv4 Page 40, Paragraph 2, Line 3: Unfortunately there -> Unfortunately, there (missing comma) Page 42, Paragraph 1, Line 2: First consider -> First, consider (missing comma) Page 42, Section 11.4 Paragraph 1, Line 7: extention -> extension (spelling) Page 42, Section 12.1: I think the first paragraph is a little confusing, maybe the idea can be specified more explicit. Page 44, Paragraph 3, Line 1: Alternatively an -> Alternatively, an (missing comma) Regards, Kerim Gokarslan On Mon, Jul 2, 2018 at 3:43 PM, Vijay K. Gurbani <vijay.gurbani@nokia.com> wrote: > Kerim: Great, thanks a lot for volunteering. > > Please post your review on the WG email list. > > I suspect that you are getting acquainted with IETF processes; in that > vein, here's some quick advice that I hope will help you as you perform > a WGLC. > > A WGLC covers the entire I-D, you can point out anything in the draft > that you feel needs to be improved. Generally speaking, every reviewer > has their own style of performing WGLC reviews, you can see some > examples here [1, 2]. However, all reviews should include issues that > are 'major' (needs attention of author AND WG to moving the work ahead), > minor (may only need the attention of author to clarify things), and > 'nits' (needs attention of authors only). It is okay if one or more of > these categories is empty, however, due diligence must be done to ensure > that there were indeed no issues to raise under that particular category. > > [1] https://www.ietf.org/mail-archive/web/alto/current/msg03581.html > [2] https://www.ietf.org/mail-archive/web/alto/current/msg03513.html > > Cheers, > > On 07/02/2018 05:30 PM, Kerim Gokarslan wrote: > > Hi Vijay, > > > > I talked with Richard and I would like to help with a review. > > > > Regards, > > Kerim Gokarslan > > > > On Mon, Jul 2, 2018 at 3:12 PM, Y. Richard Yang <yry@cs.yale.edu > > <mailto:yry@cs.yale.edu>> wrote: > > > > Dear WG, > > > > The authors have gone ahead to fix the coupling issue between update > > stream and stream control. To allow the community to read what the > > document reads like, we have uploaded the newer version, which can > > be found at: > > https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/ > > <https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/> > > Please see version 12. > > > > It is a much cleaner, modular, complete design. Last-call feedbacks, > > of course, are still highly appreciated and the authors will update > > as soon as possible, to improve on reactiveness. > > > > Thanks a lot! > > Richard > > > > > > On Mon, Jul 2, 2018 at 11:09 AM Vijay K. Gurbani > > <vijay.gurbani@nokia..com <mailto:vijay.gurbani@nokia.com>> wrote: > > > > Richard, one of them must provide a WGLC review for the draft. > > The WG > > must to due diligence through dedicated reviews to ensure that > > the work > > reflects the consensus of the WG. > > > > I will like to see new members to start contributing to the WG, > > as such > > while my preference would be for Danny to review the draft and > > post WGLC > > comments, I will leave it to the WG members to decide who will > > review it. > > > > I was hesitant to ask Sabine and Jensen since, in all fairness, > they > > have done their share of reviews and comments over the years. I > > iterate, it would be great if other members of the WG step up to > > move > > the work ahead. > > > > >From a process point of view, I realize that the cutoff is > > today so I am > > expecting that we will not be in time to submit a version. > However, > > that is fine as long as we have a WGLC on the currently > > submitted draft > > by the time we have our meeting on Monday, Jul-16. > > > > After the meeting, I can do the proto-writeup and move the work > > ahead. > > > > Cheers, > > > > On 07/02/2018 09:46 AM, Y. Richard Yang wrote: > > > Vijay, > > > > > > The ideas that I posted were discussed with Sabine, Jensen, > > and Danny, > > > who are not co-authors of the document. > > > > > > I assume that they are busy today, as 8 pm ET today is IETF > draft > > > deadline. Maybe they can help with our review tomorrow (July > > 3) or the > > > day after tomorrow (July 4), before the close :-) > > > > > > Thanks! > > > Richard > > > > > > > > > > > > On Mon, Jul 2, 2018 at 9:34 AM Vijay K. Gurbani > > <vijay.gurbani@nokia.com <mailto:vijay.gurbani@nokia.com> > > > <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com>>> wrote: > > > > > > Folks: Following up on Richard's email, we need a > > dedicated WGLC review > > > for SSE from the WG. Jan and I will like to invite at > > least one person > > > who is not an author to volunteer to review the draft as > > part of WGLC. > > > > > > Thus far, besides Richard's email, there has not been any > > review or > > > comments on the draft since it was released for WGLC. We > > will need to > > > be more proactive as a WG to move pending work ahead. > > > > > > Please send me and Jan a message on whether you are able > > to perform a > > > review of the draft in short order so we can move it ahead > > > expeditiously. > > > > > > Thank you, > > > > > > On 07/01/2018 10:32 PM, Y. Richard Yang wrote: > > > > Dear WG, > > > > > > > > Thanks a lot for those who already sent comments to the > > authors! As an > > > > important service, this document can benefit from > > in-depth reviews, as > > > > Vijay pointed out. > > > > > > > > The main substantive comment so far is on clarifying the > > coupling > > > > between the Update Stream Service (USS), which will be > > used by the > > > > network to send SSE Update Messages to a client, and the > > Update Stream > > > > Control Service (USCS), which will be used by the client > to > > > control the > > > > server, by sending add/remove of resources messages. In > > the current > > > > design, SSE update messages can provide the final > > outcome of a control > > > > request. The comment was whether this is a generic > design. > > > > > > > > After extensive discussions among the authors, we > > propose to make the > > > > following revisions---these revisions will be simple and > > clean, and if > > > > approved by the WG, they can be updated right away: > > > > > > > > M1. The document clarifies that USS uses a *modular* > > design, in > > > that the > > > > Update Stream Service (USS) is a modular service. Hence, > > it can be > > > > controlled by not only USCS but also other potential > > control channels, > > > > such as a private control protocol. Hence, the messaging > > of USS, in > > > > particular, its Control Update Messages, should be > > (slightly) > > > revised to > > > > reflect this spirit. > > > > > > > > M2. The document clarifies that USS uses a > > self-contained design, to > > > > take advantage that current design can be simply, > elegantly > > > extended to > > > > also report error updates. > > > > > > > > The authors request that the WG approve these edits so > > that the > > > authors > > > > can proceed to submit a revision shortly, in just a > > couple days. > > > > > > > > Of course, the authors will also wait for other > > comments, until > > > the July > > > > 4th closing, to make a single, coherent edit. > > > > > > > > Thank you so much! > > > > Richard > > > > > > > > On Wed, Jun 20, 2018 at 11:21 AM Vijay K. Gurbani > > > > <vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com>> > > > <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com>>>> > > > wrote: > > > > > > > > All: This email announces the WGLC for SSE [1]; the > > WGLC runs > > > from Wed, > > > > Jun 20, 2018 to Wed, Jul 4, 2018. > > > > > > > > We will like the community members to perform an > > in-depth > > > review of the > > > > draft and post their comments, concerns or approval > > to the > > > mailing list > > > > during this period, even if it is one liner > > expressing support for > > > > moving the draft ahead. > > > > > > > > [1] > > https://tools.ietf.org/html/draft-ietf-alto-incr-update-sse-11 > > <https://tools.ietf.org/html/draft-ietf-alto-incr-update-sse-11> > > > > > > > > Thank you, > > > > > > > > - vijay > > > > -- > > > > Vijay K. Gurbani / vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> > > > <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com>> > > > > <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> > > <mailto:vijay..gurbani@nokia.com <mailto:vijay.gurbani@nokia.com > >>> > > > > Network Data Science, Nokia Networks > > > > Calendar: http://goo.gl/x3Ogq > > > > > > > > _______________________________________________ > > > > alto mailing list > > > > alto@ietf.org <mailto:alto@ietf..org> > > <mailto:alto@ietf.org <mailto:alto@ietf.org>> > > <mailto:alto@ietf.org <mailto:alto@ietf.org> > > > <mailto:alto@ietf.org <mailto:alto@ietf.org>>> > > > > https://www.ietf.org/mailman/listinfo/alto > > <https://www.ietf..org/mailman/listinfo/alto> > > > > > > > > > > > > > > - vijay > > > -- > > > Vijay K. Gurbani / vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> > > > <mailto:vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com>> > > > Network Data Science, Nokia Networks > > > Calendar: http://goo.gl/x3Ogq > > > > > > > > > > > > -- > > > -- > > > ===================================== > > > | Y. Richard Yang <yry@cs.yale.edu <mailto:yry@cs.yale.edu> > > <mailto:yry@cs.yale.edu <mailto:yry@cs.yale.edu>>> | > > > | Professor of Computer Science | > > > | http://www.cs.yale.edu/~yry/ | > > > ===================================== > > > > - vijay > > -- > > Vijay K. Gurbani / vijay.gurbani@nokia.com > > <mailto:vijay.gurbani@nokia.com> > > Network Data Science, Nokia Networks > > Calendar: http://goo.gl/x3Ogq > > > > > > > > -- > > -- > > ===================================== > > | Y. Richard Yang <yry@cs.yale.edu <mailto:yry@cs.yale.edu>> | > > | Professor of Computer Science | > > | http://www.cs.yale.edu/~yry/ | > > ===================================== > > > > _______________________________________________ > > alto mailing list > > alto@ietf.org <mailto:alto@ietf.org> > > https://www.ietf.org/mailman/listinfo/alto > > <https://www.ietf.org/mailman/listinfo/alto> > > > > > > - vijay > -- > Vijay K. Gurbani / vijay.gurbani@nokia.com > Network Data Science, Nokia Networks > Calendar: http://goo.gl/x3Ogq >
- [alto] WGLC for draft-ietf-alto-incr-update-sse-11 Vijay K. Gurbani
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Y. Richard Yang
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Vijay K. Gurbani
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Y. Richard Yang
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Y. Richard Yang
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Vijay K. Gurbani
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Vijay K. Gurbani
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Y. Richard Yang
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Vijay K. Gurbani
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Y. Richard Yang
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Kerim Gokarslan
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Dawn Chan
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Isabelle Carson
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Dawn Chan
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Dawn Chan
- Re: [alto] WGLC for draft-ietf-alto-incr-update-s… Kerim Gokarslan