Hello, I think what you suggest is good (be liberal while receiving and adhere to standards while sending).
It's possible that the Parser may fail to parse Expires header, but may still be able to parse rest of the message successfully. If that's the case, then the omission of Expires header would suggest the default expiry (i.e., 3600 seconds). -Vishal -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Wright Sent: Monday, May 05, 2008 5:26 PM To: [email protected] Subject: [Sip-implementors] Expires: header field w/ missing expiration param What should the behavior of a registrar be if it receives a REGISTER request w/ an Expires: header that has no expiration parameter? In other words, instead of getting Expires: 3600 it gets Expires: I looked briefly through Section 7 of 3261 and didn't immediately see anything addressing this anomalous case. On the one hand I could see a case for just dropping the message (since it's malformed); on the other hand, a robust implementation might want to reply w/ 200 OK that has a default expiration value associated with it. Thanks, Jeffrey Wright System Test Engineering Manager Aztek Networks _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
