hi Joachim,
Strictly going by the spec, which clearly spells out the Max Forward value to be 70, one would by default reject the request with an appropriate 4xx Response.
Though as Chris mentioned, you could just simply ignore the value provided and consider it to be 70, which means that you do not even need to look at that header. So this puts the question on why do we want to have the header then.
Also if you do not reject it the UA which has this implementation will continue to retain the Max Fwd with the wrong value, which is not helping its cause either. So i guess sticking to the guidelines may help here.
Rama
(LeapStone Systems)
Kross Joachim ICM N PG U ID A 1 <[EMAIL PROTECTED]> wrote:
Hi all,
I am wondering about other people's opinion:
How should a proxy behave that receives a Max-Forwards header field with a
value that is outside the bounds given by RFC 3261 (i.e. 0-255):
* Reject the request with a 400 Bad Request, or
* Silently lower the value to be within the bounds? What value should
be used? The recommended 70?
Thank you!
Regards,
Joachim
--
Joachim Kro� SIEMENS ICM N PG C E A 1
UMTS IP Multimedia Subsystem - CSCF development
Phone: +49 89 722 34513 Hofmannstra�e 51
Fax: +49 89 722 58726 D-81359 M�nchen
email: [EMAIL PROTECTED]
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
