I2CP spec minor clarifications
This commit is contained in:
@ -3,8 +3,8 @@ I2CP Specification
|
||||
==================
|
||||
.. meta::
|
||||
:category: Protocols
|
||||
:lastupdated: 2020-11
|
||||
:accuratefor: 0.9.48
|
||||
:lastupdated: 2021-12
|
||||
:accuratefor: 0.9.52
|
||||
|
||||
.. contents::
|
||||
|
||||
@ -226,7 +226,7 @@ information to communicate correctly with old routers. Clients and routers
|
||||
should not send messages that are unsupported by the other side, as they
|
||||
generally disconnect the session upon reception of an unsupported message.
|
||||
|
||||
The exchanged version information is the "core" version or I2CP protocol
|
||||
The exchanged version information is the "core" API version or I2CP protocol
|
||||
version, and is not necessarily the router version.
|
||||
|
||||
A basic summary of the I2CP protocol versions is as follows. For details, see
|
||||
@ -373,6 +373,8 @@ Notes
|
||||
The payload is in a gzip format as specified on the I2CP Overview page
|
||||
[I2CP-FORMAT]_.
|
||||
|
||||
Actual message length limit is about 64 KB.
|
||||
|
||||
.. _struct-SessionConfig:
|
||||
|
||||
Session Config
|
||||
@ -404,7 +406,7 @@ Offline Signatures
|
||||
* If the [Destination]_ is offline signed, the [Mapping]_ must contain
|
||||
the three options i2cp.leaseSetOfflineExpiration, i2cp.leaseSetTransientPublicKey,
|
||||
and i2cp.leaseSetOfflineSignature.
|
||||
The [Signature]_ is then by the transient [SigningPrivateKey]_ and is verified
|
||||
The [Signature]_ is then generated by the transient [SigningPrivateKey]_ and is verified
|
||||
with the [SigningPublicKey]_ specified in i2cp.leaseSetTransientPublicKey.
|
||||
See [I2CP-OPTIONS]_ for details.
|
||||
|
||||
@ -424,6 +426,7 @@ Contents
|
||||
|
||||
Notes
|
||||
`````
|
||||
Session ID 0xffff is used to indicate "no session", for example for hostname lookups.
|
||||
|
||||
|
||||
Messages
|
||||
@ -663,8 +666,7 @@ Notes
|
||||
The PrivateKeys match each of the [PublicKey]_ from the LeaseSet.
|
||||
The PrivateKeys are necessary for decrypting garlic routed messages.
|
||||
|
||||
The contents and format for EncryptedLeaseSet are preliminary and subject to change.
|
||||
See proposal 123 for more information.
|
||||
See proposal 123 for more information on Encrypted LeaseSets.
|
||||
|
||||
The contents and format for MetaLeaseSet are preliminary and subject to change.
|
||||
There is no protocol specified for administration of multiple routers.
|
||||
@ -828,7 +830,7 @@ Sent from Client to Router. The router responds with a SetDateMessage_.
|
||||
|
||||
Contents
|
||||
````````
|
||||
1. I2CP Version [String]_
|
||||
1. I2CP API Version [String]_
|
||||
2. Authentication [Mapping]_ (optional, as of release 0.9.11)
|
||||
|
||||
Notes
|
||||
@ -1244,7 +1246,7 @@ Description
|
||||
Request that a client authorize the inclusion of a particular set of inbound
|
||||
tunnels.
|
||||
|
||||
Sent from Router to Client. The client responds with a CreateLeaseSetMessage_.
|
||||
Sent from Router to Client. The client responds with a CreateLeaseSetMessage_ or CreateLeaseSet2Message_.
|
||||
|
||||
Contents
|
||||
````````
|
||||
@ -1508,7 +1510,7 @@ handshake to notify the client of a clock shift.
|
||||
Contents
|
||||
````````
|
||||
1. [Date]_
|
||||
2. I2CP Version [String]_
|
||||
2. I2CP API Version [String]_
|
||||
|
||||
Notes
|
||||
`````
|
||||
|
Reference in New Issue
Block a user