[sipcore] About Join and Replaces Headers:

gao.yang2@zte.com.cn Sat, 25 September 2010 08:29 UTC

Return-Path: <gao.yang2@zte.com.cn>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF3593A6A70 for <sipcore@core3.amsl.com>; Sat, 25 Sep 2010 01:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.888
X-Spam-Level:
X-Spam-Status: No, score=-99.888 tagged_above=-999 required=5 tests=[AWL=1.350, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3YpDVfSAqrX for <sipcore@core3.amsl.com>; Sat, 25 Sep 2010 01:29:04 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 5BB1B3A6A6E for <sipcore@ietf.org>; Sat, 25 Sep 2010 01:29:03 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951727820181; Sat, 25 Sep 2010 16:27:24 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 55813.1727820181; Sat, 25 Sep 2010 16:29:29 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o8P8TPMd086987 for <sipcore@ietf.org>; Sat, 25 Sep 2010 16:29:25 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
To: "sipcore@ietf.org" <sipcore@ietf.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OFA80B079B.EE0E79D1-ON482577A9.002C6A2E-482577A9.002E9C5B@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Sat, 25 Sep 2010 16:27:13 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-09-25 16:29:11, Serialize complete at 2010-09-25 16:29:11
Content-Type: multipart/alternative; boundary="=_alternative 002E9C5A482577A9_="
X-MAIL: mse2.zte.com.cn o8P8TPMd086987
Subject: [sipcore] About Join and Replaces Headers:
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Sep 2010 08:29:05 -0000

By RFC3911 and RFC3981, the handling object of Join and Replaces headers 
is dialog:

RFC3911: The Join header is used to logically join an existing SIP dialog 
with a new SIP dialog.
RFC3981: The Replaces header is used to logically replace an existing SIP 
dialog with a new SIP dialog. 

Dialog has meaning is signalling level, not for service level. So, if we 
use Join and Replaces's semantics to build call service, the real handling 
object should be session.

For normal usage, such as:
A and B has a session;
C send a INVITE with Join header to A;
A build a basic conference for the three-party.

But if we consider some more complex use case, there might be problems. A 
and B has a audio and video call, and C just want to join to the audio 
part(part of the streams). 

Abstractly, the problem is how can we express the semantics, such as Join 
part of the streams in current session or Replaces part of the streams in 
current session? 

Thanks,

Gao

===================================
 Zip    : 210012
 Tel    : 87211
 Tel2   :(+86)-025-52877211
 e_mail : gao.yang2@zte.com.cn
===================================

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.