HI Ben,
I edited the H/2 and 3 bullet to read as follows:
o Support for modern transport protocols. ALTO only uses the capabilities
of HTTP version 1. While ALTO can operate successfully over any version of
HTTP, it would benefit from leveraging HTTP/2 and HTTP/3 capabilities such
as push. The WG
Hi Lars,
I'm initiating a discussion about the value of the document deliverables in
the charter. Meanwhile, I've already edited the charter to be a little more
explicit why the routing WG activities are called out in the text.
Thanks for your comments.
On Thu, Aug 26, 2021 at 7:46 AM Peng Liu
Hi Eric, I've edited the charter to reflect your concerns.
On Thu, Aug 26, 2021 at 5:48 AM Qin Wu wrote:
> Thanks Eric, see comments inline below.
> -邮件原件-
> >发件人: Éric Vyncke via Datatracker [mailto:nore...@ietf.org]
> >发送时间: 2021年8月26日 14:06
> >收件人: The IESG
> >抄送: alto-cha...@ietf.or
Hi Zahed,
The original use case for ALTO -- peer to peer -- is largely dead. The
current charter's work supports the new CDN Interconnect use case.
It is too early to see how this affects adoption of ALTO, and I'm not
convinced we understand the current level of ALTO adoption.
So, this charter f
Reviewer: Thomas Fossati
Review result: Ready with Nits
# Abstract
I suggest to slightly increase the precision:
OLD
[...] This document defines an FCI
protocol using the Application-Layer Traffic Optimization (ALTO)
protocol, following the guidelines defined in RFC 8008.
NEW
[...]
