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

A description is ordered lines

01

SDP is a structured sequence of single-letter fields, not a negotiation or transport protocol.

Related RFCs and changes

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

DIAGRAM§ 5 ↗
RFC 8866 · § 5EXAMPLE
3 / 3
A description is ordered linesSDP is a structured sequence of single-letter fields, not a negotiation or transport protocol. Current state: Media descriptions.A description is ordered linesv=0o=…s=Example sessiont=0 0m=audio 49170 RTP/AVP 0Ordered type=value lines; v=0 is not an RFC revision number.
03
Media descriptions

Each m= starts a media-level description.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 4566RFC 8866 § 10

This revision clarifies syntax and behavior, obsoletes the k= encryption-key field, and updates attribute and internationalization guidance.

Read the updated RFC section ↗
KEY POINT

Each line has the form type=value.

  • Each line has the form type=value.
  • Field ordering and required fields are specified by the grammar.
  • The v=0 value identifies the SDP format version, not an RFC revision number.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