[Sipping] parallel transactions on separate dialogs
"Daniel G. Petrie" <dpetrie@pingtel.com> Fri, 14 December 2001 03:47 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 WAA07462 for <sipping-archive@odin.ietf.org>; Thu, 13 Dec 2001 22:47:47 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA05281 for sipping-archive@odin.ietf.org; Thu, 13 Dec 2001 22:47:48 -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 WAA04679; Thu, 13 Dec 2001 22:29:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA04648 for <sipping@ns.ietf.org>; Thu, 13 Dec 2001 22:29:07 -0500 (EST)
Received: from mail.pingtel.com (IDENT:root@mail.pingtel.com [216.91.1.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06122 for <sipping@ietf.org>; Thu, 13 Dec 2001 22:29:04 -0500 (EST)
Received: from pingtel.com (32-201-131-12.bellhead.com [12.131.201.32]) by mail.pingtel.com (8.11.0/8.11.0) with ESMTP id fBE3TGo03821; Thu, 13 Dec 2001 22:29:16 -0500
Message-ID: <3C197080.F45EED60@pingtel.com>
Date: Thu, 13 Dec 2001 22:22:40 -0500
From: "Daniel G. Petrie" <dpetrie@pingtel.com>
Organization: Pingtel Corp. http://www.pingtel.com
X-Mailer: Mozilla 4.73 [en]C-{C-UDP; EBM-SONY1} (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Sparks <rsparks@dynamicsoft.com>, Alan Johnston <alan.johnston@wcom.com>, sipping@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] parallel transactions on separate dialogs
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
Content-Transfer-Encoding: 7bit
This is perhaps a general issue for drafts that have multi-dialog example message flows. There are situations in these flows where some transactions can occur in varying orders. For example in the consultative transfer examples there is no reason, that a hold on the original dialog and the original INVITE on the consultative dialog cannot happen at the same time. The examples typically serialize these sorts of flows as it is difficult to illustrate otherwise. As people tend to take the examples too literally or as gospel, it would be good if we can annotate this in the flows and in the descriptive text. This is an issue to the drafts and perhaps others: draft-ietf-sip-cc-transfer-05.txt draft-ietf-sip-service-examples-03.txt _______________________________________________ Sipping mailing list http://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] parallel transactions on separate dialo… Daniel G. Petrie