Opened 6 years ago

Closed 5 years ago

Last modified 4 years ago

#1600 closed enhancement (wontfix)

add "send via slowest tunnel" functionality

Reported by: psi Owned by:
Priority: minor Milestone: undecided
Component: api/i2cp Version: 0.9.20
Keywords: latency, tunnel, profiling Cc: zzz
Parent Tickets: Sensitive: no


Enable applications to send messages via the tunnels that have the higest latency instead of having it sent via the "best" ones.
May be useful for applications that want to have higher latencies like i2pbote.


Change History (3)

comment:1 Changed 6 years ago by zzz

We don't currently have any tunnel-selection capabilities, but we do have a few unused bits in the flags field of the SendMessageExpires? message http://i2p-projekt.i2p/en/docs/spec/i2cp#msg_SendMessageExpires — this would be on a per-packet basis.

OCMOSJ picks both our OB and his IB tunnel, and if necessary, our IB reply tunnel. Far-end picks his OB reply tunnel.

We don't measure per-tunnel latency now.

Client-side now knows nothing about tunnels. Not sure what it needs to know if anything.

On a session basis, some option in the SessionConfig? to say what class of peers to use for all tunnels (say, high-cap or not-failing instead of fast) … instead of a per-packet option… may be a lot easier and more interesting… at the cost perhaps of lower build success.

comment:2 Changed 5 years ago by zzz

Resolution: wontfix
Status: newclosed

On further consideration, this sounds difficult to impossible. If there's something easier, perhaps as I suggested above, or you would like to kick off a discussion, please elaborate in a new thread on zzz.i2p with "Proposal:" in the title.

Note: See TracTickets for help on using tickets.