On Sun, Feb 06, 2011 at 11:44:39PM +0000, John Case wrote:
On Sat, 5 Feb 2011, coderman wrote:
Re Mesh - I have been mucking with it for many years and reading about it even longer. Seems solutions for getting what appears a group that Fun fact: a local /64 is fully enough to encode lat/long/alt (24, 24, 16 bit) with about 2 m resolution....
ORCHID address space is perfect for this type of thing, and there are particular extensions well suited to this. [0][1]
Why, in (egyption) situations like this, would you want location data embedded in your addressing scheme ?
Location is only available in point-to-point connections, of course you're free to run remixing layers on top of that infrastructure.
It seems like one would do hard work to ensure such encapsulation was NOT happening...
If you want to do cut-through at relativistic speed there are not many options left. If you want to obscure origins, use anonymization implemented in higher layers.
Or is this just a scheme for fair and reasonable address allocation in an anarchy to avoid collisions ?
That's one of the side effects: it cuts out the middlemen like IANA, RIRs and LIRs. Anyone can compute one's geographical positions either from global or local references, and you're free to refuse peering from position fakers. Faking disturbances takes ownership of the local loop, and is easily checked by referencing global beakons. -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE