I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

link typo

Browse Source
This commit is contained in:
zzz
2018-08-08 18:32:32 +00:00
parent d0d2118dfa
commit a9c20d3f63
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/spec/proposals/123-new-netdb-entries.rst
View File

@ -2,10 +2,10 @@
New netDB Entries New netDB Entries
================= =================
.. meta:: .. meta::
:author: zzz :author: zzz, orignal, str4d
:created: 2016-01-16 :created: 2016-01-16
:thread: http://zzz.i2p/topics/2051 :thread: http://zzz.i2p/topics/2051
:lastupdated: 2018-08-06 :lastupdated: 2018-08-08
:status: Open :status: Open
:supercedes: 110, 120, 121, 122 :supercedes: 110, 120, 121, 122
@ -386,7 +386,7 @@ publishers for the top-level or intermediate-level Meta LSes on failure.
Mix-and-match leasesets where leases from multiple routers are combined, signed, and published Mix-and-match leasesets where leases from multiple routers are combined, signed, and published
in a single leaseset is documented in proposal 140, "invisible multihoming". in a single leaseset is documented in proposal 140, "invisible multihoming".
This proposal is untenable as written, because streaming connections would not be This proposal is untenable as written, because streaming connections would not be
"sticky" to a single router, see http://zzz.ip2/topics/2335 . "sticky" to a single router, see http://zzz.i2p/topics/2335 .
The back-end protocol, and interaction with router and client internals, would be The back-end protocol, and interaction with router and client internals, would be
quite complex for invisible multihoming. quite complex for invisible multihoming.