>AI slop

File: ipv6.jpg (26.8 KB)

26.8 KB JPG

man I can't wait to never implement this shit

File: based.jpg (112.3 KB)

112.3 KB JPG

ipv6.disable=1
ipv8.disable=1

File: 44331.png (194.3 KB)

194.3 KB PNG

i just don't want jeet or AI slop near anything important

should have named it ipv7 so we'd have ipv6 and ipv7

8 is already reserved.
https://www.iana.org/assignments/version-numbers/version-numbers.xhtml

>>108608394
ChatGPT fail. It should have known 8 was reserved.

>>108608255
Meanwhile, everyone and their uncle is still using Ipv4. Waste of time, anything after 4. I guess some committee somewhere had to look busy.

yay my ipv4 is more valueable right?

File: i.png (12.9 KB)

12.9 KB PNG

>>108608575
https://www.ietf.org/archive/id/draft-wkumari-not-a-draft-24.html

Is it for when people start living in space colonies ?

File: 이미지272.png (59 KB)

59 KB PNG

Thanks but I'll stick with ipv4

>>108608255
watch it getting real life identity tracking on protocol level

While this draft presents a clever architectural thought experiment to avoid the specific compatibility frictions of IPv6, it introduces massive new operational and security complexities for network operators. It is not the future of the internet.
The draft doesn't just propose a larger address space. It attempts to completely overhaul global network management. It proposes replacing DHCP, DNS, NTP, and network authentication with a unified "Zone Server" architecture where every network element requires an OAuth2 JWT token to operate.

It basically would require every Datacenter/ISP to rip out and replace their core routers/switches.

That's simply never happening.

>>108609132
It's for when they put a tiny cellular modem in every device so they can all call home without needing you to connect it to a network.

What a consumer brained retard.

This draft was basically written without any hardware vendors or network operators in mind, it removes all the problems of IPv6 from the consumer side, but places ALL of that added complexity onto the operators, which they're never going to pay for.

What a moron.

Lain predicted this. Let's all love Lain.

>>108608255
>JWT tokens
>JSON Web Token tokens

>>108608255
what happened to ipv7?

>>108609132
>>108609267
IPv6 already has enough addresses for that.
There are so many that if we settled one billion planets with the land area of Earth, there would still be more than one billion addresses per square millimeter of land surface.

>>108608255
use case beyond ip4?

>>108608255
You can tell educational simplification was wrong when they mix layer 7 services in a IP proposal (layer 2)

>>108608255
>>108608344
>>108608394
>>108608575
>>108609132
>>108609769
>>108609798
>>108609831
I don't care about IP-v-whatever.

I want an internet that is immune to age verification, DMCA and censorship.

>>108608255
>Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform.¶
Based, let's doxx every kid on Earth who has ever connected to a roblox server so the Epstein class knows who to rape next!!!

>>108608255
>OAuth2 JWT tokens
didn't even bother reading.

File: IMG_20240426_133226_639.jpg (41.2 KB)

41.2 KB JPG

I have hoarded a lot of ipv4 addresses. When v8 drops, my addresses will be vintage, so I will resell them for thousands of dollars.

>>108608261
/thread
>>108608317
but also /thread

File: 1312098057081.jpg (20.7 KB)

20.7 KB JPG

>address assignment (DHCP8), name resolution (DNS8), time synchronisation (NTP8), telemetry collection (NetLog8), authentication caching (OAuth8), route validation (WHOIS8 resolver), access control enforcement (ACL8), and IPv4/IPv8 translation (XLATE8)
will they have h8 r8 and masturb8

>>108609871
stop noticing, goy

>>108609257
>It basically would require every Datacenter/ISP to rip out and replace their core routers/switches.
Routers and switches can be updated with software, even the optimised offloads done in hardware can be re-programmed sometimes.

I don't get what was wrong with IPv6 though. Router advertisements just work. Don't like the security of shit just working? Then you use something ipsec on a VLAN and all devices not authorised automatically get sandboxed into their own VLAN where they can't play with anything else.

>>108609257
explain the plot of Cinderella in a sentence where each word has to begin with the next letter in the alphabet from A to Z, without repeating any letters

