On 25 January 2018 at 16:32, Jonas Wielicki <[email protected]> wrote: > On Donnerstag, 25. Januar 2018 13:42:55 CET Jonas Wielicki wrote: >> URL: https://xmpp.org/extensions/xep-0380.html > > I wasn’t aware of this XEP until I deferred it today, so here a few comments. > > > First, OMEMO definitions should be added to the table for completeness. > > Second, I’m not sure the rule about not including the @name attribute by > default on the sending side makes sense. I don’t think we should be needing > namespace bumps of EME to add new values for @namespace, so if @name is > supposed to be usable for error messages when encryption is *not* supported, > it should always be included by the sender (but ignored by the receiver iff > they know the @namespace). > > > I’m not sure the third requirement: >> Enable a client to offer the user a possibility to decrypt a received >> message (depending on the encryption method). > > makes sense to me. If a client is theoretically able to decrypt a given > protocol, it would also be able to detect it based on characteristics of the > <message/> (usually an additional element in a certain namespace). > > If the encryption protocol has had a namespace bump, EME doesn’t help with > that either.
I agree with the above feedback, and would love to see this XEP move forwards. Regards, Matthew _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
