[sipcore] About RFC3911(Join header)'s potential error:

gao.yang2@zte.com.cn Sun, 26 September 2010 02:28 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 0C2243A68F1 for <sipcore@core3.amsl.com>; Sat, 25 Sep 2010 19:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.17
X-Spam-Level:
X-Spam-Status: No, score=-100.17 tagged_above=-999 required=5 tests=[AWL=1.668, 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 EYjFH-wDYL5h for <sipcore@core3.amsl.com>; Sat, 25 Sep 2010 19:28:50 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 7B1233A6814 for <sipcore@ietf.org>; Sat, 25 Sep 2010 19:28:48 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101727820181; Sun, 26 Sep 2010 10:28:12 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 85748.1727820181; Sun, 26 Sep 2010 10:18:11 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o8Q2TGJ5078151 for <sipcore@ietf.org>; Sun, 26 Sep 2010 10:29:16 +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: <OF779D11DC.0016793B-ON482577AA.000C1946-482577AA.000DA642@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Sun, 26 Sep 2010 10:27:11 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-09-26 10:29:08, Serialize complete at 2010-09-26 10:29:08
Content-Type: multipart/alternative; boundary="=_alternative 000DA63D482577AA_="
X-MAIL: mse2.zte.com.cn o8Q2TGJ5078151
Subject: [sipcore] About RFC3911(Join header)'s potential error:
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: Sun, 26 Sep 2010 02:28:51 -0000

Hi,

By section 4 of RFC3911(User Agent Server Behavior: Receiving a Join 
Header), UAS always create mixing or conferencing resources for authorized 
INVITE with Join header:

If authorization is successful, the UA attempts to accept the new INVITE, 
and assign any mixing or conferencing resources necessary to complete the 
join.

But I think it is not necessary, while it should depend on SDP's send and 
recv attribute.

Let's consider a use case for IPTV system or VoD system:
User_A connects to a vedio channel/file;
User_A want to share this vedio with User_B synchronous, and shared the 
dialog information with User_B;
User_B send INVITE with Join header to Join in the vedio 
broadcast/multicast;

In fact, User_A and User_B all just have downlink media for the stream. 
So, the media server needn't create  any mixing or conferencing resources. 
The server just need to duplicate the media stream to User_B.

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.