Re: [alto] Some comments on draft-ietf-alto-incr-update-sse-07

"Y. Richard Yang" <yry@cs.yale.edu> Tue, 25 July 2017 21:08 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 3927812F274; Tue, 25 Jul 2017 14:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 HLTdcoCRTEJR; Tue, 25 Jul 2017 14:08:34 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 EF010131F0F; Tue, 25 Jul 2017 14:08:33 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id l81so29652010wmg.1; Tue, 25 Jul 2017 14:08:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=54SMXhF0yB8HWCVy/J2ZKhYV52d37MDFMgLhOULZueU=; b=I7BoUpHxoYA3+kDCPViRTXSTn24dKAx0Upl+N/kYv4lXgnpjhoJI/PxumkTl9373IG qcuGJud+unXHTm6uRKyUIGnwdzb0JGaHxUhAN0iqbVbRS4V/z57U6bIRWH+eBHUFDsT/ 1qFfekoQiv1KiAKSBy/tKU2j4nlko/m0vmwQoMkTp4qBW1MdwWPHzAIYNRUMsseuzMyU UHToonV6qx3Svsj/MNOsO0hzP3XrNvOfd+fVuDC1feELAqOCcYWDvkh3EGvP9YaO7GZj lVw0jT8TBMqUGAkD/0tfHD6b6xYN7z45MLrtx0W0C88iPXgDXwjQsViLbd4QF/KuWlRC FDAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=54SMXhF0yB8HWCVy/J2ZKhYV52d37MDFMgLhOULZueU=; b=gVGLgDwO4awfzTy+rHLElJYSfXZXpVbILtO8GPmfk6k6AcSvCKmT2QAk/FvLrdMT5K ldo/Ny7cSi4T234mAVZ7XdEBxf6GQcE7I310S1uYmhpj6XDMT36tnnW6S/TpmVRww0dI z0KN7goyHNBS8sAQ6Tjc+djEEv21RgkFmtdSXP1ITVjCDhp0KhS+wnExn4UB138GHDBz dAnXRsYe0mEA4eU8JkDY2wS6SPZ/W4zUk39TMHM8w/qG7xEv8bM+osrVBb9BFXDCcYoD JgLNaIAt+AjK62e+unZgAMfD3uuUs3PhhC6TQRow5Nl5ohyTZ+xWv2uI4ji6kMDGUCmY Qg/g==
X-Gm-Message-State: AIVw1105RQZGoeg8imjAWFR3Fr5dL1tcEBRzS36Snl213qOn7DgOiGcM 6F6WKuZBwhSBoKNNWxnpdWX4vEIG5w==
X-Received: by 10.28.220.85 with SMTP id t82mr8553479wmg.10.1501016912529; Tue, 25 Jul 2017 14:08:32 -0700 (PDT)
MIME-Version: 1.0
Sender: yang.r.yang@gmail.com
Received: by 10.28.91.138 with HTTP; Tue, 25 Jul 2017 14:08:32 -0700 (PDT)
In-Reply-To: <72488a71-11a3-a94a-86d1-e64da9a7fd42@nokia-bell-labs.com>
References: <KL1PR03MB14003B3941862899BC6015DAA8A70@KL1PR03MB1400.apcprd03.prod.outlook.com> <CAC5bAia3Vvkir-vN9gWKOGoZHWiQoGxVw4BrR+76yOdn=E9uZw@mail.gmail.com> <72488a71-11a3-a94a-86d1-e64da9a7fd42@nokia-bell-labs.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Tue, 25 Jul 2017 17:08:32 -0400
X-Google-Sender-Auth: 4ytFOoCV2PPo8BjTmYzXQvYs6zo
Message-ID: <CANUuoLqa7MV7K603jvaZjtERswTbiYr3063c2gRr0MQkr7422A@mail.gmail.com>
To: "Vijay K. Gurbani" <vijay.gurbani@nokia-bell-labs.com>
Cc: Lyle Bertz <lyleb551144@gmail.com>, xin wang <xinwang2014@hotmail.com>, "draft-ietf-alto-incr-update-sse@ietf.org" <draft-ietf-alto-incr-update-sse@ietf.org>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b30c6df98eb05552abb7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/CgMo-oCFZFIh6WKiQIZ0fDL12OQ>
Subject: Re: [alto] Some comments on draft-ietf-alto-incr-update-sse-07
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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, 25 Jul 2017 21:08:37 -0000

