Resolution:
In BCRN 5.1.0 and BC 5.2.0, the timestamp and content-length of an RNIF 1.1 and 2.0 messages can be used to trace the transactions between DMZ and BCRN.

In addition to the timestamp and content-length, BC records the “boundary” value also in the BC interior log for RNIF 2.0 messages ONLY. The same boundary value can be verified in BC 5.2.0 DMZ log file, BC 5.2.0 interior log file and Audit log message.

Example: For BCRN 5.1.0 and BC 5.2.0

BC DMZ Server
-----------
content-type: multipart/related; type="multipart/signed"; boundary="4028c45917199a230117199a32d60003"

BC Interior Server
----------
-- content-type: multipart/related; type="multipart/signed"; boundary="4028c45917199a230117199a32d60003"


Note:
1. BC 5.2.0 always records the “boundary” value in the DMZ log file, but BC 5.1.0 does not in the BC DMZ log file.
2. The detail tracing must be enabled in BCDMZ as well as BC interior server to trace a message between BCDMZ and BC interior server. The BC user guide will provide the details on how to enable detail tracing.