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

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 02 July 2018 03:32 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 71541130E2C for <alto@ietfa.amsl.com>; Sun, 1 Jul 2018 20:32:54 -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 yfsndKhjpWpD for <alto@ietfa.amsl.com>; Sun, 1 Jul 2018 20:32:52 -0700 (PDT)
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (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 72421130E1F for <alto@ietf.org>; Sun, 1 Jul 2018 20:32:52 -0700 (PDT)
Received: by mail-lf0-f52.google.com with SMTP id y200-v6so5250161lfd.7 for <alto@ietf.org>; Sun, 01 Jul 2018 20:32:52 -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; bh=VOyMfeTk8tn4n6ULrkvCSW5sw2f/XZBNYN3EXQVKPSw=; b=T5rkdf8uISIVYMJfOTK2QmOkU8i2Wtw0XOzDYLrzdElM9lNot7XJdtxPU+3LgouBc4 /lW50wO7pAo/ScOCOeseek/rnlixYO9W367FGK6Oro/xNDh0ErQm4H3Vuw8H/b6rJ1T/ 18euqqtk1TGz91cEUK6xgKbst6hNijOH8uAKHUxCE8Ms35N9CBHZtNfQJsZrYtXweDt2 5IQbsj20l0RCWFBhbmkdbvJZJeE1lEGPVoalCGwZxuZR0FH1K5vMgJCCW2JAmKIiMFKz lEMfEbgGjhQHeCG3MpP9O1G/5UEGD/AFpk05izaKHJwyn2gP7+g9UN6dqJ7UCpSC6g9M Vprg==
X-Gm-Message-State: APt69E1zKG+7n7lIUvbXxRoOYfjlQfY0kns/p4ISlVWQff4eyUd5FxRd oYRK/u1HQtL/4LoYzOIyib5MqrfJ/pybxDpcDf4=
X-Google-Smtp-Source: AAOMgpeB00+EwSNkSUZ/ma3VHtnX+5JOSW8sz3dzZeSTZ7xKu9m1I2OidHfB97quIRl5M0Ry9x43IXETKtJ5ofCIF9Q=
X-Received: by 2002:a19:e955:: with SMTP id g82-v6mr14656451lfh.44.1530502370495; Sun, 01 Jul 2018 20:32:50 -0700 (PDT)
MIME-Version: 1.0
References: <66e930c9-8cb8-4ef7-d3fd-721c1c85c350@nokia.com>
In-Reply-To: <66e930c9-8cb8-4ef7-d3fd-721c1c85c350@nokia.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Sun, 1 Jul 2018 23:32:39 -0400
Message-ID: <CANUuoLqzXzBT_NOR58Gr=6UVcGAa6B264rEPrRQ4bKjBFL=Dsg@mail.gmail.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001f105b056ffbdab4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/DdvkRp0hbCOc-XkTp739QgiHYVk>
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 03:32:55 -0000

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>
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
> Network Data Science, Nokia Networks
> Calendar: http://goo.gl/x3Ogq
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>