[Sipping] Document Action: 'Multiple Dialog Usages in the Session Initiation Protocol' to Informational RFC
The IESG <iesg-secretary@ietf.org> Tue, 11 September 2007 19:21 UTC
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVBJ0-0003iS-LV; Tue, 11 Sep 2007 15:21:50 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1IVBIy-0003iG-H2 for sipping-confirm+ok@megatron.ietf.org; Tue, 11 Sep 2007 15:21:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVBIy-0003i5-5u; Tue, 11 Sep 2007 15:21:48 -0400
Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IVBIx-00073z-Qp; Tue, 11 Sep 2007 15:21:48 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 6BC68175EE; Tue, 11 Sep 2007 19:21:47 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IVBIw-0001di-Ur; Tue, 11 Sep 2007 15:21:46 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1IVBIw-0001di-Ur@stiedprstage1.ietf.org>
Date: Tue, 11 Sep 2007 15:21:46 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Internet Architecture Board <iab@iab.org>, sipping mailing list <sipping@ietf.org>, sipping chair <sipping-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Sipping] Document Action: 'Multiple Dialog Usages in the Session Initiation Protocol' to Informational RFC
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
The IESG has approved the following document: - 'Multiple Dialog Usages in the Session Initiation Protocol ' <draft-ietf-sipping-dialogusage-06.txt> as an Informational RFC This document is the product of the Session Initiation Proposal Investigation Working Group. The IESG contact persons are Jon Peterson and Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialogusage-06.txt Technical Summary Several methods in the Session Initiation Protocol can create an association between endpoints known as a dialog. Some of these methods can also create a different, but related, association within an existing dialog. These multiple associations, or dialog usages, require carefully coordinated processing as they have independent life-cycles, but share common dialog state. Processing multiple dialog usages correctly is not completely understood. What is understood is difficult to implement. This memo argues that multiple dialog usages should be avoided. It discusses alternatives to their use and clarifies essential behavior for elements that cannot currently avoid them. This is an informative document and makes no normative statements of any kind. Working Group Summary There was strong consensus within the WG that this was an important issue that needed to be documented in an RFC. Protocol Quality Jon Peterson is the Responsible Area Director. The PROTO shepherd for the document is Gonzalo Camarillo. Gen-ART review was provided by Pasi Eronen. Note to RFC Editor Section 5.4 OLD: Target refresh requests update the remote target of a dialog when they are successfully processed. The currently defined target refresh requests are INVITE, UPDATE, SUBSCRIBE and NOTIFY (clarified in a bug against RFC3565) and REFER (clarified in a bug against RFC3515 [4]). NEW: Target refresh requests update the remote target of a dialog when they are successfully processed. The currently defined target refresh requests are INVITE, UPDATE, SUBSCRIBE, NOTIFY, and REFER [4]. _______________________________________________ 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