#Denog16 Nachtrag
#ipv6excuses
Größtes #Hotel in #de und dann sowas:
"Ich kann Ihren Wunsch durchaus nachvollziehen, kann Ihnen da aber leider nicht entgegenkommen.
Unser allgemein zugängliches und kostenfreies WLAN bietet in der jetzigen Konfiguration keine Möglichkeit, IPv6 Adressen bereit zu stellen.
Im Verhältnis zu der gegen Null gehenden Nachfrage nach IPv6, ist der Konfigurations– und Wartungsaufwand dafür einfach zu hoch.
Mit der Bitte um Verständnis verbleibt … "
Another great reason why IPv6 is bad:
https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968/5
> if your NIC is replaced it gets a new IP
> almost nobody understands it or can explain it
> IPv6 is stupid and it will die soon
> Almost nobody uses it
Luckily, there’s a solution!
> Time for IPv4+, keep the current but just add a few more numbers, or change them from 256 to max 1024
> I never understood why they didn’t simply make more numbers and keep what we have.
I have played with IPv6 but it’s a bad design, because if your NIC is replaced it gets a new IP and you can change all records again. I tried to understand the stupid protocol but it makes no sense. They should bury it and let people decide if they want NAT or not as today you can not use NAT and that means that every change in your local network, you have to do a lot of work to get things back to working order again. I stopped trying to understand it, as it seems almost nobody understands it...
Soo someone running infrastructure at the #IETF decided that legacy-IP only would be an ok decision for some part of their mail infrastructure.
In 2024.
https://mailarchive.ietf.org/arch/msg/ietf/GLDqO_ck6zjlg-P3HUP0O8ikGMQ/
#ipv6 #ipv6excuses
I found a great #IPv6Excuse today from #Mailgun:
> IPv4 still plentiful.
https://feedback.mailgun.com/forums/156243-feature-requests/suggestions/47172679-ipv6-support
Thomas Schäfer
Antonis Chariton
Fink 
