RFC 5318: The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)
In plain English — editorial summary, not part of the RFC
This document specifies the Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header). This P-Header is used in the Open Mobile Alliance's (OMA) Push to talk over Cellular (PoC) system. It enables URI-list servers to refuse the handling of incoming URI lists that have embedded URI lists. This P-Header also makes it possible for the URI-list server to inform the client about the embedded URI list that caused the rejection and the individual URIs that form such a URI list. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5318
- Published
- December 2008
- Authors
- J. Hautakorpi; G. Camarillo
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 8217
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4964The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over CellularUpdated
September 2007
- RFC 5224Diameter Policy Processing ApplicationCurrent
March 2008
- RFC 4354A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) ServiceCurrent
January 2006
- RFC 5373Requesting Answering Modes for the Session Initiation Protocol (SIP)Current
November 2008
- RFC 4909Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM TransportObsoleted
June 2007
- RFC 6309IANA Rules for MIKEY (Multimedia Internet KEYing)Current
August 2011
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?