[sipcore] 199 issue: UAC issue when proxies send unreliable 199 in case of Require:100rel

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 24 January 2011 17:09 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFC1D3A6AF6 for <sipcore@core3.amsl.com>; Mon, 24 Jan 2011 09:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.461
X-Spam-Level:
X-Spam-Status: No, score=-6.461 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 frwkZINoNwHT for <sipcore@core3.amsl.com>; Mon, 24 Jan 2011 09:09:52 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 319953A6B09 for <sipcore@ietf.org>; Mon, 24 Jan 2011 09:09:52 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-a5-4d3db30ecb93
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 10.07.23694.E03BD3D4; Mon, 24 Jan 2011 18:12:46 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Mon, 24 Jan 2011 18:12:28 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Mon, 24 Jan 2011 18:12:26 +0100
Thread-Topic: 199 issue: UAC issue when proxies send unreliable 199 in case of Require:100rel
Thread-Index: Acu76d/T5rktUPNuRt+UPdEqX8dydQ==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058519441FDB80@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7F2072F1E0DE894DA4B517B93C6A058519441FDB80ESESSCMS0356e_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [sipcore] 199 issue: UAC issue when proxies send unreliable 199 in case of Require:100rel
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2011 17:09:53 -0000

Hi,

An issue that came up during the review of 199 was whether the fact that a proxy was allowed to send unreliable 199 responses, even in the case of Require:100rel.

The WG previously agreed that Require:100rel as such does not affect proxies. But, the issue that has been raised is more related to the UAC: it could receive unreliable 199 responses even if it has required provisional responses to be sent reliably.

So, people asked whether we would need to update RFC 3262, and state that a UAC has to be ready to receive unreliable provisional responses even in the case of Require:100rel.

Another proposal was so simply say that a proxy is not allowed to send 199 responses in case of Require:100rel, and include a recommendation that the UAC does not use Require:100rel when also indicating support of 199 - unless the UAC also uses other extensions that mandates Require:100rel, that is.

My suggestion is to move forward with the second proposal, i.e. to say that a proxy must not send 199 responses in case of Require:100rel.

If someone objects to such way forward, please indicate it on the list (preferable together with an alternative solution) by Friday this week.

Thanks!

Regards,

Christer