Ouroboros Frequently Asked Questions - Revision history

Dimitri at 20:29, 12 August 2024

2024-08-12T20:29:27Z

← Older revision		Revision as of 20:29, 12 August 2024
Line 11:		Line 11:
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code.

	= Q: Do you guys think you can replace TCP/IP? =		== Q: Do you guys think you can replace TCP/IP? ==
	No-one can replace TCP/IP. We think the TCP/IP stack is - from a modern day perspective - incredibly rickety. All we can do is take what we learned over the past 25 years and try to come to a better integrated solution for secure and reliable end-to-end packet networking. We have no control over technology adoption, all we can do is provide a possible path for it. Ouroboros runs fine as an overlay on top of TCP/IP. There is no need to throw out your routers and switches. Replacing TCP/IP is not up to us, it's completely up to you.		No-one can replace TCP/IP. We think the TCP/IP stack is - from a modern day perspective - incredibly rickety. All we can do is take what we learned over the past 25 years and try to come to a better integrated solution for secure and reliable end-to-end packet networking. We have no control over technology adoption, all we can do is provide a possible path for it. Ouroboros runs fine as an overlay on top of TCP/IP. There is no need to throw out your routers and switches. Replacing TCP/IP is not up to us, it's completely up to you.

Dimitri at 20:29, 12 August 2024

2024-08-12T20:29:16Z

← Older revision		Revision as of 20:29, 12 August 2024
Line 7:		Line 7:

	Until implementations exist which properly leverage the capacity of Ouroboros as an infrastructure, it is difficult to make a comparison to the specific use cases addressed by existing network paradigms.		Until implementations exist which properly leverage the capacity of Ouroboros as an infrastructure, it is difficult to make a comparison to the specific use cases addressed by existing network paradigms.


	== Q: Why are you using C instead of rust / golang / zig / ... ==		== Q: Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code.

			= Q: Do you guys think you can replace TCP/IP? =
			No-one can replace TCP/IP. We think the TCP/IP stack is - from a modern day perspective - incredibly rickety. All we can do is take what we learned over the past 25 years and try to come to a better integrated solution for secure and reliable end-to-end packet networking. We have no control over technology adoption, all we can do is provide a possible path for it. Ouroboros runs fine as an overlay on top of TCP/IP. There is no need to throw out your routers and switches. Replacing TCP/IP is not up to us, it's completely up to you.

Dimitri: /* Q: Why are you using C instead of rust / golang / zig / ... */

2024-08-12T18:28:15Z

Q: Why are you using C instead of rust / golang / zig / ...

← Older revision		Revision as of 18:28, 12 August 2024
Line 10:		Line 10:

	== Q: Why are you using C instead of rust / golang / zig / ... ==		== Q: Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code~~. Given what we're up against, complaints about the choice of programming language are the least of our worries~~.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code.

Dimitri: /* Q: Why are you using C instead of rust / golang / zig / ... */

2024-08-12T18:27:59Z

Q: Why are you using C instead of rust / golang / zig / ...

← Older revision		Revision as of 18:27, 12 August 2024
Line 10:		Line 10:

	== Q: Why are you using C instead of rust / golang / zig / ... ==		== Q: Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require ~~mostly~~ unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require a lot of unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.

Dimitri: /* Q: Why are you using C instead of rust / golang / zig / ... */

2024-08-12T18:27:24Z

Q: Why are you using C instead of rust / golang / zig / ...

← Older revision		Revision as of 18:27, 12 August 2024
Line 10:		Line 10:

	== Q: Why are you using C instead of rust / golang / zig / ... ==		== Q: Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work ~~we did on~~ IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work/code from IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.

Dimitri at 18:26, 12 August 2024

2024-08-12T18:26:57Z

← Older revision		Revision as of 18:26, 12 August 2024
Line 9:		Line 9:


	== Why are you using C instead of rust / golang / zig / ... ==		== Q: Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work we did on IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work we did on IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.

