Re: [alto] WGLC for draft-ietf-alto-incr-update-sse-11

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 02 July 2018 22:13 UTC

Return-Path: <yang.r.yang@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 5E21C1313C5 for <alto@ietfa.amsl.com>; Mon, 2 Jul 2018 15:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level:
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 j-DatxAkV8vj for <alto@ietfa.amsl.com>; Mon, 2 Jul 2018 15:13:12 -0700 (PDT)
Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (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 AB1391313DE for <alto@ietf.org>; Mon, 2 Jul 2018 15:13:11 -0700 (PDT)
Received: by mail-lf0-f45.google.com with SMTP id u202-v6so13194741lff.9 for <alto@ietf.org>; Mon, 02 Jul 2018 15:13:11 -0700 (PDT)
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=XwI+LMlkrBjPmOC+kIoUtdiujygqC8HGnFvivVtpXVc=; b=BhQ19LTvDuX/E5IFW6NkCF6y+dyHMMzlOnYeyD/iJrLL8izBjJt6QhkWV5ZbBuuXR0 1dYW1HRUyDvR1WVjBnZv1mLYepjzR8BXnpgkhED4cktvy/EGkVfyo+fHgQtY63NF1DQ7 9mKRCkpCxtIls1Zr+62JaRNn1HZouw78Xx5htEW9mdHk8qKHcqKJgsJON353ZS5DAMMn bCTgoHRBpVNFWCnEkkEQaAuCeyo2DN1krbg653MTz93Q3mRq9dgW+OKWyjOtKhK97JiF VOc4DDzAlsfDgE3EmvvCDR4G0TPVOg93nX3V7dYqD0IDvQywz9n+3GfRCrJCxJMpgitu 4GJw==
X-Gm-Message-State: APt69E2a6RTFYvwa8kuOjqkZCOfhkOojQoCoFP4nbag4dtCEtTHX0Y5N TLED4mjgZQSpoVwQTlx+E9bhLjbT5ig3nsXyxSs=
X-Google-Smtp-Source: AAOMgpfOGHh+MvZd6iAuytpWF+pGh5DsJCwWBwp+7N5EAQ8lf3UccgWwOmaNqy6PcgC1FSSBYXV18Zu3pGoQRERfWYQ=
X-Received: by 2002:a19:5d54:: with SMTP id p20-v6mr17154054lfj.143.1530569589841; Mon, 02 Jul 2018 15:13:09 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <8dda1824-148c-4afb-859e-1685f8f59226@nokia.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 2 Jul 2018 18:12:58 -0400
Message-ID: <CANUuoLq7nN5gtQSiU1R50+EtFv+q90LbOjr=7SSMgki1PRAqmA@mail.gmail.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b4e5fe05700b80e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/OBsA-UkSpPpS5fPwEIpMcH6EYC8>
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: Mon, 02 Jul 2018 22:13:18 -0000

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/
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>
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>> 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>>>
> >     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
> >     >
> >     >     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>>
> >     >     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>>
> >     >     https://www.ietf.org/mailman/listinfo/alto
> >     >
> >     >
> >
> >     - 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/        |
> >  =====================================
>
> - vijay
> --
> Vijay K. Gurbani / vijay.gurbani@nokia.com
> Network Data Science, Nokia Networks
> Calendar: http://goo.gl/x3Ogq
>


-- 
-- 
 =====================================
| Y. Richard Yang <yry@cs.yale.edu>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================