The IETF working group for IPv6 maintenance is called 6man.
Despite my repeated emails, they REFUSE to acknowledge whether 6man is related to Five Guys.
Reader, I promise you: I will not let them dodge this question.
My blog teaches network engineering with jokes & fun!
Instructor/course writer for Juniper. JNCIE-SP, meme fanatic. CEO of the internet. Your new goth uncle.
Co-author of the book Beginners Guide to Learning Junos, which you might maybe enjoy?
| Website | https://www.networkfuntimes.com |
The IETF working group for IPv6 maintenance is called 6man.
Despite my repeated emails, they REFUSE to acknowledge whether 6man is related to Five Guys.
Reader, I promise you: I will not let them dodge this question.
NEW POST: After many months of work, my four-day instructor-led SR-MPLS course is now live! Plus, Krzysztof Szarkowicz has written some great blogs introducing SRv6.
Want to find out more? Clicky-click: https://www.networkfuntimes.com/my-new-sr-mpls-course-and-krzysztofs-srv6-blogs/
Catching up on half a year of Ivan Pepelnjak's blog (partly in research for an upcoming post of my own), and found this gem:
https://blog.ipspace.net/2024/04/ipv6-slaac-unintended-consequences/
...where he explains why someone's IPv6 neighbor cache was artificially filling up. Well worth a read.
One of my friends is running a large IPv6 network and has already experienced a shortage of IPv6 neighbor cache on some of his switches. Digging deeper into the root causes, he discovered: In my larger environments, I see significant neighbor table cache entries, especially on network segments with hosts that make many long-term connections. These hosts have 10 to 20 addresses that maintain state over days or weeks to accomplish their processes. What’s going on? A perfect storm of numerous unrelated annoyances:
To be clear - the new option might well be an excellent and much-needed replacement for the current choice. Nothing wrong with that.
But when people use "legacy" to refer to something currently in use, it always feels like a marketing trick. If the new option is good, then show us why it's good on its own terms. Don't play tricks with language.
PROTIP: Want to convince people that your tech is good? Simply call the alternatives "legacy" - even if people are still using it perfectly happily.
IPv6 is a replacement for legacy IPv4.
SD-WAN is a replacement for legacy MPLS (never mind that this isn't what MPLS means).
Our monitoring system is a replacement for your legacy monitoring system.
Coffee is a replacement for legacy tea. Dogs are a replacement for legacy cats. Try it yourself. It's a fun hobby, and it's free for you to try!
Today I Learned that IPv7 was proposed in 1993 https://www.rfc-editor.org/rfc/rfc1475.html
(It's not a successor to IPv6 - there were just a few "next gen" protocols proposed at the time. Still, it's funny to call it IPv7!)