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

On 11/6/13 6:25 PM, Mandyam, Giridhar wrote:
>
> OK, let’s go back to a statement of your from a previous email:
>
> ØWhy differentiate unknown from unsupported?
>
>
> The constraints listed in Section 12 are known.  If an implementation 
> supports a subset of them, they are known and unsupported.  I was 
> trying to respond by saying that I didn’t think this was possible – a 
> valid implementation must support all the known constraints outlined 
> in the specification.
>

I was responding directly to your "related note" that you believed the 
spec was "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".

So you were talking about constraints in IANA, *not* in section 12, so I 
don't see the relevance. I found your phrasing peculiar, because it 
doesn't affect the algorithm whether a vendor-specific constraint is 
IANA-registered or not.

.: Jan-Ivar :.