Opened 6 years ago

Last modified 4 years ago

#1154 open defect

Document peer selection fast tier slicing

Reported by: zzz Owned by: zzz
Priority: minor Milestone: soon
Component: www/i2p Version: 0.9.9
Keywords: docs Cc: str4d
Parent Tickets: Sensitive: no

Description

Slicing of the fast tier slicing into 4 parts for slower churn is not documented on the website, according to str4d. From discussion during CCC.

Subtickets

Change History (2)

comment:1 Changed 5 years ago by zzz

Cc: str4d added

details:

<str4d> zzz, http://i2p-projekt.i2p/en/docs/tunnels/implementation#ordering vs net.i2p.router.peermanager.ProfileOrganizer?.getSubTier() - I think there is a discrepancy?
<iRelay> Title: Tunnel Implementation - I2P (at i2p-projekt.i2p)
<str4d> Docs:
<str4d> p = peer hash
<str4d> k = random key
<str4d> d = XOR(H(p+k), k)
<str4d> Code:
<str4d> d = H(p+k[4]) & 0x03
<str4d> Oh, not even that, it's:
<str4d> d = H(p+k[4])[0] & 0x03
<str4d> IIUC that uses the first two bits of the hash as the subtier identifier
<str4d> Oh wait, i'm looking at the wrong bit, sorry
<str4d> Okay, I see:
<str4d> The web docs don't appear to specify that the fast tier is split into subtiers
<str4d> That's why I was looking at the closest part
<str4d> And the peer ordering specified on the website only is relevant for middle nodes on client tunnels (vs. all nodes for expl)

comment:2 Changed 4 years ago by str4d

Milestone: soon
Status: newopen
Note: See TracTickets for help on using tickets.