A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)
RFC 8498

Document Type RFC - Informational (February 2019; No errata)
Updates RFC 5502
Last updated 2019-02-14
Replaces draft-mohali-sipcore-originating-cdiv-parameter
Stream IETF
Formats plain text html pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jean Mahoney
Shepherd write-up Show (last changed 2018-08-29)
IESG IESG state RFC 8498 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to Jean Mahoney <mahoney@nostrum.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                         M. Mohali
Request for Comments: 8498                                        Orange
Updates: 5502                                              February 2019
Category: Informational
ISSN: 2070-1721

             A P-Served-User Header Field Parameter for an
         Originating Call Diversion (CDIV) Session Case in the
                   Session Initiation Protocol (SIP)

Abstract

   The P-Served-User header field was defined based on a requirement
   from the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia
   Subsystem) in order to convey the identity of the served user, his/
   her registration state, and the session case that applies to that
   particular communication session and application invocation.  A
   session case is metadata that captures the status of the session of a
   served user regardless of whether or not the served user is
   registered or the session originates or terminates with the served
   user.  This document updates RFC 5502 by defining a new P-Served-User
   header field parameter, "orig-cdiv".  The parameter conveys the
   session case used by a proxy when handling an originating session
   after Call Diversion (CDIV) services have been invoked for the served
   user.  This document also fixes the ABNF in RFC 5502 and provides
   more guidance for using the P-Served-User header field in IP
   networks.

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 candidates 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
   https://www.rfc-editor.org/info/rfc8498.

Mohali                        Informational                     [Page 1]
RFC 8498         P-Served-User Parameter for CDIV in SIP   February 2019

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Mohali                        Informational                     [Page 2]
RFC 8498         P-Served-User Parameter for CDIV in SIP   February 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Basic Use Case  . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Problem Statement . . . . . . . . . . . . . . . . . . . .   5
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   5
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Proxy Behavior and Parameter Handling . . . . . . . . . . . .   6
   5.  Clarification of RFC 5502 Procedures  . . . . . . . . . . . .   7
   6.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  ABNF  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Call Flow Examples  . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Call Diversion Case . . . . . . . . . . . . . . . . . . .   9
     7.2.  Call Diversion and Privacy  . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
Show full document text