Token type for Autocharge #526
Comments
|
We're having some discussions about this as we speak in the development working group. You take a step back and even wonder if MAC addresses used for Autocharge are even tokens, or if they are merely ways to look up the RFID token which should be treated as the token for the session. If you use MAC addresses as tokens for roaming with OCPI, that comes with security and privacy concerns. So, in short, we don't really have an answer to this at the moment. |
|
Yes, we received requests to use MAC addresses as tokens for Autocharge. We know Autocharge is insecure compared to 15118 Plug & Charge, but many stations and servers aren't ready for 15118 Plug & Charge. Since the OCPI 3.0 review version mentions Autocharge in B3.1, can I ask if OCPI 3.0 will support Autocharge? |
Which token type should be used for Autocharge tokens? Since the token type is a part of the unique key of a token, the CPO and the eMSP need to agree on the same token type for Autocharge to work. It looks like two types are possible: RFID and OTHER.
The reason to choose RFID is that Autocharge uses the same field as RFID in OCPP 1.6, so it is straight forward to treat them the same.
The reason to choose OTHER is that Autocharge is not RFID, but we may need some namespaces in this OTHER type.
The text was updated successfully, but these errors were encountered: