[Council] Notes on XEP-0262: Use of ZRTP in Jingle RTP Sessions

Peter Saint-Andre stpeter at stpeter.im
Wed May 25 17:24:59 UTC 2011


On 5/25/11 11:22 AM, Matthew A. Miller wrote:
> 
> On May 25, 2011, at 11:18 , Peter Saint-Andre wrote:
> 
>> On 5/25/11 10:50 AM, Matthew A. Miller wrote:
>>> Section 1. Protocol
>>> ===================
>>>
>>> * 2: The following sentence is missing some words (maybe an entity that isn't processed correctly?):
>>>
>>> 	"An alternative approach to end-to-end encryption of RTP traffic is provided by , developed by Phil Zimmermann, the inventor of "Pretty Good Privacy" (PGP)"
>>>
>>> * 1: There is no reference to the ZRTP specification (e.g. <http://tools.ietf.org/html/rfc6189>)
>>
>> XEP Editor error with a reference update. Fixed:
>>
>> An alternative approach to end-to-end encryption of RTP traffic is
>> provided by RFC 6189 [3], developed by Phil Zimmermann, the inventor of
>> "Pretty Good Privacy" (PGP).
> 
> Two birds with one stone!  Yay!
> 
>>
>>> Section 2. Determining Support
>>> ==============================
>>>
>>> * N: Example 4. A disco#info response is a bit short, if it's meant to be representative.  For instance, it lacks an <identity/>, and is missing <features/> for disco#info and other Jingle protocols.
>>
>> That's not much different from, say, XEP-0216:
>>
>> http://xmpp.org/extensions/xep-0261.html#example-16
>>
>> The disco#info results are not meant to be representative, I think, only
>> to show the exact feature being defined in the relevant spec.
>>
>> Peter
>>
> 
> Glancing at some other XEPs, I notice we follow the "simplified" form more than the "minimally correct" form (-:  I'm fine leaving this part alone, and should have indicated that better from the start.

Perhaps at least including <feature var='urn:xmpp:jingle:1'/> would be
appropriate (as in 261).

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6105 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/council/attachments/20110525/450db18e/attachment.bin>


More information about the Council mailing list