3.7.5.3 Receiving Message #5
On receipt of message #5, the host MUST check for the presence of flags within a notification payload of type EXCHANGE_INFO.
IKE_EXCHANGE_INFO_ND_BOUNDARY: If this flag is set, the host MUST set the Boundary flag for the corresponding QM SA.
IKE_EXCHANGE_INFO_GUARANTEE_ENCRYPTION: If this flag is set, the host MUST set the Guaranteed Encryption flag for the corresponding QM SA.
Message #6 MUST be constructed in response as follows:
The IPsec implementation MUST send the packet and MUST trigger IKE to negotiate the corresponding QM SA. The first quick mode negotiation message is message #5. Message #6 MUST be constructed as follows:
The header and payloads MUST be constructed as specified in [RFC2409] section 5.5.
If the SPD rule matching the traffic for which the QM SA is negotiated has the Boundary flag set, the host MUST add a notification payload with the following fields:
Notify Message Type (2 bytes): 0x9C45 (EXCHANGE_INFO).
The Notification Data field is interpreted as a flags field.
Flag 0x00000001 (IKE_EXCHANGE_INFO_ND_BOUNDARY) MUST be set if the corresponding rule in the SPD has the Boundary flag set.
This notification payload MUST be constructed as specified in section 2.2.6.