Re: [alto] a survey of ALTO

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 11 June 2018 22:22 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 8E24C130ED8 for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 15:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level:
X-Spam-Status: No, score=-1.421 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_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 P-xy9qTe5AcT for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 15:22:39 -0700 (PDT)
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.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 C06EC130EB4 for <alto@ietf.org>; Mon, 11 Jun 2018 15:22:38 -0700 (PDT)
Received: by mail-lf0-f52.google.com with SMTP id d24-v6so32922174lfa.8 for <alto@ietf.org>; Mon, 11 Jun 2018 15:22:38 -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=y3GAPVqsYhEFhKIcEF8TA8wkLjTILKyLURlVq4p4N9U=; b=GgygWAjQkOvNmfv9BgRyz0Rc7iGT0U69X24S14QGoAXmsftQm/6CXcwNdK2eye8U/m r/GLWssHtS/EqS6XNT31dig9k5xp4uV7yeoXJJ3vsJAwh8k3liXMAgnMtZ6syBWN1Nfr BTZCNX7KYuPMiAbqi1dWjqBqDf1Zh5pFtYI/vELomludM/iutNtoAHd8YEQRkQf3mKyr vKer+dOm0jhGpdq4+Hq+Hg99vBSPh1Mbrvr5J1t8dp7qa8pgEEulwAFK+7dMrPyM0Ji0 CPFZn+uhXB18EyTjeQ3VpQLL/rgVmR57bdRxZ5nA7Cc0H2GUUEu2yTmFu8U7b/5s2kUQ cGjg==
X-Gm-Message-State: APt69E04W4TPAUstrHpJlVG7HsV7er2izL++xttzOI7c5BgYpZlMMRyK L47BKaIrMYtGVBOwqy51grT3Jopp1j5aMMF+4lc=
X-Google-Smtp-Source: ADUXVKJ2wT2w+cCPRaMXbD/WeESzC04nXRXINvvjg3beNx/i5fHCl/Mk62D44aOP1RKg7FjhQTGMZlh68N6OvGhKC6Y=
X-Received: by 2002:a2e:63db:: with SMTP id s88-v6mr607031lje.78.1528755756777; Mon, 11 Jun 2018 15:22:36 -0700 (PDT)
MIME-Version: 1.0
References: <CA+oaSDp3Pq9jBat8E_3BFpX8iqLaPxgjr_PJbkeeXFSOOr_QTQ@mail.gmail.com> <CAAbpuypa=1mEsTZ94bc98ns+FSEPrkTPwgATKCc3AKAV+5zEfw@mail.gmail.com> <CAEj5p9SWLnKSRu_fHJL=A4+KYCSfUqL+9yYMGMSJ3S+DFhZA5g@mail.gmail.com> <CAOB1xS8_LpkQvaoBcN0e9C-+r3YYY4J=3nx75cEUmi6Q+Rasxw@mail.gmail.com>
In-Reply-To: <CAOB1xS8_LpkQvaoBcN0e9C-+r3YYY4J=3nx75cEUmi6Q+Rasxw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 11 Jun 2018 18:22:24 -0400
Message-ID: <CANUuoLpo3P9SH9WQtHy6HQ9QM0FwOEh3krni+24EyOMQ2S9s9g@mail.gmail.com>
To: Qiao Xiang <xiangq27@gmail.com>
Cc: Christian Esteve Rothenberg <chesteve@dca.fee.unicamp.br>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d4c51b056e652f25"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/sGL-zFgt4JSCq61fewewA3x7lzA>
Subject: Re: [alto] a survey of ALTO
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 11 Jun 2018 22:22:42 -0000

Great suggestion, Christian!

Qiao: thanks for pointing out the related work. The IWQoS'17 and ICNP'16
work are highly related indeed.

Shawn: I will be more than happy to review the addition of the table, as
Christian suggested. It can be part of the draft, or you can post such a
table on the mailing list for discussions, as IETF uses mailing list as one
key venue of discussions.

Thanks!
Richard

On Mon, Jun 11, 2018 at 5:09 PM Qiao Xiang <xiangq27@gmail.com> wrote:

