Well, the advantage of what we have is that it is based on well known, well studied algorithms which are known to work in practice. So any replacement would have to either be some means of enforcing the existing algorithms (which would require being able to identify local requests, which is bad... unless they are premix routed before becoming local requests), or something that had been *extensively* simulated and proven to work.
Personally I rather like the old Minimum Request Interval algorithm, but this is by no means well enough studied or simulated to work. On Tue, Apr 11, 2006 at 08:12:20PM +0100, Michael Rogers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Matthew Toseland wrote: > > Is this the best option? It is perhaps closest to "propagate the load > > back to the originator"? > > One disadvantage is that if the originator isn't well behaved, load > limiting won't work - a selfish originator might refuse to throttle > back. TCP has the same problem but it's not designed for such an > adversarial environment. > > Unfortunately this boils down to the problem of encouraging users to > contribute as many resources as they use, which is a can of worms. I've > been doing some work in this area and I think the problem can be solved > in a way that doesn't compromise anonymity or decentralisation, but it > requires some additional mechanisms for measuring the level of service > provided by your peers and allocating resources to them accordingly. > > This is a robustness issue as well as a performance issue, because > without load limiting a small number of senders might be able to flood > the network. > > Cheers, > Michael -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20060411/f66aae29/attachment.pgp>
