[jdev] Checking the from of iq replies

[Lars Noschinski]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTFanFAAoJEOUX5T7UhMS6d00H/2B3aBOClDd9SQj9A/lHpsAa
PjFYQMg2ocEMFI2zyXHAvWyCxUolH998aFXblo2ugdXpU6X47KRhSROV3baBxY+/
tiVbX+ai97HsYJvEt+FMEr6hM+8U/cFt7ndqx5xAyjSkqqEuTFlD0HUdlbiXvNtE
2SsDqj3gQ4DyGHWdGfEMAwmUExHkplIc0JOjIp+psy1B8x3SNwUP98xYBMEW+5GK
okIKe0OKAwosApSGEbD70iNEPnzY/bZ6zsanC+gq+/PlaKYItenUDD6DX9lMbp60
nJJmBsiFwsEOFLw167hBh5H3yQFZR1TLW7j1bifPmWXpwPds0hrGTtQAFU2zuPg=
=n395
-----END PGP SIGNATURE-----