<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div><div>On 4 mrt. 2014, at 10:24, Lars Noschinski <<a href="mailto:lars@public.noschinski.de">lars@public.noschinski.de</a>> wrote:</div> <blockquote type="cite"><fieldset style="padding-top: 10px; border: 3px solid rgb(204, 204, 204); padding-left: 20px; position: static; z-index: auto;"><legend style="font-weight:bold">Signed PGP part</legend><div style="padding-left:3px;">On 04.03.2014 11:12, Lars Noschinski wrote: > The following table shows the IQ-replies accepted by P(i)dgin[1], > P(s)i (Task::iqVerify) and P(y)XMPP. > > From\to| e | l | bl | dl+s | o > -------+-----+-----+-----+------+----- e | isy | | | s > | l | isy | isy | s | s | bl | isy | s | isy | s > | dl+s | isy | s | s | isy | o | | | | > | isy > > Legend e: empty l: local (client) jid bl: bare local jid dl: > domainpart of local jid s: server jid o: other jid Originally, in the table above, I made a distinction between "domainpart of the local jid" (dl) and "server jid" (s). In the JDev chatroom, I was told that these should always be the same[1], which is why a put them together. Here is how the table originally looked: From\to | e | l | bl | dl | s | o --------+-----+-----+-----+----+----+----- e | isy | | | | s | l | isy | isy | s | | s | bl | isy | s | isy | | s | dl | is | s | s | iy | s | s | y | | | | iy | o | | | | | | isy Pidgin consistently uses dl, while PyXMPP uses s. However, Psi uses a mixture between s and dl, which made me wonder whether there is server software out there, for which there might be a distinction between s and dl? [1] I cannot find a rule in RFC6120 which guarentees s == dl, but it might the consensus in interpreting the spec. — Lars</div></fieldset></blockquote> </div><div>Hello Lars,</div><div> </div><div><div><div>The changes to Pidgin were proposed for the situations where to=e and</div><div>from=l/dl/s, because those are used by a number of (broken) servers out there.</div><div>I have not seen it necessary to look at the other possiblities in your table,</div><div>except for to=l from=e, which is empty in your table, but should be allowed</div><div>(I've submitted a new patch to Pidgin for this, but it hasn't been accepted</div><div>yet).</div><div> </div><div>So I think it makes sense to add the rule: "if you do use an explicit JID,</div><div>that's not your own bare JID, the reply must match exactly".</div><div> </div><div>Best regards,</div><div>Thijs</div></div></div> </body></html>