Re: [Sip] response to merged requests

[Jonathan Rosenberg <jdrosen@dynamicsoft.com>]

I don't think there was an explicit decision to not define a new 
response code. The error condition seemed close enough to a loop (its 
another topology failure) that it was reasonable to reuse the code.

-Jonathan R.

Ravi Shiroor wrote:
> posting this on sip as there were no responses on sip-implementors.
>
> --------->
>
> section 8.2.2.2 in RFC 3261 says that when a UAS receives
> merged requests, it should respond to the INVITEs receieved
> after the first one (those detected as merged) with 482 (loop detected).
>
> i was wondering why "loop detected" is being being used when
> merged requests are receieved? wouldnt it be appropriate to
> define a specific 4xx response for merged requests?
>
> can somebody please clarify if there is a valid reason for
> using "loop detected" in this scenario?
>
> TIA,
> ravi.
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
--
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip