kubo/net/handshake
2014-11-16 16:46:06 -08:00
..
pb swarm + handshake: better observed addr check 2014-11-05 04:01:38 -08:00
doc.go copy handshake readme into a doc.go for pretty godoc results 2014-11-08 21:42:37 -08:00
handshake1_test.go handshake1 renaming 2014-10-22 04:56:18 -07:00
handshake1.go implement ipfs id in the new commands library 2014-11-16 16:46:06 -08:00
handshake3.go handshake: log whether new addr observed 2014-11-05 04:05:30 -08:00
README.md minimal doc on handshake 2014-10-22 13:10:55 -07:00

IFPS Handshake

The IPFS Protocol Handshake is divided into three sequential steps

  1. Version Handshake (Hanshake1)
  2. Secure Channel (NewSecureConn)
  3. Services (Handshake3)

Currently these parts currently happen sequentially (costing an awful 5 RTT), but can be optimized to 2 RTT.

Version Handshake

The Version Handshake ensures that nodes speaking to each other can interoperate. They send each other protocol versions and ensure there is a match on the major version (semver).

Secure Channel

The second part exchanges keys and establishes a secure comm channel. This follows ECDHE TLS, but isn't TLS. (why will be written up elsewhere).

Services

The Services portion sends any additional information on nodes needed by the nodes, e.g. Listen Address (the received address could be a Dial addr), and later on can include Service listing (dht, exchange, ipns, etc).