[Sipping] comments on draft-ietf-sipping-cc-framework-00.txt
"Even, Roni" <roni.even@polycom.co.il> Tue, 05 March 2002 18:30 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15324 for <sipping-archive@odin.ietf.org>; Tue, 5 Mar 2002 13:30:38 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA24855 for sipping-archive@odin.ietf.org; Tue, 5 Mar 2002 13:30:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA21644; Tue, 5 Mar 2002 13:00:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA21613 for <sipping@optimus.ietf.org>; Tue, 5 Mar 2002 13:00:32 -0500 (EST)
Received: from accord-ntsrv3.accord-domain ([212.199.61.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12666 for <sipping@ietf.org>; Tue, 5 Mar 2002 13:00:26 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19) id <FSC8NFA0>; Tue, 5 Mar 2002 14:10:45 +0200
Message-ID: <B2518D608282D511BEA400508BBB9148EA9D73@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: sipping@ietf.org
Date: Tue, 05 Mar 2002 14:10:44 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="windows-1255"
Subject: [Sipping] comments on draft-ietf-sipping-cc-framework-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Hi, I read the draft and I think it is a good idea to put a framework document for multiparty. I have a couple of comments 1. The document include a reference to a conferencing bridge and to a mixer. I think that the terms should be clear. My understanding of a mixer as defined in RTP (see 4.5.1.1) is that it handles only the media streams and is not dependent on a signalling protocol. I think that the decomposed approach of a conference bridge that is build from controller and media processor (mixer) may be used. In section 4.3.2 it says "In a centralized mixing model, all participants have a pairwise SIP and media relationship with the mixer." a mixer does not have SIP relationship. Same in 4.4 "For example, a mixer involved in a conversation space may wish to provide URLs for conference status, and/or conference/floor control. " 2. In section 4.3.2.2 "Once the server is discovered, a conference ID is chosen. This ID must be globally unique." I think that we need to specify how this is done. Does the server select the ID for the ad-hoc conference. If the user defines it, we need to specify how to inform that the conference ID is not unique. 3. Section 4.4 presents the topic of conveying Information and Events based on draft-rosenberg-sip-call-package-00.txt. How do you see the relationship between the documents, does this document present requirements for the draft-rosenberg-sip-call-package-00.txt document. I think that this is a question about the way we address other requirements that are related to other documents. I have some specific events that make sense in a conferencing environment. For example in audio conference to notify who is the loudest speaker currently (enabling an application that will present it to the participants) In video conference the requirement is to know who is being seen by the others. 4. In 4.5.1.1 "For example, the default combining for an audio conference would be an N-1 configuration. In other words, each user receives a mixed media stream that represents the combined audio of all the users except himself or herself. " This statement may be true for a small conference. In large conferences the policy is to mix M loudest speakers out of the N participants (M is typically 3). Thanks Roni Even *********************** Roni Even Polycom Network Systems Tel: +972-3-9251200 Mobile: +972-55-481099 Fax: +972-3-9211571 Email: roni.even@polycom.co.il _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP