-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> This is exactly the problem I was pointing out with TimedOut. I think that
> the way that nodes will be configured is that you will have a few
> references to your college network (say 3) and then a few to other
> networks (freenet developer's network, Bill's Super Freenet Cluster, and
> some place in Finland). If it's in the college network, you don't want it
> all of your HTL to get sucked up by the nation of Finland. If it's in the
> Internet somewhere, you don't want your HTL to get sucked up by the
> college network. The easy, simple, and very workable solution to this is
> to have some hops go to each of the nodes you know about. That way each
> network gets a chance to provide the data within a given HTL. The trick,
> of course, is coming up with an algorithm that doesn't grow too fast. My
> last proposal was to divide the HTL by the number of nodes it will be sent
> to. Also, a separate Depth field can be set to specify the maximum number
> of references to use. That way the growth of messages and how long they
> take is carefully controlled and mathematically determined to be a known
> quantity.
Are we talking about sending out multiple requests for the same key? If
so, could we pick one node, then select the second and third and so on,
but rejecting the additional nodes if they have the same subnet in the IP
field? How about IPv6 concerns?
Scott
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4+2MgpXyM95IyRhURAl/EAJ9QdSnL4+ScFfwAo40OaGXcg3m7GQCeL+s+
rgnZoIbYKEquKxmzw9CTydo=
=BYb3
-----END PGP SIGNATURE-----
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
