Re: [sipcore] About RFC3911(Join header)'s potential error:
Paul Kyzivat <pkyzivat@cisco.com> Mon, 27 September 2010 13:34 UTC
Return-Path: <pkyzivat@cisco.com>
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 3717C3A6AD2 for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 06:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.505
X-Spam-Level:
X-Spam-Status: No, score=-110.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 n8Gb9Kv9RlEm for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 06:34:54 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 2E60F3A6AFF for <sipcore@ietf.org>; Mon, 27 Sep 2010 06:34:54 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAOs5oExAZnwM/2dsb2JhbACUM44AcaoonAqFRASKOoJ+
X-IronPort-AV: E=Sophos;i="4.57,243,1283731200"; d="scan'208";a="163913337"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 27 Sep 2010 13:35:32 +0000
Received: from [161.44.174.118] (dhcp-161-44-174-118.cisco.com [161.44.174.118]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o8RDZWqF006786; Mon, 27 Sep 2010 13:35:32 GMT
Message-ID: <4CA09DA4.3000402@cisco.com>
Date: Mon, 27 Sep 2010 09:35:32 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: gao.yang2@zte.com.cn
References: <OF779D11DC.0016793B-ON482577AA.000C1946-482577AA.000DA642@zte.com.cn>
In-Reply-To: <OF779D11DC.0016793B-ON482577AA.000C1946-482577AA.000DA642@zte.com.cn>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 13:34:56 -0000
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
- [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