Hi,
I'm going through the IoT discovery XEP (XEP-0347). In chapter 3.17 (disowning Thing) the following is stated:
> If such a Thing is found, and it is owned by the caller, but not online as a friend, the Thing cannot be disowned, since it would put the Thing in a state from which it cannot be re-claimed. Therefore, the Thing Registry must respond in the following manner:
I am wondering about the piece "but not online as a friend". A "friend" of whom? How should this be checked?
Wouldn't it be more practical to determine this situation by just sending the disowned IQ message to the Thing?
When the server responds with a service-unavailable message it can be assumed that the thing is currently offline (or at least unavailable). Otherwise there always should be a friendship relation between the thing and the registry.
Cheers,
Eelco
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.
Hello all in the IoT list. Is anybody wanting to help out in anyway to
update the http://xmpp-iot.github.io page?
we need examples examples examples
fork and update please
and if you would like to sign the backers page feel free to do a
pullrequest with your writing
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
Hello
Google has asked for proposals regarding the "Open Web of Things", and they are interested in funding interesting projects (500.000-800.000 USD is it is a group of researchers at a university, or 50.000-150.000 USD if it is a private investigator). If you have not seen it:
https://docs.google.com/file/d/0B3B49KOvpS8TbnRlcDVDOTdlYmc/edit
They have five categories:
1) Human-Computer Interaction
2) Privacy & Security
3) Systems & Protocols
Since we are strong within these areas, we can offer help to mount such projects. (The grants go only to the university involved.) What we can do:
* Help with project ideas.
* Assist in the technical description of the project.
* Provide technology and a platform for rapid application development for IoT.
* Act as mentors.
* Help with evaluating the project.
What we cannot do is help with the actual development, nor in the description of the results, or hardware for the project. (Such things need to be covered by the grant.)
The proposals (which can be various) have to be sent before the 21st of January 2015. Here comes a few proposals of projects that can be done, and that fall within what they are looking for:
Securing the Life Cycle for things and provisioning for Internet of Things using XMPP
The majority of solutions for the IoT are manually configured. Very few solutions exist where the end user can buy a product designed for massive use in a retail store, connect it, and then use it on the Internet in a secure manner.
We have made a proposal of a distributed architecture that takes the entire life cycle of an IoT product into account, designed for massive scale, from production, sales, installation, creation of identities, configuration, authorization, change of ownership and decommissioning, in a secure and scalable way, without losing real-time communication capabilities. The architecture also supports distributed transactions, protects information (the owners of the things are also owners of all its data and control who can access it and do what with it.)
You can find more information about the control of a things life cycle here:
https://www.thingk.me/Provisioning/Papers/Securing%20the%20Life%20Cycle%20o…
More information about provisioning of things (who can access what things, and read/control what data):
https://www.thingk.me/Provisioning/Papers/Security%20in%20IoT%20using%20Del…
More details:
https://www.thingk.me/Provisioning/Api.xml
The project could include:
* Implementation of the indicated protocols for use in things. (Open source code exist on GitHub, for reference: https://github.com/Clayster/Learning-IoT-XMPP)
* Implementation of the indicated protocols for servers, or use of existing servers. (The thingk.me platform already supports them)
* Define "normal use"
* Measure efficiency of different use cases.
* Simulate large volumes of things, and different distributions of servers.
* Security analysis.
* Proposal of extensions.
Extension of the Semantic Web to Peer-to-Peer-like Sensor Networks based on XMPP
One of the problems with the Semantic Web, or the Web of Things, is the problem of security and distributed transactions using the HTTP protocol. In the traditional web, the web servers are centralized, and security is managed on the same web servers. For the Web of Things, each sensor has the possibility to become a small web server. How do you manage security in a similar distributed environment? HTTP does not have any good solutions by itself, except it supports the use of directory services (which are designed for use within intranets and not on the global Internet). The same happens for the Semantic Web or with SPARQL. Another problem is how to bypass firewalls. Normally, sensors are installed in protected environments, behind firewalls. This This prohibits access to the sensor directly from outside of the firewall, unless holes are punched in the firewall.
To resolve this, most solutions store all information centrally. This later permits the management of security to that centralized location. But, by doing this, you lose the local control and the real-time communication with the devices, something that prohibits many different types of applications, and limits the scalability of the implemented solutions. Furthermore, one has to store much more data than what would otherwise be necessary, simply to solve the problem of latency (since there is no connection that permits communication in real-time).
Another manner to solve this problem, is to use another transport for HTTP than TCP, for example XMPP. This protocol (standardized by the IETF, like HTTP) gives all participants a global identity, permits authorization of messages and, because of this, also distributed transactions, real-time communication, it bypasses firewalls in a secure manner, and is scalable to many billions of devices (today, already billions of devices are using it).
More information can be found here:
https://www.thingk.me/Provisioning/Papers/Extending%20the%20Semantic%20Web%…
The project could include:
* Implementation of the HTTP over XMPP protocol, and the HTTPX URI scheme, as plug-ins to browsers (Mozilla, Chromium), web servers (Apache), and perhaps media players (VLC)
* Implementation of the same into a public SPARQL endpoint (or SPARQL database), or use an existing one. (Clayster platform already supports it)
* Implementation of an ontology for the Internet of Things.
* Measurement of efficiency.
* Simulation of huge networks.
* Security analysis.
* Proposal of extensions.
BIOTIC
The BIOTIC protocol (Binary Internet Of Things Interoperable Communication) proposes to solve many of the problems that exist today for the internet of things, and it also proposes several new innovative solutions. To learn more, look at the documents published here:
http://biotic-community.tumblr.com/
This document describes the reason for creating and using the protocol:
https://dl.dropboxusercontent.com/u/3064761/Biotic%20-%20Executive%20Summar… <https://dl.dropboxusercontent.com/u/3064761/Biotic%20-%20Executive%20Summar…>
This document describes the protocol, including new innovative communication patterns:
https://dl.dropboxusercontent.com/u/3064761/Biotic%20-%20Protocol%20v1.0.pdf<https://dl.dropboxusercontent.com/u/3064761/Biotic%20-%20Protocol%20v1.0.pd…>
The project could include:
* Implementation of BIOTIC-servers, which can be installed in home gateways, on routers or publicly on the Internet.
* Tiny implementations for microcontrollers
* Measurement of efficiency.
* Simulation of huge networks.
* Security analysis.
* Proposal of extensions.
If there are any interested parties, I propose that we schedule a meeting to talk about this, and how we can advance to be able to send one or more proposals before the indicated end date.
If you know any other researchers that could be interested, please resend this email to them.
Best regards,
Peter Waher
I am putting a strophe implementation for XEP-323 and 325 into the
https://github.com/strophe/strophejs-plugins track but there are a bunch of
different licensing models anyone here knowledgable of what should be used?
MIT, MIT/X11 seems to be the one mostly used
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
In the IoT mailing list (cc)?!
Cheers,
Eelco
On 24 Nov 2014, at 16:49, Dave Cridland <dave(a)cridland.net<mailto:dave@cridland.net>> wrote:
On 24 November 2014 at 15:29, XMPP Extensions Editor <editor(a)xmpp.org<mailto:editor@xmpp.org>> wrote:
Version 0.3 of XEP-0347 (Internet of Things - Discovery) has been released.
Abstract: This specification describes an architecture based on the XMPP protocol whereby Things can be installed and safely discovered by their owners and connected into networks of Things.
Changelog: [See revision history] (pw)
Diff: http://xmpp.org/extensions/diff/api/xep/0347/diff/0.2/vs/0.3
URL: http://xmpp.org/extensions/xep-0347.html
I've noticed two updates to this XEP, yet no discussion on the mailing list at all. While that's certainly not a formal requirement, the changes looks like functional ones - where's the discussion for these changes happening?
Dave.
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.
Adam great that you put XMPP +IoT on the agenda, I will gladly help out
there.
I have just started http://xmpp-iot.github.io a github site to ease the
introduction of "xmpp internet of things" making it possible to fork and
help in updating. Also with a "manifest" for backers.
*Regards*
Joachim Lindborg
CTO, systems architect
Sustainable Innovation SUST.se
Barnhusgatan 3 111 23 Stockholm
Email: Joachim.lindborg(a)sust.se
linkedin: http://www.linkedin.com/in/joachimlindborg
Tel +46 706-442270
2014-11-24 1:10 GMT+01:00 Adam Brault <adam(a)andyet.com>:
>
> Laura <laura.gill(a)surevine.com>, wrote:
>
>> What goals would you like to see set for the Board for the year ahead?
>
> Just thought I’d share my goals for the board in this thread, which I’ll
> be raising in the board meeting tomorrow and trying to figure out how to
> succinctly add to the Trello board without overloading it :)
>
> My strong desire is to help the board best serve the interests of the
> XSF—and I hope these things are aimed in that direction.
>
> In that light, I’d love to hear feedback / criticism / reality checks from
> XSF members on these. Guaranteed many of you have been thinking about these
> things so much longer than I have.
>
> *Active website *
>
> - Active and strategically opinionated blog—dismantle myths, responses
> to blog posts on other sites, present pros for using XMPP instead of
> bespoke protocols or building YAMS (yet another messaging silo)
> - Link to and feature howtos and new XMPP projects on the XSF site and
> blog.
> - "Position paper" style pages on various topics (optimization,
> performance, federation, s2s, mobile), with relevant blog posts and howtos
> linked
> - Publicly summarizing the Council's agenda
> - XMPP +IoT, XMPP + WebRTC sections
> - Use GitHub to empower the XSF and extended XMPP community to
> collaborate on the site — Allow submission of new/revised content and blog
> posts via pull request
>
> *Proactively build the community*
>
> - There are 2600 repositories on GitHub containing "XMPP"(
> https://github.com/search?q=xmpp&type=Repositories) Who are these
> people and how many of them are connected to the XSF?
> - Invite people to idle in an easily accessible channel (IRC + Web +
> XMPP)
> - Feature, publicize, and praise new XMPP based projects
> - Seek to grow the active XSF membership, particularly those working
> in growing areas of tech intersecting with XMPP (IoT, WebRTC, indie tech)
> - Encourage and feature meetups and relevant conferences
> - Encourage members to attend technical conferences and submit talks
> supportive of the XSF's strategic agenda
>
> *Invite and listen to criticism of XMPP*
>
> - Listen, and work to address it where the Council agrees we should
> - Answer misconceptions with position pages and education
> - Help council prioritize work based on this feedback
>
> I would love to hear feedback and criticism from XSF members on all of the
> above. Do you agree? Disagree? Does anything stand out to you as blatantly
> ignorant or wrong or naively overambitious? Let me have it! :)
>
> Thanks so much.
>
> —Adam
>
I’m working my way through the IoT discovery XEP.
For my use case I would like to update the Meta Information in the registry after a device has been claimed. For example:
1. I install a Thing in a room and the Thing registeres itself in the registry.
2. I claim ownership of the Thing.
3. I now want to update the Meta Information with information not known by thing itself like for example location, room number, building number etc.
How should I proceed with step 3? A Thing can update its meta-information in the registry but an owner cannot update the meta-information of the Thing or tell a Thing to do so as of the current version of the spec.
Any ideas?
Thanks,
Eelco
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.
Hello everybody
Is anybody interested in speaking about XMPP & IoT at this IoT conference?
http://gogonetlive.com/
We got a question to participate, but can't attend due to other engagements those days. If you're interested, send me a mail and I'll forward your interest.
Best regards,
Peter Waher
Has anyone looked into adding XMPP support to the open-source meshblu
framework?
https://developer.octoblu.com/
I met the Octoblu folks recently and they were enthusiastic about adding
XMPP support (well, about having someone else add it).
Peter
--
Peter Saint-Andre
https://stpeter.im/