From: "Elwell, John" <[EMAIL PROTECTED]> [JRE] The BLISS ACH design team feels that, on balance, 6xx response codes should be strictly "everywhere", to be consistent with RFC 3261. Also, the design team had seen "global rejection" as being a 6xx response code and applying "everywhere".
In the general case, a call will have many targets, and no one recipient can speak authoritatively for all the targets. The fact that the call is unwanted by one recipient is not evidence that it is unwanted by all recipients, and sending a global rejection is simply incorrect, it puts more power in the hands of a recipient than they are authorized to have. Now it is true that if the call is "telephone-like" and the original request-URI is an AOR all of whose targets are in some small domain, then one recipient may be able to speak for all targets. But as SIP becomes more popular, more and more calls won't be like this. Designing features that break in the face of complex call routing is building in trouble for the future. Dale _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
