Re: [alto] a survey of ALTO
Qiao Xiang <xiangq27@gmail.com> Mon, 11 June 2018 21:09 UTC
Return-Path: <xiangq27@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 B8846130EC1 for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 14:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Z1_WLWKmPw_G for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 14:09:44 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 603C5127598 for <alto@ietf.org>; Mon, 11 Jun 2018 14:09:44 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id j15-v6so19239067wme.0 for <alto@ietf.org>; Mon, 11 Jun 2018 14:09:44 -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=vPwd34RnqEzR9RhJWhoL1jMZCho0WELgg8dId5EorJE=; b=hYNGe2Emzh60c2fp8F8wROkq42tTZ+0Fq8DRFWeq7U+1/wSlaYACPk8kF9eSnQ+6T/ 9VhGx5QaiqMSFe4Cp0IpvAOpsdInfli0HTtjqHr/ql3HCPSK88cHnNc56Ev9brM+W7J5 eJ/ULWoSsLL07ITljswvgchbnxpaks9DHiC0/Ll3nCMzaOvnqIq3wwUtj7hlTIMCblUV xuiGkqiWX4OqMtqbkLchUTgDWF225pogrqvFjTtS4IH9l0l9Y2KeJVwGwtNvcff0sIkG BOoyAGbGyvqXA2HtVvceJZlacWQkXAZEUjZAvEEvZzZkojwXaTQKyN07HebSB8hVfAyN qHeg==
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=vPwd34RnqEzR9RhJWhoL1jMZCho0WELgg8dId5EorJE=; b=B/Hjz+US4s2PEPAlx19k8fF2/VEg1v5aTx3ZXkNbpSlWHgrCOsvzQ/qxSzHgCZerdk U/s7irFRSAzMTcWgEsaySIUNV/V5PROeQUCv5ZvZI9e99Rnzo4YME1+7/h7PtNCPPpUt b5/ZV0HzCN0ndZ3o9EWFMdr4RF6HKLqixYotUna0rU/jWnWxfCOr0F09F5gjeGSfAYUT YyKR2UU//KjL78ldjIcBDNj67wFWA+8/r4ubUdi3Eadg6dtv2X2wT3v0y+ttwSIeHJFF /WCEFzd/4Q/FgXoZquotoi+9VZCOFsvxJGrQjkxsnalDVafP/fve7Ca49W6Astfwxl5n SIGg==
X-Gm-Message-State: APt69E1Tg6wrwUuU/wWrR7z6z7w3QfnScrCP2jDhKNfEkX361bgKZ5Tj xnJr+pIM8EDXTAtKcLxM4P4d4GUKXlgXiHxm2BpN5g==
X-Google-Smtp-Source: ADUXVKIHH81JJdRT4MSf1POoYE3ULoW5CZ983hj7XtBUSOdBuwrvuqT1WjaQDrsjOpq/R1ORS7lOOu0/5YXOdvIs2Qg=
X-Received: by 2002:a50:88c2:: with SMTP id d60-v6mr670789edd.281.1528751382686; Mon, 11 Jun 2018 14:09:42 -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>
In-Reply-To: <CAEj5p9SWLnKSRu_fHJL=A4+KYCSfUqL+9yYMGMSJ3S+DFhZA5g@mail.gmail.com>
From: Qiao Xiang <xiangq27@gmail.com>
Date: Mon, 11 Jun 2018 17:09:31 -0400
Message-ID: <CAOB1xS8_LpkQvaoBcN0e9C-+r3YYY4J=3nx75cEUmi6Q+Rasxw@mail.gmail.com>
To: Christian Esteve Rothenberg <chesteve@dca.fee.unicamp.br>
Cc: Jensen Zhang <jingxuan.n.zhang@gmail.com>, IETF ALTO <alto@ietf.org>, Xiao Lin <x.shawn.lin@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000001d70b8056e642b06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ErjmwXXSi6YolJwe61kCrm3v-BA>
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 21:09:48 -0000
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> 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
- Re: [alto] a survey of ALTO Y. Richard Yang
- Re: [alto] a survey of ALTO Shawn Lin
- Re: [alto] a survey of ALTO Qiao Xiang
- Re: [alto] a survey of ALTO Shawn Lin
- [alto] a survey of ALTO Shawn Lin
- Re: [alto] a survey of ALTO Jensen Zhang
- Re: [alto] a survey of ALTO Christian Esteve Rothenberg
- Re: [alto] a survey of ALTO Vijay K. Gurbani
- Re: [alto] a survey of ALTO Qiao Xiang
- Re: [alto] a survey of ALTO Y. Richard Yang
- Re: [alto] a survey of ALTO Dawn Chan