> When a request reaches the proxy, if mf becomes 0 once proxy > decrements the mf,then it means it has already hopped n > number of times right, then why proxy should send to next hop. > > i mean, see this example where mf is 5 > mf=5 mf =4 mf =3 mf =2 mf =1 > mf =0 > UA1--> Proxy A--> Proxy B--> Proxy C-->Proxy D--> Proxy E-->UA2 > > Now at Proxy E mf is 0, means it has already visited 5 nodes, > so it shdn't be forwarded anymore,so proxy E shd return with > 483 response. > > Please correct me if i am wrong.
If the received value is 1, it should proxy it instead of returning a 483. Since numerous vendors might be interpreting this differently, someone potentially should open a bug against rfc3261 for clarification purposes. My understanding of Max-Forwards is mainly taken from section rfc3261 section 16.3 step 3 and rfc2543 section 6.23. I mention rfc2543 because section 6.23 is extremely clear and I do not think rfc3261 is attempting to introduce a non backward compatible meaning of Max-Forwards. rfc3261 section 16.3 step 3: "If the request contains a Max-Forwards header field with a field value of zero (0), the element MUST NOT forward the request." rfc2543 section 6.23: "If the received value is zero (0), the recipient MUST NOT forward the request." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
