Slashdot Mirror
US Agency Lines Up Broad Support For ICANN Transition (pcworld.com)
An anonymous reader quotes a report from PCWorld: A U.S. agency has lined up broad support for its plan to end the government's oversight of the Internet's domain name system, despite opposition from some Republicans in Congress. The U.S. National Telecommunications and Information Administration (NTIA) on Thursday released statements of support for a plan to end its oversight of the Internet Corporation for Assigned Names and Numbers (ICANN). Among supporters of a plan, developed by the ICANN community, to transition ICANN's domain name coordination functions to a multistakeholder governance model are Amazon.com, Google, Cisco Systems, Microsoft, Facebook, Hewlett Packard Enterprise, the U.S. Chamber of Commerce, and the Computer and Communications Industry Association. NTIA on Thursday announced it had reviewed the community proposal and found it meets the agency's criteria for allowing the ICANN privatization plan to move forward. The community plan maintains the openness of the Internet and maintains the security and stability of the DNS, said NTIA Administrator Lawrence Strickling. It does not replace NTIA's oversight with another government organization, he said, although that's been a fear of some critics of the NTIA plan. On Wednesday, Ted Cruz proposed a bill, the Protecting Internet Freedom Act, that would prohibit the U.S. government from relinquishing its role with respect to overseeing the web's domain name system (DNS), unless explicitly authorized by Congress.
Their doing a pretty shitty job with IPv6 too. I recently got the run-around with ICANN / AT&T trying to get IPv6 PTR records fixed. I was implementing a postfix server on an external IP, and google kept giving me "this message does not meet IPv6 sending guidelines regarding PTR 550-5.7.1 records and authentication. " This sent me down a rabbit hole, contacting AT&T and ICANN. AT&T said the SOA of my assigned IP was with ICANN, ICANN said the v6 was a multicast and AT&T needed to fix that...which then AT&T said the only was to fix it was to sign up for their "Managed Services" and pay them more $$$. This whole "we must transition to IPv6!" is being co-opted by corps into a non-technical money grab. I pay extra $$$ per month ALREADY for my subnet, apparently this doesn't cover IPv6.
As it turns out, the REAL issue was implementing IPv6 on the mail server, adding my client's external IPv6 address into the postfix relay conf, and then it started working. Google is misleading with their "PTR" message; it can be fixed without SOA PTR. If anyone is curious, I made a tutorial on my site on how to figure out your IPv6, the conf files to edit, etc.