Re: [rtcweb] Fwd: Last Call: <draft-ietf-rtcweb-audio-10.txt> (WebRTC Audio Codec and Processing Requirements) to Proposed Standard

[Harald Alvestrand <[e-mail]>]

Den 01. mars 2016 11:17, skrev Asveren, Tolga:
> Well, in your case, it is obviously app. developers fault to supply duration/interval without knowing what they mean/what he is doing (assuming those values are breaking something for whatever reason for that particular deployment). This would be a bug on the application/unintelligent behavior by the app. developer. 

That's the part that I don't get.
I pointed out how the choice *not* to have hard limits imposes cost on a
lot of people - most of which are *not* the people doing the
unintelligent behavior.

And there's *no* mechanism for asking the app developer to pay for their
wasted time.


> I am for convenience and accommodating people who are not savvy about DMTF aspects but enforcing limits to guard against stupidity would sacrifice flexibility, which IMHO is another important aspect. And enforcing min/max would do exactly that, limiting flexibility.

Again - is there any *realistic* use case that is impossible when a
consistent min/max is enforced, and impossible when some other limits
are enforced?

Remember that *all* browsers *will* impose *some* limit.