[Standards] Jingle: what's left?

Unnikrishnan V ukv1977 at gmail.com
Wed Jun 27 19:41:13 UTC 2007

Why not transport descriptions carry the key info than using media band,
jingle also is  offer answer model.

2 cents :-)

On 6/26/07, Peter Saint-Andre <stpeter at jabber.org> wrote:
> Unnikrishnan V wrote:
> >  SRTP for media
> I don't think it's up to us to solve the secure media problem. There is
> a lot of ongoing discussion about this topic on the rtpsec mailing list
> at the IETF (mostly ZRTP vs. DTLS-SRTP). What we need to do is enable
> the two parties to include the right bits in their signalling exchange
> so they can use DTLS-SRTP if they want to (ZRTP is negotiated entirely
> within the media band, so it is totally out of scope for Jingle). And I
> think we have already defined those bits in XEP-0167 and XEP-0180,
> because the Jingle client can include "UDP/TLS/RTP/AVP" as the value of
> the <content/> element's 'profile' attribute -- this essentially a
> Jingle mapping of what is specified in draft-fischl-mmusic-sdp-dtls.
> Naturally the XMPP signalling path should also be secure, but that is a
> separate problem (join the security at xmpp.org list to discuss it if you'd
> like).
> Peter
> --
> Peter Saint-Andre
> XMPP Standards Foundation
> http://www.xmpp.org/xsf/people/stpeter.shtml
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070627/8e157e01/attachment.html>

More information about the Standards mailing list