Re: [Sip] Comments on draft-ietf-sip-199-00.txt
"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 05 August 2008 12:06 UTC
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E17F13A6CE9; Tue, 5 Aug 2008 05:06:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8803A28C264 for <sip@core3.amsl.com>; Tue, 5 Aug 2008 05:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level:
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWJ0q+fewKHw for <sip@core3.amsl.com>; Tue, 5 Aug 2008 05:06:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 614333A6BB1 for <sip@ietf.org>; Tue, 5 Aug 2008 05:06:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 78F8D20F1E; Tue, 5 Aug 2008 14:06:47 +0200 (CEST)
X-AuditID: c1b4fb3e-ae198bb000004ec0-11-48984257b251
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 49D8720EB0; Tue, 5 Aug 2008 14:06:47 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Aug 2008 14:06:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 05 Aug 2008 14:06:44 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0750A4EC@esealmw113.eemea.ericsson.se>
In-Reply-To: <48862EFF.3000908@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Comments on draft-ietf-sip-199-00.txt
thread-index: AcjsLbhdnHdc2li5QLWFG07rb8fWWQKw/Png
References: <88EAF47F-A9BE-4A8D-A849-41659EB90D12@nostrum.com> <48862EFF.3000908@cisco.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Robert Sparks <rjsparks@nostrum.com>
X-OriginalArrivalTime: 05 Aug 2008 12:06:47.0327 (UTC) FILETIME=[BC188AF0:01C8F6F3]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Comments on draft-ietf-sip-199-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
Hi, >>7) Section 7: "A UAC that receives a 199 response for an early dialog MUST NOT >>send any further requests on that dialog...". Can you point to any list discussion >>around this requirement? I think there's some danger to consider there. At the >>very least we need to make this statement multiple-usage safe. > >This is a very good catch. This needs to be aligned with dialogusage. If the 199 contained the final response that triggered it, then that final response could be used to determine the impact >on the dialog or dialog usage or just the transaction. But if the 199 doesn't contain the final response, then this is a problem. I forgot to bring this issue up in Dublin. Sorry for that. First, we need to remember that the UAS may terminate every dialogusage when sending the final response (depending on what final response is sent), without the UAC knowing it. And, due to the forking rules, the final response which is sent to the UAC may not even be the same which was sent by the UAS, if a final response from another UAS is chosen as the "best". Second, we need to remember that this only affects early-dialogusages. If needed, I guess we could include the final response which triggered the 199, but we could also simply say that if the UAC does not know to which dialogusage (if there are many) the 199 applies, it should not do anything which may affect other usages for the same early dialog. >>12) The open issue in section 10 (can we get a proxy involved in >>sending its own 199 reliably) is a big part of the confusion I pointed to at >>the beginning of these comments. This is the part of the draft that I expected >>needing face time in Dublin, but maybe we can make enough progress on it in the >>hallway. >>I don't think there's any way to allow it, and what we'll need instead is text >>more strongly recommending the endpoints do this themselves and >>restrict any proxy genesis of 199s to the unreliable case (and explain >>more that this is just a transitionary optimization - we _really_ want the >>endpoints doing this work if anything's going to be doing it at all. > >If the "proxy" wants to send a reliable 199, then I think it needs to do so on its own dialog. But that makes no sense. Having the proxy attempt to send the reliable response on the dialog >belonging to the UAS is *insane*. Let's discuss this in the "open issues" thread. Regards, Christer _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Comments on draft-ietf-sip-199-00.txt Robert Sparks
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Paul Kyzivat
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Paul Kyzivat
- [Sip] Should early dialogs be dropped when 2xx is… Paul Kyzivat
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Paul Kyzivat
- Re: [Sip] Should early dialogs be dropped when 2x… Bob Penfield
- Re: [Sip] Should early dialogs be dropped when 2x… Sanjay Sinha (sanjsinh)
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt -… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt -… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt -… Paul Kyzivat
- Re: [Sip] Should early dialogs be dropped when 2x… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Ian Elz
- [Sip] Multiple early-dialog usages [was RE: Comme… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Paul Kyzivat
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Ian Elz
- Re: [Sip] Multiple early-dialog usages [was RE: C… Paul Kyzivat
- Re: [Sip] Multiple early-dialog usages [was RE: C… Christer Holmberg
- Re: [Sip] Multiple early-dialog usages [was RE: C… Paul Kyzivat
- Re: [Sip] Multiple early-dialog usages [was RE: C… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt -… Christer Holmberg
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Robert Sparks
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Ian Elz
- Re: [Sip] Comments on draft-ietf-sip-199-00.txt Paul Kyzivat
- Re: [Sip] Routing when B2BUA involved (was Commen… Ian Elz