A P-Served-User Header Field Parameter for Originating CDIV session case in Session Initiation Protocol (SIP)
draft-ietf-sipcore-originating-cdiv-parameter-08

Document Type Active Internet-Draft (sipcore WG)
Last updated 2018-12-10 (latest revision 2018-12-09)
Replaces draft-mohali-sipcore-originating-cdiv-parameter
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html 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 Approved-announcement to be sent
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 None
SIPCORE Working Group                                          M. Mohali
Internet-Draft                                                    Orange
Updates: 5502 (if approved)                            December 10, 2018
Intended status: Informational
Expires: June 13, 2019

A P-Served-User Header Field Parameter for Originating CDIV session case
                  in Session Initiation Protocol (SIP)
            draft-ietf-sipcore-originating-cdiv-parameter-08

Abstract

   The P-Served-User header field was defined based on a requirement
   from 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 this
   particular communication session and application invocation.  A
   session case is metadata that captures the status of the session of a
   served user: whether the served user is registered or not, and
   whether the session originates or terminates with the served user.
   This document updates RFC5502 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 13, 2019.

Mohali                    Expires June 13, 2019                 [Page 1]
Internet-Draft      P-Served-User parameter orig-cdiv      December 2018

Copyright Notice

   Copyright (c) 2018 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Basic Use Case  . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Problem Statement . . . . . . . . . . . . . . . . . . . .   4
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   5
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Proxy behavior and parameter handling . . . . . . . . . . . .   5
   5.  Clarification of RFC5502 procedures . . . . . . . . . . . . .   6
   6.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  ABNF  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Call Flow Examples  . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Call diversion case . . . . . . . . . . . . . . . . . . .   8
     7.2.  Call diversion and privacy  . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text