Somewhat of a good point, but I don't think it applies here - some implementations, particularly inexpensive devices like SOC's, do exact search on common prefi

Somewhat of a good point, but I don't think it applies here - some implementations, particularly inexpensive devices like SOC's, do exact search on common prefix lengths like /64 and /48. I can't imagine this would be a huge problem within a home network, though. Even then, DRAM, which is essentially software switching, is rarely used. Further, you said you had 6 VLANs - this is well within the route scale of the vast majority of network devices regardless of how they implement their lookup data structures. Good example: The SRX300, a desktop router/firewall implemented on a MIPS based Cavium Octeon (both control and data plane) can handle up to 256K IPv6 routes: https://www.juniper.net/assets/us/en/local/pdf/datasheets/1000550-en.pdf https://www.juniper.net/assets/us/en/local/pdf/datasheets/10... The Trident series SOC's can do 8K by default, and 64K with ALPM enabled: https://www.juniper.net/us/en/local/pdf/datasheets/1000480-en.pdf https://www.juniper.net/us/en/local/pdf/datasheets/1000480-e... >(I mean, you only use /127's for point-to-point links that don't need link-rate switching anyway)? /126's and /127's are often used for PTP's for peering/transit. Line rate is table stakes. Bear in mind that the gear used in these situations has plentiful lookup memory (SRAM, RLDRAM, HMC, or HBM).