Re: [alto] WG Review: ALTO Charter Update Tue, 04 May 2021 12:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 364503A3318; Tue, 4 May 2021 05:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oUxvvf08Xrlm; Tue, 4 May 2021 05:49:43 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id EE57C3A3317; Tue, 4 May 2021 05:49:41 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Tue, 4 May 2021 20:49:34 +0800 (GMT+08:00)
X-Originating-IP: []
Date: Tue, 04 May 2021 20:49:34 +0800
X-CM-HeaderCharset: UTF-8
To: Qin Wu <>
Cc: IETF ALTO <>, "" <>, Zaheduzzaman Sarker <>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.13 build 20210104(ab8c30b6) Copyright (c) 2002-2021 mail
In-Reply-To: <>
References: <>
Content-Type: multipart/alternative; boundary="----=_Part_286552_765895882.1620132574777"
MIME-Version: 1.0
Message-ID: <>
X-Coremail-Locale: en_US
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQAKB138kk+0PQANs0
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VW3Jw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <>
Subject: Re: [alto] WG Review: ALTO Charter Update
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: Tue, 04 May 2021 12:49:48 -0000

Hi Qin and all,

Thanks for sharing the proposal. I just have one comment on the milestones and deliverables:

The last bullet mentioned that "The objective of this discussion will be to determine a small set of use cases that have strong support and a realistic chance of implementation and deployment.". However, the output of this bullet does not seem to be included in the milestones and deliverables. I suggest we change the first sentence of the 1st milestone to

Conduct a survey of working group participants and the wider community to discover ALTO implementation, deployment experience, and future use cases that have strong support and realistic chance of implementation and deployment. 

By the way, the end of the 2nd milestone should be "configuration and management of ALTO servers", right?


2021-04-24 00:05:46"Qin Wu" <>wrote:

Dear Martin and working group,


Thank you for the useful rechartering discussions on the mailing list and at IETF-110.


I have listened to the people who say that further protocol work needs to be based on strong deployment needs, and I also hear very many different use cases proposed. I think we need more discussion and understanding to work out which use cases are high priority and which are more research-based.


This makes me think that we need a small short-term recharter to allow us to work on immediate issues (protocol maintenance, operational support) while we discuss and investigate the best uses cases for further work.


So I propose this as our new charter with input from our AD.


Application-Layer Traffic Optimization Working Group Charter Update

The ALTO working group was established in 2008 to devise a request/response protocol to allow a host to benefit from a server that is more cognizant of the network infrastructure than the host is.

The working group has developed an HTTP-based protocol and recent work has reported proof-of-concepts of ALTO based solutions supporting applications such as content distribution networks (CDN).

To support current and future deployments of ALTO, the working group is now chartered for the following activities:

o Provide a place to collect implementation deployment and experience. It is hoped that implementer and deployers of ALTO will report their experiences on the mailing list, and the working group will track implementation and deployment reports on a wiki or in an Internet-Draft.

o Perform protocol maintenance for the existing published protocol. It is anticipated that questions and issues will arise concerning the existing protocol specifications: The working group will develop and publish updates as necessary to resolve any interoperability, performance, operational, or security, or privacy problems that arise. The working group will also help resolve any errata reports that are raised. This work item might be addressed by discussions and reviews, or might require additional RFCs.

o Develop operational support tools for the ALTO protocol. Based on experience from deployments, the advice in RFC 7971, and considering the latest opinions and techniques from the Operations and Management Area, the working group will develop tools to configure, operate, and manage the ALTO protocol and networks that use ALTO. This may include YANG models and OAM mechanisms. The working group may also update RFC 7971 in the light of new experience and protocol features that were added to ALTO after that RFC was published.

o Support for modern transport protocols. When work on ALTO began, the protocol was supported using HTTP version 1. Since then, the IETF has developed HTTP/2 and HTTP/3. The working group will develop any necessary protocol extensions and guidance to support the use of ALTO over HTTP/2 and HTTP/3.

o Future use cases. The working group will provide a forum to discuss possible future use cases. The objective of this discussion will be to determine a small set of use cases that have strong support and a realistic chance of implementation and deployment. The working group will not develop protocol extensions for these use cases until it has been re-chartered specifically for that purpose.

At the conclusion of the OAM and HTTP2/3 deliverables, plus completion of any adopted drafts emerging from the other work items, the working group will close or recharter.

Milestones and Deliverables:

Conduct a survey of working group participants and the wider community to discover ALTO implementation and deployment experience. Record the results in a publicly visible wiki.
Develop and standardize at least one OAM mechanisms to support ALTO including a YANG model for configuration and management of YANG servers.
Perform an analysis of ALTO over HTTP/2 and HTTP/3 and publish a support document. Develop any necessary protocol modifications.


Please comment here on this draft charter proposal.


-Qin (on behalf of chairs)