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

["Asveren, Tolga" <[e-mail]>]

So, you think that we shouldn’t expect that an App. Dev., who doesn’t know much about DTMF, can’t call the right API, which would use the browser defaults(despite explanations in relevant specifications)? I respectfully disagree. What about some other App. Dev., who calls APIs in a nilly-willy way, in the wrong order, with wrong values... Maybe we should have a single API: Make_Call(phone number)?!?

Thanks,
Tolga

> -----Original Message-----
> From: Harald Alvestrand [mailto:[e-mail]]
> Sent: Tuesday, March 01, 2016 6:46 AM
> To: Asveren, Tolga <[e-mail]>; Ted Hardie
> <[e-mail]>
> Cc: Roman Shpount <[e-mail]>; [e-mail]
> Subject: Re: [rtcweb] Fwd: Last Call: <draft-ietf-rtcweb-audio-10.txt>
> (WebRTC Audio Codec and Processing Requirements) to Proposed Standard
> 
> 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.