Re: [alto] PANRG Lightning Talk at IETF100 on ALTO

Jensen Zhang <> Mon, 04 December 2017 16:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4EB15126BF7 for <>; Mon, 4 Dec 2017 08:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id brGAFuYcCIaw for <>; Mon, 4 Dec 2017 08:40:20 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4003:c0f::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D4CAD124239 for <>; Mon, 4 Dec 2017 08:40:19 -0800 (PST)
Received: by with SMTP id s4so15270100ote.4 for <>; Mon, 04 Dec 2017 08:40:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4sE2XXpJjSRO6iDJ7PyOEvl1rr3GCAXfkZEMC19h5Aw=; b=KQ7xoqccIY7Hq9m7lrJ9mAClXorXnAp3n0E47HU9n24Y4sgCXZvFrD+Zelyje9AMjD Re5h52+3AkYLfIfGUa0NKVvwRsdI3FfM4lKQJ9bfWQmrV92RW62NjQdZT2KS9/Fc1uRZ jYHIkxwKJoMWt3wlTcQK9DGvdFh4o9+xhvlN4wIhG+XHe+zuBUwdwQTGiDqn3CuSMUvP kSCBfMw62JHdZkZS4qsMJ5Bh0kjZHxNbhaOQ/Sse4fv7I9euGdkzi6G77xgiaZB5dnDv 4vVEYbdGMVG5jIA/TrNyeUi/MvztpjO2CptdRnqTzl+sl+zeEG8TU5I9dgsXyKL6E9oq jo3A==
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:cc; bh=4sE2XXpJjSRO6iDJ7PyOEvl1rr3GCAXfkZEMC19h5Aw=; b=P3xyS/fLJmA61FCOgicQD6fJ1fXOw37zGd8HNJYYvNmdL2z33RsC6GFCWPSx+aDAck vu3LilT9U94lCr1mY3FcRLVZVl20RKYB0uL8ntsaL44qRilOvqk09ZJ1ph/fE5FuR7yC vuBOl00cwjL3rid9f5RuOovmIMBlPbbAvHp30FcauED/uYkX857AjiY9YFCkEXp+iXD/ Us6zcLoMxCM7aXesw//HdnW+zUNYkU9GIV7c6TqXnOrC4tt0inF2OJLh2G1bgLqNoKyK KQppxZ5fbrL+k/NmrAJQixphnnsAjyvWEFPl9dAh1RJ919wiP7hK3BBO2iChn40SaoIU /XUg==
X-Gm-Message-State: AJaThX7SodgXDWQtw1U/IvhcUzNrQ45bQpHbJYDytINXQPM6QOGQUHVw wNBQDMApjB5Y+3E1Hl03akaOiE6dRcnDFkQsOIU=
X-Google-Smtp-Source: AGs4zMaaclB7TcB916sOgCKamrh8Tr8TLGi5oh6D8rh7Qit21boeT+rjXhX6WC3hFcFM+yAjXsmXNTfbZiHJedAow88=
X-Received: by with SMTP id m1mr16860965otm.15.1512405619217; Mon, 04 Dec 2017 08:40:19 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Jensen Zhang <>
Date: Mon, 04 Dec 2017 16:40:08 +0000
Message-ID: <>
To: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="001a114343c6b0a36e055f865f4f"
Archived-At: <>
Subject: Re: [alto] PANRG Lightning Talk at IETF100 on ALTO
X-Mailman-Version: 2.1.22
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, 04 Dec 2017 16:40:22 -0000

Hi Sabine,

I also agree that we need to get in touch with PANRG. And really thanks for
your effort in introducing ALTO to PANRG and introducing PANRG to our WG!

I just talk about some of my thinking. "how do endpoints discover
trustworthy path properties?" can also be a basic question for ALTO. In my
opinion, this question should cover three pieces:

- Representation (which is like "How to connect" in your lightning talk
- Storage (which includes "When to connect" in your slides. Currently,
alto-calendar is about it)
- Requirements (rsa, fcs and incr-update-sse are related to it)

I think a lot of previous efforts of ALTO WG focused on the first topic.
But for the goal of PANRG and the future potential use cases, I think
providing the on-demand network information will be more helpful. So maybe
"how to define application requirements" is more important. The legacy ALTO
approach can only support the simple cross-product filter requirement. To
satisfy more requirements, we still need to make more efforts.

btw. Shall we involve some people from PANRG into our coming interim


On Mon, Dec 4, 2017 at 11:32 PM Randriamasy, Sabine (Nokia -
FR/Paris-Saclay) <> wrote:

> Hello ALTO WG,
> At the last IETF, there was a PANRG session during which, as they have
> shown interest in the ALTO work, I gave a lightning talk on ALTO and its
> relevant extensions, see slides at
> The goal of PANRG is to extend path awareness from the control plane to
> the edge with mechanisms allowing: Endpoint discovery of paths, explicit
> association of properties to paths by endpoints, explicit endpoint
> selection of paths. The identified underlying hard problems are mainly:
> conflict of interest between hosts and networks, path property exposition
> by the network to third parties considering network confidentiality and
> information aggregation level, diversity of timescale for configuration,
> discovery, selection and dissemination. The PANRG would like to leverage
> its work on existing IETF protocols and their potential extensions.
> The last presentation was upon a draft by Brian Trammel, one of the RG
> chairs, to open the discussions.
> See the slides at
> Regarding question "how do endpoints discover trustworthy path
> properties?", the slides mention that SCION (a path-aware Internet
> architecture presented at IETF99) and ALTO represent points in this design
> space.
> The other presentations are on
> I think it is worth getting in touch with this RG to see how ALTO can
> serve their goals. As they focus on the mechanisms leveraging on protocols
> rather than on protocols themselves, they may expose use cases motivating
> existing and future protocol extensions and defining needs for particular
> features.
> Cheers,
> Sabine
> _______________________________________________
> alto mailing list