Re: [alto] a survey of ALTO
Qiao Xiang <xiangq27@gmail.com> Thu, 14 June 2018 01:32 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 E5D60130DFD for <alto@ietfa.amsl.com>; Wed, 13 Jun 2018 18:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 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, URIBL_BLOCKED=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 vwyp0hE0Wpqi for <alto@ietfa.amsl.com>; Wed, 13 Jun 2018 18:32:17 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 033C2130DC5 for <alto@ietf.org>; Wed, 13 Jun 2018 18:32:17 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id r125-v6so8768248wmg.2 for <alto@ietf.org>; Wed, 13 Jun 2018 18:32:16 -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=FIFVob2b/lRRyU11BsFBN4lHb8OhBRgBg7KpE/D+3KU=; b=gAKe7XxzreTuT5UyokXAKZBkZD/8Xoqt7SDTrVJDuo+/p0DoIioVZ6tdfDAKlBoczz Zx8eEashT9N2hl7aLTdXNpMnXl9BFskNdyn5iVpDJvi2Xxc/pG/wrOxTKCQQIoCojS3c rB5VD6TlgH+aPL+B7LJBByTspehAKEYKyKQPl8xPK892YY9bDOmnLgGkrN9egGpE8p64 JhKzLeAHB2GEtBYYx0raNconFj/G3EAh9KDdsV7O14WqCYMn0kf1kUNrCkSAdTSbh31v 67AfkHGJx9bpXfJ/myS27Z49GDobTbBiewvoZCYcm9E8KJMVvdLmHVvnRBaGIusZxqS4 Ei2w==
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=FIFVob2b/lRRyU11BsFBN4lHb8OhBRgBg7KpE/D+3KU=; b=JrvKrL4vm+mpJUa3vuZ9If7pGtP+QTPxL7zPdxN8slB3R/LSoVJLH2D+KhBGqSCf96 ucoMwXBjhDoheJvrRP0O/QQzm6DQwpvp3NqtJozrCplkGwJQQ4hsSEnWuub4+s9mT9M6 ji8CYxbhth7RYYAe8+ZOL3vSKZFvNxaurMBeDPkA93vdDXH174tUax6Gk8QnsD3Aw2V7 KCmJ5ReVXYJ2EQhdC25MIip6wrAh4X72ZTId1D6ltRZFAiFIKno46n+8GRgk4X+nNq2Z 74Tvb/veu4dTM+C30DR4SQ0dOaZpivlg6uMU2IkapES8v7BDzgLmPbPzJziSHaEjdz9u cWVA==
X-Gm-Message-State: APt69E1yRryYnndUIpWY0i2usdvefJ3cvCYjq628AhXZoXFo7W3nAxJp wr+VHBr0G1fnv25242DUy1ZPw3Sl+bD/3XFS8vobROf1
X-Google-Smtp-Source: ADUXVKLHfoUPwL+kreGlnz8lxHC5lxJDA+wmr51Gtpjk7ADZdr3yyFmTeV6X7PRWB+9txHbEMjvXI/hXh4YklmMcK+8=
X-Received: by 2002:a50:dac9:: with SMTP id s9-v6mr433546edj.241.1528939935211; Wed, 13 Jun 2018 18:32:15 -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> <CANUuoLpo3P9SH9WQtHy6HQ9QM0FwOEh3krni+24EyOMQ2S9s9g@mail.gmail.com> <CA+oaSDpTF+5dRtBjyS6=Jq9YtQom9pRofQj9=BdGHKq-5mSkEA@mail.gmail.com> <BLUPR02MB120232D291B7C27FFDF8B0BDB57F0@BLUPR02MB1202.namprd02.prod.outlook.com> <CA+oaSDo-7v86rZ56UoDFJ7JzPCpGSQoyHsDyVzXtLNRg2p+xzA@mail.gmail.com>
In-Reply-To: <CA+oaSDo-7v86rZ56UoDFJ7JzPCpGSQoyHsDyVzXtLNRg2p+xzA@mail.gmail.com>
From: Qiao Xiang <xiangq27@gmail.com>
Date: Wed, 13 Jun 2018 21:32:03 -0400
Message-ID: <CAOB1xS_d2=DM2Wr7+S+2Y+_NsGD8w6ttbb-RK4rL04Bwrk=G5Q@mail.gmail.com>
To: Xiao Lin <x.shawn.lin@gmail.com>
Cc: Chan Dawn <dawn_chen_f@hotmail.com>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8a435056e901166"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/qChK16NNHMdVbiktsaUhUI4KTBI>
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: Thu, 14 Jun 2018 01:32:21 -0000
Hi Shawn, I added a column "single/multi domain" in the spreadsheet. I feel this is important because as we are seeing more and more multi-domain use cases of ALTO. For starters, there are two active drafts in the WG documenting the design and deployment of ALTO in multi-domain networks, i.e., Unicorn and Broker-assisted orchestration. Danny, Christian and I are also working on a new draft on multi-domain service function chaining with ALTO. Best Qiao On Tue, Jun 12, 2018 at 6:50 AM Shawn Lin <x.shawn.lin@gmail.com> wrote: > Thanks, Dawn. > > The current setting of this Google Sheets is *"Anyone with the link can > edit"*. So I think everyone can edit it through that link. > If anyone has a problem with editing that sheet, please ping me, and I > will send an invitation:) > > Bests, > Shawn > > > On Tue, Jun 12, 2018 at 1:07 PM Dawn Chan <dawn_chen_f@hotmail.com > <dawn_chen_f@hotmail..com>> wrote: > >> Hi Shawn, >> >> I remember that the document is set privacy, so could you please send an >> invitation to others? >> >> Dawn >> >> ________________________________________ >> From: alto <alto-bounces@ietf.org> on behalf of Shawn Lin < >> x.shawn.lin@gmail.com <x..shawn.lin@gmail.com>> >> Sent: Tuesday, June 12, 2018 10:11:53 AM >> To: Y. Richard Yang >> Cc: IETF ALTO >> Subject: Re: [alto] a survey of ALTO >> >> Hi Jensen, Vijay, Christian, Qiao, and Richard, >> >> Thank you so much for your confirmations and fruitful suggestions! >> >> We created a Google Sheets [1] to collect such information. Please feel >> free to edit or comment on it! >> The current header of this Google Sheets mainly includes >> "Paper/Project/RFC Name", "Cited", "Year", "Extend Standard ALTO or not", >> "How they use ALTO?", "Challenges and Research Opportunities", "Others" and >> "Catagory". >> >> Qiao: Just add NOVA and ORSAP, please see row 124 and 125. >> >> [1] >> https://docs.google.com/spreadsheets/d/1dgbVApnyyiIjbSFp49jSIz3XQHMbmme3WXMQfOZVpY0/edit?usp=sharing >> >> Bests, >> Shawn >> >> On Tue, Jun 12, 2018 at 6:22 AM Y. Richard Yang <yry@cs.yale.edu<mailto: >> yry@cs.yale.edu>> wrote: >> 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<mailto: >> 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<mailto: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<mailto: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 >> <mailto: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<mailto:alto@ietf.org> >> >> https://www.ietf.org/mailman/listinfo/alto >> > >> > _______________________________________________ >> > alto mailing list >> > alto@ietf.org<mailto:alto@ietf.org> >> > https://www.ietf.org/mailman/listinfo/alto >> >> _______________________________________________ >> alto mailing list >> alto@ietf.org<mailto: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<mailto:alto@ietf.org> >> https://www.ietf.org/mailman/listinfo/alto >> >> >> -- >> -- >> ===================================== >> | Y. Richard Yang <yry@cs.yale.edu<mailto:yry@cs.yale.edu>> | >> | Professor of Computer Science | >> | http://www.cs.yale.edu/~yry/ | >> ===================================== >> _______________________________________________ >> alto mailing list >> alto@ietf.org<mailto: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