RFC 4538: Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This specification defines the Target-Dialog header field for the Session Initiation Protocol (SIP), and the corresponding option tag, tdialog. This header field is used in requests that create SIP dialogs. It indicates to the recipient that the sender is aware of an existing dialog with the recipient, either because the sender is on the other side of that dialog, or because it has access to the dialog identifiers. The recipient can then authorize the request based on this awareness. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4538
- Published
- June 2006
- Authors
- J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4508Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER MethodUpdated
May 2006
- RFC 4569Internet Assigned Number Authority (IANA) Registration of the Message Media Feature TagCurrent
July 2006
- RFC 4571Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented TransportCurrent
July 2006
- RFC 4573MIME Type Registration for RTP Payload Format for H.224Current
July 2006
- RFC 4575A Session Initiation Protocol (SIP) Event Package for Conference StateCurrent
August 2006
- RFC 4497Interworking between the Session Initiation Protocol (SIP) and QSIGUpdated
May 2006
- RFC 4579Session Initiation Protocol (SIP) Call Control - Conferencing for User AgentsCurrent
August 2006
- RFC 4582The Binary Floor Control Protocol (BFCP)Obsoleted
November 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?