RE: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC
"Ian Elz \(CV/ETL\)" <ian.elz@ericsson.com> Tue, 08 May 2007 14:06 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlQKb-0001Ws-Cg; Tue, 08 May 2007 10:06:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk0Nq-00049Q-0z; Fri, 04 May 2007 12:11:50 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hk0Nn-0007SP-Bi; Fri, 04 May 2007 12:11:50 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id C8E1C20B2C; Fri, 4 May 2007 18:11:46 +0200 (CEST)
X-AuditID: c1b4fb3c-a7ce9bb0000073d5-a1-463b5b425188
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id AB122209DB; Fri, 4 May 2007 18:11:46 +0200 (CEST)
Received: from esealmw118.eemea.ericsson.se ([153.88.200.77]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 May 2007 18:11:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 04 May 2007 18:11:43 +0200
Message-ID: <C0E80510684FE94DBDE3A4AF6B968D2D0120AA11@esealmw118.eemea.ericsson.se>
In-Reply-To: <E1Hh6Bl-0003Cd-Lg@megatron.ietf.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC
Thread-Index: AceIGjSPl8117rF3ReiPJxV5QNkF0gGSPf3g
From: "Ian Elz (CV/ETL)" <ian.elz@ericsson.com>
To: ietf@ietf.org
X-OriginalArrivalTime: 04 May 2007 16:11:46.0487 (UTC) FILETIME=[E9DF1C70:01C78E66]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
X-Mailman-Approved-At: Tue, 08 May 2007 10:06:14 -0400
Cc: sipping@ietf.org
Subject: RE: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
I have noted the last call on this draft and the proposal to raise the draft to Informational RFC status. While this draft gives a very detailed view of the issues relating to multiple dialog usage it also provides recommendations in areas where there is no or little examination of specific areas. In section 5.7 Replacing Usages there is the statement: ...the interactions between Replaces and multiple dialog usages have not been well explored. More discussion of this topic is needed. Implementers should avoid this scenario completely. I do not believe that an informational RFC should include recommendations based upon little or no examination or lack of understanding of specific areas. The draft as a whole recommends avoiding multiple dialog usage as it may be difficult to implement the required logic while only offering alternatives in simple network cases. With new ietf draft documents being published which highlight the impact on the network of B2BUA nodes I believe that there should be some examination of the impact of proposing that each new dialog usage be on a new dialog will have on networks which include B"B User Agents. If recommendations are made which influence vendors to only develop user agents which support single usage dialogs we may come to the situation where B2BUAs cannot be used in the network. This would prevent specific security measures such as identity hiding from untrusted networks as it would not be possible to map Contact headers. It would also prevent topology hiding. Preventing both of these measures could result increase the prevalence of denial of service and other attacks on the network. While the proposals in this draft may prove to be a worthwhile addition to the knowledge of dialog and usage handling in the internet I believe that raising this draft to RFC status before the relevant studies have been undertaken in the associated areas, which are currently being studied, is premature. Ian Elz Office: + 44 24 764 35256 gsm: +44 7801723668 ian.elz@ericsson.com ------------------------------------------------------------------------ - Message: 3 Date: Thu, 26 Apr 2007 09:39:45 -0400 From: The IESG <iesg-secretary@ietf.org> Subject: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC To: IETF-Announce <ietf-announce@ietf.org> Cc: sipping@ietf.org Message-ID: <E1Hh4CH-0005jM-0q@stiedprstage1.ietf.org> The IESG has received a request from the Session Initiation Proposal Investigation WG (sipping) to consider the following document: - 'Multiple Dialog Usages in the Session Initiation Protocol ' <draft-ietf-sipping-dialogusage-06.txt> as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-05-10. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialogusage-06.tx t IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag= 14041&rfc_flag=0 _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- RE: [Sipping] Last Call: draft-ietf-sipping-dialo… Ian Elz (CV/ETL)
- RE: [Sipping] Last Call: draft-ietf-sipping-dialo… Ian Elz (CV/ETL)