6
IPv6 subnetting thought experiment (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by Scoopta@programming.dev to c/ipv6@lemmy.world
16 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments
[-] Scoopta@programming.dev 1 points 1 year ago

🤔 does it actually break PD?...that's actually not an awful reason if it does. Would actually make sense...outside of this post I fall into the /64 everywhere crowd, minus the cases for /127. Your gripe with point 2 is fair...although I haven't come across any applications that need it...beyond the applications I've written that use it...because again IRL I'm in the /64 everywhere crowd. Thanks for the response though

this post was submitted on 25 Sep 2023
6 points (87.5% liked)

IPv6

316 readers
3 users here now

IPv6 Discussions

founded 1 year ago
MODERATORS
apearson@lemmy.world
unquietwiki@programming.dev