[Standards-JIG] JEP-0030 - Disco to resources

Peter Saint-Andre stpeter at jabber.org
Tue Apr 18 16:41:16 UTC 2006


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

Vinod Panicker wrote:
> On 4/17/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Vinod Panicker wrote:
>>> Hi,
>>>
>>> Is anyone aware of a use case where a disco query needs to be made to
>>> CONNECTED/ACTIVE resources? (not AVAILABLE).
>>>
>>> Since according the spec, a disco to the bare jid will result in the
>>> server auto-replying with the AVAILABLE resource(s) of the user.  But
>>> in example 8, a disco is being sent to the full jid, of the CONNECTED
>>> resource.
>>>
>>> How will another jabber entity determine the CONNECTED resources of
>>> another jabber entity?  Have I stumbled across a bug?
>> I think JEP-0030 needs to say connected, not available. We have not
>> always been crystal-clear about the difference.
> 
> Thanks for the clarification... Surprised that no one else had this
> issue till now.

Well, now that I look at the text again, it refers to IM systems, so I
think "available resource" is the appropriate term. However, I think
some clarification is in order, which is unfortunate since we already
spent a lot of time wordsmithing those security considerations...

/me updates his .plan

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFERRasNF1RSzyt3NURAhUdAJwOjxuNrWbNAbQMeqZM6CjGP9jeywCeJEPd
9RP1fF3f4dbQQc+mYZVH0tg=
=iEhW
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060418/b6e4962d/attachment.bin>


More information about the Standards mailing list