Re: [sipcore] About Join and Replaces Headers:

gao.yang2@zte.com.cn Tue, 28 September 2010 00:54 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 DBBF83A6A80 for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 17:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.268
X-Spam-Level:
X-Spam-Status: No, score=-100.268 tagged_above=-999 required=5 tests=[AWL=1.570, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 cCepIsyZBymc for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 17:54:52 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 7630A3A6A20 for <sipcore@ietf.org>; Mon, 27 Sep 2010 17:54:50 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101727820181; Tue, 28 Sep 2010 08:54:10 +0800 (CST)
Received: from [10.32.0.74] by [192.168.168.16] with StormMail ESMTP id 58640.3533455949; Tue, 28 Sep 2010 08:44:13 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse3.zte.com.cn with ESMTP id o8S0tUq0048438; Tue, 28 Sep 2010 08:55:31 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <4CA0D473.20903@cisco.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OF34EFE065.7FEFA79A-ON482577AC.0004629F-482577AC.00051161@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Tue, 28 Sep 2010 08:53:27 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-09-28 08:55:26, Serialize complete at 2010-09-28 08:55:26
Content-Type: multipart/alternative; boundary="=_alternative 0005115F482577AC_="
X-MAIL: mse3.zte.com.cn o8S0tUq0048438
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [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: Tue, 28 Sep 2010 00:54:52 -0000

Hi,

> That's not surprising, since Join is an extension to 3261.
> The semantics come from the join spec.

Yes, the Join's semantics should be defined in join spec(RFC3911).

> It seems those say that when you get an invite with Join, you should 
> create a conference. And then do mixing as required. If the conferencing 

> of the new call doesn't require mixing, that's fine too.

But I really didn't find the detailed defintion for Join header, about 
when to do mixing or not, in the join spec.

Maybe, some people would say thai it is intuitionistic. But there are 
people feel that it is not intuitionistic :)

Thanks,

Gao


--------------------------------------------------------
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.