William Voorsluys wrote: > Hello, > >> > But, according to the XEP, it is not allowed to include any inner XML >> > stanza on the <iq> of type RESULT used as ACK: >> > >> > <iq from='[EMAIL PROTECTED]/balcony' to='[EMAIL PROTECTED]/orchard' >> > type='result' id='ibb1'/> >> >> That's just an example. >> The RFC allows zero or one child element in IQ result stanzas. >> This would work: >> >> <iq from='[EMAIL PROTECTED]/balcony' to='[EMAIL PROTECTED]/orchard' >> type='result' id='ibb1'> >> <data xmlns='http://jabber.org/protocol/ibb' sid='mySID' seq='0'> >> </iq> > > Well, I don't think that XEP-0047 would allow such a response. It is > not clear in the XEP that a client should reply including a <data> > element preserving 'sid' and 'seq'. So, most clients wouldn't do that, > preventing our implementation to interoperate. > Am I right?
AFAIK, few clients have implemented IBB. We could definitely update the spec to reflect this kind of acking, which makes a lot of sense IMHO. Justin, what say you? /psa
smime.p7s
Description: S/MIME Cryptographic Signature
