Re: [sipcore] About RFC3911(Join header)'s potential error:
gao.yang2@zte.com.cn Mon, 27 September 2010 15:31 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 EB6773A6D6E for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 08:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.649
X-Spam-Level:
X-Spam-Status: No, score=-96.649 tagged_above=-999 required=5 tests=[AWL=-2.028, BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_102=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 iJGnPvo5YudY for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 08:31:41 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id D807E3A6D75 for <sipcore@ietf.org>; Mon, 27 Sep 2010 08:31:39 -0700 (PDT)
Received: from [10.34.0.130] by mx5.zte.com.cn with surfront esmtp id 35101727820181; Mon, 27 Sep 2010 23:31:06 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 55813.3533455949; Mon, 27 Sep 2010 23:32:12 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o8RFWVav096342; Mon, 27 Sep 2010 23:32:31 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <4CA09DA4.3000402@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: <OF38464CD2.E448294E-ON482577AB.00537C5F-482577AB.00555596@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Mon, 27 Sep 2010 23:30:10 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2010-09-27 23:32:08, Serialize complete at 2010-09-27 23:32:08
Content-Type: multipart/alternative; boundary="=_alternative 00555593482577AB_="
X-MAIL: mse2.zte.com.cn o8RFWVav096342
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [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: Mon, 27 Sep 2010 15:31:43 -0000
Paul, IMO, no matter the original concept of RFC3911 is always create mixing or conferencing resources, or it depends on SDP attributes(as I showed in the IPTV scenario), the UAS's behavior for INVITE with Join header is not quit correct/clear by current text in RFC3911. The UAS's behavior in the IPTV scenario is my understanding. It seems that you have the similar understanding(that's nice). But there's people said that this is not defined in the RFC3911, once in one discussion. Though I think my/our understanding is reasonable, but I admit that RFC3911 really hasn't do such definition. And if the Join INVITE with less or more media streams(m= lines), how would the UAS behave as? I think this also not clear now. Thanks, Gao =================================== Zip : 210012 Tel : 87211 Tel2 :(+86)-025-52877211 e_mail : gao.yang2@zte.com.cn =================================== Paul Kyzivat <pkyzivat@cisco.com> 2010-09-27 21:35 收件人 gao.yang2@zte.com.cn 抄送 "sipcore@ietf.org" <sipcore@ietf.org> 主题 Re: [sipcore] About RFC3911(Join header)'s potential error: Gao, I think the works you are concerned about already are consistent with the scenario you raise. Specifically, > and assign any mixing or conferencing resources necessary to complete the join includes the case where no mixing or conferencing resources are necessary. Thanks, Paul On 9/25/2010 10:27 PM, gao.yang2@zte.com.cn wrote: > > 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. > > > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore -------------------------------------------------------- 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.
- [sipcore] About RFC3911(Join header)'s potential … gao.yang2
- Re: [sipcore] About RFC3911(Join header)'s potent… Paul Kyzivat
- Re: [sipcore] About RFC3911(Join header)'s potent… gao.yang2
- Re: [sipcore] About RFC3911(Join header)'s potent… Worley, Dale R (Dale)
- Re: [sipcore] About RFC3911(Join header)'s potent… gao.yang2