Oops, typo: Below, I meant that "A received 6xx response *is*
quarantined until all other branches have generated
a final response." Sorry about that.
On 04/22/2011 03:27 PM, Worley, Dale R (Dale) wrote:
> Tsk! But you don't know that every fork of the request has a
> request-URI in the invalid domain. That's the trouble with 6xx
> responses -- they assert something about every fork of a request,
> but no UAS can possibly know the RURIs of all the forks.
Dale: Right, but a proxy knows how many branches it
forked and the state of each branch.
Unlike rfc2543 where a received 6xx was immediately
forwarded, in rfc3261 this is not the case. A received
6xx response is not quarantined until all
other branches have generated a final response.
Admittedly, this is specified with a SHOULD normative
strength in rfc3261, but all the same because the rfc2543
behaviour caused the UAC to actually receive two final
responses for a request, I would presume that most
proxies today will handle 6xx processing as specified
by rfc3261. In that context, I think a 604 may be the
best response, no?
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / [email protected]
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
