Re: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC
Paul Kyzivat <pkyzivat@cisco.com> Fri, 04 May 2007 16:32 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 1Hk0iB-0003dB-Qu; Fri, 04 May 2007 12:32:51 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Hk0iA-0003X5-6m for sipping-confirm+ok@megatron.ietf.org; Fri, 04 May 2007 12:32:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk0i9-0003W7-T4; Fri, 04 May 2007 12:32:49 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hk0i9-00033w-Gy; Fri, 04 May 2007 12:32:49 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 04 May 2007 12:32:50 -0400
X-IronPort-AV: i="4.14,492,1170651600"; d="scan'208"; a="59418280:sNHT112886394"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l44GWn1T020759; Fri, 4 May 2007 12:32:49 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l44GWglk001721; Fri, 4 May 2007 16:32:49 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 May 2007 12:32:37 -0400
Received: from [161.44.174.124] ([161.44.174.124]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 May 2007 12:32:37 -0400
Message-ID: <463B6024.1080902@cisco.com>
Date: Fri, 04 May 2007 12:32:36 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Ian Elz (CV/ETL)" <ian.elz@ericsson.com>
Subject: Re: [Sipping] Last Call: draft-ietf-sipping-dialogusage (Multiple Dialog Usages in the Session Initiation Protocol) to Informational RFC
References: <C0E80510684FE94DBDE3A4AF6B968D2D0120AA11@esealmw118.eemea.ericsson.se>
In-Reply-To: <C0E80510684FE94DBDE3A4AF6B968D2D0120AA11@esealmw118.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 May 2007 16:32:37.0151 (UTC) FILETIME=[D3534AF0:01C78E69]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4100; t=1178296369; x=1179160369; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sipping]=20Last=20Call=3A=20draft-ietf-sipping-dialo gusage=20(Multiple=0A=20Dialog=20Usages=20in=20the=20Session=20Initiation= 20Protocol)=20to=20Informational=20RFC |Sender:=20 |To:=20=22Ian=20Elz=20(CV/ETL)=22=20<ian.elz@ericsson.com>; bh=6HqN4xQ8xBrIkeOAwLgEg3ndCBDaIQauRWv7WNajMag=; b=MxbxTtUuBkhYuS9x1/Bg7Ik3dEyr9McCs3v41QCn7+TQDL4OM2FFcRcws7shn21dpAev8KN2 q3wGgbbup9Cde2MgMCewZHNtS/Z2QKN2hfqj9LHcUyUrNsG5DBn4qGTz;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: sipping@ietf.org, ietf@ietf.org
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
Ian, Can you say more about what issues you see presented by B2BUAs when choosing between a multiple-usage dialog and several single-usage dialogs? Thanks, Paul Ian Elz (CV/ETL) wrote: > > 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 > > > > > > > > _______________________________________________ > 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 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] Last Call: draft-ietf-sipping-dialogusa… The IESG
- RE: [Sipping] Last Call: draft-ietf-sipping-dialo… Ian Elz (CV/ETL)
- Re: [Sipping] Last Call: draft-ietf-sipping-dialo… Paul Kyzivat
- RE: [Sipping] Last Call: draft-ietf-sipping-dialo… Ian Elz (CV/ETL)