Re: [alto] ALTO meeting info for Oct. 02, 2019

"Y. Richard Yang" <yry@cs.yale.edu> Wed, 02 October 2019 12: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 D0BC6120019 for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 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, HTTPS_HTTP_MISMATCH=0.1, 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 i42i1_wDwdP3 for <alto@ietfa.amsl.com>; Wed, 2 Oct 2019 05:38:45 -0700 (PDT)
Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com [209.85.217.44]) (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 C29E312000F for <alto@ietf.org>; Wed, 2 Oct 2019 05:38:44 -0700 (PDT)
Received: by mail-vs1-f44.google.com with SMTP id p13so11784440vsr.4 for <alto@ietf.org>; Wed, 02 Oct 2019 05:38:44 -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=w068HLqNsQNWvxtm8XlYw+fOSA9Pb6A3s7WXAYC+q7Q=; b=uREL97dRJmliIST0c3wjb+cRu1ESkaO9GirHGXPIzHinKBXQkf/p8OKf1zB7gLd0BY xgwJ20bNypnnozhc5/eLFpYqFFR3XReRtTQAaLT2BuiyYnJR2E/y30FxA5TELelh9N04 62X65MM5s0NjJpvCfxHzAx0j5jTyH2WTOQG0KOMh1Qj9DKxP4zljfaJ0yMhZ3r8/2WNi Q4uXyj03V5GZ41I8l3oNVI40rZoTPvDUyMF1sMzDgcqUf3JBUovBMt81Xmf6vDZ4lN4x w6ESWRztzeDEXaWCSj1a+0OWFt6JUlvyki4VaoDyzhS1wnw7mlc1XY8eu2ZFcirpq8aI Eg/A==
X-Gm-Message-State: APjAAAXCvmAjBTiqxOSqw4wp6jZ4LeO6g0TKd0gfbgEIjKchWWZygQgE CU8OVw1xjFapBPvEGTBHYnBbTlwPTuwbt6fqFgA=
X-Google-Smtp-Source: APXvYqwAiIwcME18OQvYnnwA8dnKWfKpp5F4TkI1lWomHrBizgVfjSGXWkkUXOhxBMGow+P02KIkj1Gl7Lw1qk4Xa6Q=
X-Received: by 2002:a67:2202:: with SMTP id i2mr1698806vsi.103.1570019923600; Wed, 02 Oct 2019 05:38:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAEDarXJG=XW=BjppyR5qdvGBp7vdkZrT4QvcT0J+TUr9zj-Dhg@mail.gmail.com> <PR1PR07MB5100FE304ED24F5A80276C01959D0@PR1PR07MB5100.eurprd07.prod.outlook.com> <A14F57A6-C3AD-48B3-8DC2-BE6400B08ADA@ericsson.com>
In-Reply-To: <A14F57A6-C3AD-48B3-8DC2-BE6400B08ADA@ericsson.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Wed, 2 Oct 2019 08:38:31 -0400
Message-ID: <CANUuoLrFjp6Frw7PSt8cZwB9sUvkjLNTtuzmiS39p46iMKw+Hw@mail.gmail.com>
To: =?UTF-8?Q?B=C3=B6rje_Ohlman?= <borje.ohlman@ericsson.com>
Cc: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>, 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="000000000000d62b500593ecbf44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/pgkPGp33JH-CcDzMiwQhDwO0Htw>
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:38:47 -0000

I am on a train to the airport and hence might need to be on the mute mode
most of the time.

Talk to you soon,
Richard

On Wed, Oct 2, 2019 at 3:22 AM 'Börje Ohlman' via alto-weekly-meeting <
alto-weekly-meeting@googlegroups.com>; wrote:

> I might join up to 30 min late (due to other conflicting meeting), but I
> will definitely join.
>
>
>
>                 Börje
>
>
>
> *From: *<alto-weekly-meeting@googlegroups.com>; on behalf of "Randriamasy,
> Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>;
> *Date: *Tuesday, 1 October 2019 at 19:56
> *To: *Danny Alex Lachos Perez <dlachosper@gmail.com>;, IETF ALTO <
> alto@ietf.org>;, "alto-weekly-meeting@googlegroups.com"; <
> alto-weekly-meeting@googlegroups.com>;
> *Subject: *RE: ALTO meeting info for Oct. 02, 2019
>
>
>
> 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
>
> o     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://protect2.fireeye.com/url?k=97cffe92-cb45dc78-97cfbe09-0cc47ad93e32-3b5d63579af047f5&q=1&u=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Falto-weekly-meeting%2FCAEDarXJG%253DXW%253DBjppyR5qdvGBp7vdkZrT4QvcT0J%252BTUr9zj-Dhg%2540mail.gmail.com%3Futm_medium%3Demail%26utm_source%3Dfooter>
> .
>
> --
> 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://protect2.fireeye.com/url?k=1f710251-43fb20bb-1f7142ca-0cc47ad93e32-2b2f037057ef28a9&q=1&u=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Falto-weekly-meeting%2FPR1PR07MB5100FE304ED24F5A80276C01959D0%2540PR1PR07MB5100.eurprd07.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter>
> .
>
> --
> 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/A14F57A6-C3AD-48B3-8DC2-BE6400B08ADA%40ericsson.com
> <https://groups.google.com/d/msgid/alto-weekly-meeting/A14F57A6-C3AD-48B3-8DC2-BE6400B08ADA%40ericsson.com?utm_medium=email&utm_source=footer>
> .
>


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