Comments on Web Socket binding for oBIX WD02

Section 11.4 of the Web Socket Bindings deals with Application Specific Extensions. Several sections within the core information model (1.1) and in Encodings, speak to oBIX header information. Should oBIX header be handled in this binding as an Application Specific Extension?

 

Should information from the Lobby be passed in the Header? See page 7 of RFC6455 (4.2.1, 4.2.2)

 

In oBIX 1.1, we have discussed contract “passing” in which one node client may define a contract, pass that handle to another client, which is then able to access the same contract. This seems inimical to the web-sockets approach.  Should this sort of interaction be forbidden in this binding?

 

Move TLS References from section 2.2 to the normative references section.

 

 

"Energy and persistence conquer all things." -- Benjamin Franklin 

Toby Considine
TC9, Inc

OASIS TC Chair: oBIX & WS-Calendar

OASIS TC Editor: EMIX, Energy Interoperation

SGIP Smart Grid Architecture Committee

  

Email: 
Phone: (919)619-2104

http://www.tcnine.com
blog: http://www.NewDaedalus.com