Back to matrix

F20-HP: Yes

Rationale

HIP association state and ESP security associations reside at the communicating hosts. The selected direct IPv4/IPv6 transit forwards outer IP locators without mandatory per-HIP-association or application-flow entries. RFC 7402 section 3.2 places HIT/IP translation and ESP processing at the endpoints.

Assessment method

Documentary role/state inventory; no runtime test

Source context

Primary protocol specifications and unchanged selected compositions

Outstanding qualification

This does not mean endpoints are stateless. No NAT, HIP proxy or stateful traversal relay is selected; optional middleboxes can add state. No routing-scale or runtime qualification follows.

Public sources

• https://www.rfc-editor.org/rfc/rfc7402.html#section-3.2
• https://www.rfc-editor.org/rfc/rfc9147.html
• https://www.rfc-editor.org/rfc/rfc4291.html
• https://www.rfc-editor.org/rfc/rfc4760.html

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

• round260-sources.json