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

Danny Alex Lachos Perez <dlachosper@gmail.com> Tue, 01 October 2019 20:32 UTC

Return-Path: <dlachosper@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 9C6C812006F for <alto@ietfa.amsl.com>; Tue, 1 Oct 2019 13:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tVZT0u7ockse for <alto@ietfa.amsl.com>; Tue, 1 Oct 2019 13:32:27 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 EC00D12001E for <alto@ietf.org>; Tue, 1 Oct 2019 13:32:26 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id v10so10348523vsc.7 for <alto@ietf.org>; Tue, 01 Oct 2019 13:32:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RqbA0plHczafx5D/FqBXo8G+1mSXry+gCKpZ1Os9W/w=; b=Sgry60cibQFQIoPBA5nSRkkZXSJbUNCer5BlSzvXs20+FKJyrFPol731f5bM3BiMHm zkI9QAg6Eu2qJKgFKkFz1PNHtfaqTW4K3OFl2HJVrNGJCfwmDWwd8XqmDVrQyKFjxHJO XeL648P29EEZVeFHroBT043+yPjfpjQyhSm1siB+kKHbtLh8tCkUVsokjMSrkiIH/rGJ dmcWZwocgklz4W8WWmHwNkVMzYqPF1tDp7gqpcBer3aQTZALB4jGBouee6YiNLEAAtrv cMeN1osGasEdJMgda1OdRImXkYkfRuyLBKSnj3gj+9+XLSdsQ/sEhAh8CH11XKuikScG aiTg==
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=RqbA0plHczafx5D/FqBXo8G+1mSXry+gCKpZ1Os9W/w=; b=QY88NPz+67WZ4RtiIitop6fUBJSNEzLp5wH3hnvwLPWnX+Vy21Rw8gG0zGdIyw29SZ 8FuLoTCsvYjfyTWS5frs2FZ7it88TPQ0DzaLBfKHWXJwqfRkdnuCFVfCTS2/YtchX7dZ TbOwmtdzv+Co/bKI8jONUi8OWyJzXTl77OHoaDvw2HmI1kikY+PfnsoAWdesFDsR15Kh wqfaXtjjtMpvxAR11xCc0h648noeB3jwUeWh3vTXLKgqQpBD0F+lGT8bEBoaWL16CD0D 58jcfceGYcBM7e5vMSlVUOKTu4TYtQm9WQ9FJ5g3xpw/Pj9pVdEDHO6I+4tt3c4U3bPJ YJew==
X-Gm-Message-State: APjAAAXTOYs/SGjLzvwC0Fw+DK6JCjp4VwsDA//PwIhnkVzA9WtGWw0n SE/NxDpdtt9hYMww4M52m8N+F0a+ZLxIruya1m8=
X-Google-Smtp-Source: APXvYqyUohQoNz4cWg4HN7nOPExI34Dm3cP9FH9l2r4vPpJ8dDv3mSR4N+sjoldvBHFSmyHMgohj4EyFvHyVcgJDy1o=
X-Received: by 2002:a67:2d95:: with SMTP id t143mr14049476vst.47.1569961945742; Tue, 01 Oct 2019 13:32:25 -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: Danny Alex Lachos Perez <dlachosper@gmail.com>
Date: Tue, 1 Oct 2019 17:32:14 -0300
Message-ID: <CAEDarX+9F9XpFHPjOhjSDH8tdOcpiKAf6xtMhJmV_kMRsN21yw@mail.gmail.com>
To: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>
Cc: IETF ALTO <alto@ietf.org>, "alto-weekly-meeting@googlegroups.com" <alto-weekly-meeting@googlegroups.com>
Content-Type: multipart/alternative; boundary="00000000000016444d0593df40b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/-QNNlteSU1bzd4oa_gC0mJSc-gA>
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: Tue, 01 Oct 2019 20:32:30 -0000

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


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.

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>
> .
>