Dear Lyle, all,

Thanks a lot for the feedback. We will then continue to push the work
forward as soon as we can.

Richard

On Mon, Jul 24, 2017 at 4:52 PM, Vijay K. Gurbani <
vijay.gurbani@nokia-bell-labs.com> wrote:

> Lyle, all: Correct; I believe W3C SSE is the right choice here.
>
> Many moons ago, when we were all very young (okay, ~3.5 years ago, but
> we were still younger), there were other contenders; websockets comes to
> mind [1].  But as the work progressed, it made sense to stick with W3C
> SSE.
>
> Cheers,
>
> [1] https://tools.ietf.org/html/draft-marocco-alto-ws-02
>
> On 07/24/2017 12:49 PM, Lyle Bertz wrote:
> > All,
> >
> > I asked during the meeting about whether or not it made sense to look at
> > alternatives to W3C SSE.  However, in subsequent WG meetings such as
> > netconf use of W3C SSE is the norm and the right way to go.
> >
> > tl;dr - don't change the draft - keep the use of W3C SSE.
> >
> > Lyle
> >
> > On Wed, Jul 19, 2017 at 10:14 PM, xin wang <xinwang2014@hotmail.com
> > <mailto:xinwang2014@hotmail.com>> wrote:
> >
> >     Dear authors of ALTO Incremental Updates Using Server-Sent Events
> (SSE),
> >
> >
> >     The draft about incremental updates by using Server-Sent Events
> >     (SSE) proposes a general framework for incremental updates of
> >     network information. The concept of update stream resource in the
> >     framework allows a unified interface to ALTO clients. The interface
> >     not only considers GET-mode ALTO services but also POST-mode
> >     services, which should support most future extensions of ALTO
> >     services. The following is my comments:
> >
> >
> >     a. The benefits of the general framework
> >
> >
> >     Besides of the extension-friendly design, I am thinking of other
> >     benefits of bringing all ALTO services together by using a new
> >     update stream resource. First, let me propose an alternative simple
> >     solution of incremental updates. The solution views each
> >     subscription independently, which means that each time a client
> >     calls an ALTO service (e.g., get network-map) to get incremental
> >     updating data, the server will establish a connection for the data.
> >     Then, by comparing with the simple solution, we can find an obvious
> >     benefit of the solution in the draft should be reducing redundant
> >     connections. Also, another benefit would be that it makes removing
> >     resources very easily. Though SSE itself supports disconnection API,
> >     it will add new APIs to the simple solution. Moreover, because one
> >     connection could manage multiple resources which may have
> >     overlapping (also dependencies) between each other, I am considering
> >     whether there exists an efficient way to make scheduling for
> >     updating these resources.
> >
> >
> >     b. Full replacement or incremental updates
> >
> >
> >     In the client side, if the data is updated in incremental ways, then
> >     there should be some algorithms to apply the updates like the
> >     algorithm in Section 4.2.1. However, if the data allows full
> >     replacement, then the client can easily replace the data with the
> >     new one instead of applying the algorithms. Also, the
> >     “incremental-updates” field is “true” indicates the server MAY send
> >     incremental update events, which means that the client may receive
> >     either a full replacement or incremental updates in each time (is
> >     this right?). My idea is that if the response from the server can
> >     indicate whether this update is a full replacement or incremental
> >     one, the client should benefit from that.
> >
> >
> >     Also, there are some typos may be fixed:
> >
> >
> >     Page 10: "we now gives" -> "we now give";
> >
> >     Page 13: missing “)” in "(see Section 6.3.”;
> >
> >
> >     Best,
> >
> >     X.Tony Wang
> >
> >
> >
> >     _______________________________________________
> >     alto mailing list
> >     alto@ietf.org <mailto:alto@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/alto
> >     <https://www.ietf.org/mailman/listinfo/alto>
> >
> >
> >
> >
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org
> > https://www.ietf.org/mailman/listinfo/alto
> >
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Nokia Networks
> Email: vijay.gurbani@nokia-bell-labs.com / vkg@bell-labs.com
> Web: https://www.bell-labs.com/usr/vijay.gurbani
> Calendar: http://goo.gl/x3Ogq
>



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