Some may wonder why only Princeton has reported this problem. Some may believe that because other sites are not reporting it, the problem must be due to a problem with Princeton's network.

Princeton detected this issue because we take a very pro-active stance to monitor for certain kinds of common network problems, including this one. Our network monitoring includes comparing actual IP address usage to DHCP server lease assignments on a daily basis. This allows us to detect some devices using IP addresses not assigned for their use. This is a degree of monitoring that many sites do not perform. We also monitor our DHCP servers very closely for any problems they detect, including when they see DHCP-leased IP addresses in-use when they should not be, or when a client tries to SELECT an offer that was not made to it, or when a client tries to renew or rebind an IP address after the client's lease on that IP address has already expired.

As a result, Princeton tends to learn about some kinds of bugs in DHCP client implementations sooner and more often than do many other sites.