This is the file Peter Bowen created a few times to let all the CAs know about issues that lead up to the identification of GlobalSign certificates with IP addresses in dnsName:
At the time this list of non-compliant certificates was reported, there was continued discussion about this IP address topic and how browsers handled (or not) IP addresses in the SAN. Some need IP address in dnsName, others need in the ipAddress:
During this period, the incident reporting process and rules for what constituted an "incident" weren't as formal nor as high visibility. The report Peter posted had over 45,000 entries from essentially every CA, and I don't recall there being hundreds of incidents. Certainty today there would be no question about how to handle an issue like this. In late 2015 and early 2016 the process wasn't as clear.
As you noticed, we updated our systems in July 2016 to address this to stop issuing new certificates with IP addresses in the dnsName field. We'll initiate revocation shortly on the list of still-active certificates.