1 |
On 03/08/2013 07:50 PM, Kevin Chadwick wrote: |
2 |
>> Unfortunately, your logic is flawed. |
3 |
>> |
4 |
>> Where would you put the additional bits of address? |
5 |
>> |
6 |
>> That would involve rewriting the IP Header. |
7 |
>> |
8 |
> |
9 |
> Your assumption that I do not know that is flawed. I did a review of |
10 |
> ipv6 before it was released and determined ipv4 to be superior then. |
11 |
> That was before I was shown some of the bad sides more recently. |
12 |
> |
13 |
>> And while we're at it, why not *totally* remake IP based on decades of |
14 |
>> observation & experience? |
15 |
>> |
16 |
> |
17 |
> Who's observations and who's experience. Not everyones that's for damn |
18 |
> sure. |
19 |
|
20 |
This is why the IETF exists, to allow vendors and engineers with field |
21 |
knowledge to argue and debate until they come up with something that |
22 |
most of them can agree on. IPv6 is what came out of that process. |
23 |
|
24 |
I'm not going to say IPv6 doesn't have flaws...but it's certainly a lot |
25 |
better than IPv4, and features it adds (even beyond address space |
26 |
expansion) are very nice. |
27 |
|
28 |
> |
29 |
>> Hence, IPv6. |
30 |
> |
31 |
> Lookup ipvshit |
32 |
> |
33 |
> I'll give you a hint. |
34 |
> |
35 |
> The guy who wrote most of the pf firewall that MAC OSX now uses as well |
36 |
> as QNX, the latest version originating from OpenBSD and being far better |
37 |
> than iptables has bought up lots of ipv4 just to stay away from ipvshit. |
38 |
> |
39 |
|
40 |
Tried searching for it. You're going to have to provide some useful |
41 |
direct reference, because a basic search wasn't very illuminating. |