I’m curious about something so I’m going to throw this thought experiment out here. For some background I run a pure IPv6 network and dove into v6 ignoring any v4 baggage so this is more of a devils advocate question than anything I genuinely believe.

Onto the question, why should I run a /64 subnet and waste all those addresses as opposed to running a /96 or even a /112?

  1. It breaks SLAAC and Android

let’s assume I don’t care for whatever reason and I’m content with DHCP, maybe android actually supports DHCP in this alternate universe

  1. It breaks RFC3306 aka Unicast-prefix-based multicast groups

No applications I care about are impacted by this breakage

  1. It violates the purity of the spec

I don’t care

What advantages does running a /64 provide over smaller subnets? Especially subnets like a /96 where address count still far exceeds usage so filling subnets remains impossible.

  • @orangeboats
    link
    English
    21 year ago

    I think someone will still have to route the /96 networks eventually? Aggregation is helpful for routers located in the upper part of the network hierarchy only.

    There’s also the problem of service providers “racing to the bottom” if /64 is not standardized, for example some ISPs may choose to delegate /96 instead, or /116, or /120, … you get it. We still have ISPs assigning people /128 in spite of /64 being standardized everywhere.

    • @[email protected]OP
      link
      fedilink
      English
      11 year ago

      Yeah but what I’m getting at is that upper router routing /96s shouldn’t be impacted. 10 /96s is basically indestinguisable from 10 /64s in terms of memory consumed. If I’m only using 10 subnets it shouldn’t matter what the size of those subnets are as long as the count stays the same. It’s when you start deagregating blocks into smaller chunks and consuming more of them than you would otherwise that you start eating table space. I can’t think of a situation where someone would consume more /96s than /64s given they’re both basically infinite addresses.

      …you know…that’s a really good point. Honestly this whole thought started because I saw someone adamantly defend not wanting to use an entire /64 and being annoyed Android didn’t have DHCP and it got me thinking…if someone genuinely didn’t care about the design goals of v6 are there good reasons to stick to them if DHCP works everywhere. Like I care about the elegance…but not everyone does. I’ve never seen ISPs assign a /128 although I have heard about it. I have seen 1x/64 assignments though which is only marginally better…but if you stop caring about clean /64 subnets then it becomes manageable without having to resort to an NDP proxy.

      I personally have mixed feelings on Google’s decision with DHCP. On the one hand I understand the frustration as it’s not their place to dictate your network architecture…on the other hand I think it’s admirable because it might be the one thing keeping that part of the v6 design goals alive when some wish it weren’t.

      • @orangeboats
        link
        English
        31 year ago

        You are right - although I dislike Google in general, the fact that Android supports only SLAAC is most likely the dominating reason why residential ISPs delegate /64 at all.

        • @[email protected]OP
          link
          fedilink
          English
          1
          edit-2
          1 year ago

          🤔 I hope you’re wrong but also I doubt you are. Ik a lot of people have been making a fuss about Android and DHCP, I do hope Google will stick to their guns on this. I feel like whether they do or not will have a massive impact on the direction v6 goes with subnet sizes in the future. Mostly in business environments which largely haven’t deployed v6 yet.