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

Peter Saint-Andre stpeter at jabber.org
Wed Apr 19 16:26:59 UTC 2006


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

Vinod Panicker wrote:
> On 4/18/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
>> -----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...
> 
> Seems like this would also clash with xmppbis -
> http://www.xmpp.org/xmppbis.html#bind
> 
> Disco was proposed as a possible solution to the problem stated above.
> But if disco is sent only to available resources, then it's not
> possible to use it here.
> 
> Can anyone please point me to an instance where "connected" resources
> are being used for a practical purpose?

I didn't say we would not modify the text in JEP-0030 to mention
connected resources. All I said was that the current text is fine,
albeit limited. So it would need to be expanded, and we'll do that
sometime in the semi-near future.

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

iD8DBQFERmTSNF1RSzyt3NURAlkBAKCg0NvCfODxANUE8SNjm/m1Na6wpgCgtWu+
oxMqPEdzqpm1YGpnYkHab3A=
=eatC
-----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/20060419/1a050341/attachment.bin>


More information about the Standards mailing list