Dimitri: /* Why are you using C instead of (rust, golang, ...) */

2024-08-12T18:26:45Z

Why are you using C instead of (rust, golang, ...)

← Older revision		Revision as of 18:26, 12 August 2024
Line 9:		Line 9:


	== Why are you using C instead of (rust, golang, ...) ==		== Why are you using C instead of rust / golang / zig / ... ==
	Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work we did on IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.		Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work we did on IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.

Dimitri at 18:25, 12 August 2024

2024-08-12T18:25:49Z

← Older revision		Revision as of 18:25, 12 August 2024
Line 2:		Line 2:

	== Q: How does Ouroboros compare to [Tor, CJDNS, I2P, Wireguard, etc.]? ==		== Q: How does Ouroboros compare to [Tor, CJDNS, I2P, Wireguard, etc.]? ==
	A: The goal of Ouroboros is to tackle problems in the world of information transfer by re-establishing network architecture at a system level.		The goal of Ouroboros is to tackle problems in the world of information transfer by re-establishing network architecture at a system level.

	As such, comparing Ouroboros to projects which rely on existing network architecture (IP/TCP, TLS, DNS) is akin to comparing a concrete foundation to a pre-existing structure. It is possible to move these structures onto the foundation (or build new ones!), but it is ineffective to compare Ouroboros to any existent networking protocol before any practical implementations have been built.		As such, comparing Ouroboros to projects which rely on existing network architecture (IP/TCP, TLS, DNS) is akin to comparing a concrete foundation to a pre-existing structure. It is possible to move these structures onto the foundation (or build new ones!), but it is ineffective to compare Ouroboros to any existent networking protocol before any practical implementations have been built.

	Until implementations exist which properly leverage the capacity of Ouroboros as an infrastructure, it is difficult to make a comparison to the specific use cases addressed by existing network paradigms.		Until implementations exist which properly leverage the capacity of Ouroboros as an infrastructure, it is difficult to make a comparison to the specific use cases addressed by existing network paradigms.


			== Why are you using C instead of (rust, golang, ...) ==
			Our previous experience was building a RINA stack in C in Linux kernel space (IRATI), so we had a few years of experience developing in a spartan C environment. Since the Ouroboros project was initially targeting a user-space RINA stack that should be portable to constraint IoT devices, we hoped to leverage some of the work we did on IRATI. When we started early in 2016, rust was not really a thing, definitely not on small COTS IoT boards. Today we may or may not choose something else, but even in rust, the nature of what we are designing will require mostly unsafe code. Given what we're up against, complaints about the choice of programming language are the least of our worries.

Zen at 23:04, 19 February 2024

2024-02-19T23:04:09Z

← Older revision		Revision as of 23:04, 19 February 2024
Line 1:		Line 1:
	~~{{Under construction}}~~		Ouroboros is a project with the capacity to make fundamental changes to the way we share information in the digital world. When encountering this project for the first time, plenty of people have questions: what it is, how it works, and how it compares to other projects. This is where you'll find the answers to some of the most common questions.

			== Q: How does Ouroboros compare to [Tor, CJDNS, I2P, Wireguard, etc.]? ==
			A: The goal of Ouroboros is to tackle problems in the world of information transfer by re-establishing network architecture at a system level.

			As such, comparing Ouroboros to projects which rely on existing network architecture (IP/TCP, TLS, DNS) is akin to comparing a concrete foundation to a pre-existing structure. It is possible to move these structures onto the foundation (or build new ones!), but it is ineffective to compare Ouroboros to any existent networking protocol before any practical implementations have been built.

			Until implementations exist which properly leverage the capacity of Ouroboros as an infrastructure, it is difficult to make a comparison to the specific use cases addressed by existing network paradigms.

Dimitri at 12:06, 9 December 2023

2023-12-09T12:06:01Z

← Older revision	Revision as of 12:06, 9 December 2023
Line 1:	Line 1:
		{{Under construction}}