[Council] Fwd: Re: [Jingle] Fwd: [Standards] LAST CALL: XEP-0262 (Use of ZRTP in Jingle RTP Sessions)
stpeter at stpeter.im
Thu May 19 13:42:07 UTC 2011
Pokage loop completed. :)
-------- Original Message --------
Subject: Re: [Jingle] Fwd: [Standards] LAST CALL: XEP-0262 (Use of ZRTP
in Jingle RTP Sessions)
Date: Thu, 19 May 2011 12:14:35 +0200
From: Emil Ivov <emcho at jitsi.org>
To: XMPP Jingle <jingle at xmpp.org>
CC: Peter Saint-Andre <stpeter at stpeter.im>
A quick note to let you that we've reviewed the XEP-0262's latest
version again and can now confirm that this is exactly what Jitsi does.
На 20.04.11 17:51, Peter Saint-Andre написа:
> -------- Original Message --------
> Subject: [Standards] LAST CALL: XEP-0262 (Use of ZRTP in Jingle RTP
> Date: Wed, 20 Apr 2011 15:49:00 +0000
> From: XMPP Extensions Editor <editor at xmpp.org>
> Reply-To: XMPP Standards <standards at xmpp.org>
> To: standards at xmpp.org
> This message constitutes notice of a Last Call for comments on XEP-0262
> (Use of ZRTP in Jingle RTP Sessions).
> Abstract: This specification defines a Jingle application type for
> negotiating one or more sessions that use the Real-time Transport
> Protocol (RTP) to exchange media such as voice or video. The application
> type includes a straightforward mapping to Session Description Protocol
> (SDP) for interworking with SIP media endpoints.
> URL: http://www.xmpp.org/extensions/xep-0262.html
> This Last Call begins today and shall end at the close of business on
> Please consider the following questions during this Last Call and send
> your feedback to the standards at xmpp.org discussion list:
> 1. Is this specification needed to fill gaps in the XMPP protocol stack
> or to clarify an existing protocol?
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
> 3. Do you plan to implement this specification in your code? If not, why
> 4. Do you have any security concerns related to this specification?
> 5. Is the specification accurate and clearly written?
> Your feedback is appreciated!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6105 bytes
Desc: S/MIME Cryptographic Signature
More information about the Council