3 ms·

> because Android does not implement support for DHCP option 121, it was uniquely unaffected Curious if that was a deliberate decision because Google knew abou

• skissane 2y ago
  There are so many DHCP options, for something like Android it makes sense to start with only supporting the bare minimum and then only enable support for an additional option if there is a requirement raised for it. Given this DHCP option isn’t commonly used, such a strategy would likely result in it not being supported, irrespective of any security concerns with it.
• megous 2y ago
  Android doesn't even implement the new DHCP version defined first 21 years ago: https://www.rfc-editor.org/rfc/rfc3315 https://www.rfc-editor.org/rfc/rfc3315 So not really a surprise.
• kccqzy 2y ago
  Looking at https://issuetracker.google.com/issues/117544989 https://issuetracker.google.com/issues/117544989 seems like Google mostly just ignored this feature request without giving any reason. I wonder the same. Perhaps someone who works at Google with access to the internal Buganizer will know more. But if you want me to speculate, my speculation is that the team behind Android networking is highly pro-IPv6. They don't really care about missing niche features in IPv4. Even for IPv6 they have a specific vision for how IPv6 should be used, resulting in deliberate non-support of features like stateful DHCPv6.