kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Proposal bugfixes

Browse Source
This commit is contained in:
str4d
2017-05-22 10:46:07 +00:00
parent f1d367e0ec
commit 281c4eb1f6
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
i2p2www/spec/proposals/120-meta-leaseset-for-multihoming.rst
View File

@@ -35,7 +35,7 @@ for the LS, but the first stage could be cached for hours.
Specification Specification
============= =============
The meat-LeaseSet would have the following format:: The meta-LeaseSet would have the following format::
- Destination - Destination
- Published Time stamp - Published Time stamp

12
i2p2www/spec/proposals/140-invisible-multihoming.rst
View File

@@ -27,7 +27,7 @@ Motivation
Multihoming is where multiple routers are used to host the same Destination. Multihoming is where multiple routers are used to host the same Destination.
The current way to multihome with I2P is to run the same Destination on each The current way to multihome with I2P is to run the same Destination on each
router independently; the router that gets used by clients at any particular router independently; the router that gets used by clients at any particular
time is the last one to publish a LeaseSet. time is the last one to publish a [LeaseSet]_.
This is a hack and presumably won't work for large websites at scale. Say we had This is a hack and presumably won't work for large websites at scale. Say we had
100 multihoming routers (edges) each with 16 tunnels. That's 1600 LeaseSet 100 multihoming routers (edges) each with 16 tunnels. That's 1600 LeaseSet
@@ -35,8 +35,8 @@ publishes every 10 minutes, or almost 3 per second. The floodfills would get
overwhelmed and throttles would kick in. And that's before we even mention the overwhelmed and throttles would kick in. And that's before we even mention the
lookup traffic. lookup traffic.
[Prop120]_ solves this problem with a meta-LeaseSet, which lists the 100 real [Prop123]_ solves this problem with a meta-LeaseSet, which lists the 100 real
[LeaseSet]_ hashes. A lookup becomes a two-stage process: first looking up the LeaseSet hashes. A lookup becomes a two-stage process: first looking up the
meta-LeaseSet, and then one of the named LeaseSets. This is a good solution to meta-LeaseSet, and then one of the named LeaseSets. This is a good solution to
the lookup traffic issue, but on its own it creates a significant privacy leak: the lookup traffic issue, but on its own it creates a significant privacy leak:
It is possible to determine which multihoming routers are online by monitoring It is possible to determine which multihoming routers are online by monitoring
@@ -254,7 +254,7 @@ modifications:
packet sizes. The maximum feasible LeaseSet size is defined by the MTU of the packet sizes. The maximum feasible LeaseSet size is defined by the MTU of the
underlying transports, and is therefore around 16kB. underlying transports, and is therefore around 16kB.
- Implement [Prop120]_ for tiered LeaseSets. In combination with this proposal, - Implement [Prop123]_ for tiered LeaseSets. In combination with this proposal,
the Destinations for the sub-LeaseSets could be spread across multiple edges, the Destinations for the sub-LeaseSets could be spread across multiple edges,
effectively acting like multiple IP addresses for a clearnet service. effectively acting like multiple IP addresses for a clearnet service.
@@ -280,5 +280,5 @@ References
.. [LeaseSet] .. [LeaseSet]
{{ ctags_url('LeaseSet') }} {{ ctags_url('LeaseSet') }}
.. [Prop120] .. [Prop123]
{{ proposal_url('120') }} {{ proposal_url('123') }}