RFC 4961: Symmetric RTP / RTP Control Protocol (RTCP)

In plain English — editorial summary, not part of the RFC

This document recommends using one UDP port pair for both communication directions of bidirectional RTP and RTP Control Protocol (RTCP) sessions, commonly called "symmetric RTP" and "symmetric RTCP". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID

RFC4961

Published

July 2007

Authors

D. Wing

Status

BEST CURRENT PRACTICE

Stream

IETF

Area

—

Pages

6

Also known as

BCP131

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4961

Topics

• real time transport protocol
• symmetric rtcp

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4588RTP Retransmission Payload FormatCurrent

  July 2006

• RFC 4573MIME Type Registration for RTP Payload Format for H.224Current

  July 2006

• RFC 4184RTP Payload Format for AC-3 AudioCurrent

  October 2005

• RFC 4175RTP Payload Format for Uncompressed VideoUpdated

  September 2005

• RFC 3640RTP Payload Format for Transport of MPEG-4 Elementary StreamsUpdated

  December 2003

• RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current

  November 2003

• RFC 3558RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)Updated

  July 2003

• RFC 3557RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition EncodingCurrent

  July 2003

Also filed under

• BEST CURRENT PRACTICE
• 2007
• IETF stream
• BCP 131