Re: [alto] SSE final touches

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 19 March 2018 12: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 5CFB41243FE for <alto@ietfa.amsl.com>; Mon, 19 Mar 2018 05:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.419
X-Spam-Level:
X-Spam-Status: No, score=-1.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 RLow0rjrMW-z for <alto@ietfa.amsl.com>; Mon, 19 Mar 2018 05:08:52 -0700 (PDT)
Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (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 AE80F124234 for <alto@ietf.org>; Mon, 19 Mar 2018 05:08:51 -0700 (PDT)
Received: by mail-lf0-f53.google.com with SMTP id t132-v6so25040400lfe.2 for <alto@ietf.org>; Mon, 19 Mar 2018 05:08:51 -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=aP7ErtQmcthmjKBNCgq/eAt17vg3HnjEusxEV2KhEGQ=; b=UdKbgCJthqf/3S+pT3tQ/oxsOQ1GdIoC42eZCUmuARAiKrdZMGXlrf0RDCkAp5kdw+ cD4pjHbrqMF9cEnC9vaFTppE7/uL5d3sp7wRCuL5PL/AcXJxOvor4Og0cfS3PlrCN5o8 nn84O3BHy1IoF3bATedxDmfb7zDNYU8aa2Cdun7U5r1joc1v8KU+gJjg3Q7hL7TlP6+e n8lVVR4tqKhp1wE4ujbHal521TXNCC4FKUA8CUsp0jSoWd+YMC5uSYZOBndhjMMyUo2S 8Vf5GKkvNQ5Cfvyc7dpfhmgoygulpxctpeR3h+AeZDzNzFvAVBHcLNnkzhHtmE3tZWSR wnRQ==
X-Gm-Message-State: AElRT7GTZcYqpnmlOoMmMHTbZ7ZVD3nSHQVoBs938qlTEaf8ZHbYqIot dU6fJnHXHUFJlUGGuKelyHRtCuSSLXN8AZW1MTg=
X-Google-Smtp-Source: AG47ELul8ocDN3vS7pXh5NS9lzTNXapyApTvxHfFpWvHU/y9OjR0CnOLzsCyKs20R3KdrZ+ko8Kclz0fceIxx7tGNlE=
X-Received: by 2002:a19:101a:: with SMTP id f26-v6mr8422148lfi.42.1521461329834; Mon, 19 Mar 2018 05:08:49 -0700 (PDT)
MIME-Version: 1.0
References: <CANUuoLqaWxkXddVJ5jmvEP4a2OC3mN43L8YmPGnmeDKAyW1=sA@mail.gmail.com> <1fd9305f-ae9b-914d-ad25-2d112f92e9f4@j-f-s.de> <CANUuoLryigrC7QSZbB1Sf7iaciCOH=FvjfkxHPtJ4zFRSsq82Q@mail.gmail.com> <ac6e4262-9588-1c97-4902-5fb3a3fea4d3@j-f-s.de>
In-Reply-To: <ac6e4262-9588-1c97-4902-5fb3a3fea4d3@j-f-s.de>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 19 Mar 2018 12:08:39 +0000
Message-ID: <CANUuoLpzyMpLYZ-ZK81v9oM_kZBaaJtLJ=2VR6xzHkn5Fg++5A@mail.gmail.com>
To: Jan Seedorf <ietf@j-f-s.de>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001ab6a10567c2d2a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/raIh8LyK6unoBF6UG5pL-CFv7E0>
Subject: Re: [alto] SSE final touches
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: Mon, 19 Mar 2018 12:08:54 -0000

Jan, Vijay,

Thanks a lot for the guidance!

Some on this mailing list sent me some notes and it looks that they have
good thinking on SSE. We can engage later.

Richard

On Mon, Mar 19, 2018 at 10:47 AM Jan Seedorf <ietf@j-f-s.de> wrote:

> Hi Richard,
>
> great, thanks, as chair I support that decision in the light of finishing
> some charter items soon.
>
>  - Jan
>
> On 18.03.18 18:16, Y. Richard Yang wrote:
>
> Jan,
>
> The authors had a very extensive discussion again. We have decided to
> support only single-object ALTO resources, and leave multipart, which can
> be a nice feature to support composition without the need of accumulating
> all objects into a single object, as future work. We edited a few sentences
> to make clear.
>
> Thanks a lot for the guidance!
> Richard
>
> On Sun, Mar 18, 2018 at 5:55 AM, Jan Seedorf <ietf@j-f-s.de> wrote:
>
>> Hi Richard,
>>
>>
>> 2. One next step we are considering is the support of multipart update.
>> The sever may send a multipart message consisting of multiple objects say
>> A, B, ... each of which is a top level JSON object.. Both merge patch and
>> JSON patch support only a single object and hence cannot apply if we want
>> incremental updates. Hence, if we want incremental updates, we need to
>> provide an individual client-id for each part of a multipart content.
>>
>> what is the motivation behind the multipart update? Sure it is a nice
>> feature, but as you know, we are trying to finalise SSE asap. So we would
>> only like to introduce new feature at this time if they are absolutely
>> needed.
>>
>>  - Jan
>>
>> On 17.03.18 14:07, Y. Richard Yang wrote:
>>
>> Dear all,
>>
>> As we finalizing all aspects of SSE, two issues need some discussions.
>> Quick updates, without delaying the progress, can produce a higher quality
>>  document.
>>
>> 1. It is the notification-of-remove response issue. It is already being
>> started in an earlier thread. Any opinions will be appreciated.
>>
>>
>> Another alternative design is that we require that each potential
>> multipart service also allow individual transmissions. This is the write up
>> in the current version. Any quick discussions will be great.
>>
>> See you in London.
>> Richard
>> --
>> Richard
>>
>>
>> _______________________________________________
>> alto mailing listalto@ietf.orghttps://www.ietf.org/mailman/listinfo/alto
>>
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>>
>
>
> --
> --
>  =====================================
> | Y. Richard Yang <yry@cs.yale.edu>   |
> | Professor of Computer Science       |
> | http://www.cs.yale.edu/~yry/        |
>  =====================================
>
>
> --
Richard