HTTP 5.0 Security Boundary
HTTP 5.0 retains the HTTP 4.0 security boundary.
FP is an application quota. It is not an authentication token, authorization token, routing command, network-reachability control, reputation score, or geographic restriction.
Bonus references do not grant access by themselves and must be evaluated by normal application policy.
Defensive audit kits may contain bounded parser tests, malformed-frame fixtures, replay tests, capability tests, rate-limit tests, resource-limit tests, and interoperability records. They must not implement router disruption, traffic flooding, credential theft, route manipulation, or unauthorized network interference.
HTTP 5.0 does not replace TLS or QUIC. Geographic location does not change the protocol's defensive rules.