Re: [alto] End of WGLC for update-sse; need reviews.

Jensen Zhang <> Wed, 18 December 2019 14:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 36D2C12004C for <>; Wed, 18 Dec 2019 06:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e2nWD4Y3b_a3 for <>; Wed, 18 Dec 2019 06:19:23 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::b32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2908D12002F for <>; Wed, 18 Dec 2019 06:19:23 -0800 (PST)
Received: by with SMTP id b145so783181yba.8 for <>; Wed, 18 Dec 2019 06:19:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=jiXGutHRgq92CN0XdqLwoeAhzdWsm/2z2un+rNnNmz4=; b=LEy9YiSiN1Nl3yUfUm7nss7xIfrxEHvObPrR6BtclJmu+cNRfEL6MV+ERP9BNAyKPc UYipuzJ5LsBxwsYNcOiCGbBPcgSIsmsKgDDO+v82g5RX+SJOrKB1j/AVOUExJgCmF82m dfwImrwFErMppWCBk0Nlfxo3fWKgd8mGWEtXoYUIXVAF5NiySdixiX8x/HPOLsRp7Ore +qawKDnYi6A2f1G7dfH/mlLyqZ7Jl98jQzKuCO42FsDOiwRQNRpV3hjnmyAee2APMnlt VoIXAV3Z+YFiXHQfDifAYTVYAFrTNTSS0Fi8XQOGUkPYufO1pRYY/PC5VHaYobJytnuh LT0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=jiXGutHRgq92CN0XdqLwoeAhzdWsm/2z2un+rNnNmz4=; b=qodqPDAP1aCd9NMw9NUgT7hPInBZRuqs6/Jp4a1Uj9QLkAX2Tm43NxquL1tUAQhq9R 2lnMMTrFrFkAkxl95/diC+ehd3B6x84stoDzPVnycwWgouh6XWKkV6lvYVJPNysllaXb OJC1rCZwf/2duWuQ2GhNr2p2sz6pFEoKn5lL61RNVghxfe67D4amvwUq4vvvvTqSpi9Y 1RRA3M58H0e91oTE90l07+YtQgKOgh8S60ALCOERkG8jwZm+W6kfZ1AJcdv4oR4aq3Vt hWyktJlyaPNiB5p94IC3R64vL1CU7pBE6Rm6rC7BbqH5XJT3Akh0DRNtm9rrc0cN2gOu 2e7w==
X-Gm-Message-State: APjAAAUbdLdyXhLUSKAuWwErcrBoov33J8HzCsYZWxqYZ3L9yl/RRcXM zOPDdZaHme6wVUrHGGjy1hFCdJJi0gYmUbLrJrsLo4EzvE8=
X-Google-Smtp-Source: APXvYqz6nFVOWM6k3BkD8R0umKI45IHxzzJyyIk4wkzNhvkwnGcKauEOYfvhrvsYQ0IvbTxZ8kfn3hxxtln48wJygAY=
X-Received: by 2002:a25:d9c3:: with SMTP id q186mr2133373ybg.466.1576678761975; Wed, 18 Dec 2019 06:19:21 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Jensen Zhang <>
Date: Wed, 18 Dec 2019 09:19:11 -0500
Message-ID: <>
Content-Type: multipart/alternative; boundary="0000000000008853e90599fb21b2"
Archived-At: <>
Subject: Re: [alto] End of WGLC for update-sse; need reviews.
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Dec 2019 14:19:25 -0000

Hi WG,

Sorry for my late review. This document is quite long. But I think the
overall write-up is clear enough. Please see my comments inline:

Section 6.1., paragraph 3:

>    Hence, the event field of ALTO update message can include two sub-
>    fields (media-type and data-id), where the two sub-fields are
>    separated by a comma:
  As the SSE message can support unicode, indicating that the comma is
  (',', U+002C) may be better. This is also consistent with the
  character encoding used in other ALTO documents (e.g., Section 10.1
  of RFC7285).

Section 6.1., paragraph 5:

>    To allow non-ambiguous decoding of the two sub-fields, the media-type
>    name used by ALTO SSE MUST NOT contain a comma (character code 0x2c),
>    and the string before the comma is the media-type name.  [To RFC
>    editor: please check this conforms to Section 4.2 of [RFC6838] and
>    confirms to IANA.]
  According to the ABNF of Section 4.2 of [RFC6838], the media-type
  name can never include a comma. So the "MUST NOT" requirement
  can be removed. Instead, we can emphasize there is no ambiguity,
  if necessary.

Section 6.2., paragraph 2:

>    The `data-id` sub-field identifies the ALTO data to which a data
>    update message applies.  For a resource containing only a single JSON
>    object, the substream-id assigned by the client when requesting the
>    SSE service is enough to identify the data.  In this document,
>    substream-ids MUST follow the rules for ALTO ResourceIds
>    (Section 10.2 of [RFC7285]).  Substream-ids MUST be unique within an
>    update stream, but need not be globally unique.  For a resource using
>    multipart/related, the `data-id` sub-field must include the
>    substream-id, `.` and the unique Content-ID.
  "must" should be capitalized: the `data-id` sub-field must xxx ->
  MUST The description "must include substream-id, `.` and the unique
  Content-ID" is not clear for me. It seems that this document does
  not just require the `data-id` to include these three components,
  but be exactly the concatenation of them in order.

The latest revision introduces more generic `data-id` to support multipart
messages. But I do not see an example to show how to use it. We know path
vector is a potential example. Maybe authors do not want to make this
document coupled with path vector.


On Fri, Dec 13, 2019 at 10:19 AM Vijay Gurbani <>

> Jensen: Excellent.  Thank you!
> On Fri, Dec 13, 2019 at 9:04 AM Jensen Zhang <>
> wrote:
>> Hi Vijay and WG,
>> I am reviewing the latest revision of SSE. I will post my review by
>> tonight.
>> Thanks,
>> Jensen
>> On Fri, Dec 13, 2019 at 10:01 AM Vijay Gurbani <>
>> wrote:
>>> Folks: The WGLC ended for update-sse on Dec 8 [1].  However, we have had
>>> absolutely no discussion on the mailing list about this draft after it was
>>> posted for WGLC.
>>> I am shepherding this draft, and as such, I will need at least one, and
>>> perhaps two, members from the WG who are not associated with the draft to
>>> perform an indepth review of this draft.  I will review it as well as part
>>> of shepherding.
>>> Please send me an email indicating that you will like to review this
>>> draft, and please let me know when to expect the review by.
>>> Thank you.
>>> [1]
>>> _______________________________________________
>>> alto mailing list