Re: [alto] ALTO meeting info for Oct. 02, 2019
"Y. Richard Yang" <yry@cs.yale.edu> Wed, 02 October 2019 12:42 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 6BEA2120045 for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.476
X-Spam-Level:
X-Spam-Status: No, score=-1.476 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 77zvA7M4bXdt for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:42:54 -0700 (PDT)
Received: from mail-ua1-f52.google.com (mail-ua1-f52.google.com [209.85.222.52]) (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 94B88120019 for <alto@ietf.org>; Wed, 2 Oct 2019 05:42:54 -0700 (PDT)
Received: by mail-ua1-f52.google.com with SMTP id 107so6604572uau.5 for <alto@ietf.org>; Wed, 02 Oct 2019 05:42:54 -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=7GSD61qMwWsS8FD0/Q2kM+ZiqFPpZuQOXhoGfp0WTaU=; b=eNRK53S11AXBCCcAQQaTARubDbbrrIKWoUNv1qVixbPMkqZ8z1/Vqck6/QxX+85ahY u5z5uWcEU3UhLHs0iaDXlFMWaSGE7sfsFy75yEHwfafGqwB5MGS3i/7p8YJQaPSm9tZf cSa0+DAMXrGu4nirrua6qG+5VFLVX7Q4KWlTvTFNdfEG0iV98dsoUaH2tt9V00VP4ZUb JFDZmgKHIp1Uhd7zSMH8anvlEDr4yda6FlGhcezlNDtUhDzZv8Ds38YTK81GWTfjJ6Oh bctZLSGE3M54XSz1hWU3OyGkqw1HcxMROXcMnnZ1QmmkzHUjkWs8qpLS6MsQS4nvrmUH 2fvg==
X-Gm-Message-State: APjAAAV4QlcxHhLK0890n3rTiYtTM0te2TsxZQ6veTSd9uTnRJUk70Tl J8z+nWZ8KMLm/6REBa2N3ic0W3Iv6OrepHkHITU=
X-Google-Smtp-Source: APXvYqwfcOp69s4xbLBeahNIcHzIp8IDBjB6wKADgFc934Sb1UM3oDVrDXY7gJZ5OfrXonkfYmvBf6zJpbM+HCseOJY=
X-Received: by 2002:ab0:67d9:: with SMTP id w25mr1475436uar.128.1570020173393; Wed, 02 Oct 2019 05:42:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAEDarXJG=XW=BjppyR5qdvGBp7vdkZrT4QvcT0J+TUr9zj-Dhg@mail.gmail.com> <PR1PR07MB5100FE304ED24F5A80276C01959D0@PR1PR07MB5100.eurprd07.prod.outlook.com> <CAEDarX+9F9XpFHPjOhjSDH8tdOcpiKAf6xtMhJmV_kMRsN21yw@mail.gmail.com>
In-Reply-To: <CAEDarX+9F9XpFHPjOhjSDH8tdOcpiKAf6xtMhJmV_kMRsN21yw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Wed, 02 Oct 2019 08:42:40 -0400
Message-ID: <CANUuoLprhP_Da+qTv90ySUNhf_HWcj5WKzD2mBQyOhcF0+sk2A@mail.gmail.com>
To: Danny Alex Lachos Perez <dlachosper@gmail.com>
Cc: IETF ALTO <alto@ietf.org>, "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000b9b5ad0593ecce25"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/wCqWEu5jCFzXlzQ7-9CpZ_Cn1Jg>
Subject: Re: [alto] ALTO meeting info for Oct. 02, 2019
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, 02 Oct 2019 12:42:58 -0000
Danny, On Tue, Oct 1, 2019 at 4:32 PM Danny Alex Lachos Perez <dlachosper@gmail.com> wrote: > Hi Sabine, > > Thank you so much for your draft text. > > See a couple of comments inline: > > Below is some draft text based on our discussion last Friday, to be >> updated and amended upon your feedback and suggestions tomorrow. > > > - We could create a Google Doc to make editing easier > > Good idea. I created one :-) > What misses is are extensions to support applications covering multiple >> network domains and technologies, multiple paths, etc… The changes that we >> need to consider are the prevalence of wireless and cellular networks, 5G >> multi-technology e2e, > > > - Maybe, we could add a reference to our ANRW19 paper: "Supporting > Multi-domain use cases with ALTO" [0] (or the slides [1]). This could be a > way of letting people know about the current interest of the research > community and operator community in this type of multi-domain scenarios. > - Slide 8 in [1] includes other examples about ALTO extensions > (current drafts and potential topics to be considered): e.g., new settings > NFV, SFC, Edge Cloud. > > It looks that we have someone has volunteered to be a speaker :-) Richard > - > > Best regards, > > Danny Lachos > [0] https://dl.acm.org/citation.cfm?id=3341126 > [1] https://irtf.org/anrw/2019/slides-anrw19-final28.pdf > > On Tue, Oct 1, 2019 at 2:56 PM Randriamasy, Sabine (Nokia - > FR/Paris-Saclay) <sabine.randriamasy@nokia-bell-labs.com> wrote: > >> Hello, >> >> >> >> Would it be possible to start with the side-meeting at IETF 106 ? We need >> to contact potential participants early enough for them to plan their >> participation and agree on a schedule. So we need to prepare some >> invitation text to introduce the context and purpose of the meeting. Below >> is some draft text based on our discussion last Friday, to be updated and >> amended upon your feedback and suggestions tomorrow. >> >> >> >> Cheers, >> >> Sabine >> >> >> >> >> >> The IETF ALTO WG is planning a 2-3hours meeting with 20-30 participants at >> the IETF 106. The focus is to prepare the evolution of ALTO and explore >> both topics of application-aware networking (AAN) and network-aware >> applications (NAA). >> >> >> >> To this end, we would like to invite a group of speakers willing to >> share their experience and insights about cooperative interactions between >> networks and applications. In particular: given today’s network usage >> trends, where do we identify problems that would be solved with the help >> of such a cooperation? >> >> >> >> AAN or NAA: what is it? What problems did we address? What did we try? >> What worked? What did not? What is missing ? What are the changes in >> networks, applications, in research, technology that we need to take >> into account? >> >> >> >> The goal of this meeting is to gather input helping to better identify >> how ALTO evolutions can complement with other IETF protocols or research >> activities. We therefore seek for insights of participants involved in >> network operations, application or cooperation thereof. A fruitful >> meeting would both collect experience and expectations in this field. >> >> >> >> To start with (text to be shortened + completed): ALTO is addressing >> the need for network-aware applications. It helps addressing issues such as >> unnecessary network costs or performance loss due: to network topology >> agnostic selection of application endpoints such as peers or CDN >> surrogates, bad timing of connection, poor information on e2e network >> paths (no insight, outdated, too voluminous). What misses is are >> extensions to support applications covering multiple network domains and >> technologies, multiple paths, etc… The changes that we need to consider are >> the prevalence of wireless and cellular networks, 5G multi-technology e2e, >> >> >> >> >> >> *From:* alto-weekly-meeting@googlegroups.com < >> alto-weekly-meeting@googlegroups.com> *On Behalf Of *Danny Alex Lachos >> Perez >> *Sent:* Tuesday, October 01, 2019 6:05 PM >> *To:* IETF ALTO <alto@ietf.org>; alto-weekly-meeting@googlegroups.com >> *Subject:* ALTO meeting info for Oct. 02, 2019 >> >> >> >> Dear all, >> >> Just a friendly reminder that we will have our weekly meeting this >> Wednesday (*Oct-02*) at *9:30 am US ET*. >> >> Current Agenda*: >> >> - Quick updates on existing WG documents >> - Discussion about integration design between ALTO and >> Globus/HTCondor >> >> >> - Go over how to extend Globus for some simple but important use >> cases using ALTO >> >> >> - Planning for ALTO workshop (IETF106) >> >> *If people have other agenda items, please feel free to post. >> >> Bridge: https://yale.zoom.us/j/8423318713 >> >> >> Best regards, >> >> >> >> Danny Lachos >> >> -- >> 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/CAEDarXJG%3DXW%3DBjppyR5qdvGBp7vdkZrT4QvcT0J%2BTUr9zj-Dhg%40mail.gmail.com >> <https://groups.google.com/d/msgid/alto-weekly-meeting/CAEDarXJG%3DXW%3DBjppyR5qdvGBp7vdkZrT4QvcT0J%2BTUr9zj-Dhg%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/CAEDarX%2B9F9XpFHPjOhjSDH8tdOcpiKAf6xtMhJmV_kMRsN21yw%40mail.gmail.com > <https://groups.google.com/d/msgid/alto-weekly-meeting/CAEDarX%2B9F9XpFHPjOhjSDH8tdOcpiKAf6xtMhJmV_kMRsN21yw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Richard
- [alto] ALTO meeting info for Oct. 02, 2019 Danny Alex Lachos Perez
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Danny Alex Lachos Perez
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Börje Ohlman
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Y. Richard Yang
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Y. Richard Yang
- Re: [alto] ALTO meeting info for Oct. 02, 2019 Y. Richard Yang