[Smartgrid] Fwd: Solicitation for feedback on OpenADR 2.0 transport mechanisms

Tue Jun 7 18:21:52 EDT 2011

Hello all, attached, is a note from Girish Gatikar on OpenADR transport and
his request for feedback.

-- Shidan

---------- Forwarded message ----------
From: Girish Ghatikar <gghatikar at lbl.gov>
Date: Tue, Jun 7, 2011 at 5:47 PM
Subject: Solicitation for feedback on OpenADR 2.0 transport mechanisms
To: SGIP-B2GWG at smartgridlistserv.org

B2G Group,

The OpenADR Alliance is currently in the process of evaluating demand
response message transport mechanisms for OpenADR Version 2.0. The
transports currently under consideration are included in the attached
document. If your organization would like to; 1) recommend another transport
for consideration or 2) comment on the transports currently listed by the
OpenADR Alliance, please forward your recommendation or comments to Ed Koch
(ed at ed@akuacom.com) by COB on June 13th.

Thank you!
-Rish

OpenADR Version 2 Potential Transport Mechanisms

The protocols listed below have been designed based on a range of
requirements. There is no best or good or bad protocol. They all have their
strengths relative to specific applications. The OpenADR Alliance will
evaluate these protocols based on their ability to satisfy the requirements
of current and future demand response applications.

·       SOAP Web services (Simple Object Access Protocol)

o   http://www.w3.org/TR/ws-arch/

o   Supported on many software platforms

o   Widely used in enterprise SOA and ESBs and for accessing  web resources

o   Supported by W3C, OASIS and others

·       REST web services (Representational State Transfer)

o   http://en.wikipedia.org/wiki/Representational_State_Transfer

o   Supported on many software platforms

o   Widely used for accessing web resources

o   Based on HTTP

·       AtomPub (Atom Publishing Protocol)

o   http://tools.ietf.org/html/rfc5023

o   The AtomPub is an application-level protocol for publishing and editing
Web resources.  The protocol is based on HTTP transfer of Atom-formatted
representations.

o   Supported on many software platforms

o   Widely used for accessing web resources from browsers

o   Uses the Atom Syndication Format metadata container

·       XMPP (Extensible Messaging and Presence Protocol)

o   http://www.ietf.org/rfc/rfc3920.txt, http://xmpp.org/

o   XMPP is a set of open technologies for instant messaging, presence,
multi-party chat, voice and video calls, collaboration, lightweight
middleware, content syndication, sensor data acquisition, device control and
generalized routing of XML data including point-to-point and
publish-subscribe message exchanges.

o   An IETF standard

o   Widely used in a variety of messaging applications

o   Supported on many software platforms

·       AMQP (Advanced Message Queuing Protocol) (also RabbitMQ)

o
http://www.amqp.org/confluence/display/AMQP/Advanced+Message+Queuing+Protocol

o   The Advanced Message Queuing Protocol is an open Internet Protocol for
Business Messaging. AMQP is divided up into separate layers. At the lowest
level is an efficient binary peer-to-peer protocol for transporting messages
between two processes over a network. At the higher levels, abstract message
format is defined, with concrete standard encoding.

·       PubSubHubub

o   http://code.google.com/p/pubsubhubbub/

o   A simple, open, server-to-server web-hook-based pubsub
(publish/subscribe) protocol as an extension to Atom and RSS.

o   Uses the Atom Syndication Format metadata container

o   Aimed at improving efficiency and performance of AtomPub

·       SIP (Session Initiation Protocol)

o   http://en.wikipedia.org/wiki/Session_Initiation_Protocol

o   The Session Initiation Protocol (SIP) is an
IETF<http://en.wikipedia.org/wiki/IETF>-defined
signaling <http://en.wikipedia.org/wiki/Signalling_(telecommunications)>
protocol <http://en.wikipedia.org/wiki/Communications_protocol>, widely used
for controlling multimedia <http://en.wikipedia.org/wiki/Multimedia>
communication
sessions <http://en.wikipedia.org/wiki/Communication_session> such as
voice<http://en.wikipedia.org/wiki/Internet_telephony>and
video <http://en.wikipedia.org/wiki/Video> calls over Internet
Protocol<http://en.wikipedia.org/wiki/Internet_Protocol>(IP). Used in
conjunction with an application-specific wire-protocol.

o   White paper:
http://robotics.tmcnet.com/librarydownload.aspx?id=2684&title=Realizing+the+OpenADR+Demand+and+Response+specification+using+SIP&type=white%20papers

·       Comet

o   http://en.wikipedia.org/wiki/Comet_(programming)

o   Comet is an umbrella term that refers to a variety of Http techniques
specifically designed for pushing data in a way that is compatible with
existing browsers. Sometimes referred to as HTTP push and long polling.

·       Web Socket

o   http://dev.w3.org/html5/websockets/

o   *WebSocket* is a technology providing for bi-directional,
full-duplex<http://en.wikipedia.org/wiki/Duplex_(telecommunications)#Full-duplex>communications
channels, over a single Transmission
Control Protocol<http://en.wikipedia.org/wiki/Transmission_Control_Protocol>(TCP)
socket <http://en.wikipedia.org/wiki/Internet_socket>. It is designed to be
implemented in web browsers <http://en.wikipedia.org/wiki/Web_browser> and web
servers <http://en.wikipedia.org/wiki/Web_server>, but it can be used by any
client or server application.

·       IMS (IP Multimedia Subsystem)

o   http://en.wikipedia.org/wiki/IP_Multimedia_Subsystem

o   An architectural framework for delivering Internet
Protocol<http://en.wikipedia.org/wiki/Internet_Protocol>(IP)
multimedia <http://en.wikipedia.org/wiki/Multimedia> services.

·       OPC-Unified Architecture

o   http://www.opcfoundation.org/Default.aspx/01_about/UA.asp?MID=AboutOPC

o   An advanced high-speed point-to-point industrial protocol for both
wide-area and local-area networking.

o   Incorporates integrated security, data telemetry, event messaging,
historical data access, information browsing.

·       BACnet Web Services

o   May be using AtomPub and CSML?

·       Constrained Application Protocol (CoAP)

o   Constrained Application Protocol (CoAP), is an emerging IETF standard (
https://datatracker.ietf.org/doc/draft-ietf-core-coap/) and is a specialized
RESTful (Representational State Transfer) protocol for use with constrained
networks and nodes for machine-to-machine applications such as smart energy
and building automation.

-- 
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720
GGhatikar at lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential
information and should not be copied without permission. If you are not the
intended recipient, please contact the sender as soon as possible and delete
the email from computer[s].

-- 
__________________________________
Shidan Gouran
President & CEO, Gulf Pearl Ltd.
Suite 2200, 4950 Yonge Street
Toronto, ON M2N 6K1
shidan at gulfpearl.com
Office: (416) 218-5583
Cell: (416) 854-3017
Fax: (416) 221-4668
__________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/smartgrid/attachments/20110607/70270267/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenADR Transport Mechanism List.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 42057 bytes
Desc: not available
Url : http://sipforum.org/pipermail/smartgrid/attachments/20110607/70270267/attachment-0001.bin 