Back to matrix

F34-HP: No

Rationale

HIPv2/ESP with application UDP delivers routed datagrams or transport data rather than an Ethernet frame service across multiple forwarding hops.

Assessment method

Selected-composition primary documentary assessment; no runtime experiment

Source context

Primary selected transport/routing specifications and declared profile boundary

Outstanding qualification

HIP identifies hosts and ESP protects host-to-host packets; no content-service or application-authentication wrapper is selected. The existence of Ethernet beneath the stack does not make it an Ethernet bridge. No TAP service, pseudowire or Ethernet-carrying application is selected.

Public sources

• https://www.rfc-editor.org/rfc/rfc7401.html
• https://www.rfc-editor.org/rfc/rfc7402.html
• https://www.rfc-editor.org/rfc/rfc8046.html

Editorial evidence references

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

• round469.html
• round469-sources.json