Optimised link establishment

docs/manual/understanding.html

@@ -490,7 +490,7 @@ At the same time we establish an efficient encrypted channel. The setup of this
 terms of bandwidth, so it can be used just for a short exchange, and then recreated as needed, which will
 also rotate encryption keys. The link can also be kept alive for longer periods of time, if this is
 more suitable to the application. The procedure also inserts the <em>link id</em> , a hash calculated from the link request packet, into the memory of forwarding nodes, which means that the communicating nodes can thereafter reach each other simply by referring to this <em>link id</em>.</p>
-<p>The combined bandwidth cost of setting up a link is 3 packets totalling 409 bytes (more info in the
+<p>The combined bandwidth cost of setting up a link is 3 packets totalling 240 bytes (more info in the
 <a class="reference internal" href="#understanding-packetformat"><span class="std std-ref">Binary Packet Format</span></a> section). The amount of bandwidth used on keeping
 a link open is practically negligible, at 0.62 bits per second. Even on a slow 1200 bits per second packet
 radio channel, 100 concurrent links will still leave 95% channel capacity for actual data.</p>
@@ -762,8 +762,8 @@ proof           11
 
  - Path Request    :    33  bytes
  - Announce        :    151 bytes
- - Link Request    :    182 bytes
- - Link Proof      :    141 bytes
+ - Link Request    :    77  bytes
+ - Link Proof      :    77  bytes
  - Link RTT packet :    86  bytes
  - Link keepalive  :    14  bytes
 </pre></div>