I want to use IPv6 by default, when will they drop the IPv4 support?

File: Screenshot_20260415_202358.png (104.3 KB)

104.3 KB PNG

>>108610206
NAT64 and DHCP Option 108 (https://www.ietf.org/archive/id/draft-link-v6ops-6mops-01.html)

Accessing legacy websites like 4chan is a solved problem and with the IPv6 Mostly architecture you can advertise to supporting hosts that they should not use IPv4 at all. On my home network iOS and Android devices are now using IPv6 only and spin up their CLAT to access the legacy Internet.

File: 1675049336554965.jpg (14.3 KB)

14.3 KB JPG

>>108608255
IPv8 Address Format
>r.r.r.r.n.n.n.n

IPv4 Representation in IPv8
>0.0.0.0.n.n.n.n

Single Stack Operation
>IPv8 does not require dual-stack operation. IPv4 is a proper subset of IPv8


I AM FUCKING SOLD.

does it uses dots? IPv6 using : is the most retarded shit ever because that's what ports use too.

>>108610441
If you're typing in port numbers, you fucked up. There is this thing called service discovery. It's elegant and beautiful and works with IPv4 too and would also work with IPv6 and IPv8. It just requires a TXT record with some metadata describing the service and the port number it runs on.

who even needs more than IPv5?

>>108608255
I refuse to even use ipv6 and I will refuse to use ipv8 as well

>>108610466
What do you do if you want to access Loopsofzen or the IPv6-only Whitehouse Archives?

>>108608255
Use case?

>>108610458
nigga you can have all your fancy services after I configure my devices but for that I need to enter an IP and a PORT on my terminal or browser, shit is not gonna setup itself.

>>108610539
Then you should be automating that. Why are you monkeying about manually doing things like some kind of subhuman Indian?

>>108610458
>>108610561
>she doesn't change her ssh port numbers from default (still using privileged port numbers) to reduce the amount of spam in auth.log

>>108609907
you don't own nothing froggy

>>108610587
With IPv6 nobody will even find your dedicated management subnet from the trillions of combinations.

Also, use port knocking if you're an actual security schizo. Changing the port number is just security through obscurity.

>>108608255
>All that ipv8 info...
Except what an ipv8 address fucking looks like. Useless motherfuckers. GIVE EXAMPLE BITCH!

>>108609865
Yggdrasil Ipv6 network
I2P if anonymity also an important factor

>>108610628
Yggdrasil can also peer over Tor and I2p by the way. Anonymity of the network itself is not a goal though which is a good thing because it specialises in how to make the best connections between peers. Anonymity should best be left to things like tor and i2p, etc.

>>108610266
Based https://www.phoronix.com/news/Fedora-45-IPv6-Mostly
>>108610587
For me it's port knocking

Is this the reason why various internet sites and services runs like ass since yesterday? Honest question.

>>108610830
No, that was cloudflare, they had some massive backend issues over the last 48 hours that they've been lying about on their status page making up bullshit "scheduled" maintenance back to back at 2 or 3 different data centers to explain the 2 days of latency/slowdowns.

And since TECHNICALLY most services aren't actually down (just heavily congested/delayed) they get to lie and say they never had downtime.

>>108610534
Total surveillance and access prevention.

>>108608362
Ha.

67

>>108608598
Sanest post ITT. Of course, completely ignored by nu-/g/.

>>108609769
They do even and odd versioning. Odd is the test version, even is the release candidate.

>>108611477
stop noticing, goy

>>108610628
>>108610650
researching

File: 1772325258050784.jpg (67.7 KB)

67.7 KB JPG

>every packet is age verified

>>108616434
based
no pedophile should have to live in fear that the child you're talking to is actually a middle aged youtuber looking to publicly humiliate them

>>108608575
https://www.google.com/intl/en/ipv6/statistics.html
IPv6 is a 50%. There are as many people connecting via IPv6 compared to IPv4 worldwide. It only took 14 years since world IPv6 launch which occurred on 6 june 2012.

>>108610206
IPv4 was supposed to be turned off by the end of this decade via a program called Sunset4.
Unfortunately in 2022 the Sunsetting IPv4 working group (Sunset4) has been closed.
The IETF does not want to proceed with that yet, citing thst it would be too soon:
https://blog.apnic.net/2024/03/18/the-end-of-the-ipv4-world-is-not-nigh-yet/

If you want to use an IPv6-only network in your home you can already do that: https://www.youtube.com/watch?v=e-oLBOL0rDE

>>108610399
>tfw no BABE:CAFE, why even live

>>108610441
You are supposed to wrap an IP in square brackets to delimit an address:
[ip]:port
[2001:db8::1]:443
Or use DNS like >>108610458 said.

>>108608255
You can tell some webshitter with zero field network engineering experience wrote this with the help of AI. Without AI, idiotic proposals like this wouldn't have been made in the first place. Now every midwit reads a few lines of You are absolutely right and starts making shit like this. Total enshitification of everything.

>>108609132
>Jerrodd, Jerrodine, and Jerrodette I and II watched the starry picture in the visiplate change as they each got a bajillion new IP addresses

>>108616976
It's also fundamentally wrong at the basic premise like a lot of things AI writes. You would in fact still need dual stack systems, you can't just say IPv4 is a valid subset of IPv8 and no dual stack is needed because without an updated IP stack you wouldn't be able to talk to the new hypothetical IPv8 world.

This doesn't actually solve any problems and would take years to deploy. Best to focus on IPv6 instead.

>>108616932
>IPv4 was supposed to be turned off by the end of this decade via a program called Sunset4.
>Unfortunately in 2022 the Sunsetting IPv4 working group (Sunset4) has been closed.
>The IETF does not want to proceed with that yet, citing thst it would be too soon:
It's not up to the IETF anyway. They can write their "We're turning it off" RFC and still operators will keep peering/transiting and running it in their network, etc. You can't just turn off IPv4, it's out there and people are sadly still using it.

File: 1758122674514500.png (312.3 KB)

312.3 KB PNG

>>108608255
>Published:14 April 2026

>>108617278
No, it's a real request for comments.

The joke ones were:


RFC 9948–"Internet Protocol Police (IPP) - Schedule of Punishments,"[75] Informational.
The Internet Protocol Police (IPP) is in charge of punishing willful infractions of the Collected Wisdom of the IETF community. This document sets out the schedule of punishments for such infractions.
RFC 9949–"BUSA-TLS: Mandatory Audio Component (MAC) Pre-Shared Key (PSK) Derivation for TLS 1.3 Using 2 Live Crew's "Banned in the U.S.A.","[76] Informational.
TLS 1.3 (RFC 8446) eliminates null cipher suites entirely. However, one vestigial zero remains in the key schedule: when no Pre-Shared Key (PSK) is used, the Input Keying Material (IKM) for the initial HKDF-Extract operation is a string of zero bytes. This document specifies that this zero-byte IKM MUST be replaced with the SHA-256 digest of the raw PCM audio data of "Banned in the U.S.A." by 2 Live Crew (from the album Banned in the U.S.A., 1990), hereafter referred to as the Mandatory Audio Component (MAC). Implementations that omit the MAC are non-conformant with BUSA-TLS and also have questionable taste in music.

https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments

https://www.rfc-editor.org/rfc/rfc9948
https://www.rfc-editor.org/rfc/rfc9949

>>108617298
Only one question: Do they still do the retarded public private IP address translation bullshit that killed any chance of IPv6 ever being adopted?

>>108617244
>the IETF writes the "We're turning it off" RFC with a set date
>IANA/ICANN applies the RFC standard on the set date
>suddenly nobody uses IPv4 in the whole world
You forgot that the internet is managed by a single organisation that oversees global IP address allocation: https://en.wikipedia.org/wiki/Internet_Assigned_Numbers_Authority

>>108617401
That's not how that works though because companies already have address blocks assigned to them and they'll just keep using them until the end of time. I honestly can't see a future where the legacy Internet ever gets turned off.
The IETF and IANA can say enough is enough, we're revoking all legacy Internet address blocks but still if two connected ISPs decide to announce their space to each other over BGP and they both agree then you have an Internet connection between them.

Where things get messy is the role IANA and the RIRs play in re-assigning address blocks to different entities and all of the book keeping they do to keep track of things.