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

The information below is for an old version of the document
Document Type Active Internet-Draft (rtcweb WG)
Last updated 2014-02-06
Replaces draft-holmberg-rtcweb-ucreqs
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state In WG Last Call (wg milestone: Feb 2014 - Send Use Cases docum... )
Revised I-D Needed - Issue raised by WG
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2014-01-16)
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
RTCWEB Working Group                                         C. Holmberg
Internet-Draft                                              S. Hakansson
Intended status: Informational                               G. Eriksson
Expires: August 10, 2014                                        Ericsson
                                                        February 6, 2014

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

Abstract

   This document describes web based real-time communication use-cases.
   Requirements on the browser functionality are derived from the 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 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 August 10, 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.

Holmberg, et al.         Expires August 10, 2014                [Page 1]
Internet-Draft                   RTC-Web                   February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Use-cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Common requirements . . . . . . . . . . . . . . . . . . .   4
     3.3.  Browser-to-browser use-cases  . . . . . . . . . . . . . .   4
       3.3.1.  Simple Video Communication Service  . . . . . . . . .   4
       3.3.2.  Simple Video Communication Service, NAT/Firewall that
               blocks UDP  . . . . . . . . . . . . . . . . . . . . .   5
       3.3.3.  Simple Video Communication Service, Firewall that
               only allows traffic via a HTTP Proxy  . . . . . . . .   5
       3.3.4.  Simple Video Communication Service, global service
               provider  . . . . . . . . . . . . . . . . . . . . . .   5
       3.3.5.  Simple Video Communication Service, enterprise
               aspects . . . . . . . . . . . . . . . . . . . . . . .   6
       3.3.6.  Simple Video Communication Service, access change . .   7
       3.3.7.  Simple Video Communication Service, QoS . . . . . . .   7
       3.3.8.  Simple Video Communication Service with screen
               sharing . . . . . . . . . . . . . . . . . . . . . . .   8
       3.3.9.  Simple Video Communication Service with file exchange   8
       3.3.10. Hockey Game Viewer  . . . . . . . . . . . . . . . . .   8
       3.3.11. Multiparty video communication  . . . . . . . . . . .   9
       3.3.12. Multiparty on-line game with voice communication  . .  10
     3.4.  Browser - GW/Server use cases . . . . . . . . . . . . . .  10
       3.4.1.  Telephony terminal  . . . . . . . . . . . . . . . . .  11
       3.4.2.  Fedex Call  . . . . . . . . . . . . . . . . . . . . .  11
       3.4.3.  Video conferencing system with central server . . . .  11
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.2.  Browser requirements  . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     6.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .  16
     6.2.  Browser Considerations  . . . . . . . . . . . . . . . . .  16
     6.3.  Web Application Considerations  . . . . . . . . . . . . .  17
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  17
   8.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  17
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  23
   Appendix A.  API requirements . . . . . . . . . . . . . . . . . .  23
Show full document text