draft-ietf-sipcore-originating-cdiv-parameter-06.txt   draft-ietf-sipcore-originating-cdiv-parameter-07.txt 
SIPCORE Working Group M. Mohali SIPCORE Working Group M. Mohali
Internet-Draft Orange Internet-Draft Orange
Updates: 5502 (if approved) November 05, 2018 Updates: 5502 (if approved) November 05, 2018
Intended status: Informational Intended status: Informational
Expires: May 9, 2019 Expires: May 9, 2019
A P-Served-User Header Field Parameter for Originating CDIV session case A P-Served-User Header Field Parameter for Originating CDIV session case
in Session Initiation Protocol (SIP) in Session Initiation Protocol (SIP)
draft-ietf-sipcore-originating-cdiv-parameter-06 draft-ietf-sipcore-originating-cdiv-parameter-07
Abstract Abstract
The P-Served-User header field is used to convey the identity of the The P-Served-User header field is used to convey the identity of the
served user and the session case that applies to this particular served user and the session case that applies to this particular
communication session and application invocation. This document communication session and application invocation. This document
updates RFC5502 by defining a new P-Served-User header field updates RFC5502 by defining a new P-Served-User header field
parameter, "orig-cdiv". The parameter conveys the session case used parameter, "orig-cdiv". The parameter conveys the session case used
by a proxy when handling an originating session after Call Diversion by a proxy when handling an originating session after Call Diversion
(CDIV) services have been invoked for the served user. This document (CDIV) services have been invoked for the served user. This document
skipping to change at page 5, line 5 skipping to change at page 5, line 5
(Alice) should not be restricted because the diverting user (Bob) has (Alice) should not be restricted because the diverting user (Bob) has
a privacy service for his own identity. The privacy of the diverting a privacy service for his own identity. The privacy of the diverting
user should apply to information related to this user only (eg. in user should apply to information related to this user only (eg. in
the History-Info header field). In the same manner, some specific the History-Info header field). In the same manner, some specific
services will need to be triggered on the outgoing leg after a call services will need to be triggered on the outgoing leg after a call
diversion. Without a dedicated session case for originating after diversion. Without a dedicated session case for originating after
CDIV, the S-CSCF cannot trigger an originating service for the CDIV, the S-CSCF cannot trigger an originating service for the
diverting user, nor can an AS execute the procedures for this diverting user, nor can an AS execute the procedures for this
particular session case. particular session case.
For this use case, this document creates a new parameter for the For this use case, this document creates a new parameter ("orig-
originating after CDIV session case to be embedded in the P-Served- cdiv") for the originating after CDIV session case to be embedded in
User header field. the P-Served-User header field.
2. Conventions and Terminology 2. Conventions and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Applicability 3. Applicability
 End of changes. 2 change blocks. 
4 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/