Looking for earliest decision to use an IANA registry for constraints

Re LC-3024
(https://www.w3.org/2006/02/lc-comments-tracker/47318/WD-mediacapture-streams-20150414/3024):

Did some archaeology on my mailbox. First mention I could find is
reproduced below.

It seems that we made the decision to use a registry at that time, we
have discussed revisiting the discussion at many later times, but I
can't find a consensus to discard the registry.

            Harald

Minutes from WebRTC WG F2F in Santa Clara, November 2011:


   burn: Moving on to hings API, last discussed on the mailing-list.
   Simple example is "audioType: 'spoken"music"
   ... question is which level of details.
   ... Agreement that this is needed.
   ... Question is do we need an API for that?

   anant: new things will keep coming. Extensibility is needed.

   cullen: agree.
   ... IANA registry could be used, I think.

   burn: problem in other groups is knowing the IETF process. Won't be
   a problem here.

   hta: we have to define some kind of namespaces for hints. Just one
   level, multiple levels, strings, tokenized, etc.

   DanD: two things, structure and semantics.

   burn: someone may want to propose finer granularity that you want to
   relate to other values.
   ... in the end, they are hints, so it doesn't matter so much. If you
   give something that is general, and something that is specific, you
   don't know what you're going to end up with.

   adam: side comment that the hints should be an optional argument to
   addStream.

   [agreed]

   stefan: we should reuse MediaStreamHints object for getUserMedia

   anant: true.

   hta: having just one registry is probably ok. The video, you could
   have a hint saying low resolution.

   burn: one registry makes sense.

   anant: different object but same values

Received on Tuesday, 26 May 2015 12:35:26 UTC