A little late, but one consideration:
Deprecating the last hop exception means that if the last hop proxy supports
this specification, the UAC has no way to request SIPS up to the last hop
(which it may want to do; best-effort TLS using sip: will probably not work
in the intermediate period until this specification is widely supported).
Would it be an idea for the draft to define request disposition tags
(RFC3841) "last-hop-exception" and "no-last-hop-exception"? Then the UA
could use SIPS, but indicate its preference to allow the last hop exception,
and get "almost-end-2-end" security
Regards,
Jeroen
Dean Willis wrote:
I'm pleased to announce that the authors think that the SIPS draft is
ready for working group last call. This draft has had the privilege
of more review prior to WGLC than most of our other efforts, so
perhaps it won't be too controversial.
Please make a final read through the draft and bring any comments
back to this list.
I'd like to conclude this WGLC by July 16, 2007, so get your comments
back in by then. And I'll plan to put some discussion time on the
agenda in Chicago.
Thanks, and have a great weekend.
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
