Hi, see below.
[EMAIL PROTECTED] wrote: > > rfc3261/bis-09 state the following in section 8.1.1.7 > > " > The branch parameter value MUST be unique across space and time for > all requests sent by the UA. The exceptions to this rule are CANCEL > and ACK for non-2xx responses. As discussed below, a CANCEL request > will have the same value of the branch parameter as the request it > cancels. As discussed in Section 17.1.1.3, an ACK for a non-2xx > response will also have the same branch ID as the INVITE whose > response it acknowledges. > > The uniqueness property of the branch ID parameter, to facilitate > its use as a transaction ID, was not part of RFC 2543. > " > > Does the uniqueness of the branch id applies to the proxy also? Although > the section in the rfc for > the proxy(16.6.8) mentions that it shall follow the guidelines of section > 8.1.1.7 . > > Does the proxy have to use a different via for each SIP request, for > example a reinvite from a > UAC whould be proxied using a different via? > Refer > > The call flows in draft-ietf-sipping-call-flows-00.txt don't reflect such a > scenario. I just send comments about this issue last weeks and the authors are actually fixing that issue (among other ones..) So this is an error from the draft-ietf-sipping-call-flows-00.txt. Aymeric > -Deepak > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
