RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) has a mechanism for conveying the identity of the originator of a request by means of the P-Asserted-Identity and P-Preferred-Identity header fields. These header fields are specified for use in requests using a number of SIP methods, in particular the INVITE method. However, RFC 3325 does not specify the insertion of the P-Asserted-Identity header field by a trusted User Agent Client (UAC), does not specify the use of P-Asserted-Identity and P-Preferred-Identity header fields with certain SIP methods such as UPDATE, REGISTER, MESSAGE, and PUBLISH, and does not specify how to handle an unexpected number of URIs or unexpected URI schemes in these header fields. This document extends RFC 3325 to cover these situations. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5876
- Published
- April 2010
- Authors
- J. Elwell
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 3325
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5874An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) ResourcesCurrent
May 2010
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
- RFC 6035Session Initiation Protocol Event Package for Voice Quality ReportingCurrent
November 2010
- RFC 6080A Framework for Session Initiation Protocol User Agent Profile DeliveryCurrent
March 2011
- RFC 5630The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5629A Framework for Application Interaction in the Session Initiation Protocol (SIP)Current
October 2009
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?