W3C home > Mailing lists > Public > public-media-capture@w3.org > November 2013

[Bug 22209] "each key MUST be a valid registered constraint name in the IANA-hosted RTCWeb Media Constraints registry"

From: <bugzilla@jessica.w3.org>
Date: Tue, 05 Nov 2013 17:20:48 +0000
To: public-media-capture@w3.org
Message-ID: <bug-22209-5753-ehlozG8iDe@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22209

Giri Mandyam <mandyam@quicinc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mandyam@quicinc.com

--- Comment #5 from Giri Mandyam <mandyam@quicinc.com> ---
We discussed vendor-specific constraints during the F2F at TPAC 2012
(http://lists.w3.org/Archives/Public/public-media-capture/2012Dec/att-0196/minutes-2012-10-30.html). 

I believe what reflected consensus was that vendor-specific constraints be
added to the IANA registry, which would allow such constraints to undergo
expert review as per RFC 5226.  We can reconfirm this at the next F2F however.

On a related note, I do believe the spec is unclear as to what the
implementation should do when a valid IANA-registered vendor-specific
constraint is provided to MediaStreamTrack.applyConstraints() that the
implementation does not recognize or support.  I assume an exception can be
raised, but I did not find specific guidance in the latest working draft.  The
constrainable interface proposal also defines an error callback on
applyConstraints().

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 5 November 2013 17:20:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:24:43 UTC