datatracker.ietf.org
Sign in
Version 5.3.1, 2014-04-16
Report a bug

WebSocket-based server-to-client notifications for the Application-Layer Traffic Optimization (ALTO) Protocol
draft-marocco-alto-ws-02

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-14
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Internet Engineering Task Force                               E. Marocco
Internet-Draft                                            Telecom Italia
Intended status: Standards Track                              J. Seedorf
Expires: August 18, 2014                                             NEC
                                                       February 14, 2014

WebSocket-based server-to-client notifications for the Application-Layer
                  Traffic Optimization (ALTO) Protocol
                        draft-marocco-alto-ws-02

Abstract

   The Application-Layer Traffic Optimization (ALTO) protocol is
   designed to allow entities with knowledge about the network
   infrastructure to export such information to applications that need
   to choose one or more endpoints to connect to among large sets of
   logically equivalent ones.  The base protocol specification adopts a
   simple pull-based model, according to which the client retrieves the
   information encoded as JSON objects over HTTP directly from the
   server.

   This document proposes (for discussion) a mechanism for providing
   server-initiated information update notifications through a
   WebSocket-based ALTO protocol extension that easily integrates in the
   basic protocol model.

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 August 18, 2014.

Marocco & Seedorf        Expires August 18, 2014                [Page 1]
Internet-Draft        WebSocket transport for ALTO         February 2014

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Overview of operations  . . . . . . . . . . . . . . . . . . .   4
   3.  Information Resource Directory (IRD) Extensions . . . . . . .   5
     3.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Client-to-server Version Indication . . . . . . . . . . . . .   6
   5.  Partial Updates Encoding  . . . . . . . . . . . . . . . . . .   6
   6.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Application-Layer Traffic Optimization (ALTO) protocol
   [I-D.ietf-alto-protocol] is designed to allow entities with knowledge
   about the network infrastructure to export such information to
   applications that need to choose one or more endpoints to connect to
   among large sets of logically equivalent ones.  The base protocol
   specification adopts a simple pull-based model, according to which
   the client retrieves the information encoded as JSON objects over
   HTTP directly from the server.

   Such a pull-based model is well suited for use cases where the
   information does not change frequently, e.g. when it represents
   network and cost maps intended to provide a hint to peer-to-peer
   applications that have to perform initial peer selection (i.e. the
   primary use case that motivated the specification of the ALTO

Marocco & Seedorf        Expires August 18, 2014                [Page 2]

[include full document text]