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

Document Type Active Internet-Draft (alto WG)
Last updated 2017-03-12
Replaces draft-roome-alto-incr-update-sse
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Vijay Gurbani
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Vijay Gurbani" <vkg@bell-labs.com>
ALTO WG                                                         W. Roome
Internet-Draft                                           Nokia Bell Labs
Intended status: Standards Track                                 Y. Yang
Expires: September 13, 2017                       Tongji/Yale University
                                                          March 12, 2017

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

Abstract

   The Application-Layer Traffic Optimization (ALTO) [RFC7285] protocol
   provides network related information to client applications so that
   clients may make informed decisions.  To that end, an ALTO Server
   provides Network and Cost Maps.  Using those maps, an ALTO Client can
   determine the costs between endpoints.

   However, the ALTO protocol does not define a mechanism to allow an
   ALTO client to obtain updates to those maps, other than by
   periodically re-fetching them.  Because the maps may be large
   (potentially tens of megabytes), and because only parts of the maps
   may change frequently (especially Cost Maps), that can be extremely
   inefficient.

   Therefore this document presents a mechanism to allow an ALTO Server
   to provide updates to ALTO Clients.  Updates can be both immediate,
   in that the server can send updates as soon as they are available,
   and incremental, in that if only a small section of a map changes,
   the server can send just the changes.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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

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

   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 13, 2017.

Copyright Notice

   Copyright (c) 2017 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.  Overview of Approach  . . . . . . . . . . . . . . . . . . . .   4
   3.  Changes Since Version -01 . . . . . . . . . . . . . . . . . .   5
   4.  Overview of Server-Sent Events (SSEs) . . . . . . . . . . . .   5
   5.  Incremental Update Message Format . . . . . . . . . . . . . .   6
     5.1.  Overview of JSON Merge Patch  . . . . . . . . . . . . . .   7
     5.2.  JSON Merge Patch Applied to Network Map Messages  . . . .   8
     5.3.  JSON Merge Patch Applied to Cost Map Messages . . . . . .  10
   6.  ALTO Event Stream . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  ALTO Event Format . . . . . . . . . . . . . . . . . . . .  11
     6.2.  ALTO Update Events  . . . . . . . . . . . . . . . . . . .  12
     6.3.  ALTO Control Events . . . . . . . . . . . . . . . . . . .  12
   7.  Update Stream Service . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Media Type  . . . . . . . . . . . . . . . . . . . . . . .  13
     7.2.  HTTP Method . . . . . . . . . . . . . . . . . . . . . . .  13
     7.3.  Accept Input Parameters . . . . . . . . . . . . . . . . .  13
     7.4.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .  15
     7.5.  Uses  . . . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.6.  Response  . . . . . . . . . . . . . . . . . . . . . . . .  16
       7.6.1.  Keep-Alive Messages . . . . . . . . . . . . . . . . .  16
Show full document text