datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Web Real-Time Communication Use-cases and Requirements
draft-ietf-rtcweb-use-cases-and-requirements-10

Active Internet-Draft (rtcweb WG)
Document Stream: IETF
Last updated: 2012-12-19
Replaces: draft-holmberg-rtcweb-ucreqs
Intended RFC status: (None)
Other versions: plain text, xml, pdf, html

IETF State: In WG Last Call (rtcweb)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

RTCWEB Working Group                                         C. Holmberg
Internet-Draft                                              S. Hakansson
Intended status: Informational                               G. Eriksson
Expires: June 22, 2013                                          Ericsson
                                                       December 19, 2012

         Web Real-Time Communication Use-cases and Requirements
          draft-ietf-rtcweb-use-cases-and-requirements-10.txt

Abstract

   This document describes web based real-time communication use-cases.
   Based on the use-cases, the document also derives requirements
   related to the browser, and the API used by web applications to
   request and control media stream and data exchange services provided
   by the browser.

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 22, 2013.

Copyright Notice

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

Holmberg, et al.          Expires June 22, 2013                 [Page 1]
Internet-Draft                   RTC-Web                   December 2012

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Use-cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . .  4
     4.2.  Browser-to-browser use-cases . . . . . . . . . . . . . . .  5
       4.2.1.  Simple Video Communication Service . . . . . . . . . .  5
       4.2.2.  Simple Video Communication Service, NAT/FW that
               blocks UDP . . . . . . . . . . . . . . . . . . . . . .  6
       4.2.3.  Simple Video Communication Service, FW that only
               allows http  . . . . . . . . . . . . . . . . . . . . .  6
       4.2.4.  Simple Video Communication Service, global service
               provider . . . . . . . . . . . . . . . . . . . . . . .  6
       4.2.5.  Simple Video Communication Service, enterprise
               aspects  . . . . . . . . . . . . . . . . . . . . . . .  7
       4.2.6.  Simple Video Communication Service, access change  . .  8
       4.2.7.  Simple Video Communication Service, QoS  . . . . . . .  8
       4.2.8.  Simple Video Communication Service with sharing  . . .  9
       4.2.9.  Simple Video Communication Service with file
               exchange . . . . . . . . . . . . . . . . . . . . . . .  9
       4.2.10. Simple video communication service with
               inter-operator calling . . . . . . . . . . . . . . . .  9
       4.2.11. Hockey Game Viewer . . . . . . . . . . . . . . . . . . 10
       4.2.12. Multiparty video communication . . . . . . . . . . . . 11
       4.2.13. Multiparty on-line game with voice communication . . . 12
       4.2.14. Distributed Music Band . . . . . . . . . . . . . . . . 12
     4.3.  Browser - GW/Server use cases  . . . . . . . . . . . . . . 13
       4.3.1.  Telephony terminal . . . . . . . . . . . . . . . . . . 13
       4.3.2.  Fedex Call . . . . . . . . . . . . . . . . . . . . . . 14
       4.3.3.  Video conferencing system with central server  . . . . 14
   5.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 15
     5.1.  General  . . . . . . . . . . . . . . . . . . . . . . . . . 15
     5.2.  Browser requirements . . . . . . . . . . . . . . . . . . . 15
     5.3.  API requirements . . . . . . . . . . . . . . . . . . . . . 19
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 21