Re: [sipcore] About Join and Replaces Headers: //Replaces header's extension

gao.yang2@zte.com.cn Thu, 07 October 2010 16:52 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 25B3D3A6F90 for <sipcore@core3.amsl.com>; Thu, 7 Oct 2010 09:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.26
X-Spam-Level:
X-Spam-Status: No, score=-100.26 tagged_above=-999 required=5 tests=[AWL=1.578, 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 DxKnWUBcoaZS for <sipcore@core3.amsl.com>; Thu, 7 Oct 2010 09:52:54 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 63ED13A6FA0 for <sipcore@ietf.org>; Thu, 7 Oct 2010 09:52:52 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101727820181; Fri, 8 Oct 2010 00:52:39 +0800 (CST)
Received: from [10.32.0.74] by [192.168.168.16] with StormMail ESMTP id 79135.1967002180; Fri, 8 Oct 2010 00:51:31 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse3.zte.com.cn with ESMTP id o97GsClH063315; Fri, 8 Oct 2010 00:54:12 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FFC79CEC@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OF0D29FE54.2E14D118-ON482577B5.005B9861-482577B5.005CD1A4@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Fri, 08 Oct 2010 00:51:48 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-10-08 00:53:51, Serialize complete at 2010-10-08 00:53:51
Content-Type: multipart/alternative; boundary="=_alternative 005CD1A3482577B5_="
X-MAIL: mse3.zte.com.cn o97GsClH063315
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] About Join and Replaces Headers: //Replaces header's extension
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: Thu, 07 Oct 2010 16:52:55 -0000

> You are focusing on the fact that you want to replace the user's 
> connection to a particular media stream.  But the Replaces header 
> specifies whether or not a *dialog* is replaced by another *dialog*,
> not whether a particular media rendering is replaced by another. 
> The only way that you can associate two dialogs while keeping them 
> both in existence is with Join.

Yes. This is the current defintion for Replaces header and Join header.

> 
> I think your usage would be helped by adding extension attributes to
> SDP so that which media stream was to replace/be mixed with which 
> other media streams (in a Join) could be specified.
> 

I once evaluated SDP extension. But the controlling semantics for the use 
case is about session control, while not session/streams attributes. So, I 
think the extension should be signalling control oriented, while not 
SDP(description) oriented.

So, I think the potential extension should be located in SIP headers, 
while not SDP.

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.