[Jingle] Jingle / e2e security (1)

[Peter Saint-Andre]

Robert McQueen wrote:
> Peter Saint-Andre wrote:
>> Robert McQueen wrote:
>>> "Enabling" ZRTP in Jingle entails doing precisely nothing in the
>>> standards we're writing. If people want to signal ZRTP usage in their
>>> signalling, they can draft a XEP for a <zomg xmlns="...zrtp"/> element
>>> you can throw in the appropriate place. If we include everything that
>>> floats by in the main XEPs they'll grow without bounds and  become very
>>> confusing. If we talk about SRTP at all it should be in the context of a
>>> loving E2E relationship. :P
>> This is true. That's why I suggested we could write a small spec that
>> would enable you to include the zrtp-hash in a session-info message.
> 
> If by "we" you mean "anyone who cares". My suspicion is that's an empty
> intersection with those currently actually implementing Jingle. 

The SIP-Communicator folks would be interested, I think, and they plan
to add Jingle support sometime before, say, FOSDEM 2010. But I can work
with them on a XEP when they are ready to help out on that front.

> For the
> moment I think it suffices to handwave and say yes it's possible and
> someone could do that if they want to, and that we've already wasted too
> many electrons on this thread let alone a XEP (even a small one). :)

It would take me very little time to move the zrtp-hash stuff that I
provisionally put in XEP-0167 to a separate spec. Maybe I'll park that
in the inbox so we have it in reserve...

/psa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/jingle/attachments/20090217/5c9fe12c/attachment.bin