SPAWN use cases
draft-bernardos-spawn-use-cases-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-25
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)
SPAWN                                                    G. Papadopoulos
Internet-Draft                                            IMT Atlantique
Intended status: Standards Track                              P. Thubert
Expires: September 26, 2019                                        Cisco
                                                            F. Theoleyre
                                                                    CNRS
                                                           CJ. Bernardos
                                                                    UC3M
                                                          March 25, 2019

                            SPAWN use cases
                   draft-bernardos-spawn-use-cases-00

Abstract

   The wireless medium presents significant specific challenges to
   achieve properties similar to those of wired deterministic networks.
   At the same time, a number of use cases cannot be solved with wires
   and justify the extra effort of going wireless.  This document
   presents some of these use-cases.

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 https://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 September 26, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Papadopoulos, et al.   Expires September 26, 2019               [Page 1]
Internet-Draft          SPAWN use cases scenarios             March 2019

   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
   2.  Amusement Parks . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Use Case Description  . . . . . . . . . . . . . . . . . .   4
     2.2.  Specificities . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  The Need for Wireless . . . . . . . . . . . . . . . . . .   5
     2.4.  Asks for SPAWN  . . . . . . . . . . . . . . . . . . . . .   6
   3.  Wireless for Industrial Applications  . . . . . . . . . . . .   6
     3.1.  Use Case Description  . . . . . . . . . . . . . . . . . .   6
     3.2.  Specificities . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Control Loops . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  Unmeasured Data . . . . . . . . . . . . . . . . . . .   7
     3.3.  The Need for Wireless . . . . . . . . . . . . . . . . . .   7
     3.4.  Asks for SPAWN  . . . . . . . . . . . . . . . . . . . . .   8
   4.  Pro Audio and Video . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Use Case Description  . . . . . . . . . . . . . . . . . .   8
     4.2.  Specificities . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  The Need for Wireless . . . . . . . . . . . . . . . . . .   9
     4.4.  Asks for SPAWN  . . . . . . . . . . . . . . . . . . . . .   9
   5.  UAV control . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Use Case Description  . . . . . . . . . . . . . . . . . .   9
     5.2.  Specificities . . . . . . . . . . . . . . . . . . . . . .   9
     5.3.  The Need for Wireless . . . . . . . . . . . . . . . . . .  10
     5.4.  Asks for SPAWN  . . . . . . . . . . . . . . . . . . . . .  10
   6.  Edge Robotics control . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Use Case Description  . . . . . . . . . . . . . . . . . .  10
     6.2.  Specificities . . . . . . . . . . . . . . . . . . . . . .  11
     6.3.  The Need for Wireless . . . . . . . . . . . . . . . . . .  11
     6.4.  Asks for SPAWN  . . . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text