Re: [sipcore] About Join and Replaces Headers:

Paul Kyzivat <pkyzivat@cisco.com> Mon, 27 September 2010 17:28 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 ADB2B3A6C59 for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 10:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.205
X-Spam-Level:
X-Spam-Status: No, score=-110.205 tagged_above=-999 required=5 tests=[AWL=-0.206, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 W7He15m4mzx3 for <sipcore@core3.amsl.com>; Mon, 27 Sep 2010 10:28:45 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D81663A6AF4 for <sipcore@ietf.org>; Mon, 27 Sep 2010 10:28:44 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAHZxoExAZnwM/2dsb2JhbACUF44AcaxnnESFRASKOoJ+
X-IronPort-AV: E=Sophos;i="4.57,243,1283731200"; d="scan'208";a="164201621"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 27 Sep 2010 17:29:23 +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 o8RHTN8w000574; Mon, 27 Sep 2010 17:29:23 GMT
Message-ID: <4CA0D473.20903@cisco.com>
Date: Mon, 27 Sep 2010 13:29:23 -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: <OF7F9D8206.EC636B7D-ON482577AB.005566D1-482577AB.00569CCB@zte.com.cn>
In-Reply-To: <OF7F9D8206.EC636B7D-ON482577AB.005566D1-482577AB.00569CCB@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 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: Mon, 27 Sep 2010 17:28:46 -0000

On 9/27/2010 11:44 AM, gao.yang2@zte.com.cn wrote:
>
> Paul,
>
>  > An INVITE with Join or Replaces has its own offer/answer to negotiate
>  > the media used. If the new party wants to use less (or more) media than
>  > the existing call it can just negotiate that.
>
> Yes, the new party can put less(or more) m= lines in the SDPs. But the
> UAS's behavior for the new party's INVITE request is not clear.
>
> Considering Join header, there's no such defintion in RFC3911.

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

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.

	Thanks,
	Paul

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