|
In section 4.2 http://www.ietf.org/internet-drafts/draft-ietf-sip-sips-04.txt proposes
that a proxy should send 403 rather than apply the last hop
exception.
Instead, I would propose that it would send a 302
with either the registered Contact or the received request URI with a "sip:"
scheme. 403 would be confusing, because the caller cannot distinguish between
this case and the callee refusing his call. Perhaps a new response code (4xx
Unsecure transport not allowed) would be better.
Perhaps a caller preference should be defined to
request such behavior, similar to "fork" and "no-fork" (RFC3841). Say
"no-sips-sip"
Regards,
Jeroen
|
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip