3 ms·
If enterprises have use cases then unless there is a good solid alternative example that shows it's universally the case one should always have many:1 it just d
by zamadatix 5y ago
If enterprises have use cases then unless there is a good solid alternative example that shows it's universally the case one should always have many:1 it just doesn't seem like there is anything beyond "I think this is the better way therefore I won't let you do the other" backing the choice. If an enterprise wants 1:1 mapping of their devices using DHCPv6 for centralized logging, tracking, monitoring, avoiding device specific RA bugs/implementations/limitations, to consolidate the function while dual stacked, certain DHCP options to be available, or any other reason they have then someone else's non-applicable use case for many:1 isn't reasoning for nullification of those cases. In general I'm against any approach from a product/service that takes the stance "we just know better" and doesn't allow the operator to say otherwise even when I agree it is actually the superior way in most cases.
Yeah PD will give you a much an overkill block but there isn't really much of a block shortage. More importantly the alternative is NAT44 on the CLAT so only a single V6 address is required, this is actually what the standard says implementations "SHOULD" do in the single IP scenario as after all 464XLAT doesn't support peer to peer or inbound anyways. And of course people and orgs are free to simply want DHCPv6 on their devices even if it isn't perfect for every scenario.
A "Android doesn't want to support NAT44 for 464XLAT, assign a prefix the the device for the 464xLAT use case" stance I could totally understand. Or even "Carriers are not asking Android to support DHCPv6 deployment methods on LTE, DHCPv6 will only be supported on wireless" is very understandable. The current stance isn't like these though, it's simply "we don't like that type of deployment so we don't allow it". Or maybe I've just missed something big and there is a reason I should have forced a couple customers away from their use cases.