Update to Remove DVI4 from the Recommended Codecs for the RTP Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)
updates
- rfc-3551 — RTP Profile for Audio and Video Conferences with Minimal Control
Extracted elements (5)
DVI4 was removed from the recommended codec list because in practice many RTP deployments do not support it, and there is little reason to use it when much more modern codecs are available. The original RFC 3551 requirement to support both PCMU and DVI4 no longer reflects real-world usage.
This update applies not only to RTP/AVP but also to profiles that build upon it: RTP/SAVP (RFC 3711), RTP/AVPF (RFC 4585), and RTP/SAVPF (RFC 5124). All of these profiles inherit the revised codec recommendation.
Audio applications operating under the RTP/AVP profile SHOULD, at a minimum, be able to send and/or receive payload type 0 (PCMU). This removes the previous requirement to also support DVI4 (payload type 5).
The updated paragraph adds a final sentence stating 'Some environments necessitate support for PCMU', acknowledging that PCMU remains a baseline interoperability requirement in certain deployment contexts.
This document does not introduce any new security considerations for RFC 3551. The update is limited to codec recommendation changes and has no security implications.