In my area it is only possible to forward mail for 6 months. It is certianly not possible to forward mail from an address I had 15 years ago.
The email is to a no longer existing ISP, using their domain of course.
The phone number is likely in use by someone else by now, and with the wrong area code in any case.
I would probably have to find some proof that I lived at that address 15 years ago and present it to RIPE. But why would I bother? I have no use for that class C. Big companies that waste a class A can not be bothered, so why would I spent time and expense to release a class C?
Some say I could sell it, but that is clearly against the rules for the allocatement. So not really.
I just checked. My 1994 class C is still allocated to me. I have no idea how to regain control over it though as every single contact detail, except my name, is outdated by 15 years.
It was never used on the public internet. But back then they said you should get one for your local lan. This was before everyone started doing 192.168.x.y. So I applied for a class C and got it.
Even if I did manage to get RIPE to correct the contact details, I do not know any ISP who would advertize it for me. So this class C is part of the dead IPv4 space that will probably never get used.
So, what was the year before 1? If you say -1 then clearly you cannot count unless you accept that there is a numbering error.
Before the first year was the first year before christ (BC). There was no year that was neither before christ nor a year of the lord (no year 0). There are no negative years, no year -1. A count of years can never be negative.
The ONLY argument for the claim that x000 does not belong to the Mill place value is that there was no zero.
No. The argument is that the year number is a numbering (count) of the years of the lord. We are currently in the 2010th year of the lord. A year has only passed when the year is done, so in a little less than a month we will have done 2010 years since the start (time 0).
The lack of a year zero was a mistake.
No at all. There simply can not be a year zero when you use the counting method (the first year, the second year etc, the language does not allow it). So it is not a mistake, just you that do not understand this basic mathematical reality. The calendar does indeed have a zero, which is the start of the first year. You think the year number is the time passed when it is actually a naming. We also have no day zero in the month or a month zero in year and so on. For the same reason.
So again, what is year 1000 - 2000? Show me how well you can count.
Year 1001 BC.
The first 1000 years back gets you 1 BC. Then subtract 1000 more and you end up at 1001 BC.
If you think this is much harder than simple arithmetic, consider that it is so with everything in the calendar. You can also not do simple arithmetic to calculate January 10 - 20 days.
So, back at you... Why would you want to start the 21st century after ~2000.8 years AND make the naming sound metric, but not be metric?
Because I can count. The first year is the FIRST year. Not the ZERO year.
Just like a ruler, like another put it. The ruler might start at zero, but the first cm is the first cm. Not the number zero cm.
This incidentially also solves your.8 year issue. We count the number of years, not the length of the years.
With risk of repeating myself: The year 1 startet at time 0 and ended at time 1. The 2000th year started at time 1999 and ended at time 2000. The 2001st year started at time 2000. Which is why the new millenium came to pass at the same time as the 2001st year.
216.34.181.48::249.183.23.56::38.245.1.59. And oddly enough, that's actually a shorter address than the IPv6 one you're going to get instead.
No it is not. The longest address you risk being assigned is of the form 1234:5678:9ABC:DEF0::1 (*) which is 22 characters. Your proposal is up to 49 characters.
(*) Remember you decide the last 64 bit of the address (the host part). You can make it just a::1 as in my example. You can also make the host part a maximum of 20 characters including the separators if it suits you, but that is your choice.
If you start calling this the 20th century just because the year is 20xx you will not be understood correctly.
Nobody is arguing that this is the 20th century, the argument was that the 21st century started in 2000, not 2001
Why would you want to start the 21st century after only 1999 years have passed? For some reason you understand that century YY does not equal year YYxx. But you don't understand the very same reasoning when counting years instead of centuries. The _first_ year in any of "decade, centuries, millenia" is always of the form xxx1. This follows easily because the very first year was indeed year 1 of the decade, century and millenia.
Configure your home router to pass the port for whatever service you want to access from work to the system that can deal with it at home. Connect to that address using that port.
This is where the trouble begins. You can do this today because it is _your_ router doing the NAT. With no more IPv4 available, you will be sharing your IPv4 with your neighbours. This means carrier NAT. How do you program your ISPs router? You don't.
This is no year zero, nor is there a year 1, 2, 3, or any of the first few hundred.
At the risk of exposing myself as a pseudo-intellectual... if there is no year zero, then how should I refer to the year that was in progress 2010 years before today?
That being the case, we as a culture have also decided that decades start a year x0, centuries start at x00, and millenniums start at x000.
No we have not. You will have a very hard time relating to historic dates if you think so. Ever wondered why we are currently in the 21st century and not the 20th? Because the first century was not the number 0 century, as you would have it. The same way, the first year was not the number 0 year, the first decade was not the number 0 decade and the first millenia was not the number 0 millenia.
Just because uneducated people have a hard time grasping this, does not make it less so. If you start calling this the 20th century just because the year is 20xx you will not be understood correctly.
That said, because the general public seems to be quite uneducated about our calendar system, the mainstream media must be careful when the exact years of the boundaries of decades, centuries and millenias is important. Books for professionals can assume the reader knows the calendar.
That would be 63.254.25.0.69.69.0.3.2.0.248.255.254.33.103.207 using your scheme which is horrible. Is also leaves out the most useful compression feature, so you can write 3ffe:1900::/32 instead of 63.254.25.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0/32. Just counting out the correct numbers of.0 is horrible.
Practical real life IPv6 addresses often use compression: ipv6.l.google.com has IPv6 address 2a00:1450:8005::63, ipv6.myip.dk has IPv6 address 2001:470:27:f9::2, ipv6.net has IPv6 address 2a00:1188:5:2::8. If you care about your address you can make it short, since the last 64 bits is yours to decide.
The weather institute had the most powerful supercomputer in this (small) country. It was not that old, but it was time to upgrade. The new supercomputer was now the fastest supercomputer and the old one became the second fastest.
What happened to the second fastest supercomputer in the country? It was scraped. They could not afford to keep running it due to cost of powering it. They could not sell or give it away, because the economics of it did not add up. Anyone needing such computing power were better off getting new equipment that would do more for the amount of electricity needed.
This is still up since nobody has yet tried to get such a car registered. At least for Denmark the answer is very likely that the car can not have an ICE at all to be tax exempt.
It will not mater if it is automatic or not. The Tesla will (does) qualify. The Volt (or Ampere) will not qualify unless you remove the ICE completely.
Are you betting on the ipv4 space usage magically decreasing ( right when everyone will start freaking out about getting their last allocations )?
No no, there is always more to be found. That link of yours only show the _known_ reserves of addresses. They continue to find new fields of IP addresses and existing fields continue to find more than initially expected. This "peak IP" is never going to happen and you know it!
How does imaging it not work? You would get a nice copy of the data on the drive, sure it is encrypted but so what. It gives you something to attack without risking loss of data.
I hope I do not have to explain how "attacking" something encrypted with say AES 256 is a waste of time?
If the key is lost, the data is garbage and will stay garbage for the rest of the lifetime of this solar system.
Large scale or ISP wide NAT is part of the solution. It will not "save" IPv4, whatever that means. It will make it possible to transition to IPv6 and still access all the old sites, that have not yet made the transition.
It is not really important that slashdot.org is still IPv4 only. You can access it just fine. And slashdot.org has no need to access you.
You use IPv6 in all the cases where you wanted that nice static IPv4 address before: When running peer to peer software. Setting up your small hobby server. Using direct peer to peer VoIP. And so on.
All the consumer ISPs will transition soon enough during the next few years. We will fairly quickly be able to assume consumers will in fact be able to access IPv6 only sites. For the next 10 years you can also assume consumers will be able to access IPv4 only sites - is anyone really surprised by that?
If all your gaming friends got IPv6, playing on your private IPv6 only game server - what do you care that some backwards dialup only ISP, in a country you never heard of, still is IPv4 only?
They would image it first. Heck if need be take the platters out to prevent this.
They image any device before they mess with it, yes even a phone.
Imaging it wont work. The data on the platers is encrypted. The key to the encryption is known only to the chip. You only know the passphrase that unlocks the real key inside the chip. It is very hard to crack a tamperproof chip. As soon the chip decides to erase the key from chip memory the data is garbage to everyone.
The system does not need to be buildin to the harddrive. It can be in the controller or even just a special purpose encryption chip the OS has to go through to get the key.
This already exists. It is a requirement for military applications. You can not destroy physical data , but you can choose to lose the key. And that is just as effective.
This is why you need hardware encryption with a selfdestruct mechanism.
A software solution can not do this. They will mirror your disk and work on the mirror. But a self contained chip can be made tamperproof and such that enough mistyped passwords or just the special self destruct passwords makes the chip irreversible lose the key.
After the selfdestruct event happened you just claim they caused it. That you gave the correct password the first time they asked. Even if you end up getting convicted on giving the selfdestruct password that might be less than what they are really after.
A variant of this scheme is to store your password on a key device with the same properties. Someone could make an application for your phone that did this. It would not be as secure, as they could be mirroring your phone, but likely they would catch on to that too late.
What will likely happen is that the price of an IPv4 address will rise (it hasn't). As it does, people holding blocks of ipv4 will release them...
No as the price for IPv4 increases IPv6 will get its killer application: It will provide something for free that has a real cost in the v4 world. It will get the ball rolling and soon enough nobody cares about IPv4.
Luckily the big ISPs have already seen this and have IPv6 trials going. In a year it will be an option for everyone.
Weren't all addresses supposed to be gone by now? That's problem with doomsday predictions IPv4, warming, God, it never happens as scheduled and then people just ignore you next time you start predicting. If we were more temperate about our predictions, people wouldn't dismiss them as more of the same "sky-is-falling" crapola.
No. That is the problem with people getting the warning early. You simply can't handle it. We said in 10 years, but now you keep saying each year, why has it not happened yet?!. Well duh, because the 10 years not over yet!.
The actual date is May 2011. This should be a short enough timespan that even normals can figure out it is going to happen real soon now.
Slashdot Mirror
In my area it is only possible to forward mail for 6 months. It is certianly not possible to forward mail from an address I had 15 years ago.
The email is to a no longer existing ISP, using their domain of course.
The phone number is likely in use by someone else by now, and with the wrong area code in any case.
I would probably have to find some proof that I lived at that address 15 years ago and present it to RIPE. But why would I bother? I have no use for that class C. Big companies that waste a class A can not be bothered, so why would I spent time and expense to release a class C?
Some say I could sell it, but that is clearly against the rules for the allocatement. So not really.
Lets just move to IPv6 and forget about it.
I just checked. My 1994 class C is still allocated to me. I have no idea how to regain control over it though as every single contact detail, except my name, is outdated by 15 years.
It was never used on the public internet. But back then they said you should get one for your local lan. This was before everyone started doing 192.168.x.y. So I applied for a class C and got it.
Even if I did manage to get RIPE to correct the contact details, I do not know any ISP who would advertize it for me. So this class C is part of the dead IPv4 space that will probably never get used.
So, what was the year before 1? If you say -1 then clearly you cannot count unless you accept that there is a numbering error.
Before the first year was the first year before christ (BC). There was no year that was neither before christ nor a year of the lord (no year 0). There are no negative years, no year -1. A count of years can never be negative.
The ONLY argument for the claim that x000 does not belong to the Mill place value is that there was no zero.
No. The argument is that the year number is a numbering (count) of the years of the lord. We are currently in the 2010th year of the lord. A year has only passed when the year is done, so in a little less than a month we will have done 2010 years since the start (time 0).
The lack of a year zero was a mistake.
No at all. There simply can not be a year zero when you use the counting method (the first year, the second year etc, the language does not allow it). So it is not a mistake, just you that do not understand this basic mathematical reality. The calendar does indeed have a zero, which is the start of the first year. You think the year number is the time passed when it is actually a naming. We also have no day zero in the month or a month zero in year and so on. For the same reason.
So again, what is year 1000 - 2000? Show me how well you can count.
Year 1001 BC.
The first 1000 years back gets you 1 BC. Then subtract 1000 more and you end up at 1001 BC.
If you think this is much harder than simple arithmetic, consider that it is so with everything in the calendar. You can also not do simple arithmetic to calculate January 10 - 20 days.
So, back at you... Why would you want to start the 21st century after ~2000.8 years AND make the naming sound metric, but not be metric?
Because I can count. The first year is the FIRST year. Not the ZERO year.
Just like a ruler, like another put it. The ruler might start at zero, but the first cm is the first cm. Not the number zero cm.
This incidentially also solves your .8 year issue. We count the number of years, not the length of the years.
With risk of repeating myself: The year 1 startet at time 0 and ended at time 1. The 2000th year started at time 1999 and ended at time 2000. The 2001st year started at time 2000. Which is why the new millenium came to pass at the same time as the 2001st year.
So to upgrade to an IP4 variant, *some* hardware needs to be upgraded. To upgrade to IPv6, *all* hardware will.
False. Much hardware can already do IPv6 and yet more can be flashed to do IPv6. *All* modern operatingsystems come with IPv6 enabled by default.
216.34.181.48::249.183.23.56::38.245.1.59. And oddly enough, that's actually a shorter address than the IPv6 one you're going to get instead.
No it is not. The longest address you risk being assigned is of the form 1234:5678:9ABC:DEF0::1 (*) which is 22 characters. Your proposal is up to 49 characters.
(*) Remember you decide the last 64 bit of the address (the host part). You can make it just a ::1 as in my example. You can also make the host part a maximum of 20 characters including the separators if it suits you, but that is your choice.
If you start calling this the 20th century just because the year is 20xx you will not be understood correctly.
Nobody is arguing that this is the 20th century, the argument was that the 21st century started in 2000, not 2001
Why would you want to start the 21st century after only 1999 years have passed? For some reason you understand that century YY does not equal year YYxx. But you don't understand the very same reasoning when counting years instead of centuries. The _first_ year in any of "decade, centuries, millenia" is always of the form xxx1. This follows easily because the very first year was indeed year 1 of the decade, century and millenia.
Configure your home router to pass the port for whatever service you want to access from work to the system that can deal with it at home. Connect to that address using that port.
This is where the trouble begins. You can do this today because it is _your_ router doing the NAT. With no more IPv4 available, you will be sharing your IPv4 with your neighbours. This means carrier NAT. How do you program your ISPs router? You don't.
This is no year zero, nor is there a year 1, 2, 3, or any of the first few hundred.
At the risk of exposing myself as a pseudo-intellectual... if there is no year zero, then how should I refer to the year that was in progress 2010 years before today?
Year 1 BC.
That being the case, we as a culture have also decided that decades start a year x0, centuries start at x00, and millenniums start at x000.
No we have not. You will have a very hard time relating to historic dates if you think so. Ever wondered why we are currently in the 21st century and not the 20th? Because the first century was not the number 0 century, as you would have it. The same way, the first year was not the number 0 year, the first decade was not the number 0 decade and the first millenia was not the number 0 millenia.
Just because uneducated people have a hard time grasping this, does not make it less so. If you start calling this the 20th century just because the year is 20xx you will not be understood correctly.
That said, because the general public seems to be quite uneducated about our calendar system, the mainstream media must be careful when the exact years of the boundaries of decades, centuries and millenias is important. Books for professionals can assume the reader knows the calendar.
3ffe:1900:4545:3:200:f8ff:fe21:67cf
That would be 63.254.25.0.69.69.0.3.2.0.248.255.254.33.103.207 using your scheme which is horrible. Is also leaves out the most useful compression feature, so you can write 3ffe:1900::/32 instead of 63.254.25.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0/32. Just counting out the correct numbers of .0 is horrible.
Practical real life IPv6 addresses often use compression: ipv6.l.google.com has IPv6 address 2a00:1450:8005::63, ipv6.myip.dk has IPv6 address 2001:470:27:f9::2, ipv6.net has IPv6 address 2a00:1188:5:2::8. If you care about your address you can make it short, since the last 64 bits is yours to decide.
... since the unexpected end of the century in '99.
Quite unexpected considering centuries start at year 1 and end in year 100.
The weather institute had the most powerful supercomputer in this (small) country. It was not that old, but it was time to upgrade. The new supercomputer was now the fastest supercomputer and the old one became the second fastest.
What happened to the second fastest supercomputer in the country? It was scraped. They could not afford to keep running it due to cost of powering it. They could not sell or give it away, because the economics of it did not add up. Anyone needing such computing power were better off getting new equipment that would do more for the amount of electricity needed.
This is still up since nobody has yet tried to get such a car registered. At least for Denmark the answer is very likely that the car can not have an ICE at all to be tax exempt.
It will not mater if it is automatic or not. The Tesla will (does) qualify. The Volt (or Ampere) will not qualify unless you remove the ICE completely.
Only if you have to brute force it. In a great many cases a dictionary attack works, why else would anyone try them?
Do you think a chip would select a dictionary word for a key? Or would it more likely select 256 completely random bits?
Are you betting on the ipv4 space usage magically decreasing ( right when everyone will start freaking out about getting their last allocations )?
No no, there is always more to be found. That link of yours only show the _known_ reserves of addresses. They continue to find new fields of IP addresses and existing fields continue to find more than initially expected. This "peak IP" is never going to happen and you know it!
How does imaging it not work?
You would get a nice copy of the data on the drive, sure it is encrypted but so what. It gives you something to attack without risking loss of data.
I hope I do not have to explain how "attacking" something encrypted with say AES 256 is a waste of time?
If the key is lost, the data is garbage and will stay garbage for the rest of the lifetime of this solar system.
Except for all the people still on XP, which has no native IPv6 support...
Has too. You just need to enable it: http://ipv6int.net/systems/windows_xp-ipv6.html
Large scale or ISP wide NAT is part of the solution. It will not "save" IPv4, whatever that means. It will make it possible to transition to IPv6 and still access all the old sites, that have not yet made the transition.
It is not really important that slashdot.org is still IPv4 only. You can access it just fine. And slashdot.org has no need to access you.
You use IPv6 in all the cases where you wanted that nice static IPv4 address before: When running peer to peer software. Setting up your small hobby server. Using direct peer to peer VoIP. And so on.
All the consumer ISPs will transition soon enough during the next few years. We will fairly quickly be able to assume consumers will in fact be able to access IPv6 only sites. For the next 10 years you can also assume consumers will be able to access IPv4 only sites - is anyone really surprised by that?
If all your gaming friends got IPv6, playing on your private IPv6 only game server - what do you care that some backwards dialup only ISP, in a country you never heard of, still is IPv4 only?
They would image it first. Heck if need be take the platters out to prevent this.
They image any device before they mess with it, yes even a phone.
Imaging it wont work. The data on the platers is encrypted. The key to the encryption is known only to the chip. You only know the passphrase that unlocks the real key inside the chip. It is very hard to crack a tamperproof chip. As soon the chip decides to erase the key from chip memory the data is garbage to everyone.
The system does not need to be buildin to the harddrive. It can be in the controller or even just a special purpose encryption chip the OS has to go through to get the key.
This already exists. It is a requirement for military applications. You can not destroy physical data , but you can choose to lose the key. And that is just as effective.
This is why you need hardware encryption with a selfdestruct mechanism.
A software solution can not do this. They will mirror your disk and work on the mirror. But a self contained chip can be made tamperproof and such that enough mistyped passwords or just the special self destruct passwords makes the chip irreversible lose the key.
After the selfdestruct event happened you just claim they caused it. That you gave the correct password the first time they asked. Even if you end up getting convicted on giving the selfdestruct password that might be less than what they are really after.
A variant of this scheme is to store your password on a key device with the same properties. Someone could make an application for your phone that did this. It would not be as secure, as they could be mirroring your phone, but likely they would catch on to that too late.
You just need to sign up with Comcast: http://www.comcast6.net/
They are only running trials at this exact moment, but they should have general IPv6 availability soon enough.
There actually isn't any need for NAT with IPV6. Each public address will have 64000 addresses available to do the equivilent of nat'ing.
Wrong. You will have at least 18446744073709551616 (2^64) addresses available for your home network.
What will likely happen is that the price of an IPv4 address will rise (it hasn't). As it does, people holding blocks of ipv4 will release them...
No as the price for IPv4 increases IPv6 will get its killer application: It will provide something for free that has a real cost in the v4 world. It will get the ball rolling and soon enough nobody cares about IPv4.
Luckily the big ISPs have already seen this and have IPv6 trials going. In a year it will be an option for everyone.
Weren't all addresses supposed to be gone by now? That's problem with doomsday predictions IPv4, warming, God, it never happens as scheduled and then people just ignore you next time you start predicting. If we were more temperate about our predictions, people wouldn't dismiss them as more of the same "sky-is-falling" crapola.
No. That is the problem with people getting the warning early. You simply can't handle it. We said in 10 years, but now you keep saying each year, why has it not happened yet?!. Well duh, because the 10 years not over yet!.
The actual date is May 2011. This should be a short enough timespan that even normals can figure out it is going to happen real soon now.