1.

Need to specify that for protocol 1, the client cant request both producer and
consumer
2. Need to clarify request protocol, there are some confusion between role,
which one need to send the server as a producer etc.
3. Need to explain the need for supporting uri=* to give all channels on the
well. For Describe and StartChannelStreaming to ?
4. Need to update the interaction with discovery stuf
a. Send /
b. Reply eml://witsml141
c. etc
5. How to negotiate the protocol and resolving the request session.
a. Only need to match major and minor version ?
6. Need to explain how the messageId and correlationId works in request
response messaging system. Need an example with a message diagram
7. Need clarification on how to convert the datetime on C#, Java, JS to
Energistics DateTime. Explanation how the ofset works. Not clear on the
document.
8. Need to make sure that is that any protocol that can already be used for
another Energistics specification. For example the Store API protocol 4?
9. Need to register to IANA for subprotocol and websocket error code ?
10.Need deployment strategy => real world usage where theres a proxy,
firewall etc. what client and server has to obey to pass all of this layer. ( John
Shields Guide)
11.Is ETP can be used in diferent port ? Do we need to limit this to 80/433
12.Should enforce to use RFC 6455. Doesnt support others
13.What do we do if something is not followed :
a. Messages within session are numbered ? monotically increasing ? how
if its not ? do we want to keep track of it ? do we need to return error
code ?
b. How if a correlation id is used but not necessary, do we want to throw
exception ?
c. Various ETP Protocol Diferent numbering ??
14.Need to define the Role of each protocol
15.Ambiguity between what if the server cant satisfied the protocol client
requested ? Page 10 and 13 (specs)
16.The wrong schema for Protocols so it wrong for the protocol number in enum
17.Core Session / Protocol. What if the client doing handshake but not requesting
any protocol ? Should we close it after time out ?
18.Security mechanism for Javascript ?
19.Reconnecting behavior ?
a. Security mechanism for reconnecting ?
b. Reauthenticated again?
c. Resume behavior
20.Exception when sending the message to something not in its role or not exist
message
21.Need to clarify the usage of common message. MessageTypeId >= 1000.
Need to confirm with JS Implementation Guide(Page 9). Specs(Page 13)

22.Need to fix ETP implementation guide about the protocol number on page 8.
(specs-page 10)
23.Wording Problem : Page 13 point 7.adequate
24.Etp-sessionId(specs page 13)
25.What error if we are not requesting energistics-tp to etp server >
26.Fix page 15, from exp-encoding to etp-encoding
27.Alternate behavior ? for page 15. When request the protocol
28.Exception when the Server hasnt follow the message flow rules ? ex: send
describe before sending start etc.
29.Page 21. We still have RaLF there.
30.Naming convention ID or Id
31.Page 26 we still have Object_Query in protocols and schema
32.Page 27. Etp-session vs etp-sessionid
33.Need to explain more about reconnection mechanism. Section ??
34.SHOULD vs MUST ?
35.Should clarify whats needed in release 1 ?
36.Need clarification about DateTime, Java and C# example ? how to convert
time, ofset ?
37.Page 29 ProtocolID enumeration ? vs Protocols ?
38.Page 30 Object_Query ??? Need to standardize the name
39.Growing object notification is not in the protocol yet ?
40.How exactly do we want to send trajectory station and geology interval ?
Page 35. We include objectMetadata ?
41.Page 36, you can only request the range request from single log for WITMSL
141. You need the same index reference
42.Page 38 Query ? do we want this one ?
43.objectType vs resourceType ? => Resources vs DataObject
44.ObjectChangeTypes ? Isnt this redundant ? we already have a intentional
message
45.Need a mapping example from existing WITSML, PRODML and RESQML object
to Resource, Data Object
46.ResourceType hasnt been explained yet in docs. Pag 40
47.hasChildreen. Is this optional ? we can return -1 ? is there any rule where we
can t return -1
48.Page 41, so we cant use Notification protocol to send trajectory ? this one is
only for specific part too ?
49.Page 42. MessageTypeID ?? Naming convention ?
50.Should we limit the ChannelDescribe ? to wellbore ? etc ?
51.Page 48: should start streaming data ? I think we need to wait until
ChannelStreamingStart ?
52.ChannelDataBlock is still in the docs ? I think it has already been replaced by
ChannelDataFrame ?
53.Need to show the example of interaction using / and eml://uri and
urn:uuid/ and etc How to use discovery with the uri
54.We need ack fr store API delete and put or exception
55.Store notification : correlation id ? overlapping subscription ? behavior ?
56.How to remove notification ?
57.Growing object protocol is not for subscription to growing part ? only request
response ?

58.Where is the stream in growing object protocol ?

59.ETP Impl : Need to add a couple of things from Implementation guide to ETP
Specs ?
a. Ex: ping pong to protocol 1 ?
60.Page 8: Need to update the name and protocols number
61.Need to list the exception and how to use it Cross Protocol .
62.Number Convention for custom protocol need to be added in the Specs
63.Page 11 : need to migrate this to (keeping the connection open)
64.Advice how to use the websocket in the real world. With proxy, known
problem ,work around etc
65.Need a convention about naming : log vs channelgroup and curve vs channel
=> Page 19 need t fix the uri => refer to ETP specification ?
66.Who is responsible for creating the channel group / log object In streaming ?
Consumer (via Store API ) or server ?
67.Who will be responsible for creating UUID ? Client or server ?
68.Ack for Notification ?