Visual RFC.
ALL RFCs / RFC 8866
Read the RFC ↗
RFC 8866 / MECHANISMS

An m line describes transport

03

The media line declares media type, transport port, protocol, and format identifiers.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 8866 · § 5.14EXAMPLE
3 / 3
An m line describes transportThe media line declares media type, transport port, protocol, and format identifiers. Current state: Interpret together.An m line describes transportm=audio 49170 RTP/AVP 96a=rtpmap:96 opus/48000/2format 96 → Opus · 48000 Hz · 2 channelsA description declares parameters; it sends no audio by itself.
03
Interpret together

Read the media and attributes as one description.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

An RTP format number is interpreted with the applicable profile and payload mappings.

  • An RTP format number is interpreted with the applicable profile and payload mappings.
  • An rtpmap attribute can map a dynamic payload type to an encoding and clock rate.
  • These declarations do not themselves send media.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A description is ordered lines
  2. Session scope and media scope
  3. An m line describes transport
  4. Time and direction are independent
  5. A description is not authorization

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