[SIPPING] question on draft-johnston-sipping-cc-conferencing-00.txt
Michael Hammer <mhammer@cisco.com> Tue, 05 November 2002 18:58 UTC
Received: via dmail-2000(11) for +imap/ietf/SIPPING; Tue, 5 Nov 2002 12:58:36 -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 gA5IwYWr005793 for <dean.willis@softarmor.com>; Tue, 5 Nov 2002 12:58:35 -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 gA5IXFv32153; Tue, 5 Nov 2002 13:33:15 -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 gA5IWhv32090 for <sipping@optimus.ietf.org>; Tue, 5 Nov 2002 13:32:43 -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 NAA03843 for <sipping@ietf.org>; Tue, 5 Nov 2002 13:30:12 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gA5IWtgX025632 for <sipping@ietf.org>; Tue, 5 Nov 2002 13:32:56 -0500 (EST)
Received: from mhammer-w2k01.cisco.com (hrn2-dhcp-161-44-87-91.cisco.com [161.44.87.91]) by cia.cisco.com (Mirapoint) with ESMTP id ABH78184; Tue, 5 Nov 2002 13:22:28 -0500 (EST)
Message-Id: <4.3.2.7.2.20021105122704.01b07458@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 05 Nov 2002 12:35:14 -0500
To: sipping@ietf.org
From: Michael Hammer <mhammer@cisco.com>
Subject: [SIPPING] question on draft-johnston-sipping-cc-conferencing-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: RO
X-Status:
X-Keywords:
X-UID: 3009
In this draft the creating of a new conference and the joining of an existing conference appear identical. Given that conference servers may host many conferences, and given that collision of selected identifiers could occur, is there any way for a user to indicate that they wish to connect to an existing conference versus creating a new one? A value such as "isnew" or "existing" could also permit, in the first case, an error indicating that a conference by that name already exists, or in the second case, an error indicating that a conference by that name does not exist. The presumption is that you do not want to interrupt an existing conference already in progress (case 1) or you do not want to create a conference (and pay corresponding charges) as an invitee if the invitor is not present (case 2). Is such a protection covered elsewhere in another draft? Mike _______________________________________________ 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
- [SIPPING] question on draft-johnston-sipping-cc-c… Michael Hammer
- Re: [SIPPING] question on draft-johnston-sipping-… Jonathan Rosenberg
- Re: [SIPPING] question on draft-johnston-sipping-… Michael Hammer
- Re: [SIPPING] question on draft-johnston-sipping-… Arjun Roychowdhury
- Re: [SIPPING] question on draft-johnston-sipping-… Paul Kyzivat