Re: [Sip] Reg. refresher param in 2xx response
Brett Tate <brett@broadsoft.com> Tue, 18 May 2010 12:19 UTC
Return-Path: <brett@broadsoft.com>
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 2A2B53A6BAE for <sip@core3.amsl.com>;
Tue, 18 May 2010 05:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.025
X-Spam-Level:
X-Spam-Status: No, score=-1.025 tagged_above=-999 required=5 tests=[AWL=-1.027,
BAYES_50=0.001, HTML_MESSAGE=0.001]
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 046zhZ6GKh7l for
<sip@core3.amsl.com>; Tue, 18 May 2010 05:18:59 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtp-out01.seaservers.net
[72.37.232.66]) by core3.amsl.com (Postfix) with ESMTP id 593293A6B93 for
<sip@ietf.org>; Tue, 18 May 2010 05:17:26 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80::a488:d1ec:a706:3a6d]) by
CASUMHUB02.citservers.local ([::1]) with mapi; Tue, 18 May 2010 05:17:18 -0700
From: Brett Tate <brett@broadsoft.com>
To: Harbhanu <harbhanu@huawei.com>, "sip@ietf.org" <sip@ietf.org>
Date: Tue, 18 May 2010 05:16:14 -0700
Thread-Topic: [Sip] Reg. refresher param in 2xx response
Thread-Index: Acr2ZuRMSu4+qoDaR7qbmzSKijoBigAG+8eQ
Message-ID: <747A6506A991724FB09B129B79D5FEB614815B6E27@EXMBXCLUS01.citservers.local>
References: <0C4DE8BD80D149D2BC3D940CA05CE74F@china.huawei.com>
In-Reply-To: <0C4DE8BD80D149D2BC3D940CA05CE74F@china.huawei.com>
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_747A6506A991724FB09B129B79D5FEB614815B6E27EXMBXCLUS01ci_"
MIME-Version: 1.0
Subject: Re: [Sip] Reg. refresher param in 2xx response
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-Archive: <http://www.ietf.org/mail-archive/web/sip>
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>
X-List-Received-Date: Tue, 18 May 2010 12:19:06 -0000
If 2xx's session-expires doesn't contain the mandatory refresher parameter, it is likely because interworking with an old implementation of the draft: http://tools.ietf.org/wg/sip/draft-ietf-sip-session-timer/ The refresher parameter was added within version 5 of the draft. Per RFC4028, it is an abnormal situation; I don't recall the RFC indicating how to act within the abnormal situation. Thus you can however you want. From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Harbhanu Sent: Tuesday, May 18, 2010 4:49 AM To: sip@ietf.org Subject: [Sip] Reg. refresher param in 2xx response As per 4028, for the following case UAS MUST specify the refresher parameter in 2xx response. UAC ----INV ----> supported=timer, SE=90-----> UAS UAC <----2XX INV -- SE=90- ---------------- UAS [Section-9, page-16] The UAS MUST set the value of the refresher parameter in the Session-Expires header field in the 2xx response. But IMO when UE sends response for INVITE and it adds Session-Expires but doesn't specify the refresher parameter. Then in this case UAC can safely assume that, either the UAS doesn't support session-timer or it doesn't want to act as a 'refresher'. So instead of sending a BYE UAC MAY treat this as a buggy/naive UE & hence "UAC" SHOULD act as 'refresher'. Please share your opinion. Thanks! Regards, Harbhanu ***************************************************************************************************************************************************************************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
- [Sip] Reg. refresher param in 2xx response Harbhanu
- Re: [Sip] Reg. refresher param in 2xx response Brett Tate
- Re: [Sip] Reg. refresher param in 2xx response Harbhanu
- Re: [Sip] Reg. refresher param in 2xx response Kevin P. Fleming