Document peer selection fast tier slicing #36
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Opened 7 years ago
Last modified 5 years ago
#1154opendefect
Document peer selection fast tier slicing
Reported by:zzzOwned 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
comment:2 Changed 5 years ago by str4d
Milestone:
→ soonStatus:new →
open
comment:1 Changed 7 years ago by zzz
Cc:str4d added
details:
zzz, http://i2p-projekt.i2p/en/docs/tunnels/implementation#ordering vs net.i2p.router.peermanager.ProfileOrganizer?.getSubTier() - I think there is a discrepancy?
Title: Tunnel Implementation - I2P (at i2p-projekt.i2p)
Docs:
p = peer hash
k = random key
d = XOR(H(p+k), k)
Code:
d = H(p+k[4]) & 0x03
Oh, not even that, it's:
d = H(p+k[4])[0] & 0x03
IIUC that uses the first two bits of the hash as the subtier identifier
Oh wait, i'm looking at the wrong bit, sorry
Okay, I see:
The web docs don't appear to specify that the fast tier is split into subtiers
That's why I was looking at the closest part
And the peer ordering specified on the website only is relevant for middle nodes on client tunnels (vs. all nodes for expl)