consistency: we use ZERO, not NULL

1 files changed, 11 insertions, 10 deletions

diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml
index 4b8e04c..cb4ccbd 100644
--- a/draft-schanzen-r5n.xml
+++ b/draft-schanzen-r5n.xml
@@ -1276,7 +1276,8 @@ ComputeOutDegree(REPL_LVL, HOPCOUNT, L2NSE):
           created the element. The signature is computed over the public keys of the
           previous peer (from which the message was received) and next peer (the
           peer the message is send to). A new message has no previous peer and
-          uses the <tt>NULL</tt> public key for the signature.
+          uses all <tt>ZEROs</tt> (32 NULL-bytes) in the
+          public key field when creating the signature.
         </t>
         <t>
           Assuming peer A sends a new <tt>PUT</tt> message to peer B, which forwards
@@ -1286,15 +1287,15 @@ ComputeOutDegree(REPL_LVL, HOPCOUNT, L2NSE):
         </t>
         <figure anchor="figure_path" title="Example PATH">
           <artwork name="" type="" align="left" alt=""><![CDATA[
-+--------------------+-------+
-| Sig A(    0,Pub B) | Pub A |
-+--------------------+-------+
-+--------------------+-------+
-| Sig B(Pub A,Pub C) | Pub B |
-+--------------------+-------+
-+--------------------+-------+
-| Sig C(Pub B,Pub D) | Pub C |
-+--------------------+-------+
++---------------------+-------+
+| Sig A(ZEROs, Pub B) | Pub A |
++---------------------+-------+
++---------------------+-------+
+| Sig B(Pub A, Pub C) | Pub B |
++---------------------+-------+
++---------------------+-------+
+| Sig C(Pub B, Pub D) | Pub C |
++---------------------+-------+
           ]]></artwork>
         </figure>
         <t>