Participant Relationship Protocol

Back to matrix

F26-IP: No

Rationale

The selected bare-IP profile forwards addressed datagrams without a native authenticated transit-admission boundary. Header checks, route lookup and hop limits do not establish permission to consume the onward link.

Assessment method

Primary architectural and forwarding-policy analysis; no bandwidth benchmark required

Source context

Selected composition and retained source assessment; new F26 criterion

Outstanding qualification

Added ACLs, provider policing or protected overlays can change deployment behavior but are not silently added to bare IP here. No assertion that every operational IP network lacks defenses.

Public sources

Editorial evidence references

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