That draft advises resetting Max-Forwards, but many people (including myself) think that is not correct because it subverts the intention of Max-Forwards loop detection, and in fact can potentially create an endless loop.
cheers, (-:bob -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vivek Talwar Sent: Friday, June 18, 2010 12:58 AM To: radhakrishna; Kamini Gangwani; [email protected] Subject: Re: [Sip-implementors] Max-Forwards Handling for B2BUA?? Hi all, Refer http://tools.ietf.org/html/draft-marjou-sipping-b2bua-01 Thanks & Regards, Vivek Talwar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of radhakrishna Sent: Friday, June 18, 2010 7:21 AM To: Kamini Gangwani; [email protected] Subject: Re: [Sip-implementors] Max-Forwards Handling for B2BUA?? Inline.... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kamini Gangwani Sent: Thursday, June 17, 2010 11:20 PM To: [email protected] Subject: [Sip-implementors] Max-Forwards Handling for B2BUA?? Hi All, I have a query regarding Max-Forwards handling in case of B2BUA. 1. If B2BUA receives Max-Forwards header as 1, then should B2BUA decrement it to 0 and then send it to peer side? No. UAC can never generate a request with Max-Forwards as 0. 2. What should happen in case when Max-Forwards received by B2BUA as 0 ? (In case of INVITE,B2BUA respond with 483 Too Many Hops But what should happen in case of ACK??) In our implementation, If the role of the stack is proxy we generate 483 and if the role of the stack is B2BUA or UAS we give it to application and let the application decide what to do. Can anybody please help me resolving these queries?? Thanks and Regards, Kamini Aricent "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ 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 ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ 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
