Here follows the specifications for adar, an automated distributed storage system utilising network coding
adar is discovered by utilising mDNS or DNS-SD or Bonjour or avahi to allow for a robust, user-friendly mechanism utilising industry standards
| Service property | Value(s) |
|---|---|
| Name | Device hostname |
| Type | _adar |
| Protocol | _tcp |
| Server | Device FQDN |
| Port | 6780 |
A full service name example: Hostname._adar._tcp.local.
The service's TXT records must include the following:
| Field | Value |
|---|---|
Description |
Network coding for automated distributed storage systems |
uuid |
Universally Unique IDentification for the device in a string format |
The service's IP addresses must include at least one IPv4 address
The service's IP addresses should include at least one IPv6 address
The device's UUID is used to identify peers persistently
The device's hostname is used to resolve peers during connection sessions
Messages contain a UTF-8 representation of text data, and are terminated by a newline character (\n)
A pair is initiated by sending pair?
Pairing is accepted by responding with sure
Encryption keys are established and stored for the duration of a connection session, using Diffie-Hellman key exchange
Keys follow the RFC3526 MODP group 14, with 1024-bit length
Key exchange is initiated by sending key? prefixed to a base64 encoding of the public key of the sender
The recipient shall respond with key! prefixed to their public key (also in base64 encoding)
Both parties can now generate a shared key