Re: [SIPPING] question on draft-johnston-sipping-cc-conferencing-00.txt

Paul Kyzivat <pkyzivat@cisco.com> Wed, 06 November 2002 17:02 UTC

Received: via dmail-2000(11) for +imap/ietf/SIPPING; Wed, 6 Nov 2002 11:02:28 -0600 (CST)
Return-Path: <sipping-admin@ietf.org>
Received: from www1.ietf.org (ietf.org [132.151.1.19]) by bdsl.greycouncil.com (8.12.5/8.12.5) with ESMTP id gA6H2RWr014013 for <dean.willis@softarmor.com>; Wed, 6 Nov 2002 11:02:28 -0600
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GcAv26617; Wed, 6 Nov 2002 11:38:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Gavv25968 for <sipping@optimus.ietf.org>; Wed, 6 Nov 2002 11:36:57 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00567 for <sipping@ietf.org>; Wed, 6 Nov 2002 11:34:24 -0500 (EST)
Received: from cannon.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gA6GbAVM020639; Wed, 6 Nov 2002 11:37:10 -0500 (EST)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140]) by cannon.cisco.com (Mirapoint) with ESMTP id AAU31249; Wed, 6 Nov 2002 11:41:45 -0500 (EST)
Message-ID: <3DC94523.F9B8A5D5@cisco.com>
Date: Wed, 06 Nov 2002 11:36:51 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Hammer <mhammer@cisco.com>
CC: "Even, Roni" <roni.even@polycom.co.il>, sipping@ietf.org
Subject: Re: [SIPPING] question on draft-johnston-sipping-cc-conferencing-00.txt
References: <4.3.2.7.2.20021106094446.00b2cb28@cia.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Status: O
X-Status:
X-Keywords:
X-UID: 3031


Michael Hammer wrote:
> 
> So, back to the key question:  Is there some requirement that ensures that
> a URI will uniquely identify a distinct conference or some other parameter
> that indicates an attempt to create a new conference, allowing a conference
> server to inform the requestor that such an identity is already in use.

Mike,

While I have been asking to have some of the terminology clarified, I think what is currently published already makes it clear that a Conference URI uniquely identifies a particular conference - such that sending an invite to that URI will result in you becoming a participant in the conference.

However that doesn't guarantee that you can tell that a URI you have is a Conference URI. It might instead be (using the terminology I have proposed) a Conference Factory URI, or something else. There is an attempt in draft-johnston-sipping-cc-conferencing-00 to use callerprefs to distinguish these cases, but I think more work is required on that.

If you have a Conference URI, you can give it to all of your friends. Then when they call they will all be in the same conference together. But if you made a mistake and actually had a Conference Factory URI instead, you could still give it to all of your friends, and they could all call it, and each would end up in a conference. But they would each end up in a distinct conference by themself. So it is important to know which kind of URI you have.

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