[alto] Recharter discussion thread: ALTO transport
"Y. Richard Yang" <yry@cs.yale.edu> Thu, 23 July 2020 21:14 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 712753A0DC6 for <alto@ietfa.amsl.com>; Thu, 23 Jul 2020 14:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 1oFa9UwIQ3YX for <alto@ietfa.amsl.com>; Thu, 23 Jul 2020 14:14:26 -0700 (PDT)
Received: from mail-vs1-f48.google.com (mail-vs1-f48.google.com [209.85.217.48]) (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 819C13A0DCA for <alto@ietf.org>; Thu, 23 Jul 2020 14:14:26 -0700 (PDT)
Received: by mail-vs1-f48.google.com with SMTP id s20so3852987vsq.5 for <alto@ietf.org>; Thu, 23 Jul 2020 14:14:26 -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=GjlyXmZMw8GlFVYANhM8mxwaWJ4qDup8getMK+fdHMs=; b=HGrXgHuuKkdZlCa969AWlbSaROeFPS3RrEQPNyRKtcTqGTqvqOy68e19IJWIRNIpNP 0ZZuBJ1sIkYaegBu2CvW1bBwfrSe4tdjJ4GmM0LLwBSlXeNpj9j3ic7D3AHRjii+S3By 4QumC9RvKfqT4ZEOCVeDIx0FW+ZijEn4gD4cva4Kezf4i8OYCvX5cbrNy5CKSIkP0nM+ Op0nsUktUAV17SNyVsEonMTaWWsMyer6arlCaQBfuKpNALK77kaapbbCon6kJXUS+For Y+6UHt+YwuNmgjHy3qLBrICBgMiuF4lCro1JmYeXsD61gp/TLpFXKd7yllFaY2Z1XGt/ 40AA==
X-Gm-Message-State: AOAM532qJalpzqN4Z0tbZK+cKMz11Qqw7TRfaYhocueZFYEa55WEcSmo NYgwA2K1+5yq2VctxKnCsd+nTKI9nozkSYcKSIHpi3bSjxs=
X-Google-Smtp-Source: ABdhPJwVVcjAOy3oUQr9ndTQgxI6Ge4l+L5IDRr4DTg7YDaVA0Ekz9+scXxxZ0LtaD/CZI7UIEjna1Mub70Mi33Z3Dg=
X-Received: by 2002:a67:79d6:: with SMTP id u205mr5852644vsc.178.1595538864499; Thu, 23 Jul 2020 14:14:24 -0700 (PDT)
MIME-Version: 1.0
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Thu, 23 Jul 2020 17:14:09 -0400
Message-ID: <CANUuoLq3PjpS9HTVfo282+NaAu1jOwm4eOFOQHChDmWrqm4jPw@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>, alto-weekly-meeting@googlegroups.com
Content-Type: multipart/alternative; boundary="0000000000003e716c05ab225704"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/YUc7hC2sZ12Cza4R7ORv9I5O2Hs>
Subject: [alto] Recharter discussion thread: ALTO transport
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: Thu, 23 Jul 2020 21:14:29 -0000
Dear ALTOers, As we get close to the discussion, many of us are conducting more regular discussions on the related topics. Danny, Ingmar, Sebastian, Chunshan have already started the multidomain thread. Another topic, which can be extremely exciting, but may also raise non-trivial issues, is the network-to-application information transport. There have been multiple extended discussions on this topic during the side meetings already. This evening (July 23) at 10:00-11:00 PM US ET, we will continue the Zoom discussions and everyone is welcome: ==== bridge info ==== Join from - PC, Mac, Linux, iOS or Android: https://yale.zoom.us/j/8423318713 - Or Telephone:203-432-9666 (2-ZOOM if on-campus) or 646 568 7788 Meeting ID: 842 331 8713 International numbers available: https://zoom.us/u/adcNQyMDb6 Below is a summary of the most basic thinking so that those who want to join can get a quick background. Email discussion is welcome as well. First terms: We consider two types of transport: inband (IB) and outband (OB). By IB transport, we mean that the network information to the applications is carried by the data plane packets. A simple example of IB is ECN, which essentially carries network information in data plane packets to the end hosts. The proposed INT approaches tend to be B as well. On the other hand, the base ALTO 7285 is OB, using HTTP/1.x as a transport. The incremental updates component of ALTO adds much flexibility to the transport structure, in particular, by adding a meta stream control protocol, but the transport is still OB. We see two directions to substantially improve ALTO transport. Direction 1 (Only OB): One is to still focus on OB, but revise the related components (e.g., incremental updates) to take advantage of the newer HTTP/2/3. This issue has been raised during SSE IESG reviews, and we feel that we have an obligation to finish this thread. Direction 2 (IB+OB): Some use cases, for example, the MOWIE use case in the context of cellular networks [1], may benefit from IB transport as well. Consider a simple initial design: an ALTO client, say an application server, requests incremental update for some last-hop, base station information. We extend SSE so that the control uri [2, Section 7] allows more flexible indication of push channels. In particular, the push channel might be a layer 3 or layer 4 optional header field, at some sample rate, on the packets on the path back to the server. Then, the server can then get lightweight, fast updates. Some can see this as a quite exciting, unified design, motivated by real use cases... Richard [1] https://datatracker.ietf.org/doc/draft-huang-alto-mowie-for-network-aware-app/ [2] https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/?include_text=1
- [alto] Recharter discussion thread: ALTO transport Y. Richard Yang