[Standards] XEP-0225: Multiple Connections Per JID?

Peter Saint-Andre stpeter at stpeter.im
Fri Feb 8 18:18:40 UTC 2008


Ralph Meijer wrote:
> On Thu, 2008-02-07 at 10:21 -0700, Peter Saint-Andre wrote:
>> Ralph Meijer wrote:
>>> On Wed, 2008-01-30 at 17:23 -0700, Peter Saint-Andre wrote:
>>>> If this is a second instance, the server could return an indication of
>>>> that fact using something like a resource:
>>>>
>>>> <iq id='bind_1' type='result'>
>>>>   <bind xmlns='urn:xmpp:tmp:component'>
>>>>     <hostname>chat.example.com</hostname>
>>>>     <instance>8ba991jag</instance>
>>>>   </bind>
>>>> </iq>
>>> Huh, what? Why not be consistent and reuse the concept of resources?
>> It seems to me that you would end up with things like this:
>>
>> pubsub.example.com/8ba991jag
>> pubsub.example.org/5fe372brd
>> pubsub.example.org/3bc716ffo
>>
>> Would those be routable addresses? If so, would they be routable only
>> within the server (like the old <route/> packets in jabberd 1.x) or also
>> from the outside?
> 
> In general I would say that they should only be reachable from within
> the thing you could call their containing server. This is kind of vague
> and that's ok. It is mostly an implementation detail and local security
> policy what you want to be reachable from the outside, IMO.

Sure, we leave that up to the local service policy. :)

OK, I will work this into the next version of the spec.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080208/8c4115ea/attachment.bin>


More information about the Standards mailing list