datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Requirements for Telepresence Multi-Streams
draft-ietf-clue-telepresence-requirements-07

Document type: Active Internet-Draft (clue WG)
Document stream: IETF
Last updated: 2014-03-01 (latest revision 2013-12-12)
Intended RFC status: Informational
Other versions: plain text, xml, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Yes
Document shepherd: Paul Kyzivat
Shepherd Write-Up: Last changed 2013-10-30

IESG State: RFC Ed Queue
IANA Review State: IANA OK - No Actions Needed
IANA Action State: No IC
RFC Editor State: EDIT
Responsible AD: Gonzalo Camarillo
Send notices to: clue-chairs@tools.ietf.org, draft-ietf-clue-telepresence-requirements@tools.ietf.org

CLUE WG                                                       A. Romanow
Internet-Draft                                             Cisco Systems
Intended status: Informational                                 S. Botzko
Expires: June 15, 2014                                         M. Barnes
                                                                 Polycom
                                                       December 12, 2013

              Requirements for Telepresence Multi-Streams
            draft-ietf-clue-telepresence-requirements-07.txt

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 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 June 15, 2014.

Copyright Notice

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

Romanow, et al.           Expires June 15, 2014                 [Page 1]
Internet-Draft       CLUE Telepresence Requirements        December 2013

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Problem Statement  . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   9.  Informative References . . . . . . . . . . . . . . . . . . . . 11
   Appendix A.  Changes From Earlier Versions . . . . . . . . . . . . 12
     A.1.  Changes from draft -06 . . . . . . . . . . . . . . . . . . 12
     A.2.  Changes from draft -05 . . . . . . . . . . . . . . . . . . 12
     A.3.  Changes from draft -04 . . . . . . . . . . . . . . . . . . 13
     A.4.  Changes from draft -03 . . . . . . . . . . . . . . . . . . 13
     A.5.  Changes from draft -02 . . . . . . . . . . . . . . . . . . 13
     A.6.  Changes from draft -01 . . . . . . . . . . . . . . . . . . 13
     A.7.  Changes From Draft -00 . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Romanow, et al.           Expires June 15, 2014                 [Page 2]
Internet-Draft       CLUE Telepresence Requirements        December 2013

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

   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

[include full document text]