[Standards] MUC invitee not found error

Peter Saint-Andre stpeter at jabber.org
Fri May 25 17:52:41 UTC 2007

Ian Paterson wrote:
> Peter Saint-Andre wrote:
>> Peter Saint-Andre wrote:
>>>> For example, at least one MUC server I know of sends the following 
>>>> error to the invitor after it receives an item-not-found error from 
>>>> the invitee's server:
>>>> <message from='room1 at conference.foo.com'
>>>>         to='user1 at foo.com' type='error'>
>>>>  <x xmlns='http://jabber.org/protocol/muc#user'>
>>>>    <invite to='user13 at foo.com'/>
>>>>  </x>
>>>>  <error code='404' type='cancel'>
>>>>    <item-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
>>>>  </error>
>>>> </message>
>>>> Can we standardize this (optional?) error and any others that MUC 
>>>> server implementors can think of?

So I think we need to answer these questions:

1. In general, how should MUC services handle stanza errors they 
receive? (Kick the occupant, return something to the original sender, etc.)

2. Specifically, how should MUC services handle message errors related 
to invites they send out? IMHO they should return a single error 
condition to the invitor and not return the original message error 
condition. I recommend that we use <undefined-condition/> since the 
invitation failure doesn't map to any of the existing conditions as far 
as I can see -- unless we define a general <delivery-failed/> condition 
in rfc3920bis.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070525/92ffd6a3/attachment.bin>

More information about the Standards mailing list