Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000247612D
Original Publication Date: 2016-Sep-01
Included in the Prior Art Database: 2016-Sep-20
Document File: 16 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Holmberg: AUTHOR [+3]

Abstract

The Third Generation Partnership Project (3GPP) has identified cases where different Session Initiation Protocol (SIP) [RFC3261] private header extensions referred to as "P-" header fields, and defined in [RFC7315], need to be included in SIP requests and responses currently 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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% of the total text.

Internet Engineering Task Force (IETF)                       C. Holmberg Request for Comments: 7976                                    N. Biondic Updates: 7315                                                   Ericsson Category: Informational                                     G. Salgueiro ISSN: 2070-1721                                                    Cisco                                                           September 2016

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

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 currently 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 also makes updates for RFC 7315 in order to fix    misalignments that occurred when RFC 3455 was updated and obsoleted    by RFC 7315.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7976.

 Holmberg, et al.              Informational                     [Page 1]
 RFC 7976                Updates to P-Header Usage         September 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Pro...