datatracker.ietf.org
Sign in
Version 5.13.0, 2015-03-25
Report a bug

Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP
RFC 7315

Document type: RFC - Informational (July 2014; No errata)
Obsoletes RFC 3455
Was draft-drage-sipping-rfc3455bis (individual in rai area)
Document stream: IETF
Last updated: 2014-07-18
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: Mary Barnes
Shepherd Write-Up: Last changed 2014-02-14

IESG State: RFC 7315 (Informational)
IANA Action State: RFC-Ed-Ack
Responsible AD: Richard Barnes
Send notices to: drage@alcatel-lucent.com, r.jesske@telekom.de, christer.holmberg@ericsson.com, draft-drage-sipping-rfc3455bis@ietf.org

Internet Engineering Task Force (IETF)                         R. Jesske
Request for Comments: 7315                              Deutsche Telekom
Obsoletes: 3455                                                 K. Drage
Category: Informational                                   Alcatel-Lucent
ISSN: 2070-1721                                              C. Holmberg
                                                                Ericsson
                                                               July 2014

                  Private Header (P-Header) Extensions
         to the Session Initiation Protocol (SIP) for the 3GPP

Abstract

   This document describes a set of private header (P-header) Session
   Initiation Protocol (SIP) fields used by the 3GPP, along with their
   applicability, which is limited to particular environments.  The
   P-header fields are used for a variety of purposes within the
   networks that the partners implement, including charging and
   information about the networks a call traverses.  This document
   obsoletes RFC 3455.

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 5741.

   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/rfc7315.

Jesske, et al.                Informational                     [Page 1]
RFC 7315              3GPP SIP P-Header Extensions             July 2014

Copyright Notice

   Copyright (c) 2014 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 Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Overall Applicability ...........................................3
   2. Conventions .....................................................3
   3. Overview ........................................................3
   4. SIP Private Header Fields .......................................4
      4.1. The P-Associated-URI Header Field ..........................4
           4.1.1. Applicability Statement for the
                  P-Associated-URI Header Field .......................5
           4.1.2. Usage of the P-Associated-URI Header Field ..........5
      4.2. The P-Called-Party-ID Header Field .........................6
           4.2.1. Applicability Statement for the
                  P-Called-Party-ID Header Field .....................10
           4.2.2. Usage of the P-Called-Party-ID Header Field ........11
      4.3. The P-Visited-Network-ID Header Field .....................12
           4.3.1. Applicability Statement for the
                  P-Visited-Network-ID Header Field ..................12
           4.3.2. Usage of the P-Visited-Network-ID Header Field .....13
      4.4. The P-Access-Network-Info Header Field ....................17
           4.4.1. Applicability Statement for the
                  P-Access-Network-Info Header Field .................18
           4.4.2. Usage of the P-Access-Network-Info Header ..........18
      4.5. The P-Charging-Function-Addresses Header Field ............19
           4.5.1. Applicability Statement for the
                  P-Charging-Function-Addresses Header Field .........20
           4.5.2. Usage of the P-Charging-Function-Addresses
                  Header Field .......................................21
      4.6. The P-Charging-Vector Header Field ........................23
           4.6.1. Applicability Statement for the
                  P-Charging-Vector Header Field .....................25
           4.6.2. Usage of the P-Charging-Vector Header Field ........25
           4.6.3. Usage of the transit-ioi ...........................27
           4.6.4. Usage of the related-icid ..........................28

Jesske, et al.                Informational                     [Page 2]
RFC 7315              3GPP SIP P-Header Extensions             July 2014

[include full document text]