charinev / opnc

CharIN Open Plug&Charge Protocol (OPNC)
Creative Commons Attribution Share Alike 4.0 International
18 stars 8 forks source link

Key topic for Robustness/headers "OPNC-From" and "OPNC-To" #27

Closed JMR-Gireve closed 1 year ago

JMR-Gireve commented 1 year ago

Key topic for Robustness/headers ""OPNC-From"" and ""OPNC-To"":

The identification of fonctional actors ("Sub-CPO"", "Sub-eMSP", "Sub-OEM") is based on explicit data (http headers) and not on data processing on object's ids

Benefits: 1°)Basic IT rule on not managing process based on data processing on object's ids 2°)Compliancy with OCPI and thus with the majority of eMSP and CPO

Impact son players already connected via OPCP:none: no change are needed"

MKeCharIN commented 1 year ago

Has already been discussed in the group and so far not supported to change. Newly to be discussed in the group? Voting if needed.

JMR-Gireve commented 1 year ago

My suggestion is to add this mode as an option which would be described in the protocol description

Since the last discussion, we worked on the "notification flows", and saw that this kind of information (regarding the source and target identification) is mandatory for notifications

MKeCharIN commented 1 year ago

@JMR-Gireve , please create accordingly a pull request.