Max-Forwards is mandatory in REGISTER request. (Table 2 of RFC 3261) You can reject with 400 Bad Request if Max-Forwards is missing.
Somesh * Please do not take print out of this e-mail unless its absolutely necessary * -----Original Message----- From: [email protected] on behalf of cool goose Sent: Tue 2/24/2009 11:06 AM To: [email protected] Subject: [Sip-implementors] Max-Forwards header field Hi Guys, RFC 3261 states that Max-Forwards is one of the mandatory field in Sec. 8.1.1. Also, it specifies that a UAC must insert Max-Forward header field into each request it originates. Now, my questions is: Is it ok for a registrar to accept a REGISTER request from UAC with out a Max-Forward header field? If not what would be an ideal response? If the registrar is not proxying the register requests will the request validation rules specified in Sec 16.3 apply ? Thanks a Lot, CoolGoose. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors EMAIL DISCLAIMER : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised distribution or copying is strictly prohibited. If you receive this transmission in error, please notify the sender by reply email and then destroy the message. Opinions, conclusions and other information in this message that do not relate to official business of Mascon shall be understood to be neither given nor endorsed by Mascon. Any information contained in this email, when addressed to Mascon clients is subject to the terms and conditions in governing client contract. Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we can not guarantee that any email or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions. Mascon grants no warranties regarding performance, use or quality of any e-mail or attachment and undertakes no liability for loss or damage, howsoever caused. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
