Subject: RE: [Sip] Typo in RFC 3261 - regarding REGISTER processing

From: [email-masked]
Date: Thu, 4 Mar 2004 04:15:53 +0200

In RFC3261, Expires header in a 200 of a REGISTER has no meaning. The contact header must contain the expires parameter. If that is not so in the flow, then there is a bug in the flow.
 
Now, if you want to be backwards compatible with RFC2543, I suggest that your UA accepts such responses and handles them appropriately.
 
/Hisham

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]On Behalf Of ext [email-masked]
Sent: 03.March.2004 17:25
To: [email-masked]
Subject: [Sip] Typo in RFC 3261 - regarding REGISTER processing

Page 66 details how a registrar should process a REGISTER message, in particular:- 

"Each Contact value MUST feature an "expires" parameter indicating its expiration interval chosen by the registrar." 

However, inspection of the registration example on page 214 shows a 200OK without an expires parameter, it has an Expires header instead. 

Which of these is correct? I really do want to do the minimum amount of parsing in my app. 

Matthew Gardiner 
Software Engineer 
Aculab 
Tel: +44 (0) 1908 273 911 
Fax: +44 (0) 1908 273 801 
Email: mailto:[email-masked] 
Website: < http://www.aculab.com> 

For Aculab's privacy policy and E-Mail disclaimer, Click Here : http://www.aculab.com/company/legal_notice.htm.