draft-ietf-rtcweb-constraints-registry-02.txt   draft-ietf-rtcweb-constraints-registry-03.txt 
RTCWEB D. Burnett RTCWEB D. Burnett
Internet-Draft Aspect Software, Inc. Internet-Draft Aspect Software, Inc.
Intended status: Standards Track March 9, 2015 Intended status: Standards Track October 2, 2015
Expires: September 10, 2015 Expires: April 4, 2016
IANA Registry for RTCWeb Constrainable Properties IANA Registry for RTCWeb Constrainable Properties
draft-ietf-rtcweb-constraints-registry-02 draft-ietf-rtcweb-constraints-registry-03
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 September 10, 2015. This Internet-Draft will expire on April 4, 2016.
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 4, line 33 skipping to change at page 4, line 33
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.
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
[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. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
5.2. Informative References 5.2. Informative References
[W3C.WD-mediacapture-streams-20150212] [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-20150212, February Consortium WD WD-mediacapture-streams-20150212, February
2015, <http://www.w3.org/TR/2015/ 2015, <http://www.w3.org/TR/2015/
WD-mediacapture-streams-20150212/>. WD-mediacapture-streams-20150212/>.
 End of changes. 6 change blocks. 
8 lines changed or deleted 13 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/