Ouroboros - Recent changes [en]

Congestion avoidance

Dimitri — Sun, 12 Jul 2026 09:13:06 GMT

Blanked the page

Ouroboros Data Transfer Protocol

Dimitri — Sat, 11 Jul 2026 20:44:26 GMT

Fields associated with the network end-to-end layer

← Older revision		Revision as of 20:44, 11 July 2026
(One intermediate revision by the same user not shown)
Line 15:		Line 15:
	\| \|		\| \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| Time-to-Live \| QoS \| ECN \| ~~PADDING~~ \|		\| Time-to-Live \| QoS \| ECN \| CAP8 \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| \|		\| \|
Line 56:		Line 56:
	==== ECN ====		==== ECN ====

	This field specifies Explicit Congestion Notification (ECN), with similar intent as the ECN bits in the Type-of-Service field in IPv4 or Traffic Class field in IPv6. The Ouroboros ECN field is by default one octet wide, and its value can be set to an increasing value as packets are queued deeper and deeper in a congested routers’ forwarding queues. Ouroboros enforces Forward ECN (FECN).		This field specifies Explicit Congestion Notification (ECN), with similar intent as the ECN bits in the Type-of-Service field in IPv4 or Traffic Class field in IPv6. The Ouroboros ECN field is by default one octet wide, and its value can be set to an increasing value as packets are queued deeper and deeper in a congested routers’ forwarding queues. Ouroboros enforces Forward ECN (FECN). See [[Congestion avoidance]].

			==== CAP8 ====

			This field specifies the capacity of the link that is flagged by Explicit Congestion Notification (ECN). See [[Congestion avoidance]].

	=== Notable fields not present in ODTP ===		=== Notable fields not present in ODTP ===

Ouroboros Protocols

Dimitri — Sat, 11 Jul 2026 20:41:40 GMT

Data Transfer Protocol

← Older revision		Revision as of 20:41, 11 July 2026
Line 19:		Line 19:
	\| \|		\| \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| Time-to-Live \| QoS \| ECN \| ~~PADDING~~ \|		\| Time-to-Live \| QoS \| ECN \| CAP8 \|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	\| \|		\| \|

Congestion avoidance

Dimitri — Sat, 11 Jul 2026 20:39:27 GMT

Created page with "{{DISPLAYTITLE:mb-ecn - Multi-bit ECN Congestion Avoidance}} mb-ecn is a congestion-avoidance (CA) policy for the Ouroboros unicast IPCP. It lives in the IPC Process: the flow-and-retransmission task (FRCP) provides reliability, in-order delivery and flow control end-to-end; congestion avoidance is orthogonal and runs per IPCP layer. Within a layer, the IPCP controls '''aggregates''', one loop per (destination address, QoS cube), shared by every flow toward that destina..."

Show changes

Ouroboros Functional Layering

Dimitri — Sat, 11 Jul 2026 20:39:15 GMT

Network end-to-end layer / Flow Allocator

← Older revision		Revision as of 20:39, 11 July 2026
Line 53:		Line 53:
	## Multiplexing: generate a local Endpoint Identifier for a flow		## Multiplexing: generate a local Endpoint Identifier for a flow
	## Map this local Endpoint Identifier to the peer address		## Map this local Endpoint Identifier to the peer address
	# Congestion avoidance: Monitor the network flow for congestion and police throughput as needed.		# [[Congestion avoidance]]: Monitor the network flow for congestion and police throughput as needed.

	The network-layer flow allocation exchange maps the application-requested QoS to a network traffic class. The application-level request/response is carried over by the network-level request/response handshake to fit the complete flow allocation process (application-level and network-level) within a single round-trip.		The network-layer flow allocation exchange maps the application-requested QoS to a network traffic class. The application-level request/response is carried over by the network-level request/response handshake to fit the complete flow allocation process (application-level and network-level) within a single round-trip.