Transport Services for Low-Latency Real-Time Applications
draft-mcquistin-taps-low-latency-services-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
TAPS Working Group                                          S. McQuistin
Internet-Draft                                                C. Perkins
Intended status: Informational                     University of Glasgow
Expires: May 4, 2017                                            M. Fayed
                                                  University of Stirling
                                                        October 31, 2016

       Transport Services for Low-Latency Real-Time Applications
              draft-mcquistin-taps-low-latency-services-00

Abstract

   This document describes the set of transport services required by
   low-latency, real-time applications.  These services are derived from
   the needs of the applications, rather than from the current
   capabilities of the transport layer.  An example API, based on the
   Berkeley Sockets API, is also provided, alongside examples of how the
   target applications would use the API to access the transport
   services described.

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 May 4, 2017.

Copyright Notice

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

McQuistin, et al.          Expires May 4, 2017                  [Page 1]
Internet-Draft       Low Latency Transport Services         October 2016

   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
   2.  Low-Latency Transport Services  . . . . . . . . . . . . . . .   3
   3.  Abstract API  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Socket Setup & Teardown . . . . . . . . . . . . . . . . .   5
     3.2.  Socket Options  . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Connection Handling . . . . . . . . . . . . . . . . . . .   6
     3.4.  Timing  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.5.  Messaging . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.6.  Utilities . . . . . . . . . . . . . . . . . . . . . . . .   8
     3.7.  Design Assumptions  . . . . . . . . . . . . . . . . . . .   8
   4.  Example Usage . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  HTTP/1.1  . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  HTTP/2  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Real-Time Multimedia  . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  Informative References  . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The goal of the TAPS working group is to break down the existing
   transport layer into a set of transport services, decoupling these
   from the transport protocols that provide them.  As a result, the
   standardisation of transport services becomes feasible and important.
   The first phase of this process has been to inspect the existing
   transport protocols, and determine the services they provide.  The
   next phase, enabled both by the use of transport services and their
   separation from transport protocols, is to define novel transport
   services based on the needs of applications.  In essence, these
   services are derived from applications by thinking about what the
   transport layer would provide to applications if the constraints of
   the existing transport protocols were not in place.

   This document considers the transport services required by low-
Show full document text