IETF Logo Mail Archive

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

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 30 September 2010 20:25 UTC

Return-Path: <dworley@avaya.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 4D6163A6E4D for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 13:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level:
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, 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 JCs1uB5ZteKd for <sipcore@core3.amsl.com>; Thu, 30 Sep 2010 13:25:36 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2B0C63A69C4 for <sipcore@ietf.org>; Thu, 30 Sep 2010 13:25:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,261,1283745600"; d="scan'208";a="209966221"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Sep 2010 16:26:21 -0400
X-IronPort-AV: E=Sophos;i="4.57,261,1283745600"; d="scan'208";a="521824787"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Sep 2010 16:26:20 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 30 Sep 2010 16:26:20 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "gao.yang2@zte.com.cn" <gao.yang2@zte.com.cn>
Date: Thu, 30 Sep 2010 16:23:18 -0400
Thread-Topic: [sipcore] About RFC3911(Join header)'s potential error:
Thread-Index: ActeSOAY/Ik+6kXUTMKMQ9Zk14Jq+AClHFkj
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C7F@DC-US1MBEX4.global.avaya.com>
References: <OF779D11DC.0016793B-ON482577AA.000C1946-482577AA.000DA642@zte.com.cn>, <4CA09DA4.3000402@cisco.com>
In-Reply-To: <4CA09DA4.3000402@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 30 Sep 2010 20:25:37 -0000

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@cisco.com]

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

I think that Paul is correct here.  If two dialogs go to a server and are joined at the server, and both dialogs are sendonly at the server, then "mixing" is very simple: the one source (generated by the server) is duplicated as RTP to each dialog's remote end.

In practice, one might say that this "does not allocate mixing resources".  OTOH, for some implementations, this duplication of the media stream may require the allocation of a mixing resource, if no other component of the server can perform the duplication.

I do not see this as a problem that needs to be solved.

Dale

v2.23.0 | Report a Bug | By Email