Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
RFC 3455

Document Type RFC - Informational (January 2003; Errata)
Obsoleted by RFC 7315
Was draft-garcia-sipping-3gpp-p-headers (individual in tsv area)
Last updated 2014-05-06
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3455 (Informational)
Telechat date
Responsible AD Allison Mankin
IESG note RFC Editor - Expedited Publication was Requested - Reply NOT received on this
Send notices to <arpanet: mills@louie.udel.edu>, <miguel.a.garcia@ericsson.com>, <ehenrikson@lucent.com>
Network Working Group                                   M. Garcia-Martin
Request for Comments: 3455                                      Ericsson
Category: Informational                                     E. Henrikson
                                                                  Lucent
                                                                D. Mills
                                                                Vodafone
                                                            January 2003

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

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

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

Table of Contents

   1. Overall Applicability . . . . . . . . . . . . . . . . . . . .  3
   2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3. Overview . . . .  . . . . . . . . . . . . . . . . . . . . . .  3
   4. SIP Private Headers . . . . . . . . . . . . . . . . . . . . .  3
     4.1 The P-Associated-URI header. . . . . . . . . . . . . . . .  3
         4.1.1 Applicability statement for the
               P-Associated-URI header. . . . . . . . . . . . . . .  4
         4.1.2 Usage of the P-Associated-URI header . . . . . . . .  4
     4.2 The P-Called-Party-ID header . . . . . . . . . . . . . . .  6
         4.2.1 Applicability statement for the
              P-Called-Party-ID header. . . . . . . . . . . . . . .  9
         4.2.2 Usage of the P-Called-Party-ID header. . . . . . . . 10
     4.3 The P-Visited-Network-ID header. . . . . . . . . . . . . . 11
         4.3.1 Applicability statement for the
               P-Visited-Network-ID header. . . . . . . . . . . . . 11

Garcia-Martin, et. al.       Informational                      [Page 1]
RFC 3455              3GPP SIP P-Header Extensions          January 2003

         4.3.2 Usage of the P-Visited-Network-ID header . . . . . . 12
     4.4 The P-Access-Network-Info header . . . . . . . . . . . . . 15
         4.4.1 Applicability Statement for the
               P-Access-Network-Info header . . . . . . . . . . . . 16
         4.4.2 Usage of the P-Access-Network-Info header .  . . . . 17
     4.5 The P-Charging-Function-Addresses header . . . . . . . . . 18
         4.5.1 Applicability Statement for the
               P-Charging-Function-Addresses header . . . . . . . . 18
         4.5.2 Usage of the P-Charging-Function-Addresses
               headerd. . . . . . . . . . . . . . . . . . . . . . . 19
     4.6 The P-Charging-Vector header . . . . . . . . . . . . . . . 21
         4.6.1 Applicability Statement for the
               P-Charging-Vector header . . . . . . . . . . . . . . 22
         4.6.2 Usage of the P-Charging-Vector header .  . . . . . . 23
   5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 25
     5.1 P-Associated-URI header syntax . . . . . . . . . . . . . . 25
     5.2 P-Called-Party-ID header syntax. . . . . . . . . . . . . . 25
     5.3 P-Visited-Network-ID header syntax . . . . . . . . . . . . 25
     5.4 P-Access-Network-Info header syntax. . . . . . . . . . . . 25
     5.5 P-Charging-Function-Addresses header syntax. . . . . . . . 26
     5.6 P-Charging-Vector header syntax. . . . . . . . . . . . . . 26
     5.7 Table of new headers . . . . . . . . . . . . . . . . . . . 27
   6. Security Considerations . . . . . . . . . . . . . . . . . . . 28
     6.1 P-Associated-URI . . . . . . . . . . . . . . . . . . . . . 28
     6.2 P-Called-Party-ID. . . . . . . . . . . . . . . . . . . . . 28
     6.3 P-Visited-Network-ID . . . . . . . . . . . . . . . . . . . 28
     6.4 P-Access-Network-Info. . . . . . . . . . . . . . . . . . . 29
     6.5 P-Charging-Function-Addresses. . . . . . . . . . . . . . . 30
     6.6 P-Charging-Vector. . . . . . . . . . . . . . . . . . . . . 30
   7.  IANA Considerations. . . . . . . . . . . . . . . . . . . . . 30
   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
   9.  Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . 32
   10. Normative References . . . . . . . . . . . . . . . . . . . . 32
   11. Informative References . . . . . . . . . . . . . . . . . . . 32
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
Show full document text