Re: [alto] ALTO Weekly Meeting Info for Sep. 09, 2020

"Y. Richard Yang" <yry@cs.yale.edu> Wed, 09 September 2020 23:38 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 EB48F3A08ED for <alto@ietfa.amsl.com>; Wed, 9 Sep 2020 16:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 vFaXOGxMTYI8 for <alto@ietfa.amsl.com>; Wed, 9 Sep 2020 16:38:11 -0700 (PDT)
Received: from mail-vk1-f172.google.com (mail-vk1-f172.google.com [209.85.221.172]) (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 844DE3A0831 for <alto@ietf.org>; Wed, 9 Sep 2020 16:38:11 -0700 (PDT)
Received: by mail-vk1-f172.google.com with SMTP id r78so1119421vke.11 for <alto@ietf.org>; Wed, 09 Sep 2020 16:38:11 -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=4Aeau6oxrJjwHzosKCVlmX7e+zozQ3lVHee9Pz1rfOM=; b=Jm06fWx+W6hR9UFfOE+RbjrcHJrJHaCAEk/8kqxa6RqY4bI9/uo5krcnrdCf+zdYEW QCYEz6mOJMbugFQ11p5XKjMW90Lu+WReBGwzrMxXjAI8LgZ0C9pUqe770gVX0GecUcRb pe83pUIQac7gyXLVzh5FFRkC22SZaAlQQcmwwgOZVwpBLht81pEoVRBZ/6386A0XzfJS 73DiPYH5uY4cvP7cjfd8hX2xEFKquXaVFF8f4a9XCvdfUOlErdOGMYY2Lhe08hlq6eQa V7qFMkiCRL/u/KTN6AKam5KDP3Gc0WBijyMgObZNKH768VQ25uuFiW33Z9M49bI2EUQt OySw==
X-Gm-Message-State: AOAM533HM1BQ7nstnmu6CukWXteNz6/7D1/jsNh61eBsi5hEwYsVB3BK S/5yzXvpTEcDRCB4pskLvtGAsvzk4wvGSwIaRZY=
X-Google-Smtp-Source: ABdhPJxgHU0nMTcQbzd5EVBydTCyKhCUhLZe9SZtr7rlQPkrGFukwtzHrXf+UXBqOwU42nZhqczVccqVouPxMsNeiy0=
X-Received: by 2002:ac5:c748:: with SMTP id b8mr2565540vkn.6.1599694690429; Wed, 09 Sep 2020 16:38:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAAbpuyq62458+OU-BA6irxPKnHPwQKTQ9mmogzNdd5qLZy0u_A@mail.gmail.com> <PR3PR07MB70180F245E324FFC4369A7D295260@PR3PR07MB7018.eurprd07.prod.outlook.com>
In-Reply-To: <PR3PR07MB70180F245E324FFC4369A7D295260@PR3PR07MB7018.eurprd07.prod.outlook.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Wed, 9 Sep 2020 19:37:59 -0400
Message-ID: <CANUuoLpmpud-fYHr-xQteL8ffxWREj+MT7ZQZMrpCZDAShMC6A@mail.gmail.com>
To: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>
Cc: Jensen Zhang <jingxuan.n.zhang@gmail.com>, IETF ALTO <alto@ietf.org>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000c5afc305aee9f1ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/D4e7o0LopvZE-2kCnu9YfdTVb2o>
Subject: Re: [alto] ALTO Weekly Meeting Info for Sep. 09, 2020
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: Wed, 09 Sep 2020 23:38:17 -0000

Hi all,

On behalf of those attending the weekly meeting today, below is the draft
text for the ALTO transport discussions. Any comments or discussions are
highly welcome:

"Protocol extensions of ALTO to convey network information with additional
transport mechanisms. The current ALTO transport is based on HTTP/1.x
connections between ALTO servers and ALTO clients. On the other hand,
recently, extensions to HTTP/1.x such as HTTP/2 and HTTP/3 introduce
capabilities such as concurrent multiple streams in a single connection.
Such new transport capabilities can be integrated into ALTO to improve ALTO
capabilities such as ALTO incremental updates. The working group will
investigate the benefits and issues of using HTTP/2(3) as ALTO transport,
for both basic ALTO services and additional ALTO services such as ALTO
incremental updates.

Initial evaluations of ALTO in the cellular network context reveal that it
may be more natural to expose network information to applications directly
through datapath packets. Consider the current ALTO transport as an
out-band (OB), network information exposure to applications through
datapath packets is a form of in-band (IB) signaling. Given the importance
of cellular network use cases, the working group will investigate the
possibility of ALTO transport using IB transport (e.g., IP/TCP, GTP-U). It
is important to realize that introducing IB as transport can have
substantial complexities. For example, the working group should coordinate
with related standardization efforts (e.g., at IETF or 3GPP) for IB
information signaling from applications to networks (e.g., network tokens,
APN), and investigate the possibility of a single coherent design. If there
is enough progress, the working group may conduct a coherent design;
otherwise, the output should be an informational document reporting
findings such as key challenges and potential solutions."


On Wed, Sep 9, 2020 at 8:14 AM Randriamasy, Sabine (Nokia -
FR/Paris-Saclay) <sabine.randriamasy@nokia-bell-labs.com> wrote:

> Dear all,
>
>
>
> I would like to add the following topic, regarding WG documents to finalize
>
> - ALTO Calendar RFC editor questions: answer to question N°6-C
>
> - Unified property review status
>
> These 2 topics would only take a couple of minutes but need to be
> addressed to finalize the WG documents.
>
>
>
> Thanks,
>
> Sabine
>
>
>
> *From:* alto-weekly-meeting@googlegroups.com <
> alto-weekly-meeting@googlegroups.com> *On Behalf Of *Jensen Zhang
> *Sent:* Tuesday, September 8, 2020 10:12 PM
> *To:* IETF ALTO <alto@ietf.org>rg>; alto-weekly-meeting@googlegroups.com
> *Subject:* ALTO Weekly Meeting Info for Sep. 09, 2020
>
>
>
> Dear ALTOers,
>
>
>
> Just a friendly reminder that we will continue our weekly meeting this
> Wednesday (*Sep-09*) at *9:00 am - 10:00 am US ET*.
>
>
>
> The draft agenda*:
>
>    - Finalize the draft write-up for WG rechertering
>    - Open discussion slots
>
> Meeting bridge: https://yale.zoom.us/my/yryang
>
>
>
> *If you have any other agenda items to be discussed, please feel free to
> post.
>
>
>
> Talk to you then.
>
>
>
> Best regards,
>
> Jensen
>
> --
> You received this message because you are subscribed to the Google Groups
> "alto-weekly-meeting" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to alto-weekly-meeting+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/alto-weekly-meeting/CAAbpuyq62458%2BOU-BA6irxPKnHPwQKTQ9mmogzNdd5qLZy0u_A%40mail.gmail.com
> <https://groups.google.com/d/msgid/alto-weekly-meeting/CAAbpuyq62458%2BOU-BA6irxPKnHPwQKTQ9mmogzNdd5qLZy0u_A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "alto-weekly-meeting" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to alto-weekly-meeting+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/alto-weekly-meeting/PR3PR07MB70180F245E324FFC4369A7D295260%40PR3PR07MB7018.eurprd07.prod.outlook.com
> <https://groups.google.com/d/msgid/alto-weekly-meeting/PR3PR07MB70180F245E324FFC4369A7D295260%40PR3PR07MB7018.eurprd07.prod.outlook.com?utm_medium=email&utm_source=footer>
> .
>


-- 
-- 
 =====================================
| Y. Richard Yang <yry@cs.yale.edu>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================