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

A dialog outlives a transaction

03

A dialog maintains peer relationships across individual request/response transactions.

Related RFCs and changes

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

DIAGRAM§ 12 ↗
RFC 3261 · § 12EXAMPLE
3 / 3
A dialog outlives a transactionA dialog maintains peer relationships across individual request/response transactions. Current state: Later request.A dialog outlives a transactiondialog: Call-ID + two tagsINVITE transactiondialog state persistslater in-dialog transactionA transaction and a dialog have different lifetimes.
03
Later request

A subsequent in-dialog request is a new transaction using that dialog.

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

A dialog is identified by Call-ID and local and remote tags.

  • A dialog is identified by Call-ID and local and remote tags.
  • CSeq orders requests within a dialog according to the method’s rules.
  • A transaction is an individual request and its associated responses.
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. Register a reachable contact
  2. Invite through a proxy
  3. A dialog outlives a transaction
  4. Cancel a request, end a session
  5. Signaling is not the media stream
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