There is no "audio/dtmf" codec MIME type #548

Closed
ibc opened this Issue May 16, 2016 · 6 comments

Projects

None yet

3 participants

@ibc
Contributor
ibc commented May 16, 2016

Related to #529 and w3c/webrtc-pc#637

ORTC mentions "dtmf" as codec.name in various parts of the spec, but there is no "audio/dtmf" MIME type but "audio/telephone-event":

http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-2

Also, ORTC mentions "red" as codec.name, but the IANA table defines:

  • audio/RED
  • text/red
  • (there is not video/RED)

It seems that being case sensitive will be important so the spec needs some fixes regarding this subject.

@rshpount

@ibc This should be audio/telephone-event

@ibc
Contributor
ibc commented May 16, 2016

Exactly, but unfortunately the spec relies too much in codec.name = "dtmf".

@aboba
Contributor
aboba commented May 19, 2016

@ibc Changed use of "dtmf" in codec.name to "telephone-event" in PR #549

@ibc
Contributor
ibc commented May 19, 2016

👍

@aboba
Contributor
aboba commented May 19, 2016

@ibc IANA table may have a typo. While there is an entry for "audio/RED", RFC 2198 examples actually use "red".

@ibc
Contributor
ibc commented May 31, 2016

IANA table may have a typo. While there is an entry for "audio/RED", RFC 2198 examples actually use "red".

Wondering whether the spec should define codec mime types as case insensitive...

@aboba aboba closed this May 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment