[Sip] Reg. refresher param in 2xx response

Harbhanu <harbhanu@huawei.com> Tue, 18 May 2010 08:53 UTC

Return-Path: <harbhanu@huawei.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 4B3523A67B6 for <sip@core3.amsl.com>; Tue, 18 May 2010 01:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.106
X-Spam-Level: **
X-Spam-Status: No, score=2.106 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 u8RTkDUna54R for <sip@core3.amsl.com>; Tue, 18 May 2010 01:53:17 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 287FC3A6A4F for <sip@ietf.org>; Tue, 18 May 2010 01:51:12 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L2L008GLXSWW1@szxga03-in.huawei.com> for sip@ietf.org; Tue, 18 May 2010 16:48:32 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L2L0038DXSWWF@szxga03-in.huawei.com> for sip@ietf.org; Tue, 18 May 2010 16:48:32 +0800 (CST)
Received: from BLRNSHTIPL1NC ([10.18.1.31]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L2L007P9XSV29@szxml04-in.huawei.com> for sip@ietf.org; Tue, 18 May 2010 16:48:32 +0800 (CST)
Date: Tue, 18 May 2010 14:18:31 +0530
From: Harbhanu <harbhanu@huawei.com>
To: sip@ietf.org
Message-id: <0C4DE8BD80D149D2BC3D940CA05CE74F@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_Ru2IxJMeWW3wJONRhpWvPA)"
Thread-index: Acr2ZuRMSu4+qoDaR7qbmzSKijoBig==
Subject: [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 08:53:20 -0000

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!