Re: [alto] WGLC for draft-ietf-alto-incr-update-sse-11
"Y. Richard Yang" <yry@cs.yale.edu> Mon, 02 July 2018 14:46 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 81D1F1311A1 for <alto@ietfa.amsl.com>; Mon, 2 Jul 2018 07:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 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, RCVD_IN_MSPIKE_H2=-0.001, 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 ESRbpXmQ1fu9 for <alto@ietfa.amsl.com>; Mon, 2 Jul 2018 07:46:21 -0700 (PDT)
Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (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 48A8E1311B1 for <alto@ietf.org>; Mon, 2 Jul 2018 07:46:21 -0700 (PDT)
Received: by mail-lj1-f176.google.com with SMTP id 1-v6so3404673ljv.9 for <alto@ietf.org>; Mon, 02 Jul 2018 07:46:21 -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=j5TQnwEyrVyi5qEKrANn7GMLNJS/Cipu96pXoIi/Y3A=; b=e/dKouMlD07TmT6GJk/l8v4/DBO0WzcnPey+DbFfZKF5T0bhdY6K5b4/4RHRAz56sy zusFTWhaVrizwbtv28GKr5REE7sOz+x5KE2iBmnlNra2fqBz5FLAMWyzl2DUSRwnnDf5 ZQihPRBzZxPImu6Wwpdgfe3jJVnEq3rSnb6ZGiF6FHcpRtvaBLCJrXHdc+D+o+f/639Y QYG4gWQc8EcBokRZHJ6ys/YIhI6yisifqR0v0dNBcXfmbyvj82r58WyfH7qrfU2coxAY ur/xZa/N/Xkbh9NiWmFdowRkftfiXu16szGZkb9CjEqzL86YcChYUGlHdkh3QoyrIXHU FWHA==
X-Gm-Message-State: APt69E05uJYFnC3eq+jWEuVolpYL5Q+rdpTG2W3ORFXAS1xY6DWCXcEI Al8NBTyS4vCL6TNldYpJpnNeoRyYTUHNeQG3bhQ=
X-Google-Smtp-Source: ADUXVKKuiSmRQeHNlBQcECLDQdWR9CA6sdWu+Iw1uXGChMs67VGB9JbnImPrwmNxBgdAyhhZshHnRPTNeRXm545vZD4=
X-Received: by 2002:a2e:7c02:: with SMTP id x2-v6mr16742123ljc.71.1530542779483; Mon, 02 Jul 2018 07:46:19 -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>
In-Reply-To: <800a1963-94eb-b39a-d0d4-d8ef695bdf88@nokia.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 02 Jul 2018 10:46:07 -0400
Message-ID: <CANUuoLoYmS_DYvoCEmZOV40k6vFe9ebGhbNGeeQ3A_zeSi-sKA@mail.gmail.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000af4beb0570054256"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/H3fr2ANSKi9N7sR1dIqFEzFMSS8>
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 14:46:33 -0000
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> 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>> 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> > > Network Data Science, Nokia Networks > > Calendar: http://goo.gl/x3Ogq > > > > _______________________________________________ > > 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 > 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/ | =====================================
- [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