Bill, I would just make it /64s all the way down. Subnetting a /64 is like taking half-breaths from a snorkel: why bother when the supply is effectively infinite?
-mel > On May 16, 2024, at 3:35 AM, William Herrin <b...@herrin.us> wrote: > > On Wed, May 15, 2024 at 10:09 PM Mel Beckman <m...@beckman.org> wrote: >> The RFC seems to be concerned with aggregation efficiency, and while that >> may be a concern someday, so far computer and memory capacity has far >> outstripped prefix growth in the default-free zone. >> >> If you can explain why a /64 would ever not be enough for a single subnet, >> I’m willing to listen. > > The subnet contains a router that gateways to another /64. For > example, there's a home automation controller and the controller > implements its own lan of components on a different media type. > > Instead of assigning a pair of /64's, you assign a /63 and then route > a /64 from the /63 to the home automation controller. > > Except you don't do that either. IPv6 is plentiful and reverse-DNS > delegates cleanly on 4-bit boundaries so you think in terms of 4-bit > boundaries instead: assign a /60, use a /64 on the immediate LAN and > route a /64 to the home automation controller and retain the balance > for the next device that wants to implement an internal subnet. > > Regards, > Bill Herrin > > > > -- > William Herrin > b...@herrin.us > https://bill.herrin.us/
