parent said it caused network issues at their university.
pretty cut & dry 'why not?' included.
>Microsoft and Apple might not be following the DHCP spec correctly, but they're breaking it for the right reasons.
these groups are both large enough to influence whatever specs they need to without out-right breaking them, in many ways they're the ones least responsible in doing so, as they often times shape the specifications themselves. If they need the spec to include arbitrarily long leases let's ask them to propose that to the spec rather than being OK with certain groups violating things.
Violated specs is exactly the kind of thing that that trickles down to unintended and unexpected user experience.
> parent said it caused network issues at their university.
No, the parent's university's apparent problem was that their DHCP was reallocating IP addresses soon after expiry. Dramatically increasing the pool size and the lease time wasn't the problem, it's the solution.
You're not wrong, but I'm saddened at this attitude. IMHO the tech giants already have so much power/ability to shape/force the standards to suit their own practices. The attitude of "Apple should be able to violate the standard all they want and it should be on network operators to accommodate them" is wildly empowering to the elephant over the ant.
parent said it caused network issues at their university.
pretty cut & dry 'why not?' included.
>Microsoft and Apple might not be following the DHCP spec correctly, but they're breaking it for the right reasons.
these groups are both large enough to influence whatever specs they need to without out-right breaking them, in many ways they're the ones least responsible in doing so, as they often times shape the specifications themselves. If they need the spec to include arbitrarily long leases let's ask them to propose that to the spec rather than being OK with certain groups violating things.
Violated specs is exactly the kind of thing that that trickles down to unintended and unexpected user experience.