Ouroboros Model: Difference between revisions
Line 5: | Line 5: | ||
= Elements of the model = | = Elements of the model = | ||
The Ouroboros packet network model for unicast works as follows: To be able to communicate, ''processes'' request ''flows'' to one another: server processes ''bind' to ''(service) names'', the client process requests a flow to such a name. | |||
The model for multicast works differently. | |||
== processes == | == processes == | ||
Processes are running software. No need for fancy buzzwords. A microservice component, a (monolithic) OS kernel, an open spreadsheet, a running background script, ... they are all nothing but processes. | |||
== names == | == names == |
Revision as of 12:52, 21 July 2024
This page is under construction
This pages provides an overview of the Ouroboros model, which summarizes our proposed organization of packet networking functionality.
Elements of the model
The Ouroboros packet network model for unicast works as follows: To be able to communicate, processes request flows to one another: server processes bind' to (service) names, the client process requests a flow to such a name.
The model for multicast works differently.
processes
Processes are running software. No need for fancy buzzwords. A microservice component, a (monolithic) OS kernel, an open spreadsheet, a running background script, ... they are all nothing but processes.
names
flows
Layers
connections
IRMd
IPCPs
Functional layering
Main page: Ouroboros Functional Layering
The model's functional layering underpinning Ouroboros has some distinct properties.
- A clear distinction between unicast and broadcast (see the multicast conjecture).
- Unicast
- The application end-to-end layer performs functionalities that require knowledge at the endpoint applications, but are not of concern to the network. These are automated repeat-request (ARQ), fragmentation and flow control. In addition, this layer also performs encryption, authentication and packet integrity (CRC). The data protocol associated with this layer is called the Flow and Retransmission control protocol (FRCP). It is considered an application protocol rather than a network protocol.
- The network end-to-end layer performs flow allocation/multiplexing, name-to-address resolution, and congestion avoidance.
- The network forwarding layer performs routing and hop-by-hop forwarding functions.
- The Unicast Layer is a distributed application that implements the network end-to-end layer and network forwarding layer functionalities. Since the elements of a Unicast Layer are also applications, they inherit the application end-to-end layer on a hop-by-hop basis.
- Broadcast
- The network flooding layer is completely stateless.
- The Broadcast Layer is a distributed application that implements the network flooding layer. Since the elements of a Broadcast Layer are also applications, they inherit the application end-to-end layer on a hop-by-hop basis.
- Unicast
- At the bottom of this network model, is the transmission layer. It is always accompanied by a (devolved) network end-to-end layer.
Network Layering and Recursion
Main Page: Network Layering