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

On Fri, Dec 18, 2015 at 10:32 AM, Roman Shpount <roman@telurix.com> wrote:

> Hi All,
>
> Since the decision not to support A-D DTMF digits was never made on the
> IETF list (I have looked through the archive and cannot find it), I do not
> think they should be removed.
>
>
Can you say more about what use there would be in supporting them?

regards,

Ted

> Minimal DTMF tone duration and gap duration should be added to the
> document.
>
> The meaning of "consuming" RFC 4733 events by WebRTC endpoints is unclear.
>
> I suggest to change the following section of the document:
>
> OLD TEXT:
> The audio/telephone-event media format as specified in [RFC4733].
>       WebRTC endpoints are REQUIRED to be able to generate and consume
>       the following events:
>
>          +------------+--------------------------------+-----------+
>          |Event Code  | Event Name                     | Reference |
>          +------------+--------------------------------+-----------+
>          | 0          | DTMF digit "0"                 |  RFC4733  |
>          | 1          | DTMF digit "1"                 |  RFC4733  |
>          | 2          | DTMF digit "2"                 |  RFC4733  |
>          | 3          | DTMF digit "3"                 |  RFC4733  |
>          | 4          | DTMF digit "4"                 |  RFC4733  |
>          | 5          | DTMF digit "5"                 |  RFC4733  |
>          | 6          | DTMF digit "6"                 |  RFC4733  |
>          | 7          | DTMF digit "7"                 |  RFC4733  |
>          | 8          | DTMF digit "8"                 |  RFC4733  |
>          | 9          | DTMF digit "9"                 |  RFC4733  |
>          | 10         | DTMF digit "*"                 |  RFC4733  |
>          | 11         | DTMF digit "#"                 |  RFC4733  |
>          +------------+--------------------------------+-----------+
>
>
> _____________
> Roman Shpount
>
> On Fri, Dec 18, 2015 at 1:13 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> The two issues that surfaced during this last call that needed resolution
>> were DTMF and comfort noise.  Based on the discussion, we believe that the
>> comfort noise requirement will be shifted to "WebRTC endpoints". The DTMF
>> language will aligned with the W3C specification and clarified that A-D are
>> not supported (as they will not be supported in the JavaScript).
>>
>> After the document is updated, the chairs plan to submit it to IETF last
>> call.
>>
>> regards,
>>
>> Ted, Cullen, Sean
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>>
>