+All routers must publish their I2NP protocol version in the "router.version" field in the RouterInfo properties. +This version field indicates their level of support for various I2NP protocol features, +and is not necessarily the actual router version. +
+If alternative (non-Java) routers +wish to publish any version information about the actual router implementation, +they must do so in another property. +Versions other than those listed below are allowed. Support will be +determined through a numeric comparison; for example, 0.9.13 implies support for 0.9.12 features. +Note that the "coreVersion" property is not used for determination of the I2NP protocol version. +
+A basic summary of the I2NP protocol versions is as follows. For details, see below. +
| Version | +Required I2NP Features | +
|---|---|
| 0.9.16 | +RI key certs / ECDSA and EdDSA sig types + Note: RSA sig types also supported as of this version, but currently unused + DLM lookup types (DLM flag bits 3-2) (proposed) + |
+
| 0.9.15 | +Dest/LS key certs w/ EdDSA Ed25519 sig type (if floodfill) | +
| 0.9.12 | +Dest/LS key certs w/ ECDSA P-256, P-384, and P-521 sig types (if floodfill) + Note: RSA sig types also supported as of this version, but currently unused + Nonzero expiration allowed in RouterAddress + |
+
| 0.9.7 | +Encrypted DSM/DSRM replies supported (DLM flag bit 1) (if floodfill) | +
| 0.9.6 | +Nonzero DLM flag bits 7-1 allowed | +
| 0.9.3 | +Requires zero expiration in RouterAddress | +
| 0.9 | +Supports up to 16 leases in a DSM LS store (6 previously) | +
| 0.7.12 | +VTBM and VTBRM message support | +
| 0.7.10 | +Floodfill supports encrypted DSM stores | +
| 0.7.9 or lower | +All messages and features not listed above | +
| 0.6.1.10 | +TBM and TBRM messages introduced + Minimum version compatible with current network + |
+
+Note that there are also transport-related features and compatibility issues; +see the NTCP and SSU transport documentation for details. +
+ + + + +
-Same format as TunnelBuildMessage, except for the addition of an "num" field in front and $num number of Build Request Records instead of 8
+Same format as TunnelBuildMessage, except for the addition of an "num" field in front
+and $num number of Build Request Records instead of 8
num ::
1 byte `Integer`