[IOT] XEP-xxxx and ISO/IEC/IEEE 21451-1-4 (12-17-12)

William Miller mact-usa at att.net
Mon Dec 17 16:34:40 UTC 2012


Mat and Peter,

There is a join standardization effort in ISO/IEC/iEEE 21451-1-4 and we will
incorporate aspects of
XEP-XXXX Sensors over XMPP and would well input from others in the
community.  There is a
reference model that we are using that is powered by XMPP and also
providesXMP linkage for
mobility including Smart Phones (i.e. Andorid, Apple, Microsfoot,
Blackberry).   This work
is also in process within ISO JTC1 SC1 Automatic Identification, SNIT-M2M
IoT (Internet of Things),
and TC 122.  This work will combine asset identification, location tracking,
and sensor monitoring
for a wide range of applciations to offer a common protoocl using XMPP.  If
there are others who
are interested please cotnact me if you would be intrested in particiapting
in this international effort.  

Regards,

W.J.MILLER, PRESIDENT, MaCT, 01 301 500-9277
ISO/IEC/IEEE 21451-1-4 WG, Chairman

-----Original Message-----
From: iot-bounces at xmpp.org [mailto:iot-bounces at xmpp.org] On Behalf Of
iot-request at xmpp.org
Sent: Monday, December 17, 2012 1:40 PM
To: iot at xmpp.org
Subject: IOT Digest, Vol 7, Issue 2

Send IOT mailing list submissions to
	iot at xmpp.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.jabber.org/mailman/listinfo/iot
or, via email, send a message with subject or body 'help' to
	iot-request at xmpp.org

You can reach the person managing the list at
	iot-owner at xmpp.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of IOT digest..."


Today's Topics:

   1. Status of XEP-xxxx: Sensor-over-XMPP (Peter Waher)
   2. Re: [Standards] Status of XEP-xxxx: Sensor-over-XMPP
      (mat henshall)


----------------------------------------------------------------------

Message: 1
Date: Mon, 17 Dec 2012 12:35:36 +0000
From: Peter Waher <Peter.Waher at clayster.com>
To: "gauravbhatia at cmu.edu" <gauravbhatia at cmu.edu>,
	"marioberges at cmu.edu"	<marioberges at cmu.edu>, "agr at ece.cmu.edu"
	<agr at ece.cmu.edu>,	"css at google.com" <css at google.com>
Cc: "iot at xmpp.org" <iot at xmpp.org>,	"Joachim Lindborg
	\(joachim.lindborg at sust.se\)" <joachim.lindborg at sust.se>,
	"standards at xmpp.org" <standards at xmpp.org>
Subject: [IOT] Status of XEP-xxxx: Sensor-over-XMPP
Message-ID:
	<1693EFE1FD641C42A0D542FCBC732DE698BC9287 at EX3.YODA.UTOPIA.LOCAL>
Content-Type: text/plain; charset="iso-8859-1"

Hello.

I'm writing to you to, to ask about the status of the following document:
http://xmpp.org/extensions/inbox/sensors.html

How is this proposed extension used today, and in what implementations?

I'm interested in developing extensions for allowing sensor data
communication and IoT, among other things. We have multiple applications
using XMPP and sensors. Before proposing an extension by ourselves, I've
been waiting to find colleagues working in the same area, so we could
propose an extension together, this increasing the probability for it to
become useful.

What is the status of the above mentioned document? Is it set in stone, or
is it possible to work on it, redefine parts of it, etc., in order for it to
become more general and suitable also to our needs? Are you able to invite
other authors to partake in the development of this proposed extension?

Sincerely,
Peter Waher



Peter Waher, Gerente General
[cid:image001.png at 01CDDC39.8577CD00]

Clayster Chile Ltda
Calle Blanco 1623, oficina 1402
Valpara?so, Chile
Tel?fono: +56-32-2122533, +56-9-71993640
Skype: peter.waher
Correo electr?nico:
peter.waher at clayster.com<mailto:peter.waher at clayster.com>
Twitter: https://twitter.com/ClaysterLabs,  https://twitter.com/PeterWaher
LinkedIn: http://se.linkedin.com/pub/peter-waher/1a/71b/a29

La informaci?n contenida en esta transmisi?n es confidencial y propietaria y
no puede ser utilizada por personas distintas a su(s) destinatario(s). La
utilizaci?n no autorizada de la informaci?n contenida en este correo por
cualquier forma puede ser sancionada criminalmente de conformidad con la Ley
Chilena e infringir normas sobre propiedad intelectual, propiedad industrial
o secretos comerciales. Si ha recibido esta transmisi?n por error, por favor
destr?yala y notifique al remitente telef?nicamente, con cobro revertido o
v?a e-mail. Atendido que no existe certidumbre que el presente mensaje no
ser? modificado como resultado de su transmisi?n por correo electr?nico
CLAYSTER Laboratorios Chile Limitada, no ser? responsable si el contenido
del mismo ha sido modificado. Visite nuestra p?gina WEB
www.clayster.com<http://www.clayster.com/>.

