Real-time Transport Object delivery over Unidirectional Transport (ROUTE)
draft-zia-route-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-20 (latest revision 2020-06-29)
Stream ISE
Intended RFC status Informational
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream ISE state Submission Received
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>
Internet Draft                                               Waqar Zia,
                                                     Thomas Stockhammer
Intended status: Informational                    Qualcomm Incorporated
Expires: December 2020                                    June 29, 2020

     Real-time Transport Object delivery over Unidirectional Transport
                                  (ROUTE)
                          draft-zia-route-00.txt

Status of this Memo

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

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008. The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on December 29, 2020.

Copyright Notice

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

Zia, et al.           Expires December 29, 2020                [Page 1]
Internet-Draft                  ROUTE                         June 2020

   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.

Abstract

   The Real-time Transport Object delivery over Unidirectional Transport
   protocol (ROUTE Protocol) is specified for robust delivery of
   application objects, including application objects with real-time
   delivery constraints, to receivers over a unidirectional transport.
   Application objects consist of data that has meaning to applications
   that use the ROUTE Protocol for delivery of data to receivers, for
   example, it can be a file, or a DASH or HLS segment, a WAV audio
   clip, etc. The ROUTE Protocol also supports low-latency streaming
   applications.

   The ROUTE Protocol is suitable for unicast, broadcast, and multicast
   transport. Therefore, it can be run over IP/UDP including multicast
   IP. ROUTE Protocol can leverage the features of the underlying
   protocol layer, e.g. to provide security it can leverage IP security
   protocols such as IPSec.

Conventions used in this document

   In examples, "C:" and "S:" indicate lines sent by the client and
   server respectively.

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

Table of Contents

   1. Introduction...................................................4
      1.1. Overview..................................................4
      1.2. Protocol Stack for ROUTE..................................5
      1.3. Data Model................................................5
      1.4. Architecture and Scope of Specification...................6
   2. ROUTE Packet Format............................................7
      2.1. Packet Structure and Header Fields........................7

Zia, et al.           Expires December 29, 2020                [Page 2]
Internet-Draft                  ROUTE                         June 2020

      2.2. LCT header extensions.....................................9
      2.3. FEC Payload ID for Source Flows..........................10
      2.4. FEC Payload ID for Repair Flows..........................10
Show full document text