[alto] Last Call: <draft-ietf-alto-new-transport-14.txt> (The ALTO Transport Information Publication Service) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 22 September 2023 16:07 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: alto-chairs@ietf.org, alto@ietf.org, draft-ietf-alto-new-transport@ietf.org, martin.h.duke@gmail.com, mohamed.boucadair@orange.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169539885509.14791.8732583830155173306@ietfa.amsl.com>
Date: Fri, 22 Sep 2023 09:07:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Ou5tqL48FmgTUytl-uUZVJQsQAE>
Subject: [alto] Last Call: <draft-ietf-alto-new-transport-14.txt> (The ALTO Transport Information Publication Service) to Proposed Standard

The IESG has received a request from the Application-Layer Traffic
Optimization WG (alto) to consider the following document: - 'The ALTO
Transport Information Publication Service'
  <draft-ietf-alto-new-transport-14.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-10-06. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for
   the simple, sequential request-reply use case, in which an ALTO
   client requests a sequence of information resources, and the server
   responds with the complete content of each resource one at a time.

   ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895)
   defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO
   server can incrementally push resource updates to clients whenever
   monitored network information resources change, allowing the clients
   to monitor multiple resources at the same time.  However, HTTP/2 and
   later versions already support concurrent, non-blocking transport of
   multiple streams in the same HTTP connection.

   To take advantage of newer HTTP features, this document introduces
   the ALTO Transport Information Publication Service (TIPS).  TIPS uses
   an incremental RESTful design to give an ALTO client the new
   capability to explicitly, concurrently (non-blocking) request (pull)
   specific incremental updates using native HTTP/2 or HTTP/3, while
   still functioning for HTTP/1.1.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/



No IPR declarations have been submitted directly on this I-D.

[alto] Last Call: <draft-ietf-alto-new-transport-… The IESG