Moneropedia: add/update/cleanup/fix entries

Added:
 - In-net
 - Lease
 - Message
 - I2NP (skeleton file)
 - Tunnel (skeleton file)

Updated/cleaned-up/fixed:
 - Router-Info
 - Lease-Set
 - Garlic-Routing
 - Floodfill
 - Destination

Note: term'ed lease-set to LeaseSet because of conflict with Lease

Referencing:
 - monero-project/kovri#256
 - monero-project/monero-site#155
This commit is contained in:
anonimal 2016-10-15 05:37:07 +00:00
parent e6661fcee1
commit 000e95cfe4
No known key found for this signature in database
GPG key ID: 66A76ECF914409F1
10 changed files with 133 additions and 29 deletions

View file

@ -3,17 +3,17 @@ layout: moneropedia
entry: "Destination" entry: "Destination"
tags: ["kovri"] tags: ["kovri"]
terms: ["destination"] terms: ["destination"]
summary: "A Kovri/I2P address that serves as a final endpoint" summary: "A in-net address that serves as a final endpoint"
--- ---
### The Basics ### The Basics
A destination is the @I2P address of the final endpoint you are trying to connect to (an @I2P website or service). A destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or simply a peer).
TODO(anonimal): finish TODO(anonimal): finish
### In-depth Information ### In-depth Information
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri will use the @base64-address. An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address or a `.i2p` hostname while, internally, @Kovri/@I2P will use the @base64-address.
TODO(anonimal): finish TODO(anonimal): finish

View file

@ -3,17 +3,13 @@ layout: moneropedia
entry: "Floodfill" entry: "Floodfill"
tags: ["kovri"] tags: ["kovri"]
terms: ["floodfill"] terms: ["floodfill"]
summary: "TODO(anonimal): finish" summary: "An I2P router which maintains a distributed network-database"
--- ---
### The Basics ### The Basics
TODO(anonimal): finish By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
### In-depth information ### In-depth information
TODO(anonimal): finish Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details.
### Notes
TODO(anonimal): finish

View file

@ -10,7 +10,7 @@ summary: "Routing technology as implemented in Kovri/I2P"
The term *Garlic Routing* has a diverse history of varying interpretations. 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.
### History ### History
@ -25,18 +25,19 @@ As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered
>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed. >during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
so we for sure thought we had invented the name, at the time. so we for sure thought we had invented the name, at the time.
Note: permission to use the aforementioned quotes were granted by Nick Mathewson and Roger Dingledine
### In-depth Information ### In-depth Information
In technical terms, for @Kovri and @I2P, *Garlic Routing* translates to any/all of the following: In technical terms, for @Kovri and @I2P, *Garlic Routing* translates to any/all of the following:
1. Layered Encryption - Layered Encryption (like Onion Routing)
2. Bundling multiple messages together (garlic cloves) - Bundling multiple @messages together (garlic cloves)
3. ElGamal/AES Encryption - ElGamal/AES Encryption
Note: as seen in [Tor](https://torproject.org/), *Onion Routing* also uses layered encryption but does not use ElGamal and is not message-based. Note: though [Tor](https://torproject.org/) uses layered encryption, Tor does not use ElGamal and is not message-based.
### Notes ### Notes
- Permission to use the aforementioned quotes granted by Nick Mathewson and Roger Dingledine - In terms of Onion/Garlic Routing, another way to envision layered encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll)
- For more technical details, read [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing) - For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)
- Another way to envision layered encryption (in terms of Onion/Garlic Routing) is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll)

View file

@ -0,0 +1,15 @@
---
layout: moneropedia
entry: "I2NP"
tags: ["kovri"]
terms: ["I2NP", "message", "messages"]
summary: "TODO(anonimal): finish"
---
### The Basics
TODO(anonimal): finish
### In-depth information
TODO(anonimal): finish

View file

@ -0,0 +1,15 @@
---
layout: moneropedia
entry: "In-net"
tags: ["kovri"]
terms: ["in-net"]
summary: "Within the I2P network"
---
### The Basics
**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network.
### In-depth information
Example: *in-net download* would be defined as downloading *only* within @I2P.

View file

@ -16,14 +16,55 @@ TODO(anonimal): finish
@address-book @address-book
@eepsite (@hidden-service, @garlic-site, @garlic-service) @base32-address
@base64-address
@canonically-unique-host
@clearnet @clearnet
@reseed @network-database @router-info @floodfill @lease-set @data-directory
@destination
@eepsite (@hidden-service, @garlic-site, @garlic-service)
@floodfill
@garlic-routing
@i2np
@i2p
@in-net
@java-i2p
@jump-service
@kovri
@lease
@leaseset
@locally-unique-host
@message @messages
@network-database
@reseed
@router-info
@subscription
@tunnel
- Kovri Cryptography (encryption, signatures, etc.) - Kovri Cryptography (encryption, signatures, etc.)
- Kovri Transports (SSU/NTCP) - Kovri Transports (SSU/NTCP)
- Kovri Tunnels (garlic routing, I2NP, etc.)
- Kovri I2PControl (links to API, clients + qtoopie) - Kovri I2PControl (links to API, clients + qtoopie)
- ...more/what else? - ...more/what else?

View file

@ -1,19 +1,25 @@
--- ---
layout: moneropedia layout: moneropedia
entry: "Lease-set" entry: "Lease-Set"
tags: ["kovri"] tags: ["kovri"]
terms: ["lease-set"] terms: ["LeaseSet"]
summary: "TODO(anonimal): finish" summary: "Contains all currently authorized Leases for a particular I2P Destination"
--- ---
### The Basics ### The Basics
TODO(anonimal): finish A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination.
### In-depth information ### In-depth information
TODO(anonimal): finish A Lease-Set contains:
- all of the currently authorized @leases for a particular @destination
- the public key to which garlic messages can be encrypted (see @garlic-routing)
- the signing public key that can be used to revoke this particular version of the structure
The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination.
### Notes ### Notes
TODO(anonimal): finish For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet)

View file

@ -0,0 +1,15 @@
---
layout: moneropedia
entry: "Lease"
tags: ["kovri"]
terms: ["lease", "leases"]
summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
---
### The Basics
A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination.
### In-depth information
For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease)

View file

@ -3,12 +3,12 @@ layout: moneropedia
entry: "Router-Info" entry: "Router-Info"
tags: ["kovri"] tags: ["kovri"]
terms: ["router-info"] terms: ["router-info"]
summary: "A file/data structure which contains an I2P peer's needed network information" summary: "A data structure or file which contains an I2P peer's needed network information"
--- ---
### The Basics ### The Basics
Router-Info is a file/data structure which contains all needed information to locate, identity, and communicate with an @I2P peer. This file/data structure includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers. Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identity, and communicate with an @I2P peer. Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers.
### In-depth information ### In-depth information

View file

@ -0,0 +1,15 @@
---
layout: moneropedia
entry: "Tunnel"
tags: ["kovri"]
terms: ["tunnel"]
summary: "TODO(anonimal): finish"
---
### The Basics
TODO(anonimal): finish
### In-depth information
TODO(anonimal): finish