kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Migrate parts of prop. 156 to spec section for 0.9.49

Browse Source 
Update I2NP spec for prop. 156
Clarify prop. 154 based on subsequent decisions made in prop. 156
Add more notes common structures spec about ECIES routers
Add notes in more places that tunnel ID must not be zero
This commit is contained in:
zzz
2021-01-08 07:56:58 -05:00
parent 41622fb2fb
commit c4ace8e9a8
7 changed files with 489 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
i2p2www/spec/tunnel-message.rst
View File

@@ -3,8 +3,8 @@ Tunnel Message Specification
============================
.. meta::
:category: Design
:lastupdated: September 2016
:accuratefor: 0.9.26
:lastupdated: 2021-01
:accuratefor: 0.9.49
.. contents::
@@ -60,7 +60,7 @@ These are the contents of a tunnel data message after encryption.
Tunnel ID :: `TunnelId`
4 bytes
the ID of the next hop
the ID of the next hop, nonzero
IV ::
16 bytes
@@ -121,7 +121,7 @@ These are the contents of a tunnel data message when decrypted.
Tunnel ID :: `TunnelId`
4 bytes
the ID of the next hop
the ID of the next hop, nonzero
IV ::
16 bytes
@@ -225,7 +225,7 @@ or a complete (unfragmented) I2NP message, and the instructions are:
Tunnel ID :: `TunnelId`
4 bytes
Optional, present if delivery type is TUNNEL
The destination tunnel ID
The destination tunnel ID, nonzero
To Hash ::
32 bytes