Re: [alto] Chair review of draft-ietf-alto-incr-update-sse-17
Danny Alex Lachos Perez <dlachosper@gmail.com> Mon, 06 January 2020 18:56 UTC
Return-Path: <dlachosper@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 7CF87120105; Mon, 6 Jan 2020 10:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, 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 wnmVOlaPGck6; Mon, 6 Jan 2020 10:56:10 -0800 (PST)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (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 1AEFF120077; Mon, 6 Jan 2020 10:56:10 -0800 (PST)
Received: by mail-vk1-xa29.google.com with SMTP id h13so12757905vkn.10; Mon, 06 Jan 2020 10:56:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=40ZSitLXM9r5BcZOXD3htkMLoSPSs0pJQbRjhCB12NE=; b=oj31VGKZ1S8lPBQu6E8K0iDrM89ZKWd/9U2MfRtab9qAdOr0v03VCIzwZwnnruZXjh Qo2iaQDZWiozRONObuAJNDywO9pOheZsNNrTjBCXV5VUC96BiNw3eEl1wc532DuAwVDI a3rQbXnN/h7NDdcC8LhuDu+y/gyNhH3lnA02g/hYFlltos04Ylsr/fBg5cz6920HDpmK gsXugt8z7Vhb9v/Y34IjjI+V2Erb8TMps3g9Ef51D+kPqD2nVyfIcURw4C32Drh128/o s3sw6WChguK0VkZymCpZyEEb05Cun4UHWEXB1FljKxkYe4rlzVnV/wlTUpbj1+dO/pWd 6Wqg==
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=40ZSitLXM9r5BcZOXD3htkMLoSPSs0pJQbRjhCB12NE=; b=OtCGm6EMn3dXuFFFYu5qJ5kHAQbwAzzZWZ9I2wEWlIaJnJWfMDS7Hvky7QTyreRaV7 3ZYxtPjjKnu5sqYaml0v3P3Rfo2hj0l5hNmGDY9RnPONOPvTpYElQrrS3DC6FxxSkFqc ilASFUi+HoH+pHxLbQYJZaOL27vOYALHLqSFfw9TDfM1MkHFiqzpwSBk6i81DdwJu2yN 6IhzCA4yvMCujHJPuP+GCf+MlkUAegr/sZOlLJ+k2FqSZdYX1J5YbQV5PCSx8SLXBB3Y FrO86c+cgiUTTZw7n+wI0EJUgb0fNrb34UNztb6o0tlOn9qQB9cTr4E4xC9tHO6pPKSx uKvA==
X-Gm-Message-State: APjAAAW7A6FUSFK9bbaOtWYkZ2HxqzqOcaVRhwvFBvBcAqTGX6bK0567 3fNItNo0z6JGuCehWgBzJQm3vMoHAJplr5ysuRo=
X-Google-Smtp-Source: APXvYqw6YLuHFFhMmjbzHBFwOeti99uSeo5GpL0FgIzq/KD3TEXRpOoklw6733WPHV4vanlZkrsHiPqWr4gPhM+dHDA=
X-Received: by 2002:a1f:18cf:: with SMTP id 198mr58379319vky.61.1578336969074; Mon, 06 Jan 2020 10:56:09 -0800 (PST)
MIME-Version: 1.0
References: <CAMMTW_KOHEfE7AojeviUdUVqmDLmJQ97+hUeoMKj1A0wwAzY6w@mail.gmail.com>
In-Reply-To: <CAMMTW_KOHEfE7AojeviUdUVqmDLmJQ97+hUeoMKj1A0wwAzY6w@mail.gmail.com>
From: Danny Alex Lachos Perez <dlachosper@gmail.com>
Date: Mon, 06 Jan 2020 16:55:57 -0200
Message-ID: <CAEDarXKPD7x35GRFiYgMy2jnq5NsfYumDR4K5DbQz_AhJHKeig@mail.gmail.com>
To: Vijay Gurbani <vijay.gurbani@gmail.com>
Cc: draft-ietf-alto-incr-update-sse@ietf.org, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000060ac83059b7d36e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/HNK9kS3V2dXKim-RK6qIpJDhhnU>
Subject: Re: [alto] Chair review of draft-ietf-alto-incr-update-sse-17
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Jan 2020 18:56:13 -0000
Hello Vijay, Happy new year!!! Just a quick comment to your question about implementations of ALTO-SSE There is a related work "Steering Hyper-Giants’ Traffic at Scale" [0] where ALTO is used as a northbound interface in a *real operational environment at scale*. The authors mention the SSE extension (but I am not sure if this extension was also tested). Best regards, Danny Lachos [0] https://mailarchive.ietf.org/arch/msg/alto/h7QJRu47NbTvfcnW2fveFqCBRdw On Mon, Jan 6, 2020 at 4:32 PM Vijay Gurbani <vijay.gurbani@gmail.com> wrote: > All: Happy new year. > > In preparation of moving alto-incr-update-sse ahead, I have performed a > chair review of the work. Overall, the document is well written, mature, > and considers various design tradeoffs. This is fairly mature work, and we > should move it out of the WG following the resolution to the review below > and an additional review by Jensen Zhang [1]. > > --- Begin chair review > > I am curious --- are there any known implementations of alto-sse? > > MAJOR > -S10.1: This is an important discussion. However, this discussion is > written primarily from a viewpoint of an ALTO client, but if I understand > it correctly, it should be written from the viewpoint of an ALTO stream > server since it is the stream server that is generating the event since > that is the source that should be told to behave conservatively. Should > this section be re-written to exhort the stream server to send out full > cost maps in chunked format, where each chunk is at most 2,000 octets? > That way, the clients are not overwhelmed. Thoughts? > > MINOR > S3: It is rather unfortunate that one of the services is named “Stream > Control Service” as this may be conflated by the uninitiated reader with > the Stream Control Transmission Protocol (SCTP) service, a transport layer > protocol. Clearly, that is not the intent here. However, I am loathe to > suggest a new naming scheme this late in the document publication phase, so > perhaps the best we can do now is to add a note explicitly disassociating > Stream Control Service of ALTO from SCTP. Perhaps something like: s/from > the update stream./from the update stream. (Note that the Stream Control > Service in ALTO has no association with the similarly named Stream Control > Transmission Protocol [RFC4960].)/ > > S4: The phrase “Using existing techniques wherever possible,” implies that > you have used other, perhaps new techniques at other places. Is that the > case? If so, please enumerate the new techniques; if not, perhaps reword > as s/Using existing techniques wherever possible,/Using existing > techniques,/ > > -S4.2.1: “This document adopts the JSON merge patch message format to > encode incremental changes, but uses a different transport mechanism.” ==> > Not sure how to interpret this. Since alto-sse uses the HTTP PATCH method > to affect incremental updates, it uses the same “transport mechanism” > (i.e., TLS). Perhaps you meant “...., but uses a different HTTP method, > i.e., it uses POST instead of PATCH (details in Section 5).”? > > -S4.2.1, page 10: s/, and (3) assigns a new tag to the network map:/, (3) > leaves “PID3” unmodified, and (4) assigns a new tag to the network map:/ > > -S6.1: Is there some magic about the numbers “1” and “2” assigned to > substream IDs? In other words, must substream IDs begin with 1 and > monotonically increase? If so, state that. If not, then state that > substream IDs must begin with a random number between [1, 10] and > monotonically increase from there on for each new substream. That is, if > the first substream ID is 6, then subsequent substream IDs from the client > should monotonically increase from this starting value. (I will let the > protocol designers come up with the exact text to impart this.) > > NITS > -S5, page 16: s/this design allows/this document allows/ > (Overworked use of “design”: “...flexible protocol design, this design…”). > > -S10.1: s/single character array./character array./ > > -S10.1: s/client computer/client/ > > --- End of chair review > > Additionally, the work has also been reviewed by Jensen [1]. > > Authors, please attend to the comments indicated in this review and > Jensen's review and release a new version in order to move the work forward. > > [1] https://mailarchive.ietf.org/arch/msg/alto/C9_tS44bz7kq84Z3cpZZkMeUDFc > > Thank you. > > - vijay > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto >
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Vijay Gurbani
- [alto] Chair review of draft-ietf-alto-incr-updat… Vijay Gurbani
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Danny Alex Lachos Perez
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Hans Seidel
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Vijay Gurbani
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Hans Seidel
- Re: [alto] Chair review of draft-ietf-alto-incr-u… Vijay Gurbani