ALTO Incremental Updates Using Server-Sent Events (SSE)
draft-ietf-alto-incr-update-sse-22

Document Type Active Internet-Draft (alto WG)
Last updated 2020-03-26 (latest revision 2020-03-20)
Replaces draft-roome-alto-incr-update-sse
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Vijay Gurbani
Shepherd write-up Show (last changed 2020-02-13)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Mirja K├╝hlewind
Send notices to "Vijay Gurbani" <vijay.gurbani@gmail.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state Waiting on Authors
RFC Editor RFC Editor state EDIT
ALTO WG                                                         W. Roome
Internet-Draft                                           Nokia Bell Labs
Intended status: Standards Track                                 Y. Yang
Expires: September 21, 2020                              Yale University
                                                          March 20, 2020

        ALTO Incremental Updates Using Server-Sent Events (SSE)
                   draft-ietf-alto-incr-update-sse-22

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.  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 section 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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119][RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 21, 2020.

Roome & Yang           Expires September 21, 2020               [Page 1]
Internet-Draft          ALTO Incremental Updates              March 2020

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Incremental Encoding: JSON Merge Patch  . . . . . . . . .   6
       3.1.1.  JSON Merge Patch Encoding . . . . . . . . . . . . . .   6
       3.1.2.  JSON Merge Patch ALTO Messages  . . . . . . . . . . .   7
     3.2.  Incremental Encoding: JSON Patch  . . . . . . . . . . . .  10
       3.2.1.  JSON Patch Encoding . . . . . . . . . . . . . . . . .  11
       3.2.2.  JSON Patch ALTO Messages  . . . . . . . . . . . . . .  11
     3.3.  Multiplexing and Server Push: HTTP/2  . . . . . . . . . .  13
     3.4.  Server Push: Server-Sent Event  . . . . . . . . . . . . .  14
   4.  Overview of Approach and High-level Protocol Message Flow . .  15
     4.1.  Update Stream Service Message Flow  . . . . . . . . . . .  16
     4.2.  Stream Control Service Message Flow . . . . . . . . . . .  17
     4.3.  Service Announcement and Management Message Flow  . . . .  18
   5.  Update Messages: Data Update and Control Update Messages  . .  19
     5.1.  Generic ALTO Update Message Structure . . . . . . . . . .  19
     5.2.  ALTO Data Update Message  . . . . . . . . . . . . . . . .  19
     5.3.  ALTO Control Update Message . . . . . . . . . . . . . . .  21
   6.  Update Stream Service . . . . . . . . . . . . . . . . . . . .  22
     6.1.  Media Type  . . . . . . . . . . . . . . . . . . . . . . .  22
     6.2.  HTTP Method . . . . . . . . . . . . . . . . . . . . . . .  22
     6.3.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .  22
     6.4.  Uses  . . . . . . . . . . . . . . . . . . . . . . . . . .  23
     6.5.  Request: Accept Input Parameters  . . . . . . . . . . . .  23
     6.6.  Response  . . . . . . . . . . . . . . . . . . . . . . . .  25
     6.7.  Additional Requirements on Update Stream Service  . . . .  27
Show full document text