3
This commit is contained in:
@@ -9,6 +9,15 @@ Secure Access Fabric.
|
||||
The fabric node-to-node transport remains QUIC-only. HTTP/HTTPS is allowed only
|
||||
as an external client-facing service edge.
|
||||
|
||||
Terminology rule:
|
||||
|
||||
- `Fabric Transport` = QUIC/UDP node-to-node runtime layer.
|
||||
- `Control API` = HTTP/HTTPS management surface for UI, automation, releases,
|
||||
policy, audit, and status.
|
||||
|
||||
The Control API may use HTTP/HTTPS, but it is not a fallback or alternate
|
||||
carrier for fabric node-to-node runtime traffic.
|
||||
|
||||
## Purpose
|
||||
|
||||
The platform needs a clear distinction between:
|
||||
|
||||
Reference in New Issue
Block a user