Ouroboros Model - Revision history

Dimitri: /* Names */

2024-07-28T06:20:43Z

Names

← Older revision		Revision as of 06:20, 28 July 2024
Line 16:		Line 16:
	Ouroboros ''service names'' are the equivalent of Domain Names in DNS. Ouroboros ties service names to processes (not hosts). Multiple processes can bind to the same name, and multiple names can be bound to the same process.		Ouroboros ''service names'' are the equivalent of Domain Names in DNS. Ouroboros ties service names to processes (not hosts). Multiple processes can bind to the same name, and multiple names can be bound to the same process.

	To communicate, a process requests a flow with as destination a certain name. Like Domain Names in DNS, service names can be authenticated using public key cryptography (certificates). Service name certificates (if present) are stored in the directory of each layer and returned as part of name queries.		To communicate, a process requests a flow with as destination a certain service name. Like Domain Names in DNS, service names can be authenticated using public key cryptography (certificates). Service name certificates (if present) are stored in the directory of each layer and returned, together with a destination address as part of name queries.

	== Flows ==		== Flows ==

Dimitri: /* Names */

2024-07-28T06:19:39Z

Names

← Older revision		Revision as of 06:19, 28 July 2024
Line 14:		Line 14:

	== Names ==		== Names ==
	Ouroboros ''service names'' are the equivalent of Domain Names in ~~TCP/IP~~. Ouroboros ties service names to processes (not hosts). Multiple processes can bind to the same name, and multiple names can be bound to the same process.		Ouroboros ''service names'' are the equivalent of Domain Names in DNS. Ouroboros ties service names to processes (not hosts). Multiple processes can bind to the same name, and multiple names can be bound to the same process.

	To communicate, a process requests a flow with as destination a certain name. Like Domain Names in DNS, service names can be authenticated using public key cryptography (certificates). Service name certificates (if present) are stored in the directory of each layer and returned as part of name queries.		To communicate, a process requests a flow with as destination a certain name. Like Domain Names in DNS, service names can be authenticated using public key cryptography (certificates). Service name certificates (if present) are stored in the directory of each layer and returned as part of name queries.

Dimitri: /* Names */

2024-07-28T06:19:13Z

Names

← Older revision		Revision as of 06:19, 28 July 2024
Line 14:		Line 14:

	== Names ==		== Names ==
	Names in Ouroboros ~~are tied~~ to processes. Multiple processes can bind to the same name, and multiple names can be bound to the same process.		Ouroboros ''service names'' are the equivalent of Domain Names in TCP/IP. Ouroboros ties service names to processes (not hosts). Multiple processes can bind to the same name, and multiple names can be bound to the same process.

			To communicate, a process requests a flow with as destination a certain name. Like Domain Names in DNS, service names can be authenticated using public key cryptography (certificates). Service name certificates (if present) are stored in the directory of each layer and returned as part of name queries.

	== Flows ==		== Flows ==

Dimitri: /* Flows */

2024-07-22T06:06:54Z

Flows

← Older revision		Revision as of 06:06, 22 July 2024
Line 17:		Line 17:

	== Flows ==		== Flows ==
	Flows exist between two flow endpoints. They are very ~~broad~~ and generalize a best-effort packet stream.		Flows exist between two flow endpoints. They are very broadly defined and generalize a best-effort packet stream.

	* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.		* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.

Dimitri: /* Elements of the model */

2024-07-22T06:06:09Z

Elements of the model

← Older revision		Revision as of 06:06, 22 July 2024
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. Flows are between flow endpoints, and the source and destination application read from and write to these ~~enpoints~~.		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. Flows are between flow endpoints, and the source and destination application read from and write to these endpoints.

	The model for multicast works differently.		The model for multicast works differently.

Dimitri: /* Flows */

2024-07-21T15:40:21Z

Flows

