Re: [Standards] LAST CALL: XEP-0166 (Jingle)
Hi, about the basic Jingle XEP, I have just read it. On a first impression, there is just one point: in section 6.7 Termination, there is no example of the probably most common termination case: the jingle media session has been done, processed and end normally (so with no-error element in reason). The example exists at the beginning (example 5), but I think this is good thing to give it again in the termination section as it will happen all the time when a Jingle session occures, isn't it? Jehan -- Jehan Jehan's Profile: http://www.jabberforum.org/member.php?userid=16911 View this thread: http://www.jabberforum.org/showthread.php?t=1133
[Standards] Small Typo in XEP-0077
Hi, there is a small typo in example 16 for XEP-0077. The title is Password Change and it should be something like Cancel Account. Since it is a final XEP, I did not dare to fix it in svn. :) Dirk -- When someone says, 'do you want my opinion?' - have you noticed that it's always a negative one.
[Standards] XEP-0071 Security Considerations
Maybe we should add in the Security Considerations that it MUST NOT be used together with XEP-0027. In Gajim, a patch adding XHTML support was recently committed. However, it always attached XHTML to the message when formattings were used. This is not as bad as other clients, who always send XHTML. However, when formattings were used and GPG was enabled, the body was encrypted and an unencrypted XHTML version of it attached. We should explicitely warn about this, IMO, maybe even in both, XEP-0027 and XEP-0071, as this leads the user into false security and is a severe bug. It is sent in plaintext and the user never notices, unless he looks at the XML console. -- Jonathan PGP.sig Description: This is a digitally signed message part
