So why do not representing IPv6 in a base64 encoding? 20 chars + 3 numbers [0-255] for the last 8 bits organized in 4 group 10 char; 8 char; 2 char; 3 numbers example: CompanyNet;inMilano;hr;121 pros: - buzzword or company name preference for choice as happened for dns name; - network partition inside a company would use the last two base64 char + 3 numbers (like ipv4) for a total of 20 bits of space (2^20 should be enough); - optimized usage of bit space, no needs for /64 as minimum for a network; - considering that it is only a representation with a well know alhorithm should be simple to implement. -CIDR mechanism can work as well. Best regards. Mirko Mancini - Telecommunication Engineer ________________________________ Da: ipv6-wg <ipv6-wg-bounces@ripe.net> per conto di Aled Morris via ipv6-wg <ipv6-wg@ripe.net> Inviato: sabato 5 ottobre 2019, 17:51 A: Jens Link Cc: ipv6-wg@ripe.net IPv6 Oggetto: Re: [ipv6-wg] Disband IPv6 WG On Thu, 3 Oct 2019 at 11:34, Jens Link <lists@quux.de<mailto:lists@quux.de>> wrote: The new successor to IPv4 should not make the same mistakes as IPv6. [...] - It MUST only have numbers and dots "." Maybe we should allow IPv6 addresses to be written in dotted quad format with the quads not being limited to 0..255 but instead 0..4294967295 So instead of writing 2001:4860:4860::8888 we would write 536954976.1214251008.0.34952 which is clearly easier to use. bonus: your old regex ^[0-9]*\.[0-9]*\.[0-9]*\.[0-9]*$ will still work Aled Ottieni Outlook per Android<https://aka.ms/ghei36>