MS Edge is using uppercase notation for codec names

Won’t fix Issue #7771963


Erik L.
Jun 2, 2016
This issue is public.
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When using MS Edge ORTC implementation, methods RTCSender.getCapabilities() and RTCReceiver.getCapabilities() returns list of codecs with subtype name as uppercase string(e.g. for Opus codec string is “OPUS”). Similar behavior is for other codecs.

In RFC 7587 - RTP Payload Format for the Opus Speech and Audio Codec section 6.1. and 7. ( it is described that subtype name should be lowercase string when communicating with other peers, therefore this naming convention might cause problem when interop with not flexible endpoints.

MS Edge should be strict in what it is sending, thus it should not emit “OPUS” but "opus". MS edge is flexible in what it is receiving already (e.g. it will accept “OPUS” or “opus”) but it’s not strict in what it sends.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Shijun S.”

      Changed Status to “Confirmed”

    • Thanks for the feedback!

      There is still ongoing effort within W3C WebRTC Working Group to finalize the codec names in the spec.  There is a preference in the group to expose the full MIME types rather than just the codec names.  We will consider making the changes in future product releases based on the final design decision in the spec.

      All the Best, MS Edge Team

    • Microsoft Edge Team

      Changed Assigned To from “Shijun S.” to “Brad E.”

      Changed Status from “Confirmed” to “Won’t fix”

    You need to sign in to your Microsoft account to add a comment.

    Sign in