On 7/9/08 4:19 PM, Dan Wing wrote:
But it doesn't matter what the ITSPs do inside their networks -
we can do this without the ITSP needing to do per-transaction
crypto, or TLS, or squat. If it causes them no harm, causes
them no grief, and lets them continue Business As Usual, it's
a win for them and a win for the edge (their subscribers).
We can provide edge-to-edge identity (between enterprises, or
handset-to-handset) in both worlds: the world that exists (which
has ITSPs with B2BUAs and SBCs) and the world that we hope will
exist (RFC3263 routing on the Internet, perhaps with some
peer-to-peer sprinkled on top). SIP's current identity mechanism,
RFC4474+RFC4916, only works with the latter.
I want an identity mechanism that works with both. And I have
long been convinced it is possible to build such a beast.
But *who* is going to deploy it?
/a
_______________________________________________
Sip mailing list https://www.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
