[Standards] eJabberD MUC Invitation Bug
richard at dobson-i.net
Wed Apr 25 03:39:26 CDT 2007
Sergei Golovan wrote:
> On 4/25/07, Chris Mullins <chris.mullins at coversant.net> wrote:
>> It looks like eJabberD (as running on Jabber.Org) is sending out
>> incorrect Invitation messages to MUC rooms.
>> XEP 0045 says (section 7.5):
>> "the message MUST NOT possess a 'type' attribute"
> I would say that it's a bug in XEP-0045. RFC-3921 clearly says that
> the absence of type attribute is equivalent to type 'normal' (citing
> from section 2.1.1): (if an application receives a message with no
> 'type' attribute or the application does not understand the value of
> the 'type' attribute provided, it MUST consider the message to be of
> type "normal" (i.e., "normal" is the default).
You have read it too literally and misunderstood it, as Chris points out
there is no type of "normal" the lack of the attribute is what signals that.
> So, it isn't reasonable to require signalling by omitting type attribute.
Why not? Seems perfectly reasonable to me.
More information about the Standards