Hello Thom Have you had any chance to look at XEP-0324: Provisioning? It provides a mechanism to control who/what talks to who/what, what users have what access rights to what services, etc. Sincerely, Peter Waher -----Original Message----- From: Thomas Nichols [mailto:tnichols@enernoc.com] Sent: den 19 juni 2013 22:52 To: XMPP in the Internet of Things Subject: Re: [IOT] OpenADR comment period One question, which is more of an implementation detail but we would like some input, is how to prevent communication between end node clients. I think during registration, VENs would have to be added to an ACL or group, and then a filter would be used at the XMPP server to block packets whose "to" and "from" belong to that group. Any general guidelines or best practices for securing a public XMPP server with possibly untrusted clients would be welcome. Thanks again! -Thom On 6/20/13 10:43 AM, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear IOTers,
It has come to my attention that the OpenADR Alliance, which produces technical guidelines for demand-response systems, has released a draft version of their 2.0 specification for public comments. You can find the spec here:
http://www.openadr.org/specification
The primary text of interest is Section 9.3, which defines their use of XMPP.
Comments can be sent to mailto:comments@openadr.org (as I understand it, preferably by the end of next week). I'll be sending my feedback before then, and encourage other folks here to do the same.
Thanks!
Peter
- -- Peter Saint-Andre https://stpeter.im/
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRwl4zAAoJEOoGpJErxa2pFjkP/j+J0mAWMqaUaVM0tYw4VRf9 BA0wql2d67tRAd/JB2LmZiW0eKfkHBNXtVhrPvXi4eCqPh7Vcr/2FENt28Rc1AWR rR0PO4I/1etLE5HCbYJSWaWQA9WREAGlPSr12hcXRs82CJdwajWUnQMuUJbx7S4t Yxe+6QVdsmqQBQBv3L0ZFiA0B+iLpqr1BW0RVqLBeaYXSynQ2GiBfsuEWZy7jXIH f3eAfB9qUz1B03BVVwLFUlazGKFkQE1KOFKxsDi9uEymvMHDpXZQSSpHYV35F9GJ 72vzSmmtJ4Gp2wZpg9eaZcrJHjoiBu7i8vnqMK9/9A7U1k58EU7DZjc5wj9pStlV taF9WLYfFcEIY7YjNwozH5yLKySCX/erKyq4CbWUyVXOt/P5XARnye4PXvyzAwQH eUhAzSYFU4Dp/9V8rqVRixP0JdVIPf6FW2ajlKjNasj31EQLyksvsPZgu4r5xsp4 MnqQ3PpAtG+JiB2pI1vN2mMPtCL9DkvACFmlxgJeJ/EU9yxkBmXGIR9aXrnLpD36 cwDK0MYvEUk0gREyA9BaOCKH6CViPgrI+XWy8CSytGi3SB475RkfNApM6YCEKuTR blcRHI4P9Dy4Q3zGcQ5FWXQwdYXmog6+KU0gI97ywox0Wap/wMjszGgWdfjaktJh U9xHZHU5UGVmrgmwIwUO =8WEq -----END PGP SIGNATURE----- _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot
This email and any information disclosed in connection herewith, whether written or oral, is the property of EnerNOC, Inc. and is intended only for the person or entity to which it is addressed. This email may contain information that is privileged, confidential or otherwise protected from disclosure. Distributing or copying any information contained in this email to anyone other than the intended recipient is strictly prohibited. _______________________________________________ IOT mailing list IOT@xmpp.org http://mail.jabber.org/mailman/listinfo/iot ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3345 / Virus Database: 3199/6420 - Release Date: 06/18/13