On July 19, 2025 at 21:03 nanog@lists.nanog.org (David Conrad via NANOG) wrote:
Whatever happened to "if your registration data is fraudulent, obsolete, or incorrect you stand to have your registration canceled"?
AFAIK, it remains a contractual requirement despite ICANN undertaking a law suit in Germany to enforce it for admin-c and tech-c and losing (if interested, see https://www.afslaw.com/perspectives/the-fine-print/recent-lawsuit-icann-agai...).
However, this gets into an “interesting” (or “infuriating”, depending on your POV) discussion about what contact information “accuracy” means. ICANN Accredited Registrars’ view (which I provide without comment) is at https://rrsg.org/wp-content/uploads/2024/03/RrSG-Approach-to-Registration-Da....
People wonder why ICANN's overhead / operating cost is so high but then one has to wrap their heads around contract enforcement in roughly 200 countries...Basically that's much of what ICANN is, a global web of contracts. Looking at that link does bring up a pet peeve though. There're no references to any other policy documents, particularly models external to ICANN. Too often it's as if the universe was created this week and ICANN sat down and named all the plants and animals etc. anew. Surely there are many models out there for similar registration systems some probably in existence and enforced for 100+ years. For example WIPO comes to mind but everything from registering ships to banking, multinational business registrations, etc. Some specifics such as email are newer concepts but even in that case email's been around for decades. I'd imagine when the validity of their contracts gets dragged into a court or other dispute resolution that after citing applicable laws and statutes the next thing would be comparing those contracts to those analogous regimens. For example how does WIPO or the ITU handle registrant disclosures. Yet it's always as if these policies were created out of thin air with no precedent or model. Perhaps there are stacks of such considerations they don't include in public documents but I can think of some specific instances where they were developing a policy and I suggested a survey of other organizations' analogous policies and felt like I was met with blank stares. -- -Barry Shein Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD The World: Since 1989 | A Public Information Utility | *oo*