Hi, Mostly unrelated to Daniel's feedback, but an idea regarding JMI that is my head for some time now.
One thing I am missing in XEP-0353 is explicit support for legacy fallback body. Which may sound absurd at the first second, isn't to me: The fallback body could include an https URL to a website that runs a JavaScript XMPP client that logs you into an anonymous account and accepts the JMI. Technically, this could be done with JMI as it currently is defined in XEP-0353 without any syntax changes: the anonymous account in web client would have to send <accept> to the recipient bare jid and <proceed> to the sender full jid. However the current XEP does not hint that this should be supported and I bet most implementations will expect the <accept>/<proceed> to be originated from the jid that the <propose> was send to. A proper fallback body would make the disco feature less needed, however I agree that most implementations will probably not be able to provide this nice fallback and thus require disco support. So changes that would make this feature obviously supported are: a) Explicitly allow <propose> and <accept> to include a fallback <body> that is not displayed to clients supporting XEP-0353 (or is presented to them when the implemented transport mechanisms are incompatible) b) Ask for JMI id's to be randomly generated with sufficient entropy. c) Explicitly allow for <accept> and <proceed> messages to be originated from a different JID than the <propose> was send to. Marvin _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
