Minutes - Security Industry Association

2 Error Handling
Handling for a wrong CRC (checksum) or time stamp are specifically covered in
the existing document. Incorrect decryption would cause a checksum failure.
The DUH message is intended as a catchall for messages that are
"unprocessable" for other reasons, so it would be difficult to further define this.
1 Check Criterion
The existing extended data definition to carry the MAC address seems sufficient.
Should this field become mandatory for some implementations?
2 Encrypted Size
Less effort is being expended in newer designs to reduce data size, so that the
data encoding is more robust and more easily debugged.
3 Checklist of Main Requirements
This would be an excellent annex.
4 Token Table
It's generally avoided to duplicate information from one standard in another
document to keep the two documents from coming into later conflict. But
repeating the reference table as an annex would be reasonable.
1 Data Encryption
The document references FIPS 197 for AES encryption. Use of encryption is
certainly desirable, but this standard does not need to mandate its use.
2 Hash
The encryption provides enough of a signature to satisfy most message
authentication requirements, but a scheme to include a specific signature could
be designed and included in the standard.
3 2009 Errata
This information needs to be incorporated in the published document.
4 Formatting
The document could be reformatted to improve clarity.
5 prEN 50136-1-7 Interoperability
Considerable analysis would be required to comment on the feasibility of
defining a translation from one protocol to the next.