SDCP: Streaming Distributed Control Protocol
draft-perez-dispatch-sdcp-01

Document Type Active Internet-Draft (individual)
Last updated 2017-01-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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)
Dispatch                                             C. Perez-Monte, Ed.
Internet-Draft                                              A. Diedrichs
Intended status: Informational                        GridTICs - UTN FRM
Expires: July 6, 2017                                    January 2, 2017

              SDCP: Streaming Distributed Control Protocol
                      draft-perez-dispatch-sdcp-01

Abstract

   This memorandum describes SDCP, a protocol to control multimedia
   streaming in cases where streaming generation should be distributed
   to improve performance.  This is especially useful for Human-Things
   streams.  Usually, real time applications such as virtual reality
   generate a user-controlled multimedia streaming.  This is a time
   continuous data flux that could be divided spatially or temporally to
   distribute processing, memory or network resources.  This protocol
   does not describe streaming communication, but the control of each
   single streaming generation in a best-effort by many nodes or things.

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 July 6, 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

Perez-Monte & Diedrichs   Expires July 6, 2017                  [Page 1]
Internet-Draft                    SDCP                      January 2017

   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 . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Distributed Scheme  . . . . . . . . . . . . . . . . . . . . .   4
   3.  SDCP Constant . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Multicast Addressing  . . . . . . . . . . . . . . . . . .   5
     3.2.  UDP Ports . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  SDCP Format . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  General DB Header . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Specific SDS Header . . . . . . . . . . . . . . . . . . .   7
     4.3.  Payload . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Identificators Format . . . . . . . . . . . . . . . . . . . .   8
     5.1.  SDS index . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Node index  . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Payload types . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Streaming considerations  . . . . . . . . . . . . . . . . . .   9
     7.1.  Streaming protocols . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The amount of information transmitted from human-to-computer (H2C) is
   usually very small.  This is the case of information generated by
   input devices, for example, keyboards, mouses or touch screens.
   Conversely, the amount of information transmitted from computer-to-
   human (C2H) is huge which is increasing over time.  This is the case
   of information generated for output devices, such as computer
Show full document text