IPv6 Over Social Networks
An anonymous reader writes "A new RFC has been published this morning to significantly speed the deployment of IPv6. With IPv6 over Social Network (IPoSN), '[e]very user is a router with at least one loopback interface,' and 'Every friend or connection between users will be used as a point-to-point link.' It is noted that latency on the network can be very high, though."
http://cr.yp.to/djbdns/ipv6mess.html
Was there something wrong with coming up with an addressing scheme that DIDN'T involve hex?
For example, go 64bit and use 16bit "hextets" -- 512.512.512.512. With that scheme you would have full backwards compatibility by using good old standard CIDR. If someone owned 1.255.255.255/8 today, with the switch they would still have that allotment, but we would now have 1.511.511.511/8 available as well. Am I missing something really obvious here?
For that matter, if we REALLY needed 128bit, go with either 32bit "somethingtets" -- 1024.1024.1024.1024...
Again, I would really like a network engineer / programmer to explain why this wouldn't work.
Who had the bright idea that we had to use hex for ipv6 AND have it not be backwards compatible.
From the people I talk to, the biggest reason they haven't gone ipv6 on their home networks is "because then I have to think in hex", with the secondary reason being "there is nothing available on ipv6 that isn't on ipv4 anyway".
Thanks,
-- Brian
-- http://anonet.org -- The internet the way it was meant to be. Check it out, you may be surprised.