On 6/9/2011 4:08 AM, Iñaki Baz Castillo wrote:
> 2011/6/9 Paul Kyzivat<pkyzi...@cisco.com>:
>> On 6/8/2011 3:50 PM, Iñaki Baz Castillo wrote:
>>
>>> Some existing proxies reply some custom 4XX codes for these kind of
>>> errors. I would like some specific and standarized 4XX response code,
>>> something like:
>>>
>>> 467 "Unsupported Transport"
>>
>> Go for it! Submit a draft. (Send it to the dispatch list.)
>> Put some text clearly explaining the problem and why existing mechanisms
>> don't provide a solution. After that motivation, you can propose the
>> solution.
>
> Thanks Paul, I'll strongly consider doing it. Just a comment before:
> wouldn't be 500/503 a suitable error code in this case? (however I do
> know that 503 is "suitable" in too much cases...).
For an unsupported/unrecognized transport, like sctp, 501 might be a
reasonable choice. It would be much better than 500 for that case. 500
could be used if its a *server* problem that you can't find anything
better for, but like 400 its overly vague.
In the cases of inconsistency (sips with udp) the problem is with the
request, not the server, and so a 4xx response is more appropriate.
503 is a terrible choice for any of these. It will cause the sender to
back off on sending requests. Its really only for overload types of
situations.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
