[IOT] Comments on discovery paragraph 5.1

Cramer, E.R. (Eelco) Eelco.Cramer at tno.nl
Wed Apr 1 11:52:35 UTC 2015


Paragraph 5.1 of XEP-0347 says it is only needed to ‘become friends’ with the Thing registry if the registry isn’t a server component.
> 5.1 JID vs Component Thing Registries <>
> A client must treat the connection between a Thing Registry differently if it is hosted as a client, having a JID, or if it is hosted as a Jabber Server Component. If it is hosted as a server component, there's no need for the thing to become friends with the Thing Registry. Messages and requests can be made directly to the server component without having to add it to the roster or request presence subscriptions. If the Thing Registry is hosted as a client, having a JID (@ in the address), the Thing Registry must be added to the roster of the client before the client can communicate with the Thing Registry.
However, for the registry to determine if a Thing is online or offline (to check if it is able to notifiy it about claimed, disowned and removed states) the Thing registry needs a presence subscription with the Thing. This does not mean that the Thing also has a presence subscription on the registry but there must be some kind of ‘friendship’ relation between the 2. So the text above is ambiguous in my opinion.

Also paragraph “3.6 Registering a Thing” states that a Thing must find and befriend a registry before the Thing can register itself with the registry.

Should paragraph 5.1 be updated or removed?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/iot/attachments/20150401/b554f780/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.jabber.org/pipermail/iot/attachments/20150401/b554f780/attachment.sig>
-------------- next part --------------
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

More information about the IOT mailing list