draft-ietf-rtcweb-constraints-registry-01.txt   draft-ietf-rtcweb-constraints-registry-02.txt 
RTCWEB D. Burnett RTCWEB D. Burnett
Internet-Draft Aspect Software, Inc. Internet-Draft Aspect Software, Inc.
Intended status: Standards Track January 16, 2015 Intended status: Standards Track March 9, 2015
Expires: July 20, 2015 Expires: September 10, 2015
IANA Registry for RTCWeb Constrainable Properties IANA Registry for RTCWeb Constrainable Properties
draft-ietf-rtcweb-constraints-registry-01 draft-ietf-rtcweb-constraints-registry-02
Abstract Abstract
Specifications in W3C's Media Capture Task Force and WebRTC Working Specifications in W3C's Media Capture Task Force and WebRTC Working
Group have need of a registry in which to maintain a list of Group have need of a registry in which to maintain a list of
constrainable properties for HTML media and other constrainable constrainable properties for HTML media and other constrainable
objects. This document defines this registry. objects. This document defines this registry.
Status of This Memo Status of This Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 20, 2015. This Internet-Draft will expire on September 10, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. Normative References . . . . . . . . . . . . . . . . . . 4 5.1. Normative References . . . . . . . . . . . . . . . . . . 4
5.2. Informative References . . . . . . . . . . . . . . . . . 4 5.2. Informative References . . . . . . . . . . . . . . . . . 4
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
There is currently one W3C specification (Media Capture and Streams There is currently one W3C specification (Media Capture and Streams
[W3C.WD-mediacapture-streams-20130903]) that has need of a registry [W3C.WD-mediacapture-streams-20150212]) that has need of a registry
in which to represent constrainable properties, and it is expected in which to represent constrainable properties, and it is expected
that others will as well. The specification makes use of a data that others will as well. The specification makes use of a data
structure representing a list of constraints on the HTML media or structure representing a list of constraints on the HTML media or
media connection to be established. Additionally, the specification media connection to be established. Additionally, the specification
defines methods that are used to query the web browser about its defines methods that are used to query the web browser about its
capabilities. The returned data structure specifies the browser's capabilities. The returned data structure specifies the browser's
capabilities in terms of constraints that it can satisfy. The data capabilities in terms of constraints that it can satisfy. The data
structures and their use are defined as the Constrainable Pattern in structures and their use are defined as the Constrainable Pattern in
the aforementioned specification. This document specifies the the aforementioned specification. This document specifies the
registry used to define individual constrainable property names, registry used to define individual constrainable property names,
skipping to change at page 3, line 46 skipping to change at page 3, line 46
3.1.1. Designated Expert Instructions 3.1.1. Designated Expert Instructions
RTCWeb Constrainable Property Names are of unlimited length according RTCWeb Constrainable Property Names are of unlimited length according
to the syntax. However, it is RECOMMENDED that they be no longer to the syntax. However, it is RECOMMENDED that they be no longer
than 80 characters in total. This is to keep them reasonable for 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, 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 i.e., when a Name consists of multiple words, the first character of
each word SHOULD be an uppercase character, with all others being each word SHOULD be an uppercase character, with all others being
lowercase. lowercase.
The references MUST define the following for each RTCWeb The References MUST define the following for each RTCWeb
Constrainable Property: Constrainable Property:
allowed values allowed values
The references MUST define the allowed values for the property, The References MUST define the allowed values for the property,
for example an enumerated list of values or a range of for example an enumerated list of values or a range of
integers. integers.
object(s) object(s)
The references MUST define the object or objects for which the The References MUST define the object or objects for which the
properties apply, for example a MediaStreamTrack. properties apply, for example a MediaStreamTrack.
The RTCWeb Constrainable Property MUST be well enough defined in the The RTCWeb Constrainable Property MUST be well enough defined in the
given references that it is understandable by implementors and given References that it is understandable by implementors and
application developers that will use the constraint. The property application developers that will use the property. The property
SHOULD NOT duplicate a condition that can be achieved using SHOULD NOT duplicate a condition that can be achieved using
properties already defined in the registry. The property name SHOULD properties already defined in the registry. The property Name SHOULD
be appropriate and specific enough for the property. be appropriate and specific enough for the property.
4. Security Considerations 4. Security Considerations
Since the constrainable properties envisioned for this registry are Since the constrainable properties envisioned for this registry are
fairly generic in nature, it is not expected that the mere existence fairly generic in nature, it is not expected that the mere existence
of this registry will introduce any particular security issues. Any of this registry will introduce any particular security issues. Any
specification defining one or more new properties SHOULD address any specification defining one or more new properties SHOULD address any
specific security issues that might be introduced by the properties specific security issues that might be introduced by the properties
or their constrainable values. or their constrainable values.
skipping to change at page 4, line 44 skipping to change at page 4, line 44
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
5.2. Informative References 5.2. Informative References
[W3C.WD-mediacapture-streams-20130903] [W3C.WD-mediacapture-streams-20150212]
Burnett, D., Bergkvist, A., Jennings, C., and A. Burnett, D., Bergkvist, A., Jennings, C., and A.
Narayanan, "Media Capture and Streams", World Wide Web Narayanan, "Media Capture and Streams", World Wide Web
Consortium WD WD-mediacapture-streams-20130903, September Consortium WD WD-mediacapture-streams-20150212, February
2013, <http://www.w3.org/TR/2013/ 2015, <http://www.w3.org/TR/2015/
WD-mediacapture-streams-20130903/>. WD-mediacapture-streams-20150212/>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank the members of the W3C Media Capture 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 Task Force and WebRTC Working Group, the members of the IETF RTCWEB
Working Group, and the people who gave specific early review and Working Group, and the people who gave specific early review and
feedback: Cullen Jennings and Travis Leithead. feedback: Cullen Jennings and Travis Leithead.
Author's Address Author's Address
 End of changes. 11 change blocks. 
15 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/