The information contained in this transmission is confidential and
proprietary and it cannot be used by any person other than its addressee(s).
Unauthorized use of the information contained in this transmission in any
form may be punished under Chilean Law and be considered a copyright,
industrial property or trade secrets infringement. If received in error,
please destroy it and notify the sender by calling collect or e-mail. As
there can be no certainty that this message will not be modified as a result
of its transmission via e-mail, CLAYSTER Laboratorios Chile Limitada shall
not be responsible if the content of the same has been modified. Visit
www.clayster.com<http://www.clayster.com/>.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.jabber.org/pipermail/iot/attachments/20121217/8a5e4d6a/attachme
nt-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10305 bytes
Desc: image001.png
URL:
<http://mail.jabber.org/pipermail/iot/attachments/20121217/8a5e4d6a/attachme
nt-0001.png>

------------------------------

Message: 2
Date: Mon, 17 Dec 2012 10:16:02 -0600
From: mat henshall <mat at squareconnect.com>
To: XMPP Standards <standards at xmpp.org>
Cc: "gauravbhatia at cmu.edu" <gauravbhatia at cmu.edu>,	"iot at xmpp.org"
	<iot at xmpp.org>,	"Joachim Lindborg \(joachim.lindborg at sust.se\)"
	<joachim.lindborg at sust.se>, "agr at ece.cmu.edu" <agr at ece.cmu.edu>
Subject: Re: [IOT] [Standards] Status of XEP-xxxx: Sensor-over-XMPP
Message-ID:
	<CABt5oAu+h2vFg4v5Vzf8+zo=Zi3S2wn8_Dvz0LcU+jNEGxx5gg at mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"

We are using XMPP for both sensor reporting and control for building and
home automation applications. We have implemented a very rich set of
stanza's that cover almost all common types of devices and it is designed to
work on very low resource embedded devices. This implementation is currently
in closed beta although there are some very large brands who have started to
develop applications and hardware using our protocol and technology. Our
intention is to make the protocol public once we had a full working public
available implementation.

When we became aware of the proposed XEP extension mentioned here we were
already a long way down the road with our own, and as there is so much more
to making a complete system than is exposed in this XEP, we felt we needed a
working implementation to compare and contrast and make meaningful
contributions based on experience...

We would be excited to work with others on creating a standard... the
problem as always is time to commit to this exercise. That being said, we do
have executing code and multiple devices talking to each otehr across
continents... so I think we are at the stage where we could add to any
serious attempt for standardization.

Mat







On Mon, Dec 17, 2012 at 9:54 AM, Hannes Tschofenig <
hannes.tschofenig at gmx.net> wrote:

> Hi all,
>
> I was actually wondering myself about the status of XMPP & SIP usage 
> for sensors. I dropped Peter a mail a month ago to hear more about the 
> deployment situation.
> It seems that if there are implementations then they are using HTTP.
>
> Ciao
> Hannes
>
> On Dec 17, 2012, at 5:47 PM, Matthew Wild wrote:
>
> > On 17 December 2012 12:35, Peter Waher <Peter.Waher at clayster.com> wrote:
> >>
> >> Hello,
> >>
> >> I?m writing to you to, to ask about the status of the following
> document:
> >>
> >> http://xmpp.org/extensions/inbox/sensors.html
> >>
> >
> >> I?m interested in developing extensions for allowing sensor data
> communication and IoT, among other things. We have multiple 
> applications using XMPP and sensors. Before proposing an extension by 
> ourselves, I?ve been waiting to find colleagues working in the same 
> area, so we could propose an extension together, this increasing the 
> probability for it to become useful.
> >>
> >> What is the status of the above mentioned document? Is it set in 
> >> stone,
> or is it possible to work on it, redefine parts of it, etc., in order 
> for it to become more general and suitable also to our needs? Are you 
> able to invite other authors to partake in the development of this 
> proposed extension?
> >
> > It was rejected by the council at its meeting 2011-04-27:
> > http://mail.jabber.org/pipermail/council/2011-May/003164.html
> >
> > Nathan posted his reasoning here:
> > http://mail.jabber.org/pipermail/standards/2011-May/024545.html - 
> > and the discussion continued here:
> > http://mail.jabber.org/pipermail/standards/2011-May/024547.html
> >
> > No new version was submitted as far as I know, and I know of no 
> > public implementations of the protocol (that's not to say there 
> > aren't any of course...).
> >
> > Regards,
> > Matthew
>
>


-- 

Mat Henshall
Founder and CEO, Square Connect, Inc.
San Jose, CA
www.squareconnect.com
cell: 650.814.7585
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.jabber.org/pipermail/iot/attachments/20121217/318174eb/attachme
nt.html>

------------------------------

_______________________________________________
IOT mailing list
IOT at xmpp.org
http://mail.jabber.org/mailman/listinfo/iot


End of IOT Digest, Vol 7, Issue 2
*********************************




More information about the IOT mailing list