Re: [rtcweb] Working group last call for draft-ietf-rtcweb-audio

[Adam Roach <[e-mail]>]

On 12/18/15 15:10, Roman Shpount wrote:
> It looks like these tones are removed for aesthetic reasons only.

I think it would be better if you directly disagreed with Cullen's 
rationale rather than simply ignoring it. Since it was made in a 
different forum, I'll copy it here.


On 12/9/15 12:48, Cullen Jennings wrote:
> I want to be clear I don't care that much one way or the other about this but I want to try again to explain the issue...
>
> A to D will often be blocked by the system that sends them from one side to the other. So if you write JS applications that use theses, they will work some times and not others. That is just inviting developers to shoot themselves in the foot and no one has identified any benefit of adding A to D yet.
>
> 100% agree that the IETF and W3C specs need to align on this and we should change the ietf audio draft if we are including A-D.
>

To be clear, this is speaking to operational aspects of the system's 
behavior that I haven't had much visibility into. We have one 
implementor effectively asserting that all commercial gateways support 
these tones, and another saying that they tend to be blocked by 
intermediaries. I suppose both assertions could be true, but the net 
effect of both being true is that these tones are broadly unusable.

But I'm in the same boat as Cullen: I don't care much whether these 
tones are supported, as long as the W3C and IETF documents agree with 
each other.

/a