> Hi Christian,
>
> Great suggestion! I fully agree. Such a table would be very helpful!
>
> Shawn: I understand this is not a complete list. Just a reminder that you
> should add Kai's IWQoS'17 paper (NOVA) and its previous ICNP'16 poster
> paper (ORSAP) in the survey. They are based on the ALTO-PV and ALTO-RSA
> drafts.
>
>
> Best
> Qiao
>
> On Mon, Jun 11, 2018 at 12:06 PM Christian Esteve Rothenberg <
> chesteve@dca.fee.unicamp.br <chesteve@dca..fee.unicamp.br>> wrote:
>
>> Nice work!
>>
>> In line with Jensen questions, I was going to suggest adding the RFC /
>> draft info to the Implementation details, e.g. Network Map, Cost Map,
>> Unified Property Map, Path Vector.
>> Especially highlighting the proposed extensions would help to identify
>> the need to move these extensions forward to become RFC, and/or
>> eventually be merged, if / after we realize through a proper Table
>> mapping proposed extensions to use case implementations and citations.
>> Such a table could also incorporate the additional requirements
>> suggested by Jensen and altogether contribute to a potential WG
>> recharter.
>>
>> -ch
>> Em seg, 11 de jun de 2018 às 03:32, Jensen Zhang
>> <jingxuan.n.zhang@gmail.com> escreveu:
>> >
>> > Hi Shawn,
>> >
>> > Thank you a lot! Also, thank Dawn and Danny. A survey on the current
>> ALTO related works is very helpful.
>> >
>> > I believe your classification for the ALTO use cases is based on the
>> role ALTO plays in the existing system. Do we have any summary of the
>> requirements? All of them use the standard ALTO without any modification or
>> extension? I believe such information is more useful and should be
>> considered in the survey. Because we try to understand what are the
>> essential additional requirements for newer scenarios. It will decide
>> whether we need to recharter the WG.
>> >
>> > Best,
>> > Jensen
>> >
>> > On Mon, Jun 11, 2018 at 1:21 PM Shawn Lin <x.shawn.lin@gmail.com>
>> wrote:
>> >>
>> >> Dear ALTOers,
>> >>
>> >>
>> >> @Dawn, @Danny and I are working on a survey of ALTO. Our goal is to
>> understand what ALTO can already do in the real system, how others use ALTO
>> and the additional requirements for newer applications (like SDN, NFV,
>> Block-chain network) to do the traffic optimization.
>> >>
>> >> Currently, we have a deck of slides and a skeleton of our draft. We
>> had some wonderful discussions with @Richard and @Sabine! So here we would
>> like to share the slides with the WG and get feedback from WG members. I
>> believe it is a good way to summarize the current status and look into the
>> next step :)
>> >>
>> >> The current slides include 6 ALTO implementations (from open source
>> project, academic research, and company production) and 18 use cases (from
>> IETF drafts/slides, papers, and white papers) in 5 categories like below:
>> >>
>> >>
>> >> ALTO Use Cases
>> >>
>> >>   |
>> >>
>> >>   +--> Information Source
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Path Selection in MPTS-AR
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Locate Content in Mobile Edge Cache
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Virtualized Service Function Chain Placement
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Intelligent VM Placement
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Service Placement in IoT
>> >>
>> >>   |
>> >>
>> >>   +--> Ranking Server
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> A Peer Ranking Service for P2P Streaming
>> >>
>> >>   |     |     Information
>> >>
>> >>   |     +---> A Service to Select CDN Surrogate
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> A Service to Select CDN Servers from
>> >>
>> >>   |     |     Different SDN Domains
>> >>
>> >>   |     +---> A Service to Select downstream CDN
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> A Service to Guide the Peer Connection
>> >>
>> >>   |           in  Blockchain
>> >>
>> >>   |
>> >>
>> >>   +--> Network Abstraction
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Network Abstraction Provider in SDN
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Topology Abstraction for VPN Scale-out
>> >>
>> >>   |     |     Decisions
>> >>
>> >>   |     +---> ALTO being Used to Solving n2  Problem
>> >>
>> >>   |
>> >>
>> >>   |--> Information Exchanger
>> >>
>> >>   |     |
>> >>
>> >>   |     +---> Network Behaviors Exchanger between
>> >>
>> >>   |           Providers
>> >>
>> >>   |
>> >>
>> >>   +--> Measure Results Interface
>> >>
>> >>         |
>> >>
>> >>         +---> An Interface to Query on the LMAP
>> >>
>> >>               measure results
>> >>
>> >>
>> >>
>> >> We attach the slides below. You can also access the editable version
>> in Google Slides:
>> >>
>> >>
>> https://docs.google.com/presentation/d/1aXIZfUjQrSFhkVIUbvt2ouKWqLgGq4kbG-EBmSaZtKo/edit?usp=sharing
>> >>
>> >>
>> >> Any comments or suggestions are welcomed and appreciated!
>> >>
>> >> Bests,
>> >> Shawn Lin
>> >> _______________________________________________
>> >> alto mailing list
>> >> alto@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/alto
>> >
>> > _______________________________________________
>> > alto mailing list
>> > alto@ietf.org
>> > https://www.ietf.org/mailman/listinfo/alto
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>
>
> --
> Qiao Xiang
> Postdoctoral Fellow,
> Department of Computer Science,
> Yale University
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


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