<div dir="ltr"><div>Hi Jens,</div><div><br></div><div>Wow, first I had to look at today's date, I thought this was a April Fools joke mail.</div><div><br></div><div>But to go forward seriously, a couple of questions to maybe clarify your thinking - from bullet points:</div><div>1. WHY should it have NAT</div><div>2. What do you understand under class, IPv4 "Classes" are just defined subnet groups (simply put)<br></div><div>3. AFAIK DHCPv6 is defined in RFC (3319,3646,4704,5007,6221,6355,6939,8415)</div><div>4. Partly agree on this one</div><div>5. Partly agree on this one, but probably with the right set of firewall rules you could achieve the same effect you are going after</div><div>6. Dots and colon, what's the difference?</div><div>7. Use DNS to resolve - no [] needed then.</div><div><br></div><div>And for the "footprints":</div><div>[4] you want classes in "IPvX" but negate the same with this point<br></div><div> [5] what does the script have to do with network layer?<br></div><div><br></div><div>Just my 2c.</div><div><br></div><div>Uros<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 3, 2019 at 12:35 PM Jens Link <<a href="mailto:lists@quux.de">lists@quux.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br> <br> after now almost 12 years using, working and teaching[1]<br> IPv6 I've come to the conclusion that IPv6 is a mistake and will<br> not work.<br> <br> Therefore the RIPE IPv6 WG should be disbanded and replaced<br> with a new WG that MUST investigate all possible solutions to<br> artificially prolong the live of IPv4 till the day a new successor<br> for IPv4 is created and implemented!<br> <br> Some great ideas[2] are already proposed, some of them already<br> implemented:<br> <br> - Use of NAT<br> - Use of the first Class-A network 0.0.0.0[3]<br> - Use of parts of localhost Class-A network 127.0.0.0<br> - Use of (parts) of Class-D address space (multicast)<br> - Use of Class-E address space (future use)<br> - Using part of the UDP / TCP port range as extension for the<br> address.<br> <br> Some of the reserved address spaces could also be used. E.g. nobody<br> is using <a href="http://192.0.2.0/24" rel="noreferrer" target="_blank">192.0.2.0/24</a> for documentation anyway.<br> <br> It should also be investigated to take back legacy IPv4 resources,<br> although the "owners" of these resources might already selling<br> them on the open market.<br> <br> It MUST also be considered not filtering on Class-C[4] bounderies<br> but going for something smaller like /26 or /27 in the global routing<br> table. Also new Class Designations for these prefixes MUST be created.<br> <br> The new successor to IPv4 should not make the same mistakes as IPv6.<br> <br> - IT MUST have NAT<br> - It MUST have Classes<br> - IT MUST have DHCP<br> - It MUST have ARP<br> - It should be possible to drop ICMP the same impact as in IPv4. Many<br> experts I talked to over the years told me that blocking ICMP has<br> no negative impacts.<br> - It MUST only have numbers and dots "."<br> - There should be absolutly no reasons to use "[ ]" in URLs<br> <br> Probably the best way to proceed is to just add one or two octets to the<br> address.<br> <br> One of the reasons for the above is that there are so is so many good<br> documentation already written about IPv4! And people already know about<br> IPv4! Why waste this knowledge and experience? There is also plenty of<br> good software out there that can't work with IPv6[5] Change is bad!<br> People don't want to learn!<br> <br> IPv4! MUST! NOT! DIE!<br> <br> Jens<br> <br> [1] at least trying to teach, as one can see from the great number of<br> people actually using IPv6 with little success<br> <br> [2] <a href="https://netdevconf.info/0x13/session.html?talk-ipv4-unicast-expansions" rel="noreferrer" target="_blank">https://netdevconf.info/0x13/session.html?talk-ipv4-unicast-expansions</a><br> <br> [3] <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96125bf9985a" rel="noreferrer" target="_blank">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=96125bf9985a</a><br> <br> [4] a Class-C network is the equivalent of an /24. I was told by experts<br> that the definition of some bit set in the first octet of an IPv4<br> address is complete and utter nonsense<br> <br> [5] like a 20 year old shell script that is so important for $university<br> that it would be hard for them to implement IPv6!<br> <br> <br> </blockquote></div>