North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: v6 subnet size for DSL & leased line customers
This is certainly one reason for such things.The primary reasons I see for separate networks on v6 would include firewall policy (DMZ, separate departmental networks, etc)...
Perhaps this is a lack of imagination.And I'm having some trouble envisioning a residential end user that honestly has a need for 256 networks with sufficiently differently policies. Or that a firewall device can't reasonably deal with those policies even on a single network, since you mainly need to protect devices from external access.
Imagine that your ethernet->bluetooth gateway wants to treat the bluetooth
and ethernet segments as separate routed segments.
Now, imagine that some of your bluetooth connected devices have reasons to have some topology behind them... For example, you have a master appliance control center which connects via Bluetooth to your network, but, uses a different household control bus network to talk to various appliances. For security reasons, you've decided not to have your kitchen appliances be able to talk to your media devices (Who wants a virus in some downloaded movie to be able to change the temperature in your refrigerator?).
I keep coming to the conclusion that an end-user can be made to work on
I can easily envision the need for more than a /64 in the average home within short order. If nothing else, the average home will probably want to be able to accommodate: Guest network Home wired network Wireless network(s) Bluetooth segment(s) Media network Appliance Control netowrk Lighting Control network etc.
However, I agree that in any vision I can come up with today, the need for more than 256 is beyond my current imagination.
I think it makes sense to assign as follows:
/64 for the average current home user. /56 for any home user that wants more than one subnet /48 for any home user that can show need.