Updates to Asserted Identity in the Session Initiation Protocol
RFC 5876, “Updates to Asserted Identity in the Session Initiation Protocol”, is an Informational document published in April 2010 by J. Elwell. It updates RFC 3325. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5876 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5875 An Extensible Markup Language Configuration Access Protocol Diff Event Package
- RFC 5877 The application/pkix-attr-cert Media Type for Attribute Certificates
- RFC 5874 An Extensible Markup Language Document Format for Indicating a Change in XML Configuration Access Protocol Resources
- RFC 5878 Transport Layer Security Authorization Extensions
- RFC 5873 Pre-Authentication Support for the Protocol for Carrying Authentication for Network Access
- RFC 5879 Heuristics for Detecting ESP-NULL Packets
- RFC 5872 IANA Rules for the Protocol for Carrying Authentication for Network Access
- RFC 5880 Bidirectional Forwarding Detection