Last Call: <draft-ietf-alto-incr-update-sse-20.txt> (ALTO Incremental Updates Using Server-Sent Events (SSE)) to Proposed Standard

The IESG <> Fri, 21 February 2020 14:30 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 4FB3812003F; Fri, 21 Feb 2020 06:30:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-alto-incr-update-sse-20.txt> (ALTO Incremental Updates Using Server-Sent Events (SSE)) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.118.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:,,, Vijay Gurbani <>,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Fri, 21 Feb 2020 06:30:49 -0800
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 21 Feb 2020 14:30:50 -0000

The IESG has received a request from the Application-Layer Traffic
Optimization WG (alto) to consider the following document: - 'ALTO
Incremental Updates Using Server-Sent Events (SSE)'
  <draft-ietf-alto-incr-update-sse-20.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 mailing lists by 2020-03-06. Exceptionally, comments may
be sent to instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   The Application-Layer Traffic Optimization (ALTO) [RFC7285] protocol
   provides network related information, called network information
   resources, to client applications so that clients can make informed
   decisions in utilizing network resources.  For example, an ALTO
   server can provide network and cost maps so that an ALTO client can
   use the maps to determine the costs between network endpoints when
   choosing communicating endpoints.

   However, the ALTO protocol does not define a mechanism to allow an
   ALTO client to obtain updates to the information resources, other
   than by periodically re-fetching them.  Because some information
   resources (e.g., the aforementioned maps) may be large (potentially
   tens of megabytes), and because only parts of the information
   resources may change frequently (e.g., only some entries in a cost
   map), complete re-fetching can be inefficient.

   This document presents a mechanism to allow an ALTO server to push
   updates to ALTO clients, to achieve two benefits: (1) updates can be
   incremental, in that if only a small s ection of an information
   resource changes, the ALTO server can send just the changes; and (2)
   updates can be immediate, in that the ALTO server can send updates as
   soon as they are available.

The file can be obtained via

IESG discussion can be tracked via

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