Skip to content

Commit

Permalink
Documented the meaning of the EncodingScheme form in the inter-router…
Browse files Browse the repository at this point in the history
… message and linked to cjdnsctrl (parser/serializer)
  • Loading branch information
cjdelisle committed Dec 29, 2016
1 parent 4ca6180 commit fd93ab3
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion doc/Whitepaper.md
Expand Up @@ -532,6 +532,9 @@ The Switch Header may be followed by three different types of packets:

TODO

See [this parser](https://github.com/cjdelisle/cjdnsctrl) for more information
about the CTRL packet.

#### Switch Data Header

The layout of the Switch Data Header is the following:
Expand Down Expand Up @@ -642,7 +645,10 @@ Possible keys in a router message include:
address `tar`.
* `pn`: ping node
* `ei` (integer): the encoding index. References one of the forms of the
encoding scheme `es`. (TODO: to do what?)
encoding scheme `es`. This is needed when crafting the label to send a
packet through the node which has returned this message. The following hop
must be encoded in this form or a greater one otherwise the return path
cannot be represented.
* `es` (byte string): the encoding scheme. See the section above about its
format.
* `n` (byte string): list of nodes. See below for its serialization.
Expand Down

0 comments on commit fd93ab3

Please sign in to comment.