[IOT] OpenADR comment period

Thomas Nichols tnichols at enernoc.com
Thu Jun 20 03:41:34 UTC 2013

An OpenADR network conceptually looks like a star network, with a single
VTN (virtual top node/ coordinator) and many VENS (virtual end nodes.)

The VEN needs to trust commands from a top node, and VENs can't
communicate -- ever -- with other VENs as far as OpenADR is concerned.

Agreed it's largely an implementation concern which is why it's not laid
out in the spec, more of a guidance.

We consider in most cases, the VTN and XMPP server will be controlled by
the same entity. The VTN could be connected as an XMPP client (or multiple
clients) or VTN endpoints could be exposed as service JIDs.

I think we have two choices.  (1) Tell VTN implementers/ deployments that
they need to secure the XMPP server to prevent VEN to VEN communication.
Or (2) we require VENs to maintain a whitelist of VTN JIDs, and drop or
reject packets that are not from an approved JID.  Or maybe both.


On 6/20/13 11:58 AM, "Peter Saint-Andre" <stpeter at stpeter.im> wrote:

>Hash: SHA1
>Hi Thom, thanks for your other post.
>On 6/19/13 8:52 PM, Thomas Nichols wrote:
>> 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.
>Would service providers want to forbid all communication among
>clients, or limit it to communication among particular "groups", as
>you say?
>That kind of thing usually is implementation-specific, but if you let
>us know what you're trying to achieve perhaps we can provide some
>- -- 
>Peter Saint-Andre
>Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
>Comment: GPGTools - http://gpgtools.org
>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

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.

More information about the IOT mailing list