RFC 5502: The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem
In plain English — editorial summary, not part of the RFC
This document specifies the SIP P-Served-User P-header. This header field addresses an issue that was found in the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an S-CSCF (Serving Call Session Control Function) and an AS (Application Server) on the ISC (IMS Service Control) interface. This header field conveys the identity of the served user and the session case that applies to this particular communication session and application invocation. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5502
- Published
- April 2009
- Authors
- J. van Elburg
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5589Session Initiation Protocol (SIP) Call Control - TransferCurrent
June 2009
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 5390Requirements for Management of Overload in the Session Initiation ProtocolCurrent
December 2008
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5621Message Body Handling in the Session Initiation Protocol (SIP)Updated
September 2009
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) 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?