Which pajeet thought this was a good idea?

>Each device will have a static ipv6 that never changes
Wrong.

and how the fuck would we upgrade EVERYTHING that uses the standard 255.255.255.255 scheme??

you fucking ignorant goat lover

>Each device will have a static ipv6 that never changes
Wrong.

we have the mac address for this

>mac addresses
>static and unchangeable
>unique
>visible outside your local LAN

Found the iplet

Which no starch book is this?

Nice meme, but ipv6 is a privacy nightmare, so I'll stick to ipv4, thanks very much.

That'll only last a short time. Breaking IPv4 was a big deal, so you're going to change it, you may as well go big or go home.
The address space problem is now "solved". The address space is so absurdly large, it should never be a problem for as long as the internet as we know it exists.

>but ipv6 is a privacy nightmare
How so?
tools.ietf.org/html/rfc4941
+ dynamic prefixes

>Nice meme, but ipv6 is a privacy nightmare
Wrong.

There are literally standard extensions designed to help that.
Basically, you periodically generate new addresses from your huge prefix and cycle through them for new connections. They can track you based on your network prefix, but that's basically as bad as you have right now with IPv4 NAT.
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:60:6e:f2:2c:ed brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global dynamic noprefixroute enp3s0
valid_lft 27590sec preferred_lft 27590sec
inet6 xxxx:xxxx:xxxx:xxxx::4/128 scope global dynamic noprefixroute
valid_lft 6080sec preferred_lft 2480sec
inet6 xxxx:xxxx:xxxx:xxxx:29bc:f7b:6013:f677/64 scope global temporary dynamic
valid_lft 6630sec preferred_lft 3030sec
inet6 xxxx:xxxx:xxxx:xxxx:819a:ff16:38b6:3e0f/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6630sec preferred_lft 3030sec
inet6 xxxx:xxxx:xxxx:xxxx:29bc:f7b:6013:f677/64 scope global temporary dynamic
valid_lft 6630sec preferred_lft 3030sec
inet6 xxxx:xxxx:xxxx:xxxx:36b1:91f7:e44f:23d3/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6630sec preferred_lft 3030sec
inet6 fe80::db6d:68e3:1c65:fdd1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Shit's great. Obviously I censored the start of my IPv6 addresses, as they are routable.

>Inb4 he submits this idea, names it IPv5, and gets the Turing award

>4 movies about a network standard

Attached: ip_man.jpg (600x316, 24K)

Based ip man

It tickles my autism that they aren't named 'man ip'

Is this a bot? ;

man 3 ip

for looking up IP in section 3 of the manual.

No, you're just wrong and wilfully ignorant (the worst kind of ignorant), and your bullshit spouting post didn't warrant a more thought through response.

With the story completed, it's only a matter of time until the IT industry catches up to v6.

>They can track you based on your network prefix, but that's basically as bad as you have right now with IPv4 NAT.
networking nup here.
my ISP currenlty gives my router a dynamic IP whenever it restarts. would that still happen with ipv6?

>my ISP currenlty gives my router a dynamic IP whenever it restarts. would that still happen with ipv6?
Most likely due to their existing business model (where they charge more money for a static IP), but it wouldn't strictly be necessary.

The largest German ISP "Telekom" uses dynamic IPv6 prefixes, so the privacy level is identical to IPv4.

Why not just use a name based address? Then you could cut the dns middle man.

Attached: 20180720_222129.jpg (2560x1440, 573K)