[alto] A paper related to ALTO from Google

Qiao Xiang <xiangq27@gmail.com> Thu, 22 April 2021 13:04 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 DBC013A1965 for <alto@ietfa.amsl.com>; Thu, 22 Apr 2021 06:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 ZeqQolpkQ-bt for <alto@ietfa.amsl.com>; Thu, 22 Apr 2021 06:04:09 -0700 (PDT)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 639E93A1946 for <alto@ietf.org>; Thu, 22 Apr 2021 06:04:07 -0700 (PDT)
Received: by mail-ot1-x32f.google.com with SMTP id 65-20020a9d03470000b02902808b4aec6dso37286517otv.6 for <alto@ietf.org>; Thu, 22 Apr 2021 06:04:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=tY4746jHpv5Rx7nokS8JVCq2KVBsoYFmT6mXl3IEiz0=; b=nLn7SawTX/nO9V8ARPRU4/Ugt9MQjaGoLozSHwM6Kh0bvZ2HRmU6PEw1XD+it+JV9I iqXKt9JLYNymeZ+gVTMP2b0VTFLXpR5aYRUgmgbw3q2rd7i7bM7Nqx2Fla1l2RFfByD3 tfXP+JnpB9EThAqbGqVNaMugRBBbNcK6LC7mLpylvqzDoD7NNaWxT5++PiZRFC6bB6sW x/gkQkj9RkraBimGVH0EGnnTyI0XXszJJlofl283MjTCGyAeKT6HqQ/3d69J88F7tcS9 Xyln7Bnp/VoCFonDqaeUK95sskz44B/TTrbsho+ZrMoMQDh/ksSFke+kIRjQ5+7IVxYd rM2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tY4746jHpv5Rx7nokS8JVCq2KVBsoYFmT6mXl3IEiz0=; b=FF59QTVJYRTBdVaae9iH7IupfdU6AtrefkUJYWBwv3gAnxMvElFUxW9ia96bqwDA0w bQvO6evh0JOhuOVmIHQOAknBzqQe6rdwCZaYxfeHYdKBhmDo/r6k6mOYd1LHCHaWwXVU tgBNzawmig5Dll08ZDiCKDl1sBdZ0qKpNTPNnr07dL6W9NHUf2SkIb8LBRl4psLQ2T8O mZonALnYBCKfhB65ZL4uaY8Is0LY3BqnsEJjVh8lEUHXIaJdQG53Vf299d0NSZGKmyyI 5+dupp0BVvmnSGlxhdrRZNJAKYZfo+3pKDu+yZ07Dsg5cJrY33mPmIC2JEsG2lx584eV DBWA==
X-Gm-Message-State: AOAM530FQ9NCuW2iVMaTdJ5vlwhdpih/n1ZI4NuSb/BvgqK1oHs0XdR+ eYLAjQOq0vz0wIe22j9ucGuKzY1Mtk7hOZhcCRDSqbjCCoc=
X-Google-Smtp-Source: ABdhPJwvI/IRCOIs1c6R+3YEoukN2ippSXk6J1ZLYoV82ApcHsAedq3cyuGX5IAjPUFitoAIkJ8w4RAP8Gxqu+iLm40=
X-Received: by 2002:a9d:2929:: with SMTP id d38mr2738281otb.121.1619096643140; Thu, 22 Apr 2021 06:04:03 -0700 (PDT)
MIME-Version: 1.0
From: Qiao Xiang <xiangq27@gmail.com>
Date: Thu, 22 Apr 2021 21:03:52 +0800
Message-ID: <CAOB1xS-WpR48n1tUGpNhUYWMea1iNMU=md5YLR9r7PE63YCc2Q@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000457ed705c08f504c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/TbOcayZXcNQFBSl8BpfgfUYPDg8>
Subject: [alto] A paper related to ALTO from Google
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: Thu, 22 Apr 2021 13:04:19 -0000

Dear all,

I'm writing to share a paper I came across that I think is related to ALTO.
The paper is titled "Experiences with Modeling Network Topologies at
Multiple Levels of Abstraction", and is an experience paper from Google to
introduce their network topology abstraction service called MALT to
facilitate their internal network management systems (e.g., B4, Jupiter,
etc). MALT uses an entity-relation graph as the underlying data
representation, and provides a query language for users to query related
topology information. The link to the paper and its slides and video is
https://www.usenix.org/conference/nsdi20/presentation/mogul

One design decision in MALT is that it only provides topology information.
Information such as bandwidth, delay and routing table are not in the scope
of MALT. IMHO, this might be sth ALTO can help with.
In addition, MALT uses sharding for storage. So queries that span multiple
shards might be related to the design of ALTO multi-domain.

I'll continue digging more details and insights about the synergy between
MALT and ALTO. In the meantime, we can all share our thoughts on the list.



Best wishes
Qiao
-- 
Qiao Xiang
Professor, Yale University