Unverified Commit 2681940c authored by anonimal's avatar anonimal
Browse files

Moneropedia: clarify Garlic Routing, add I2PControl

Referencing:
 - monero-project/kovri#256
 - monero-project/monero-site#155
parent 1af1de08
......@@ -10,11 +10,11 @@ summary: "Routing technology as implemented in Kovri"
The term *Garlic Routing* has a diverse history of varying interpretations.
As it currently stands, Monero defines *Garlic Routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers.
As it currently stands, Monero defines *Garlic Routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of internet peers. The @layered-encryption of Garlic Routing is similar to the @layered-encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing).
### History
In written form, the term *Garlic Routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing).
In written form, the term *Garlic Routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing.
As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *Garlic Routing*:
......
---
layout: moneropedia
entry: "I2PControl"
tags: ["kovri"]
terms: ["i2pcontrol", "I2PControl"]
summary: "TODO(anonimal): finish"
---
### The Basics
TODO(anonimal): finish
https://github.com/EinMByte/qtoopie
### In-depth information
TODO(anonimal): finish
......@@ -36,6 +36,8 @@ TODO(anonimal): finish
@garlic-routing
@I2PControl
@i2np
@i2p
......@@ -71,6 +73,3 @@ TODO(anonimal): finish
@transports
@tunnel
- Kovri I2PControl (links to API, clients + qtoopie)
- ...more/what else?
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment