Hi Hadriel and thanks for this draft. So last year I attempted to address your first issue (4.1) with regard to a response code that would "force" a failover (http://tools.ietf.org/html/draft-schwartz-sipping-nsr-code-01) and there was no take-up. I was relating at the time exactly to this problem you describe that has since been solved by reason phrases and other silly and proprietary mechanisms. I still think that there should be a difference between: * I can't help you and no one can (e.g. user is not online - 404) * I can't help you do to some temporary issue (network - 503 or otherwise - 480) * I can't help you but feel free to try elsewhere (e.g. cannot find a route to the target do to one of many reasons) And I still feel that there should be a new response code to this last category. Your thoughts? D. _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
