rfc9878v3.txt   rfc9878.txt 
Internet Engineering Task Force (IETF) C. Holmberg Internet Engineering Task Force (IETF) C. Holmberg
Request for Comments: 9878 N. Biondic Request for Comments: 9878 Ericsson
Obsoletes: 7976 Ericsson Obsoletes: 7976 N. Biondic
Updates: 7315 G. Salgueiro Updates: 7315 ETSI
Category: Informational Cisco Systems, Inc. Category: Informational G. Salgueiro
ISSN: 2070-1721 R. Jesske ISSN: 2070-1721 Cisco Systems, Inc.
R. Jesske
Deutsche Telekom Deutsche Telekom
October 2025 November 2025
Updates to Private Header (P-Header) Extension Usage in Session Updates to Private Header (P-Header) Extension Usage in Session
Initiation Protocol (SIP) Requests and Responses Initiation Protocol (SIP) Requests and Responses
Abstract Abstract
The Third Generation Partnership Project (3GPP) has identified cases The Third Generation Partnership Project (3GPP) has identified cases
where different SIP private header extensions referred to as "P-" where different SIP private header extensions referred to as "P-"
header fields, and defined in RFC 7315, need to be included in SIP header fields, and defined in RFC 7315, need to be included in SIP
requests and responses where they were not allowed according to RFC requests and responses where they were not allowed according to RFC
skipping to change at line 75 skipping to change at line 76
2.2. Misalignments 2.2. Misalignments
2.3. 3GPP Use Cases 2.3. 3GPP Use Cases
2.3.1. General 2.3.1. General
2.3.2. P-Access-Network-Info 2.3.2. P-Access-Network-Info
2.3.3. P-Charging-Vector 2.3.3. P-Charging-Vector
3. Updates to RFC 7315 3. Updates to RFC 7315
4. IANA Considerations 4. IANA Considerations
5. Security Considerations 5. Security Considerations
6. Operational considerations 6. Operational considerations
7. Changes since RFC 7976 7. Changes since RFC 7976
8. Acknowledgments 8. References
9. References 8.1. Normative References
9.1. Normative References 8.2. Informative References
9.2. Informative References Acknowledgments
Authors' Addresses Authors' Addresses
1. Introduction 1. Introduction
The Third Generation Partnership Project (3GPP) has identified cases The Third Generation Partnership Project (3GPP) has identified cases
where different Session Initiation Protocol (SIP) [RFC3261] private where different Session Initiation Protocol (SIP) [RFC3261] private
header extensions referred to as "P-" header fields, and defined in header extensions referred to as "P-" header fields, and defined in
[RFC7315], need to be included in SIP requests and responses where [RFC7315], need to be included in SIP requests and responses where
they were not allowed according to [RFC7315]. This document updates they were not allowed according to [RFC7315]. This document updates
[RFC7315], in order to allow inclusion of the affected "P-" header [RFC7315], in order to allow inclusion of the affected "P-" header
skipping to change at line 339 skipping to change at line 340
in this document are already defined [TS24.229], the updates are not in this document are already defined [TS24.229], the updates are not
seen to cause backward-compatibility concerns. seen to cause backward-compatibility concerns.
7. Changes since RFC 7976 7. Changes since RFC 7976
The changes related to RFC 7976 involve the inclusion of the P- The changes related to RFC 7976 involve the inclusion of the P-
Visited-Network-ID header field in SIP responses. Specifically, any Visited-Network-ID header field in SIP responses. Specifically, any
SIP response message, with the exception of a 100 (Trying) response, SIP response message, with the exception of a 100 (Trying) response,
may include a P-Visited-Network-ID header field. may include a P-Visited-Network-ID header field.
8. Acknowledgments 8. References
The author would like to acknowledge the constructive feedback
provided by Michael Kreipl, Charles Eckel, and Paul Kyzivat.
Thanks to Paul Kyzivat, Jean Mahoney, Ben Campbell, and Adam Roach
for providing comments on an earlier draft version of this document.
9. References
9.1. Normative References 8.1. Normative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<https://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC7315] Jesske, R., Drage, K., and C. Holmberg, "Private Header [RFC7315] Jesske, R., Drage, K., and C. Holmberg, "Private Header
(P-Header) Extensions to the Session Initiation Protocol (P-Header) Extensions to the Session Initiation Protocol
(SIP) for the 3GPP", RFC 7315, DOI 10.17487/RFC7315, July (SIP) for the 3GPP", RFC 7315, DOI 10.17487/RFC7315, July
skipping to change at line 373 skipping to change at line 366
TS 23.228, TS 23.228,
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=821>. SpecificationDetails.aspx?specificationId=821>.
[TS24.229] 3GPP, "IP multimedia call control protocol based on [TS24.229] 3GPP, "IP multimedia call control protocol based on
Session Initiation Protocol (SIP) and Session Description Session Initiation Protocol (SIP) and Session Description
Protocol (SDP); Stage 3", 3GPP TS 24.229, Protocol (SDP); Stage 3", 3GPP TS 24.229,
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=1055>. SpecificationDetails.aspx?specificationId=1055>.
9.2. Informative References 8.2. Informative References
[RFC3455] Garcia-Martin, M., Henrikson, E., and D. Mills, "Private [RFC3455] Garcia-Martin, M., Henrikson, E., and D. Mills, "Private
Header (P-Header) Extensions to the Session Initiation Header (P-Header) Extensions to the Session Initiation
Protocol (SIP) for the 3rd-Generation Partnership Project Protocol (SIP) for the 3rd-Generation Partnership Project
(3GPP)", RFC 3455, DOI 10.17487/RFC3455, January 2003, (3GPP)", RFC 3455, DOI 10.17487/RFC3455, January 2003,
<https://www.rfc-editor.org/info/rfc3455>. <https://www.rfc-editor.org/info/rfc3455>.
Acknowledgments
The author would like to acknowledge the constructive feedback
provided by Michael Kreipl, Charles Eckel, and Paul Kyzivat.
Thanks to Paul Kyzivat, Jean Mahoney, Ben Campbell, and Adam Roach
for providing comments on an earlier draft version of this document.
Authors' Addresses Authors' Addresses
Christer Holmberg Christer Holmberg
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
FI-02420 Jorvas FI-02420 Jorvas
Finland Finland
Email: christer.holmberg@ericsson.com Email: christer.holmberg@ericsson.com
Nevenka Biondic Nevenka Biondic
Ericsson ETSI
Krapinska 45 650 route des Lucioles
HR-10002 Zagreb 06921 Sophia Antipolis cedex
Croatia France
Email: nevenka.biondic.ext@ericsson.com Email: Nevenka.Biondic@etsi.org
Gonzalo Salgueiro Gonzalo Salgueiro
Cisco Systems, Inc. Cisco Systems, Inc.
7200-12 Kit Creek Road 7200-12 Kit Creek Road
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
United States of America United States of America
Email: gsalguei@cisco.com Email: gsalguei@cisco.com
Roland Jesske Roland Jesske
Deutsche Telekom Deutsche Telekom
 End of changes. 8 change blocks. 
26 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.48.