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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-27
Replaced by draft-ietf-alto-incr-update-sse
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO WG                                                         W. Roome
Internet-Draft                                            Alcatel-Lucent
Intended status: Standards Track                                  X. Shi
Expires: April 30, 2015                                          Y. Yang
                                                         Yale University
                                                        October 27, 2014

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

Abstract

   The goal of Application-Layer Traffic Optimization (ALTO) [RFC7285]
   is to bridge the gap between network and applications by providing
   network related information to non-priviledged, application-level
   clients.  This allows applications to make informed decisions, for
   example when selecting a target host from a set of candidates.

   Therefore an ALTO Server provides network and cost maps to its
   clients.  However, those maps can be very large, and portions of
   those maps may change frequently (cost maps in particular).

   This draft presents a method to provide incremental updates for these
   maps.  The goal is to reduce the load on the ALTO Client and Server
   by transmitting just the updated portions of those maps.

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

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

Roome, et al.            Expires April 30, 2015                 [Page 1]
Internet-Draft          ALTO Incremental Updates            October 2014

   This Internet-Draft will expire on April 30, 2015.

Copyright Notice

   Copyright (c) 2014 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.

Roome, et al.            Expires April 30, 2015                 [Page 2]
Internet-Draft          ALTO Incremental Updates            October 2014

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Incremental Update Message Format  . . . . . . . . . . . . . .  4
     2.1.  JSON Merge Patch . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  JSON Merge Patch Applied to Network Map Messages . . . . .  5
     2.3.  JSON Merge Patch Applied to Cost Map Messages  . . . . . .  7
   3.  Server-Sent Events . . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  Overview of SSEs . . . . . . . . . . . . . . . . . . . . .  8
     3.2.  ALTO SSE Update Messages . . . . . . . . . . . . . . . . .  9
     3.3.  Keep-Alive Messages  . . . . . . . . . . . . . . . . . . . 10
   4.  Update Stream Service  . . . . . . . . . . . . . . . . . . . . 10
     4.1.  Media Type . . . . . . . . . . . . . . . . . . . . . . . . 10
     4.2.  HTTP Method  . . . . . . . . . . . . . . . . . . . . . . . 10
     4.3.  Accept Input Parameters  . . . . . . . . . . . . . . . . . 10
     4.4.  Capabilities . . . . . . . . . . . . . . . . . . . . . . . 10
     4.5.  Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.6.  Event Order Requirements . . . . . . . . . . . . . . . . . 11
     4.7.  Response . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.8.  Client Actions When Receiving Update Messages  . . . . . . 12
   5.  Filtered Update Stream Service . . . . . . . . . . . . . . . . 13
     5.1.  HTTP Method  . . . . . . . . . . . . . . . . . . . . . . . 13
     5.2.  Accept Input Parameters  . . . . . . . . . . . . . . . . . 13
     5.3.  Response . . . . . . . . . . . . . . . . . . . . . . . . . 14
   6.  IRD Example  . . . . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text