Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Markdown adjustments |
---|---|
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
b289b99d73c53b48e3586423dfb2416a |
User & Date: | bernd 2019-03-07 20:38:36.306 |
Context
2019-03-09
| ||
12:11 | Markdown edits check-in: 385b2a8aa4 user: bernd tags: trunk | |
2019-03-07
| ||
20:38 | Markdown adjustments check-in: b289b99d73 user: bernd tags: trunk | |
13:34 | Bump version number check-in: 3f673a735d user: bernd tags: trunk, 0.8.8-20190307 | |
Changes
Changes to README.md.
|
| | | | | | | | | | | | | | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 | net2o — reinventing the Internet ================================ net2o is the attempt to reinvent the Internet. Get it and try it ----------------- net2o is currently under early alpha test. [Get it](https://fossil.net2o.de/net2o/doc/trunk/wiki/get-it.md) and [try it](https://fossil.net2o.de/net2o/doc/trunk/wiki/try-it.md). There are lots of things [to do](https://fossil.net2o.de/net2o/doc/trunk/wiki/todo.md). What’s broken? -------------- * The internet bases on assumptions 20–30 years old * These assumptions are wrong today * Much of it followed the “good enough” principle * There’s a huge pile of accumulated cruft * Fixing this mess one–by–one is the wrong attempt What for? --------- I’ve a dream: A peer–to–peer network, where services like search engines or social networks aren’t offered by big companies, who in turn need to make money by selling the privacy of their users. Where all data is encrypted, so that access is only possible for people who have the key and really are authorized. Which layman can use without cryptic user interfaces. Where the browser is a platform for running useful applications without the mess of Flash and JavaScript. Without the lag of “buffer bloat” and without the speed problems of a protocol not designed to be assisted by hardware. What needs to be fixed? ----------------------- * IP: Use switch–based simple routing, don’t route every packet * TCP: Most data just needs to be obtained reliable, the order doesn’t matter. And TCP’s flow control is broken (delay minimized is the way to go). * Encryption everywhere: This is no longer an expensive operation (and for symmetric encryption, fast hardware implementation is feasible) * P2P instead of client–server * A new API (render layer, markup language, scripting) — the browser is there for serious applications now. Rendering is done with OpenGL ES, GUI layer is MINOΣ 2. net2o has been inspired by Open Network Forth from Heinz Schnitter. |
Changes to wiki/topology.md.
︙ | ︙ | |||
35 36 37 38 39 40 41 | a 10Gb Ethernet now to a billion 1M packets in 40 years means this has enough headroom for the next 40 years. The packet contains these elements: 1. 2 bytes flags: 2 bits QoS (00 highest to 11 lowest), 2 bits protocol version (default is now 01), 4 bits packet size | | | | 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 | a 10Gb Ethernet now to a billion 1M packets in 40 years means this has enough headroom for the next 40 years. The packet contains these elements: 1. 2 bytes flags: 2 bits QoS (00 highest to 11 lowest), 2 bits protocol version (default is now 01), 4 bits packet size (64\*2^_n_), 2 bit switch flags (broadcast, multicast), 3 bits reserved, 3 bits for flow control (resend-toggle, burst-toggle, ack-toggle). 2. 16 bytes path (rough Internet 1.0 equivalent: "address") 3. 8 bytes address: this is the address in the destination buffer where the packet will be stored (roughly equivalent to port+sequence number) 4. 64\*2^_size_ bytes data 5. 16 bytes authentication data (keyed cryptographic checksum) The "abstraction" at packet level is shared memory; the model is read locally and write remotely (you can't read remotely, you can ask for the other side to send you packets). Of course, the addresses are virtual, so you can't write into arbitrary memory - only into the buffers provided by the other side. |
︙ | ︙ |