IANA Registry for RTCWeb Media Constraints
draft-burnett-rtcweb-constraints-registry-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-02
Replaced by draft-ietf-rtcweb-constraints-registry
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)
RTCWEB                                                        D. Burnett
Internet-Draft                                                     Voxeo
Intended status: Standards Track                           March 2, 2012
Expires: September 3, 2012

               IANA Registry for RTCWeb Media Constraints
              draft-burnett-rtcweb-constraints-registry-00

Abstract

   Specifications in W3C's Media Capture Task Force and WebRTC Working
   Group have need of a registry in which to maintain a list of HTML
   Media constraints.  This document defines this registry.

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 September 3, 2012.

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
   described in the Simplified BSD License.

Burnett                 Expires September 3, 2012               [Page 1]
Internet-Draft            constraints-registry                March 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
     3.1.  RTCWeb Media Constraints  . . . . . . . . . . . . . . . . . 3
       3.1.1.  Designated Expert Instructions  . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     5.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6

Burnett                 Expires September 3, 2012               [Page 2]
Internet-Draft            constraints-registry                March 2012

1.  Introduction

   There are two W3C specifications that have need of a registry in
   which to represent constraints: getusermedia: Getting access to local
   devices that can generate multimedia streams
   [W3C.WD-getusermedia-2012xxxx] and WebRTC 1.0: Real-time
   Communication Between Browsers [W3C.WD-webrtc-20120209].  In the
   former, the getUserMedia() method on the NavigatorUserMedia interface
   takes an "options" argument (which may be renamed "constraints").  In
   the latter, the addMedia() method on the PeerConnection interface
   takes a "hints" parameter (soon to be renamed "constraints").  Both
   of these parameters make use of a data structure representing a list
   of constraints on the HTML media or media connection to be
   established.  Additionally, both specifications also (will soon)
   define getCapabilities() methods that are used to query the web
   browser about its capabilities.  The returned data structure
   specifies the browser's capabilities in terms of constraints that it
   can satisfy.  The data structures and their use are defined in the
   aforementioned specifications.  This document specifies the registry
   used to define individual constraint names, their allowed values, and
   their meanings.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text