This preserves the address of the remote peer involved in a specific recorded IKE negotiation failure, per its description, with its type identified by the paired local-type field per the description's own wording. It's the concrete address an admin uses to identify exactly where a failed connection attempt originated, which is essential when investigating whether repeated failures are coming from the same source (suggesting a misconfigured legitimate peer) or many different sources (suggesting scanning or attack traffic). Multiple failure entries all sharing the same remote address would point clearly at one specific peer's ongoing connectivity problem rather than a broad pattern.