diff options
| author | Martin Schanzenbach <schanzen@gnunet.org> | 2022-08-01 11:06:25 +0200 |
|---|---|---|
| committer | Martin Schanzenbach <schanzen@gnunet.org> | 2022-08-01 11:06:25 +0200 |
| commit | 72e140fc2b25c07fe3249df18b2877f9333ed6fb (patch) | |
| tree | 44f4135b759235d512448e31b12c0da6574064e9 | |
| parent | 484c36781226ea9a7162a596825844e491ac0e29 (diff) | |
| download | lsd0004-72e140fc2b25c07fe3249df18b2877f9333ed6fb.tar.gz lsd0004-72e140fc2b25c07fe3249df18b2877f9333ed6fb.zip | |
fi
| -rw-r--r-- | draft-schanzen-r5n.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/draft-schanzen-r5n.xml b/draft-schanzen-r5n.xml index 14665c7..6ddf81e 100644 --- a/draft-schanzen-r5n.xml +++ b/draft-schanzen-r5n.xml | |||
| @@ -1140,8 +1140,8 @@ BEGIN | |||
| 1140 | The signature of a Path Element is created by the current hop | 1140 | The signature of a Path Element is created by the current hop |
| 1141 | after it made its routing decision identifiying the successor peer. | 1141 | after it made its routing decision identifiying the successor peer. |
| 1142 | The wire format of an example path from Peers A over B and C as it | 1142 | The wire format of an example path from Peers A over B and C as it |
| 1143 | would be received by D in a is illustrated in <xref target="figure_path_ex"/>. | 1143 | would be received by D in a <tt>PutMessage</tt> or <tt>ResultMessage</tt> |
| 1144 | <tt>PutMessage</tt> or <tt>ResultMessage</tt>. | 1144 | is illustrated in <xref target="figure_path_ex"/>. |
| 1145 | A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field | 1145 | A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field |
| 1146 | a length of 3. | 1146 | a length of 3. |
| 1147 | A <tt>PutMessage</tt> would indicate a length of 3 as the sum of | 1147 | A <tt>PutMessage</tt> would indicate a length of 3 as the sum of |
| @@ -1215,8 +1215,8 @@ BEGIN | |||
| 1215 | The wire format of a truncated example path from Peers B over C to D | 1215 | The wire format of a truncated example path from Peers B over C to D |
| 1216 | is illustrated in <xref target="figure_path_ex_trunc"/>. | 1216 | is illustrated in <xref target="figure_path_ex_trunc"/>. |
| 1217 | The wire format of an example path from Peers B over C as it | 1217 | The wire format of an example path from Peers B over C as it |
| 1218 | would be received by D in a is illustrated in <xref target="figure_path_ex_trunc"/>. | 1218 | would be received by D in a <tt>PutMessage</tt> or <tt>ResultMessage</tt> |
| 1219 | <tt>PutMessage</tt> or <tt>ResultMessage</tt>. | 1219 | is illustrated in <xref target="figure_path_ex_trunc"/>. |
| 1220 | A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field | 1220 | A <tt>ResultMessage</tt> would indicate in the <tt>PATH_LEN</tt> field |
| 1221 | a length of 1. | 1221 | a length of 1. |
| 1222 | A <tt>PutMessage</tt> would indicate a length of 1 as the sum of | 1222 | A <tt>PutMessage</tt> would indicate a length of 1 as the sum of |