Jonathan Schleifer wrote:
Peter Saint-Andre <[EMAIL PROTECTED]> wrote:

XEP-0045 doesn't say anything about this and client developers seem
to have handled it just fine. But yes we could say something about timeouts, or add an ID to the invitations, or say that the client
should match the inviter (both mediated and direct invitations will
make it clear who invites you to the room).

I'm for adding an ID. That seems like the most safe option to me.

Note that the ID is not part of the mediated invitation format defined in XEP-0045, and it's unclear how existing MUC servers would handle the new attribute:

<message
    from='[EMAIL PROTECTED]/desktop'
    to='[EMAIL PROTECTED]'>
  <x xmlns='http://jabber.org/protocol/muc#user'>
    <invite to='[EMAIL PROTECTED]'
            id='some-long-id-here'/>
            ^^^^^^^^^^^^^^^^^^^^^^
  </x>
</message>

I expect that MUC servers would ignore the 'id', rendering it useless for quite some time, or might even return a bad-request error (since the 'id' attribute is undefined according to the schema they were coded against). And clients would ignore it, too. Better, I think, to match against the inviter's JID, or at least use that as the fallback if the 'id' is missing.

/psa

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to