Update of "Specification_v_1_0"
Not logged in
Overview

Artifact ID: 6b6f60329da10a20fe7c35fc729cb1d35e0c54dc
Page Name:Specification_v_1_0
Date: 2015-09-02 01:32:43
Original User: martin_vahi
Content

General Overview

Silktorrent graph consists of vertices that are Silktorrent servers and sets of directed edges that are one-way tunnels between the 2 vertices. It is not specified, what the set of tunnels between any 2 vertices must consist of, but the existance of the tunnels is probabilistic. That is to say, any tunnel can cease to exist or re-appear at any moment and if all tunnels between the 2 vertices cease to exsist, then the 2 vertices loose direct connection.

Addressing

Background

Given the lessons learned from the TRON encoding and the American branch of character encoding formats, ASCII to Unicode, the Silktorrent is designed so that from addressing point of view the Silktorrent can cover the whole Universe. That entails infinitely large address space, which in turn entails infinitely large addresses, which can be avoided by using relative addressing. That way the huge computers of aliens can still communicate with the "tiny" computers of 2015 human race.

A link to Illustration 1

The Silktorrent graph nodes in the relative address space can originate from different, disconnected, regions of the infinite address space.

The Addressing Specification

There exist 2 levels of addressing: If some data-carrying creature walks in the tunnel, then the tunnel can be a whole world in its own right and has a lot of addressable objects, for example, houses, doors of the houses, but one of those addressable objects, a door, is an entry to a tunnel and another one, another door, is an exit from the tunnel. As the tunnel is a world in its own right, the the world can be shared with other tunnels that form other directed edges in the Silktorrent graph. That means that the data-carrying creature can get lost and accidentally use a wrong door for exiting the tunnel and end up at a wrong Silktorrent graph vertex. Different data-carrying creatures might even cooperate and exchange tasks at that world, but some of the creatures might be killed off by censorship enforcing creatures or just die there for other reasons, leaving the data undelivered.

Partial list of worlds that can be used for forming the tunnels:

As the throughput of those tunnels is very limited, a counter-measure for flooding attacks is to allow tunnel implementations and Silktorrent vertex nodes to choose, what data to relay, where to relay it and what kind of data packages to receive.

The communication protocol of the Silktorrent also has 2 levels:


Silktorrent Graph Communication Protocol (SGCP)

The V0 has been designed, but it still needs to be written down here.

A rough comment in Estonian:
Siia tuleb siis see jutt fikseeritud pakettide suurustest, kus server deklareerib suurusega ja aksepteeritava jaotusega ja muude parameetritega oma vastuvõtunõuded, toetatud räsialgoritmid, jne. pikk lugu koos turva-teemaga, a la sõprade signeeritud paketid võetakse kindlalt vastu, pakkettide saatjate ja vastuvõtjate anonüümsuse tagamise teema (mitu ID-d, muutuvad saatjate ID-d, jne.)