[alto] SSE final touches

"Y. Richard Yang" <yry@cs.yale.edu> Sat, 17 March 2018 13:07 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 57066127863 for <alto@ietfa.amsl.com>; Sat, 17 Mar 2018 06:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level:
X-Spam-Status: No, score=-1.42 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] 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 wbn0NrhnryXU for <alto@ietfa.amsl.com>; Sat, 17 Mar 2018 06:07:52 -0700 (PDT)
Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (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 D29C712783A for <alto@ietf.org>; Sat, 17 Mar 2018 06:07:51 -0700 (PDT)
Received: by mail-lf0-f54.google.com with SMTP id y2-v6so17063236lfc.5 for <alto@ietf.org>; Sat, 17 Mar 2018 06:07: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:from:date:message-id:subject:to; bh=aiC8dFZcToOYXEGkmYQIutQlSrtHD1FCEs2sG9ElwFI=; b=ishzNlnhIGCq4d+HKhdHo9+gpfHoQTfpm4usDKEiaJ4544IdnpDvHmB2iDhzn2f51o t0fIQ6fy7F+x4wzH8+1D9RbyWpPs3HR5zxvu3H0onoRzsr3Xo79WwQ0+9Zv8iaL/IQJp eZDipYJBM1pBkk2FPPN9J2JVkqv5oh7o/kxPjb47b0Op97Cd6SEL6Sr/J8q5siZz4pkQ leDvSL1Rd9JlY3uDGSBGZ0l8S5C2oWEdBwocYe9k/o3Z+eobwAHiCiFcn/VOps6xehIM Rx4c7Ef91gSbGaalyEmCylu89+Pgtz2s6FH6Nn4vHr6d5EB69hv7azIQj+IqiANtfnjO PdBA==
X-Gm-Message-State: AElRT7FqmWV64uwpdbhjwu9YqMMXGNLIHZ2yznd5r5qhZJkfJp0GCUb0 zAitQHOayZBN0a+L/cFscHIuu4gZQLtNRfUPFZs=
X-Google-Smtp-Source: AG47ELsd6XhqR7B+f6/hMdXaXYGGJGLj3DSPgkq/TsmGZea7jkC124DIjEjd44/RkADDVjgI2WiDRBmHNms2DcIVLbs=
X-Received: by 10.46.7.80 with SMTP id i16mr3707490ljd.78.1521292069817; Sat, 17 Mar 2018 06:07:49 -0700 (PDT)
MIME-Version: 1.0
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Sat, 17 Mar 2018 13:07:38 +0000
Message-ID: <CANUuoLqaWxkXddVJ5jmvEP4a2OC3mN43L8YmPGnmeDKAyW1=sA@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f73706bd43b05679b69e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/OQaFfQTlFQ5tSNXK07XxniClNXs>
Subject: [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: Sat, 17 Mar 2018 13:07:53 -0000

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.

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.

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