[Sip] About register expiration
"Rachel Danor" <Rachel@radvision.com> Tue, 22 March 2005 17:07 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05643 for <sip-web-archive@ietf.org>; Tue, 22 Mar 2005 12:07:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDmwJ-0003AQ-Sj for sip-web-archive@ietf.org; Tue, 22 Mar 2005 12:13:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDmnR-00069S-3i; Tue, 22 Mar 2005 12:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DDmnO-00069B-R6 for sip@megatron.ietf.org; Tue, 22 Mar 2005 12:03:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05311 for <sip@ietf.org>; Tue, 22 Mar 2005 12:03:56 -0500 (EST)
Received: from [80.74.106.10] (helo=rvil-mail.RADVISION.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DDmsh-0002vn-Dh for sip@ietf.org; Tue, 22 Mar 2005 12:09:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Mar 2005 19:03:49 +0200
Message-ID: <AC563C86795A3146A6997ADFA393C284FD59C1@rvil-mail.radvision.com>
Thread-Topic: About register expiration
Thread-Index: AcUvAR4o6sVAZL5oRoKc9O8D+TQLKQ==
From: Rachel Danor <Rachel@radvision.com>
To: sip@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129
Subject: [Sip] About register expiration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0068781614=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8068004c042dabd7f1301bcc80e039df
Hi, I have a question the SIP standard definitions for "expires" handling in the registration. This is what I see in paragraph 10.3: The registrar returns a 200 (OK) response. The response MUST contain Contact header field values enumerating all current bindings. Each Contact value MUST feature an "expires" parameter indicating its expiration interval chosen by the registrar. From this I understand that the 200OK must include expires parameter in the contact header. On the other hand when I look at message examples in paragraph 24.1, I see the following: F1 REGISTER Bob -> Registrar REGISTER sip:registrar.biloxi.com SIP/2.0 Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7 Max-Forwards: 70 To: Bob <sip:bob@biloxi.com> From: Bob <sip:bob@biloxi.com>;tag=456248 Call-ID: 843817637684230@998sdasdh09 CSeq: 1826 REGISTER Contact: <sip:bob@192.0.2.4> Expires: 7200 Content-Length: 0 F2 200 OK Registrar -> Bob SIP/2.0 200 OK Via: SIP/2.0/UDP bobspc.biloxi.com:5060;branch=z9hG4bKnashds7 ;received=192.0.2.4 To: Bob <sip:bob@biloxi.com>;tag=2493k59kd From: Bob <sip:bob@biloxi.com>;tag=456248 Call-ID: 843817637684230@998sdasdh09 CSeq: 1826 REGISTER Contact: <sip:bob@192.0.2.4> Expires: 7200 Content-Length: 0 Where the registrar does not set the expires parameter in the contact header, but leaves it in the Expires header. Which is correct? Is it allowed to have both Expires header and expires parameter for Contact headers in the 200OK? Regards, Rachel Danor
_______________________________________________ Sip mailing list https://www1.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] About register expiration Rachel Danor
- Re: [Sip] About register expiration Udit_Goyal
- RE: [Sip] About register expiration Brett Tate
- [Sip] another bug in rfc3261 register example Juha Heinanen