Robert, yes, 4.2.1 just says Proxies required to perform loop-detection SHOULD create a branch value separable into two parts , it does not say only when proxy need fork the req , it will add the second part. So I don't see it means as sec 4.2.2, This second part will not be present if the message was not forked when that Via header field value was added. Thanks -Rockson
________________________________ From: Robert Sparks [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2008 12:11 AM To: Rockson Li (zhengyli) Cc: [email protected] Subject: Re: [Sip] draft-ietf-sip-fork-loop-fix-07: is the second part of branch of present when req forked? What you are looking for is in this paragraph in 4.2.1: Proxies required to perform loop-detection by RFC XXXX (RFC-Editor: replace XXXX with the RFC number of this document) have an additional constraint on the value they place in the Via header field. Such proxies SHOULD create a branch value separable into two parts in any implementation dependent way. The first part MUST satisfy the constraints of Section 8.1.1.7. The second part is used to perform loop detection and distinguish loops from spirals. On Aug 17, 2008, at 8:22 AM, Rockson Li (zhengyli) wrote: Hi folks, One question on draft-ietf-sip-fork-loop-fix-07, sec 4.2.2 This second part will not be present if the message was not forked when that Via header field value was added. I am not sure why? from sec 4.2.1, I do NOT see there's any constraints that the second party would be added only when the msg is forked. thanks Regards, -Rockson _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
