RFC 9878

Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses, November 2025

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
INFORMATIONAL
Obsoletes:
RFC 7976
Updates:
RFC 7315
Authors:
C. Holmberg
N. Biondic
G. Salgueiro
R. Jesske
Stream:
IETF
Source:
sipcore (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9878

Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9878


Abstract

The Third Generation Partnership Project (3GPP) has identified cases where different SIP private header extensions referred to as "P-" header fields, and defined in RFC 7315, need to be included in SIP requests and responses where they were not allowed according to RFC 7315. This document updates RFC 7315, in order to allow inclusion of the affected "P-" header fields in such requests and responses. This document obsoletes RFC 7976. The changes related to RFC 7976 involve the inclusion of the P-Visited-Network-ID header field in SIP responses.

This document also makes updates to RFC 7315 in order to fix misalignments that occurred when RFC 3455 was obsoleted by RFC 7315.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search