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