I think this question belongs on the implementors list. Without citing a reference, I expect a proxy adding R-R to subsequent requests should follow all the same rules it did when a it added itself in the initial request.
Note on your last sentence, the UAC must not create a route-set using R-R's in subsequent requests. The route set created from the initial request persists throughout the dialog, only the Contacts can change. John Hearty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 8:31 AM To: [EMAIL PROTECTED] Subject: [Sip] Proxy inserting Record-Route RFC3261 says: "If this proxy wishes to remain on the path of future requests in a dialog created by this request (assuming the request creates a dialog), it MUST insert a Record-Route header field value into the copy before any existing Record-Route header field values, even if a Route header field is already present." It fails to mention where the proxy should adds that record-route header. On top or bottom of the existing record-route headers. I deduce that it should add it on top since a UAS must copy record-route headers to a response reserving the order. Also a UAC creating a route-set uses these record-route headers taking them in reverse order. Did I miss it in the spec? Regards, Hisham _______________________________________________ Sip mailing list https://www1.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-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
