Participant Relationship Protocol

Back to matrix

F36-HP: No

Rationale

HIP establishes authenticated host associations and ESP security state; these do not request capacity, delay or reliability from network admission control. The selected datagram application/service and operator transport policies add no such exchange.

Assessment method

Primary RFC review and explicit optional IP transport policy selection

Source context

HIP/Babel specifications and RFC 7567/2475

Outstanding qualification

Selected composition only. No RSVP/IntServ or other application reservation protocol is included. Peer authorization, route availability and priority marking are not sufficient for F36.

Public sources

Editorial evidence references

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