Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D9DF28C0D9; Tue, 20 Jan 2009 08:14:34 -0800 (PST) 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 BD6B63A6B0E for ; Tue, 20 Jan 2009 08:14:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.098 X-Spam-Level: X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, 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 uwngOhxWA1uS for ; Tue, 20 Jan 2009 08:14:31 -0800 (PST) Received: from mx03.net.com (mx03.net.com [134.56.3.133]) by core3.amsl.com (Postfix) with ESMTP id C03CA3A6929 for ; Tue, 20 Jan 2009 08:14:31 -0800 (PST) Received: from mx01-int.net.com (mx01-int.net.com [134.56.112.13]) by mx03.net.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id n0KGEAJr010988; Tue, 20 Jan 2009 08:14:10 -0800 (PST) Received: from fmt-ex01.net.com (fmt-exchange [134.56.112.251]) by mx01-int.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id n0KG8ccH028301; Tue, 20 Jan 2009 08:08:38 -0800 (PST) Received: from fmt-ex07.net.com ([134.56.113.16]) by fmt-ex01.net.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 20 Jan 2009 08:19:39 -0800 Received: from fmt-qex01.quintum.com (134.56.116.12) by fmt-ex07.net.com (134.56.113.16) with Microsoft SMTP Server (TLS) id 8.1.240.5; Tue, 20 Jan 2009 08:14:10 -0800 Received: from fmt-qex01.quintum.com ([134.56.116.12]) by fmt-qex01.quintum.com ([134.56.116.12]) with mapi; Tue, 20 Jan 2009 08:14:10 -0800 From: Neelakantan Balasubramanian To: Gert Olsson , "sip@ietf.org" Date: Tue, 20 Jan 2009 08:14:08 -0800 Thread-Topic: SIP de-REGISTER: Expires header vs expires parameter i Contact Thread-Index: Acl6+jv/20UE0jY8SkKYLXKhRqw4sgAH7RKA Message-ID: <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-OriginalArrivalTime: 20 Jan 2009 16:19:39.0466 (UTC) FILETIME=[E4CB3AA0:01C97B1A] Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1500445553==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============1500445553== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_" --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable See RFC 3261 Section 10.2.1.1 10.2.1.1 Setting the Expiration Interval of Contact Addresses When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. Thanks, Neel. From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Gert = Olsson Sent: Tuesday, January 20, 2009 6:26 AM To: sip@ietf.org Subject: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Conta= ct Hi, SIP de-registration is performed by sending a REGISTER message with either = a Contact header containing an 'expires=3D0' parameter or an Expires header= with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any = decent server, if it has found 'expires=3D0' in the Contact header (or in a= ll if many), just happily ignore an Expires header? [Neelakantan Bala] See RFC 3261 Section 10.2.1.1 10.2.1.1 Setting the Expiration Interval of Contact Addresses When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. Thanks, Neel. br /GO __________________________________________________________________| Gert Olsson / phone: +46 10 7154604 / e-mail: gert.olsson@ericsson.co= m Ericsson AB - Business Unit Mobile Platforms, SE-221 83 Lund, Sweden --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable SIP de-REGISTER: Expires header vs expires parameter i Contact</titl= e> <style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:"Comic Sans MS"; panose-1:3 15 7 2 3 3 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p {mso-style-priority:99; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman","serif";} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>See RFC 3261 Section 10.2.1.1<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>10.2.1.1 Setting the Expiration Interval of Contact Addresse= s<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   When a client sends a REGISTER request, it MAY suggest an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval that indicates how long the client wou= ld like the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registration to be valid.  (As described i= n Section 10.3, the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registrar selects the actual time interval base= d on its local<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   policy.)<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   There are two ways in which a client can sugges= t an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval for a binding: through an Expires head= er field or an<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   "expires" Contact header parameter.&n= bsp; The latter allows expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   intervals to be suggested on a per-binding basi= s when more than one<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   binding is given in a single REGISTER request, whereas the former<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   suggests an expiration interval for all Contact header field values<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   that do not contain the "expires" parameter.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Thanks,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Neel.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in = 4.0pt'> <div> <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'> <p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma= ","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] <b>On Behalf Of </b>Gert Olsson<br> <b>Sent:</b> Tuesday, January 20, 2009 6:26 AM<br> <b>To:</b> sip@ietf.org<br> <b>Subject:</b> [Sip] SIP de-REGISTER: Expires header vs expires parameter = i Contact<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>Hi,</span> <o:p= ></o:p></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>SIP de-registra= tion is performed by sending a REGISTER message with either a Contact header containing an 'expires=3D0' parameter or an Expires header with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any decent server, if = it has found 'expires=3D0' in the Contact header (or in all if many), just hap= pily ignore an Expires header?</span><o:p></o:p></p> <p><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"= ; color:#1F497D'>[Neelakantan Bala] <o:p></o:p></span></i></b></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>See RFC 3261 Section 10.2.1.1<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>10.2.1.1 Setting the Expiration Interval of Contact Addresse= s<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   When a client sends a REGISTER request, it MAY suggest an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval that indicates how long the client wou= ld like the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registration to be valid.  (As described i= n Section 10.3, the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registrar selects the actual time interval base= d on its local<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   policy.)<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   There are two ways in which a client can sugges= t an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval for a binding: through an Expires head= er field or an<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   "expires" Contact header parameter.&n= bsp; The latter allows expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   intervals to be suggested on a per-binding basi= s when more than one<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   binding is given in a single REGISTER request, whereas the former<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   suggests an expiration interval for all Contact header field values<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   that do not contain the "expires" parameter.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Thanks,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Neel.<o:p></o:p></span></p> <p><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"= ; color:#1F497D'><o:p> </o:p></span></i></b></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>br</span> <o:p>= </o:p></p> <p><i><span style=3D'font-family:"Comic Sans MS";color:maroon'>/GO</span></= i> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >__________________________________________________________________|</span> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >Gert Olsson   /  phone: +46 10 7154604   /  e-mail= : gert.olsson@ericsson.com</span> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >Ericsson AB - Business Unit Mobile Platforms, SE-221 83  Lund, Sweden</span> <o= :p></o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> </div> </div> </body> </html> --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_-- --===============1500445553== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sip mailing list https://www.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 --===============1500445553==--