[alto] Last Call: <draft-ietf-alto-incr-update-sse-20.txt> (ALTO Incremental Updates Using Server-Sent Events (SSE)) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Fri, 21 February 2020 14:30 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: alto@ietf.org
Delivered-To: alto@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (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 <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.118.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: draft-ietf-alto-incr-update-sse@ietf.org, alto@ietf.org, ietf@kuehlewind.net, Vijay Gurbani <vijay.gurbani@gmail.com>, alto-chairs@ietf.org, vkg@bell-labs.com
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <158229544925.29013.11717078554260380436.idtracker@ietfa.amsl.com>
Date: Fri, 21 Feb 2020 06:30:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/7u_rChnep-b7P6u5adnijSlQEyU>
Subject: [alto] Last Call: <draft-ietf-alto-incr-update-sse-20.txt> (ALTO Incremental Updates Using Server-Sent Events (SSE)) to Proposed Standard
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=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 last-call@ietf.org mailing lists by 2020-03-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 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 https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/ballot/ No IPR declarations have been submitted directly on this I-D.