IETF Logo Mail Archive

Re: [Sipping] Query related to draft-ietf-sipping-service-examples-11

Dale.Worley@comcast.net Sat, 11 November 2006 04:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GikVS-00076g-Pg; Fri, 10 Nov 2006 23:30:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GikVR-00076Z-GS for sipping@ietf.org; Fri, 10 Nov 2006 23:30:13 -0500
Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GikVQ-0006E4-9p for sipping@ietf.org; Fri, 10 Nov 2006 23:30:13 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (alnrmhc11) with ESMTP id <20061111043011b1100fkb1de>; Sat, 11 Nov 2006 04:30:11 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id kAB4UAQg027503 for <sipping@ietf.org>; Fri, 10 Nov 2006 23:30:10 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id kAB4UAK6027498; Fri, 10 Nov 2006 23:30:10 -0500
Date: Fri, 10 Nov 2006 23:30:10 -0500
Message-Id: <200611110430.kAB4UAK6027498@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <4554CF49.5020804@alcatel.fr> (Thomas.Froment@alcatel.fr)
Subject: Re: [Sipping] Query related to draft-ietf-sipping-service-examples-11
References: <014a01c704e0$935e3a80$3801a8c0@newportnetworks.com> <4554CD54.1080309@cisco.com> <4554CF49.5020804@alcatel.fr>
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sipping-bounces@ietf.org

   From: Thomas.Froment@alcatel.fr

   > The bookkeeping to manage the multiple dialogs is currently already 
   > required for forking, so no added implementation is required. 

   In that case, why not completely deprecate forking itself?

Heh -- you know that has been seriously proposed.  But like jumping a
chasm, it's not something to be done by halves.  Until you actually
eliminate forking, you can't twiddle the parts of the protocol that
are needed to cope with forking.

Dale

_______________________________________________
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

v2.23.0 | Report a Bug | By Email