From e4f551054f2b6e482a8ce9cfd1984bb3b7338e1d Mon Sep 17 00:00:00 2001 From: zzz Date: Fri, 8 Nov 2013 17:30:49 +0000 Subject: [PATCH] incorporate I2CP status code table --- www.i2p2/pages/i2cp_spec.html | 68 +++++++++++++++++++++++++++++++++-- 1 file changed, 66 insertions(+), 2 deletions(-) diff --git a/www.i2p2/pages/i2cp_spec.html b/www.i2p2/pages/i2cp_spec.html index 9541a9a4..c8804ec7 100644 --- a/www.i2p2/pages/i2cp_spec.html +++ b/www.i2p2/pages/i2cp_spec.html @@ -1,7 +1,7 @@ {% extends "_layout.html" %} {% block title %}I2CP Specification{% endblock %} {% block content %} -Updated June 2013, current as of router version 0.9.6 +Updated November 2013, current as of router version 0.9.9

I2P Control Protocol (I2CP) Specification

Overview

@@ -698,10 +698,68 @@ guaranteed failed. The size Integer specifies the size of the available message and is only relevant for status = 0. Even though guaranteed is unimplemented, (best effort is the only service), the current router implementation uses the guaranteed status codes, not the best effort codes. -As of router version 0.9.5, additional status codes are defined. +As of router version 0.9.5, additional status codes are defined, +however they are not necessarily implemented. See the MessageStatusMessage Javadocs for details. +All status codes: + +
Status CodeAs Of ReleaseNameDescription +
0 AvailableFor incoming messages only. + The included size is the size in bytes of the available message. + This is unused in "fast receive" mode, which is the default as of release 0.9.4. + All other status codes below are for outgoing messages. +
1 AcceptedOutgoing message accepted by the local router for delivery. + The included nonce matches the nonce in the + Send Message Message, and the included Message ID + will be used for subsequent success or failure notification. +
2 Best Effort SuccessProbable success (unused) +
3 Best Effort FailureProbable failure +
4 Guaranteed SuccessProbable success +
5 Guaranteed FailureGeneric failure, specific cause unknown. + May not really be a guaranteed failure. +
60.9.5Local SuccessLocal delivery successful. + The destination was another client on the same router. +
70.9.5Local FailureLocal delivery failure. + The destination was another client on the same router. +
80.9.5Router FailureThe local router is not ready, has shut down, + or has major problems. + This is a guaranteed failure. +
90.9.5Network FailureThe local computer apparently has no network connectivity at all. + This is a guaranteed failure. +
100.9.5Bad SessionThe I2CP session is invalid or closed. + This is a guaranteed failure. +
110.9.5Bad MessageThe message payload is invalid or zero-length or too big. + This is a guaranteed failure. +
120.9.5Bad OptionsSomething is invalid in the message options, + or the expiration is in the past or too far in the future. + This is a guaranteed failure. +
130.9.5Overflow FailureSome queue or buffer in the router is full and the message was dropped. + This is a guaranteed failure. +
140.9.5Message ExpiredThe message expired before it could be sent. + This is a guaranteed failure. +
150.9.5Bad Local LeasesetThe client has not yet signed a leaseset, or the local keys + are invalid, or it has expired, or it does not have any tunnels in it. + This is a guaranteed failure. +
160.9.5No Local TunnelsLocal problems. No outbound tunnel to send through, + or no inbound tunnel if a reply is required. + This is a guaranteed failure. +
170.9.5Unsupported EncryptionThe certs or options in the destination or its leaseset + indicate that it uses an encryption format that we don't support, so we can't talk to it. + This is a guaranteed failure. +
180.9.5Bad DestinationSomething is wrong with the far-end destination. + Bad format, unsupported options, certificates, etc. + This is a guaranteed failure. +
190.9.5Bad LeasesetWe got the far-end leaseset but something strange is wrong with it. + Unsupported options or certificates, no tunnels, etc. + This is a guaranteed failure. +
200.9.5Expired LeasesetWe got the far-end leaseset but it's expired and we can't get a new one. + This is a guaranteed failure. +
210.9.5No LeasesetCould not find the far-end leaseset. + This is a common failure, equivalent to a DNS lookup failure. + This is a guaranteed failure. +

When status = 1 (accepted), the nonce matches the nonce in the @@ -734,6 +792,9 @@ message id specified in the ReceiveMessageBeginMessage is invalid or incorrect, the router may simply not reply, or it may send back a DisconnectMessage.

+

+This is unused in "fast receive" mode, which is the default as of release 0.9.4. +

@@ -757,6 +818,9 @@ Sent from Client to Router. The ReceiveMessageBeginMessage is sent after a MessagePayloadMessage fully delivers a message's payload.

+

+This is unused in "fast receive" mode, which is the default as of release 0.9.4. +