|
|
|
| Authored by: Anonymous on Thursday, January 17 2013 @ 05:59 PM EST |
Don't confuse "is entitled to" with "has assigned" with v6.
And don't confuse the number of v4 addresses with anything relevant.
Since not all v6 addresses are assigned, the number of v6 address is "close
enough to infinity for all forseeable practical purposes", and blocks are
passed out as needed, it doesn't matter who has what at the moment. When MIT
needs more addresses, it will request them--and they will be available for
assignment and they will be assigned to MIT. And when King Mbofuso Elementary
School in Lesotho needs a block of addresses, it also will request them--and get
them just as quickly. (More likely, KMES will simply get a crate courtesy of
OLPC, and the issue will not arise.)[ Reply to This | Parent | # ]
|
- The Problem Is - Authored by: Anonymous on Thursday, January 17 2013 @ 06:11 PM EST
| |
| Authored by: Anonymous on Thursday, January 17 2013 @ 06:10 PM EST |
I was thinking along the lines of IPv6, not IPv4. So I definitely seriously
erred on misreading that point.
With regards the "gets as many addresses
as the whole continent of Africa" - that would be a factor in IPv4 addresses.
However, it wouldn't be a factor in IPv6.
IPv4 carries 2^32
number of addresses. That's only 4.2 billion addresses which would certainly
not cover 1 address per person on the planet. And that's assuming big blocks of
addresses weren't unavailable.
So yea: I can see a problem now. To put
what I see in perspective:
While MIT could easily afford to convert to IPv6,
they continue to hold a large section of IPv4 addresses instead of releasing
them for consumption by others who aren't necessarily in the position of being
able to afford to convert to IPv6.
On that note: I just don't see that as a
particularly huge problem.
Upgrade the OS software governing the Internet
handling in Africa to handle both IPv4 and IPv6.
Assign any new
computing devices the IPv6 protocol.
It can't really be that difficult to
get an up-to-date copy of the Linux kernel and dump it onto the hardware
responsible for routing and such. And given how easy it would be to parse the
difference between an IPv4 and IPv6 address, I really don't see it being that
much of an issue in handling both at the same time.
RAS[ Reply to This | Parent | # ]
|
- The Issue - Authored by: Anonymous on Thursday, January 17 2013 @ 06:19 PM EST
- My mistake: IPv4 vs IPv6 - Authored by: Anonymous on Thursday, January 17 2013 @ 07:07 PM EST
|
|
|
|
