Re: [alto] ALTO meeting info for Oct. 02, 2019
"Y. Richard Yang" <yry@cs.yale.edu> Wed, 02 October 2019 12:34 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 6FF3A120019 for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.477
X-Spam-Level:
X-Spam-Status: No, score=-1.477 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, RCVD_IN_MSPIKE_H2=-0.001, 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 Ugkw5GgvysXc for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:34:35 -0700 (PDT)
Received: from mail-vs1-f49.google.com (mail-vs1-f49.google.com [209.85.217.49]) (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 389C612000F for <alto@ietf.org>; Wed, 2 Oct 2019 05:34:35 -0700 (PDT)
Received: by mail-vs1-f49.google.com with SMTP id v19so11783950vsv.3 for <alto@ietf.org>; Wed, 02 Oct 2019 05:34:35 -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=5FVKM5w8pvPl9OGKklkA2h9NqPE7Fb/PK7qoujIZSI0=; b=XrHDcBxji+x3yWYizzqfpTrsAO4/zC7YvkW8I4+tzv7tqb54Ck0WPvFyibaC0dR72S pwsu2VSwKmasi/FACoWFA4piL47IW4Clttktq09V2M9MXMuhrTCakqojZN5w8SVVBY3D 8/d0jAjS8nD7BcDBtjeh/ID+6cgPt89UCY5PKtrnsThdYJU3XTtV4spq8UUNTCLa3Idq Qq5eUdIb1t1/CK6G8yIpFkXydZXTKwBpiSdPXwrvohRrwDDmpiGVv0LpDoXfhc2HsLPg A/hkqJlZDGct00WGw6VhtAyekhFVYCrk6FkA6jOtn4NpubWPa5yZs8Vy6riFGksorCWp t/ug==
X-Gm-Message-State: APjAAAVxMigoGV0EqQX+dF9FSrHwL4CUdHIUmzG/vRRQagWdVCE65dKW osQ4qu/XTSvrc+H3qt7qQJ6gfVXNoiLt9eAGVrZxYxfl1Uk=
X-Google-Smtp-Source: APXvYqwADNCh9JN3CQVWb4vnbKzCh79kmJOm/kDYgshTamvDzQRabuZsY4A6rJthSlksj8DeQGYo8FTUxsz+xh+OQog=
X-Received: by 2002:a67:2202:: with SMTP id i2mr1688313vsi.103.1570019673995; Wed, 02 Oct 2019 05:34:33 -0700 (PDT)
MIME-Version: 1.0
References: <CAEDarXJG=XW=BjppyR5qdvGBp7vdkZrT4QvcT0J+TUr9zj-Dhg@mail.gmail.com> <PR1PR07MB5100FE304ED24F5A80276C01959D0@PR1PR07MB5100.eurprd07.prod.outlook.com>
In-Reply-To: <PR1PR07MB5100FE304ED24F5A80276C01959D0@PR1PR07MB5100.eurprd07.prod.outlook.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Wed, 02 Oct 2019 08:34:21 -0400
Message-ID: <CANUuoLqBoz=kM5+Wrw0x7ZOzQ6RRH7cDOk7dQ8HgL-04FjN8JA@mail.gmail.com>
To: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>
Cc: Danny Alex Lachos Perez <dlachosper@gmail.com>, IETF ALTO <alto@ietf.org>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000f581190593ecb09c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/xcfdD8d1vl8CAVxkCs9nOkWi770>
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:34:37 -0000
Sabine, Good idea to start with the side meeting/workshop. Please see this Google doc for the list of questions and the invited/potential participants that I am aware of: https://docs.google.com/document/d/1GWDj8E34lyIKeasNrDgH584VEI7uV4FAy65LOV5j-10/edit?usp=sharing Below On Tue, Oct 1, 2019 at 1: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/PR1PR07MB5100FE304ED24F5A80276C01959D0%40PR1PR07MB5100.eurprd07.prod.outlook.com > <https://groups.google.com/d/msgid/alto-weekly-meeting/PR1PR07MB5100FE304ED24F5A80276C01959D0%40PR1PR07MB5100.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/ | =====================================
- [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