One document matched: draft-ietf-rtcweb-constraints-registry-02.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc5234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml">
<!ENTITY rfc5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<?rfc compact="yes"?>
<?rfc toc="yes"?>
<rfc category="std" docName="draft-ietf-rtcweb-constraints-registry-02"
     ipr="trust200902">
  <front>
    <title abbrev="constraints-registry">IANA Registry for RTCWeb
    Constrainable Properties</title>

    <author fullname="Daniel C. Burnett" initials="D." surname="Burnett">
      <organization>Aspect Software, Inc.</organization>

      <address>
        <postal>
          <street>189 South Orange Ave. #1000</street>

          <city>Orlando</city>

          <region>FL</region>

          <code>32801</code>

          <country>USA</country>
        </postal>

        <email>dburnett@voxeo.com</email>
      </address>
    </author>

    <date day="9" month="March" year="2015" />

    <area>Real-time Applications and Infrastructure</area>

    <workgroup>RTCWEB</workgroup>

    <abstract>
      <t>Specifications in W3C's Media Capture Task Force and WebRTC Working
      Group have need of a registry in which to maintain a list of
      constrainable properties for HTML media and other constrainable objects.
      This document defines this registry.</t>
    </abstract>
  </front>

  <middle>
    <section anchor="sec.introduction" title="Introduction">
      <t>There is currently one W3C specification (<xref
      target="W3C.WD-mediacapture-streams-20150212">Media Capture and
      Streams</xref>) that has need of a registry in which to represent
      constrainable properties, and it is expected that others will as well.
      The specification makes use of a data structure representing a list of
      constraints on the HTML media or media connection to be established.
      Additionally, the specification defines 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 as the
      Constrainable Pattern in the aforementioned specification. This document
      specifies the registry used to define individual constrainable property
      names, their allowed values, and their meanings.</t>
    </section>

    <section title="Requirements Language">
      <t>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 <xref target="RFC2119">
      RFC 2119</xref>.</t>
    </section>

    <section anchor="sec.iana" title="IANA Considerations">
      <t>This document defines a registry "RTCWeb Constrainable Properties"
      for use by W3C specifications needing to indicate constrainable
      properties on HTML Media and other constrainable objects, both as used
      by web application authors to indicate preferences and as used by web
      browsers to indicate constrainable properties they can satisfy.</t>

      <section anchor="sec.registry.mediacon"
               title="RTCWeb Constrainable Properties">
        <t>IANA SHALL create a new name space of "RTCWeb Constrainable
        Properties". All maintenance within and additions to the contents of
        this name space MUST be according to the "Specification Required with
        Expert Review" registration policy as defined in <xref
        target="RFC5226">RFC5226</xref>. The registry is initially empty. The
        registry is defined in the remainder of this section.</t>

        <t>Each registry entry consists of a Name and a Reference (or list of
        references).</t>

        <t>An RTCWeb Constrainable Property Name MUST satisfy the following
        <xref target="RFC5234">ABNF</xref> specification:</t>

        <figure>
          <artwork><![CDATA[
rtcweb-constrainable-property = constrainable-property-name 
constrainable-property-name   = %x41-5A 0*constraint-char
constraint-char               = ALPHA / DIGIT

]]></artwork>
        </figure>

        <t>RTCWeb Constrainable Property Names are case-sensitive.</t>

        <t>A registration request MUST include the following information:</t>

        <t><list style="symbols">
            <t>The RTCWeb Constrainable Property Name to be registered</t>

            <t>Name and Email address of a contact person for the
            registration</t>

            <t>Organization or individuals having the change control</t>

            <t>Reference(s) to the specification(s) defining the property</t>
          </list></t>

        <section title="Designated Expert Instructions">
          <t>RTCWeb Constrainable Property Names are of unlimited length
          according to the syntax. However, it is RECOMMENDED that they be no
          longer than 80 characters in total. This is to keep them reasonable
          for humans to read and use. It is RECOMMENDED that Names use camel
          case, i.e., when a Name consists of multiple words, the first
          character of each word SHOULD be an uppercase character, with all
          others being lowercase.</t>

          <t>The References MUST define the following for each RTCWeb
          Constrainable Property:</t>

          <t><list hangIndent="6" style="hanging">
              <t hangText="allowed values"><vspace blankLines="0" />The
              References MUST define the allowed values for the property, for
              example an enumerated list of values or a range of integers.</t>

              <t hangText="object(s)"><vspace blankLines="0" />The References
              MUST define the object or objects for which the properties
              apply, for example a MediaStreamTrack.</t>
            </list></t>

          <t></t>

          <t>The RTCWeb Constrainable Property MUST be well enough defined in
          the given References that it is understandable by implementors and
          application developers that will use the property. The property
          SHOULD NOT duplicate a condition that can be achieved using
          properties already defined in the registry. The property Name SHOULD
          be appropriate and specific enough for the property.</t>

          <t></t>
        </section>
      </section>
    </section>

    <section anchor="sec.securityConsiderations"
             title="Security Considerations">
      <t>Since the constrainable properties envisioned for this registry are
      fairly generic in nature, it is not expected that the mere existence of
      this registry will introduce any particular security issues. Any
      specification defining one or more new properties SHOULD address any
      specific security issues that might be introduced by the properties or
      their constrainable values.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <!--Key words for use in RFCs to Indicate Requirement Levels-->

      &rfc2119;

      <!--ABNF-->

      &rfc5234;

      <!--Guidelines for Writing an IANA Considerations Section in RFCs-->

      &rfc5226;
    </references>

    <references title="Informative References">
      <!-- getusermedia -->

      <reference anchor="W3C.WD-mediacapture-streams-20150212"
                 target="http://www.w3.org/TR/2015/WD-mediacapture-streams-20150212/">
        <front>
          <title>Media Capture and Streams</title>

          <author fullname="Daniel C. Burnett" initials="D." surname="Burnett">
            <organization>Voxeo</organization>
          </author>

          <author fullname="Adam Bergkvist" initials="A." surname="Bergkvist">
            <organization>Ericsson</organization>
          </author>

          <author fullname="Cullen Jennings" initials="C." surname="Jennings">
            <organization>Cisco</organization>
          </author>

          <author fullname="Anant Narayanan" initials="A." surname="Narayanan">
            <organization>Mozilla</organization>
          </author>

          <date day="12" month="February" year="2015" />
        </front>

        <seriesInfo name="World Wide Web Consortium WD"
                    value="WD-mediacapture-streams-20150212" />

        <format target="http://www.w3.org/TR/2015/WD-mediacapture-streams-20150212/"
                type="HTML" />
      </reference>
    </references>

    <section title="Acknowledgements">
      <t>The authors would like to thank the members of the W3C Media Capture
      Task Force and WebRTC Working Group, the members of the IETF RTCWEB
      Working Group, and the people who gave specific early review and
      feedback: Cullen Jennings and Travis Leithead.</t>

      <t></t>
    </section>
  </back>
</rfc>