← Older revision		Revision as of 15:40, 21 July 2024
Line 17:		Line 17:

	== Flows ==		== Flows ==
	Flows exist between two flow endpoints. They are very broad and ~~generalized~~		Flows exist between two flow endpoints. They are very broad and generalize a best-effort packet stream.

	* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.		* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.
	* Flows are established over a Layer, which may consist of any number of forwarding processes called IPCPs.		* Flows are established over a Layer, which may consist of any number of forwarding processes called IPCPs.
	* Packets transmitted by the source have a non-zero probability to arrive at least once at the destination.		* Packets transmitted by the source have a non-zero probability to arrive at least once at the destination.
	* Packets can follow any path in the Layer		* Packets can follow any path in the Layer
	* There is no ~~implied~~ correlation between the path taken by different packets along the same flow		* There is no correlation to be assumed between the path taken by different packets along the same flow
			* Packets may arrive out of order
	* Packets can be duplicated		* Packets can be duplicated
	* Flows can be authenticated and/or encrypted.		* Flows can be authenticated and/or encrypted.

Dimitri: /* Flows */

2024-07-21T15:37:35Z

Flows

← Older revision		Revision as of 15:37, 21 July 2024
Line 17:		Line 17:

	== Flows ==		== Flows ==
	Flows ~~are~~ between two flow endpoints. They are very broad and generalized		Flows exist between two flow endpoints. They are very broad and generalized
	* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.		* Data is sent as a packet at the source flow endpoint and arrives as a packet at the destination flow endpoint.
	* Flows are established over a Layer, which may consist of any number of forwarding processes called IPCPs.		* Flows are established over a Layer, which may consist of any number of forwarding processes called IPCPs.

Dimitri: /* Flows */

2024-07-21T15:37:20Z

Flows

← Older revision		Revision as of 15:37, 21 July 2024
Line 22:		Line 22:
	* Packets transmitted by the source have a non-zero probability to arrive at least once at the destination.		* Packets transmitted by the source have a non-zero probability to arrive at least once at the destination.
	* Packets can follow any path in the Layer		* Packets can follow any path in the Layer
	* Packets may or may not be fragmented at any point along the flow.		* There is no implied correlation between the path taken by different packets along the same flow
	* Packet fragmentation can be subject to coding techniques such as erasure codes or forward error correcting codes		* Packets can be duplicated
	* There is no implied correlation between the path taken by different packets ~~or different fragments in~~ the same flow
	* Packets ~~or fragments~~ can be duplicated
	* Flows can be authenticated and/or encrypted.		* Flows can be authenticated and/or encrypted.
	** The flow is authenticated before the flow endpoints are handed over to the server/client processes.		** The flow is authenticated before the flow endpoints are handed over to the server/client processes.
	** If encrypted, the encryption key(s) are passed to the ~~processes before~~ the flow.		** If encrypted, the encryption key(s) are passed to the process along with the flow endpoint.

	== Layers ==		== Layers ==

Dimitri: /* Flows */

2024-07-21T13:54:24Z

Flows

← Older revision		Revision as of 13:54, 21 July 2024
Line 27:		Line 27:
	* Packets or fragments can be duplicated		* Packets or fragments can be duplicated
	* Flows can be authenticated and/or encrypted.		* Flows can be authenticated and/or encrypted.
	* The flow is authenticated before the flow endpoints are handed over to the server/client processes.		** The flow is authenticated before the flow endpoints are handed over to the server/client processes.
	* If encrypted, the encryption key(s) are passed to the processes before the flow.		** If encrypted, the encryption key(s) are passed to the processes before the flow.

	== Layers ==		== Layers ==

Dimitri: /* Flows */

2024-07-21T13:54:09Z

Flows

← Older revision		Revision as of 13:54, 21 July 2024
Line 27:		Line 27:
	* Packets or fragments can be duplicated		* Packets or fragments can be duplicated
	* Flows can be authenticated and/or encrypted.		* Flows can be authenticated and/or encrypted.
	* The flow is authenticated before the flow endpoints are handed over to the server/client processes.		* The flow is authenticated before the flow endpoints are handed over to the server/client processes.
	* If encrypted, the encryption key(s) are passed to the processes before the flow.		* If encrypted, the encryption key(s) are passed to the processes before the flow.


	== Layers ==		== Layers ==