Requirements for Telepresence Multistreams
RFC 7262

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 01
• 02
• 03
• 04
• 05
• 06
• 07

Internet Engineering Task Force (IETF)                        A. Romanow
Request for Comments: 7262                                 Cisco Systems
Category: Informational                                        S. Botzko
ISSN: 2070-1721                                                  Polycom
                                                               M. Barnes
                                        MLB@Realtime Communications, LLC
                                                               June 2014

               Requirements for Telepresence Multistreams

Abstract

   This memo discusses the requirements for specifications that enable
   telepresence interoperability by describing behaviors and protocols
   for Controlling Multiple Streams for Telepresence (CLUE).  In
   addition, the problem statement and related definitions are also
   covered herein.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7262.

Romanow, et al.               Informational                     [Page 1]
RFC 7262             CLUE Telepresence Requirements            June 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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Telepresence systems greatly improve collaboration.  In a
   telepresence conference (as used herein), the goal is to create an
   environment that gives the users a feeling of (co-located) presence
   -- the feeling that a local user is in the same room with other local
   users and remote parties.  Currently, systems from different vendors
   often do not interoperate because they do the same tasks differently,
   as discussed in the Problem Statement section below (see Section 4).

   The approach taken in this memo is to set requirements for a future
   specification(s) that, when fulfilled by an implementation of the
   specification(s), provide for interoperability between IETF protocol-
   based telepresence systems.  It is anticipated that a solution for
   the requirements set out in this memo likely involves the exchange of
   adequate information about participating sites; this information that
   is currently not standardized by the IETF.

   The purpose of this document is to describe the requirements for a
   specification that enables interworking between different SIP-based
   [RFC3261] telepresence systems, by exchanging and negotiating
   appropriate information.  In the context of the requirements in this

Romanow, et al.               Informational                     [Page 2]
RFC 7262             CLUE Telepresence Requirements            June 2014

   document and related solution documents, this includes both point-to-
   point SIP sessions as well as SIP-based conferences as described in
   the SIP conferencing framework [RFC4353] and the SIP-based conference
   control [RFC4579] specifications.  Non-IETF protocol-based systems,
   such as those based on ITU-T Rec. H.323 [ITU.H323], are out of scope.
   These requirements are for the specification, they are not
   requirements on the telepresence systems implementing the solution/
   protocol that will be specified.

   Today, telepresence systems of different vendors can follow radically