Re: [alto] ALTO recharter update: ALTO services in multi-domain settings

"Y. Richard Yang" <> Fri, 13 November 2020 00:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 355273A10EB for <>; Thu, 12 Nov 2020 16:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9xAYJ6XVZg0S for <>; Thu, 12 Nov 2020 16:10:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DFC4B3A10E7 for <>; Thu, 12 Nov 2020 16:10:31 -0800 (PST)
Received: by with SMTP id o20so8617682eds.3 for <>; Thu, 12 Nov 2020 16:10:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/TM72ymKJf4uJ1mbyQWZID5icLTjYtBHqTnBSAuxS6A=; b=BbplSzQOB/9xBRAiN75+g2A392nlNL7MRZG1uRSI0xver9YhtVrBchuMIse2tEBdQE Qkd7Ax7tPioFuCuiEHi05rCAnFpWdn/co0QX/mF3AwcEkh+6KiJD4Q/7AnSxKmxwiGTJ VWi4U1PfzgleDas2GHt5lzzBXcM5mAj4Eo/bU56V68SYf787NuP/cLnJkO0OgEuV8EAK 9nrwn5/1y692AgWZyqD6RWyWM+Q1i0bs2n+1b5W5/vSdRCHBJRoUASC3WIH9IUx3EojH rigF7HbExevx5t9uu5x0abdosjoXXUR7uEe2Q18JlcDsjRhvVQObSG/WhWUHkp5Jmey2 bung==
X-Gm-Message-State: AOAM533oe9i9IYotcz/m4FP1XkBXdqnlnAH7izJEqm3F25KezzHT6KRK wxBUeB3SM59iqABBO88vo/NsfPLzFuZe+HRfpERaK8hD3rmZjg==
X-Google-Smtp-Source: ABdhPJxK7sTGmQQNOGYY8wpHGtWp9tMm21dCamBqhnbND7SVnfRp+bm1m631s8SHM9ISsdXmIt06Ro6oxlugpjXtKuY=
X-Received: by 2002:aa7:d550:: with SMTP id u16mr2532230edr.147.1605226229859; Thu, 12 Nov 2020 16:10:29 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: "Y. Richard Yang" <>
Date: Thu, 12 Nov 2020 19:10:18 -0500
Message-ID: <>
Content-Type: multipart/mixed; boundary="000000000000376e5b05b3f1dbbb"
Archived-At: <>
Subject: Re: [alto] ALTO recharter update: ALTO services in multi-domain settings
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Nov 2020 00:10:34 -0000

Dear ALTOers,

Please see attached an updated version of the slides intended to contribute
to the multidomain item. The slides are team efforts. Any feedback,
comments, suggestions are highly welcome. We see that alternative designs
such as architectures are feasible as well, but we want to post the initial
design to make clear the problem and feasibility.


On Tue, Nov 10, 2020 at 4:12 PM Y. Richard Yang <> wrote:

> Dear ALTOers,
> One item which we discussed this morning during our weekly meeting is ALTO
> extension to multi-domain settings. Please see attached for the deck of
> slides that we used.
> At a high level, it tried to extend ALTO into a multi-domain setting for
> one of the most basic ALTO services --- endpoint cost services. One item
> which was raised, but not included in the slides is to make clear the use
> cases, i.e., how the multiple-domain information is used. We sure will
> update soon, before and during the WG meeting. Any questions and/or
> comments are highly welcome.
> Richard