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

"Y. Richard Yang" <> Mon, 16 November 2020 20:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 47C0A3A13C4 for <>; Mon, 16 Nov 2020 12:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.576
X-Spam-Status: No, score=0.576 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_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=1.964] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SrO-ng2IU2Yo for <>; Mon, 16 Nov 2020 12:14:43 -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 30A163A13C1 for <>; Mon, 16 Nov 2020 12:14:43 -0800 (PST)
Received: by with SMTP id h23so21563110ljg.13 for <>; Mon, 16 Nov 2020 12:14:43 -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=ggF/g0TvAq3iuTebPXVm8cbCE6g3HXtKM3PlKt9Y/tE=; b=nyAeZy09fWck/Qnp5kWXf9pTSYKh+g1yBFm0QH+/dOsk6F1roarRHa6N6ybLPChnWC /zGqBLFVze8IeOBTRfwL9bSsKtRfsE4KSjXNJAZLdFj6Qhr2fdFpRjjs4BGGsbEf21Ma UrRaN+hAtoCn2Y8+QTXmmOBHqvjE/IqbnTl+at8kpqMv3yn8lF1GcaEzvO+jxBQAPfSg 5TSDHo27ewWgwL5Jg2xmLBlLKcXRXh8zy+glPIOpAXuWdj0AcMhs/FvCJVptkDZrddvv XBcGW3Pz7ttQ1mKpHBHAbMvK2jaGWHWunjH7KW+7wgqFcQaWyY67obAy6/IvA2SZ3taG 3f6w==
X-Gm-Message-State: AOAM53043Y+w2wGk5qKNla4M7au11SIlBw/crVOQNOVxlISCNNU0T7kE WJZZLtW9O5nhFVYMVNSjBRZST4BrT/XZ7jZH5+3CvTVqkXCKrg==
X-Google-Smtp-Source: ABdhPJzSkl9fHkyqq+0pQJM2x5l5/yv9Xn5KkB6pYpiFkLJ7HCv+PuTAZYfdC0Z8v58c7i/tL/+gnxWeQ0wSfbnNhNw=
X-Received: by 2002:a05:651c:502:: with SMTP id o2mr397053ljp.318.1605557680614; Mon, 16 Nov 2020 12:14:40 -0800 (PST)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: "Y. Richard Yang" <>
Date: Mon, 16 Nov 2020 15:14:29 -0500
Message-ID: <>
Content-Type: multipart/alternative; boundary="00000000000038312105b43f07c4"
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: Mon, 16 Nov 2020 20:14:51 -0000

Addressing some comments I received and following the same format as Sabine
did, I post the paragraph below:

Extension of ALTO services to support multi-domain settings. The current
ALTO framework focuses on providing network information from a single ALTO
server for a single network (administrative domain), but the network
devices traversed by a flow can be managed by multiple networks not in the
same domain. The working group will investigate and extend the ALTO
framework to (1) enumerate the issues of ALTO services involving network
paths spanning multiple domains with multiple ALTO servers, and (2)
introduce capabilities to query ALTO services for the settings. The working
group should specify complete ALTO multi-domain services, by using existing
services whenever possible. The working group should consider realistic
complexities including incremental deployment, dynamicity, core security
issues including access control, authorization (e.g., an ALTO server
provides information for a network that the server has no authorization),
and privacy protection in multi-domain settings.

Additional info will be discussed in the slides to be discussed in the
weekly meeting tomorrow and then during the meeting later this week.

Any comments are highly welcome.


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

> 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.
> Thanks!
> Richard
> 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

| Y. Richard Yang <>   |
| Professor of Computer Science       |
|        |