Hi, One of the use-cases for the keep parameter is non-registration emergency calls, where Outbound can't be used even if supported. However, a question has come up whether it could also be useful in certain emergency use-cases WITH registration. At least in 3GPP, when a UA performs an emergency registration, the S-CSCF/registrar does not insert itself in the "path" (it does not insert Service-Route), which means that the INVITE for the emergency call will not traverse the S-CSCF. And, therefor the usage of Outbound is not needed, since there is no idea of establishing multiple flows between the UA and the S-CSCF/registrar. So, in this case tFrom sip-bounces at ietf.org Tue Aug 26 03:36:53 2008 Return-Path: <sip-bounces at ietf.org> X-Original-To: sip-archive at optimus.ietf.org Delivered-To: ietfarch-sip-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CCD828C106; Tue, 26 Aug 2008 03:36:53 -0700 (PDT) X-Original-To: sip at core3.amsl.com Delivered-To: sip at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 400C728C0FD for <sip at core3.amsl.com>; Tue, 26 Aug 2008 03:36:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[AWL=-0.549, BAYES_50=0.001, HELO_EQ_SE=0.35, 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 0zrewFrELPdv for <sip at core3.amsl.com>; Tue, 26 Aug 2008 03:36:51 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id ABECF28C104 for <sip at ietf.org>; Tue, 26 Aug 2008 03:36:50 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1690F208B0 for <sip at ietf.org>; Tue, 26 Aug 2008 12:36:40 +0200 (CEST) X-AuditID: c1b4fb3c-ab0c8bb0000015b5-1b-48b3dcb77ed8 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id EE57420843 for <sip at ietf.org>; Tue, 26 Aug 2008 12:36:39 +0200 (CEST) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Aug 2008 12:36:39 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 26 Aug 2008 12:36:39 +0200 Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0797BFC7 at esealmw113.eemea.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: keep parameter also for registered emergency calls? Thread-Index: AckHZ59CVN5HlE4eS4iW6eo/rklIPw=From: "Christer Holmberg" <christer.holmberg at ericsson.com> To: "SIP IETF" <sip at ietf.org> X-OriginalArrivalTime: 26 Aug 2008 10:36:39.0698 (UTC) FILETIME=[9F929720:01C90767] X-Brightmail-Tracker: AAAAAA=Subject: [Sip] keep parameter also for registered emergency calls? X-BeenThere: sip at 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 at ietf.org?subject=unsubscribe> List-Post: <mailto:sip at ietf.org> List-Help: <mailto:sip-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request at ietf.org?subject=subscribe> Content-Type: multipart/mixed; boundary="==============!32609204==" Sender: sip-bounces at ietf.org Errors-To: sip-bounces at ietf.org This is a multi-part message in MIME format.Title: keep parameter also for registered emergency calls?
Hi,
One of the use-cases for the keep parameter is non-registration emergency calls, where Outbound can't be used even if supported.
However, a question has come up whether it could also be useful in certain emergency use-cases WITH registration.
At least in 3GPP, when a UA performs an emergency registration, the S-CSCF/registrar does not insert itself in the "path" (it does not insert Service-Route), which means that the INVITE for the emergency call will not traverse the S-CSCF.
And, therefor the usage of Outbound is not needed, since there is no idea of establishing multiple flows between the UA and the S-CSCF/registrar.
So, in this case the keep parameter could be used by the UA and P-CSCF/edge proxy to indicate support of keep-alive also for registration emergency calls.
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 at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip