Glossary: Difference between revisions
| Line 5: | Line 5: | ||
Ouroboros is [[Ouroboros Recursive Layers|multi-Layered]] (capitalized), allowing networks to overlay each other. There are 2 types of Layers: Unicast Layers and Broadcast Layers, consisting of Unicast IPCPs and Broadcast IPCPs respectively. | Ouroboros is [[Ouroboros Recursive Layers|multi-Layered]] (capitalized), allowing networks to overlay each other. There are 2 types of Layers: Unicast Layers and Broadcast Layers, consisting of Unicast IPCPs and Broadcast IPCPs respectively. | ||
We appreciate the fact that the different | We appreciate the fact that the different use of ''layer/Layer'' can be initially confusing, and have considered other options such as ''stratum'', but for the time being, we stick to layer/Layer. | ||
== Whatevercast (RINA) == | == Whatevercast (RINA) == | ||
A proposed concept for the ''unification of unicast, anycast, multicast and broadcast''. The proposed API is allocate(whatevercastname) and the network will resolve the correct set for you based on the ''whatevercast'' name and a ''set of rules'' associated with it. Our attempt at implementing this concept led to the [[Ouroboros multicast conjecture]]. | A proposed concept for the ''unification of unicast, anycast, multicast and broadcast''. The proposed API is allocate(whatevercastname) and the network will resolve the correct set for you based on the ''whatevercast'' name and a ''set of rules'' associated with it. Our attempt at implementing this concept led to the [[Ouroboros multicast conjecture]]. | ||
Revision as of 09:59, 12 October 2023
This page is under construction
layer/Layer (O7s)
The Ouroboros model is subdivided in layers (lowercase), with similar intent as the TCP/IP model (5 layers) or OSI (7 layers) model which it aims to improve upon. Ouroboros is multi-Layered (capitalized), allowing networks to overlay each other. There are 2 types of Layers: Unicast Layers and Broadcast Layers, consisting of Unicast IPCPs and Broadcast IPCPs respectively.
We appreciate the fact that the different use of layer/Layer can be initially confusing, and have considered other options such as stratum, but for the time being, we stick to layer/Layer.
Whatevercast (RINA)
A proposed concept for the unification of unicast, anycast, multicast and broadcast. The proposed API is allocate(whatevercastname) and the network will resolve the correct set for you based on the whatevercast name and a set of rules associated with it. Our attempt at implementing this concept led to the Ouroboros multicast conjecture.