At least two senior-level ICANN community members, including a new member of its board of directors, have been affected by US President Donald Trump’s controversial travel restrictions, imposed this weekend on the citizens of seven Muslim-majority nations.
The so-called “Muslim ban” has also attracted criticism from other members of the community.
Kaveh Ranjbar, Amsterdam-based chief information officer for RIPE/NCC and an ICANN director, said that he is unable to attend this week’s board retreat in Los Angeles because he holds an Iranian passport.
“I have checked this with ICANN’s general counsel and they have tried an external counsel with expertise in immigration,” Ranjbar told DI. “Their advice was that I might be able to travel but they were not sure. As you know the situation is really fluid and things change real fast.”
“After checking with the airline and looking at similar cases, I decided not to even try, because I did not want to risk deportation or being detained in the US,” he said.
Ranjbar was born in Iran but holds dual Dutch-Iranian citizenship.
He said he will participate remotely in the board retreat, likely until with 3am each day.
“However, the work of ICANN board is no different than any other board, it is mostly free exchange of ideas and discussing and challenging positions, outside of the formal setting of the meetings, that’s how you get a feel on your other colleagues positions and will be informed enough about their positions which will enable you to support or oppose with proper grounds and arguments,” he said. “I will miss that critical part.”
Non-Commercial Users Constituency chair Farzaneh Badiei is also affected. She’s Iranian, but recently relocated to the US on an academic visa.
She told NCUC members that she’s effectively stuck there, unable to attend an intersessional meeting in Iceland or ICANN’s March meeting in Denmark, for fear of not being allowed to return.
“I have been advised to take precautionary measures in light of the current draft executive order that might not allow current visa holders re-entry to the United States,” she said.
ICANN is still evaluating the situation.
“We are still trying to fully understand the potential impact of the President’s Executive Order on our community, Board and staff travelers. We want to ensure ICANN’s continued accessibility and openness,” a spokesperson said on Sunday.
ICANN does have Iranian-born staffers, but I’m not aware that any have reported travel problems as a result of the Trump move.
The travel ban has drawn fire from other related organizations.
Internet Society CEO Kathy Brown wrote that she was “deeply troubled” by the ban, adding:
Not only will the purported bans place an unwarranted burden on people in our organization, it is an anathema to the Internet Society whose values rest firmly on a commitment to an open, globally connected community dedicated to the open, global Internet. We are encouraged by the countries who have rejected the U.S. action this weekend and by the human rights organizations that have stood in solidarity with countless refugees and travelers who were so abruptly halted in entering the U.S.
The chairs of the IETF, IAOC and IAB indicated in a joint statement that they may reconsider holding future meetings in the US:
the recent action by the United States government to bar entry by individuals from specific nations raises concerns for us—not only because upcoming IETF meetings are currently scheduled to take place in the U.S., but also because the action raises uncertainty about the ability of U.S.-based IETF participants to travel to and return from IETF meetings held outside the United States….
Our next meeting is planned for Chicago, and we believe it is too late to change that venue. We recognize, however, that we may have to review our other planned meeting locations when the situation becomes clearer. We are already reviewing what to do as far as location for the next open North American meeting slot.
Meanwhile, the Internet Governance Project’s Milton Mueller blogged:
This has significant implications for Internet governance. Coordination and policy making for a global medium based on cooperation and voluntary standards requires open transnational institutions. Participation in those institutions requires the ability to freely travel. The United States can no longer be considered the leader, either politically or ideologically, of an open global Internet if its own society is mired in protective barriers… What a stroke of good fortune that the prior administration succeeded in freeing ICANN from the U.S. government in its waning months.
The travel ban is said to be “temporary”, lasting just 90 days, but some fear it may evolve into a permanent fixture of US policy.
ICANN’s Security and Stability Advisory Committee has told ICANN it needs to do more to address the problem of name collisions before it approves any more new gTLDs.
In its latest advisory (pdf), published just before Christmas, SSAC says ICANN is not doing enough to coordinate with other technical bodies that are asserting authority over “special use” TlDs.
The SAC090 paper appears to be an attempt to get ICANN to further formalize its relationship with the Internet Engineering Task Force as it pertains to reserved TLDs:
The SSAC recommends that the ICANN Board of Directors take appropriate steps to establish definitive and unambiguous criteria for determining whether or not a syntactically valid domain name label could be a top-level domain name in the global DNS.
Pursuant to its finding that lack of adequate coordination among the activities of different groups contributes to domain namespace instability, the SSAC recommends that the ICANN Board of Directors establish effective means of collaboration on these issues with relevant groups outside of ICANN, including the IETF.
The paper speaks to at least two ongoing debates.
First, should ICANN approve .home and .corp?
These two would-be gTLDs were applied for by multiple parties in 2012 but have been on hold since August 2013 following an independent report into name collisions.
Names collisions are generally cases in which ICANN delegates a TLD to the public DNS that is already broadly used on private networks. This clash can result in the leakage of private data.
.home and .corp are by a considerable margin the two strings most likely to be affected by this problem, with .mail also seeing substantial volume.
But in recent months .home and .corp applicants have started to put pressure on ICANN to resolve the issue and release their applications from limbo.
The second incident the SSAC paper speaks to is the reservation in 2015 of .onion
If you’re using a browser on the privacy-enhancing Tor network, .onion domains appear to you to work exactly the same as domains in any other gTLDs, but under the hood they don’t use the public ICANN-overseen DNS.
The IETF gave .onion status as a “Special Use Domain“, in order to prevent future collisions, which caused ICANN to give it the same restricted status as .example, .localhost and .test.
But there was quite a lot of hand-wringing within the IETF before this status was granted, with some worrying that the organization was stepping on ICANN’s authority.
The SSAC paper appears to be designed at least partially to encourage ICANN to figure out how much it should take its lead from the IETF in this respect. It asks:
The IETF is an example of a group outside of ICANN that maintains a list of “special use” names. What should ICANN’s response be to groups outside of ICANN that assert standing for their list of special names?
For members of the new gTLD industry, the SSAC paper may be of particular importance because it raises the possibility of delays to subsequent rounds of the program if ICANN does not spell out more formally how it handles special use TLDs.
“The SSAC recommends that ICANN complete this work before making any decision to add new TLD names to the global DNS,” it says.
The Tor Project Inc, a Massachusetts non-profit software maker, just got a new gTLD reserved for its own exclusive use, by ICANN, for free.
Tor did this without engaging in the ICANN new gTLD program, paying any ICANN application fees, or following any of the rules in the ICANN Applicant Guidebook.
It basically circumvented the entire ICANN process, and it only took six months from asking.
Neat trick, right?
Tor develops the software that creates the Tor “anonymity network” used by people who wish to obfuscate their internet usage (legal or otherwise) by routing their traffic via a series of proxies or relays.
The free software, which plugs into browsers, uses meaningless, hashed “.onion” domains because the routing method is known as “onion routing”.
IANA, an ICANN department, last night placed .onion on its list of Special Use Domains, meaning it cannot be delegated to the DNS.
If anyone were to apply for it today — assuming that were possible — they’d be out of luck. It seems .onion now has the same protected status as .example and .localhost.
The reservation was made at the instruction of the Internet Engineering Task Force, which published a new Internet Draft reserving the .onion gTLD for use with Tor.
An Internet Draft is a “work in progress” standards track document with a six-month shelf life, not yet a finalized Request For Comments (RFC).
This one was written by engineers from Tor and Facebook.
The Internet Engineering Steering Group, the IETF’s coordinating body, approved the draft last week.
Of the 13 IESG members who voted on the document, the first draft of which was published six months ago, five voted “Yes”, seven offered “No Objection” and only one abstained.
The abstainer, Barry Leiba, standards guru at Huawei Technologies, wrote:
I believe the IETF shouldn’t be involved with registering special-use TLDs for things that were used outside of IETF protocols, and should not be wading into territory that belongs to ICANN. I know there are a bunch of other such TLDs that people/organizations would have us snag for them, and I very much want to avoid doing a batch of others.
That said, I well understand the deployed code involved and the importance of keeping things working in this case, and I don’t want to stand in the way. So I’m standing aside with an “Abstain” ballot.
The logic behind the reservation is that if ICANN were to delegate .onion to somebody else (for example, The Onion) there would be a risk that the improved privacy offered by Tor would be compromised.
Voting in favor of the draft, Cisco engineer Alissa Cooper wrote:
Registering this name seems warranted in light of the potential security impact. We need to make our processes work for the Internet, not vice versa.
Another affirmative vote came from Oracle engineer Ben Campbell. He wrote:
This one took some soul searching. But I think the arguments have been made, and that on the whole this registration does more good than harm.
A number of IESG members suggested that the IETF should revisit and possibly amend the RFC in which it originally granted itself the power to reserve gTLDs.
That’s RFC6761, entitled “Special-Use Domain Names”, which dates to February 2013.
RFC6761 lays out a seven-point test that a string must pass before it can be considered “special use” and thereby reserved.
The tests cover whether humans, applications and various types of DNS software are expected to handle the string differently to a regular TLD.
The RFC also notes:
The IETF has responsibility for specifying how the DNS protocol works, and ICANN is responsible for allocating the names made possible by that DNS protocol… Reservation of a Special-Use Domain Name is not a mechanism for circumventing normal domain name registration processes.
I think reasonable people could disagree on whether that’s what has just happened in the case of .onion.
Indeed, there was some discussion on the IETF’s “dnsop” working group mailing list about whether Tor was “squatting” .onion, and whether it was appropriate to reserve its chosen TLD string.
I wonder what kind of precedent this could set.
The Tor Project Inc is a Massachusetts non-profit company. It’s primarily funded by US government grants, according to its 2013 financial statements, the most recent available. It doesn’t sell .onion domains — they’re auto-generated by the software.
Part of the argument in favor of allowing the new Internet Draft is that .onion substantially pre-dates the creation of RFC6761 — it’s not an attempt to game the RFC.
Why wouldn’t that same argument apply to, for example, alternate root operator Name.Space, which has been offering hundreds of pseudo-gTLDs since 1996?
Name.Space could argue that its strings pre-date .onion by eight years, and that the security of its registrants and users could be compromised if ICANN were to delegate them to the DNS.
What about NameCoin, another alternate root provider? It also pre-dates RFC6761 and, like Tor, uses browser software to work around the DNS.
I don’t know enough about the IETF’s processes, to be honest, to say whether it would be forced to apply its .onion logic to these other namespaces. But it’s an interesting question.
And as somebody who has spent the last five years immersed in the minutiae of the rules ICANN has created to govern the allocation of words, it’s jarring to see those rules circumnavigated so completely.
A trio of Chinese techies have proposed a new IETF standard to enable governments to break up the Domain Name System along national borders.
Named “DNS Extension for Autonomous Internet (AIP)”, the spec describes a way to operate alternate DNS root servers within national boundaries using gateways for translation.
For internet users subscribed to one of these “AIP” networks, DNS requests would carry an extra TLD, such as .a or .b, to flag the fact that the requests are headed for an alternate root:
Domain node “www.yahoo.com” in network B is expressed as “www.yahoo.com.B” for its external domain name.
Written in broken English, the Internet Draft is a poorly masked description of a way to install government censorship via officially sanctioned domain name system Balkanization.
It appears to be designed to enable governments to cut ICANN and the authoritative DNS root out of the picture entirely in favor of a national peering system more akin to traditional telecoms networks.
The paper reads:
In order to realize the transition from Internet to Autonomous Internet, each partition of current Internet should first realize possible self-government and gradually reduce its dependence on the foreign domain names, such as COM, NET et al.
It is not likely the whole Internet can be transformed synchronally in one time. In order not to affect existing domain name resolution before the Internet core part transforms into an AIP network, any country can set up an AIP DNS independently and connect to the Internet through the original link; or any two countries in agreement can set up their AIP networks and connect to each others.
The paper was written by Yuping Diao of Guangdong Commercial College, Yongping Diao of China Telecom and Ming Liao of China Mobile.
It’s just an Internet Draft at this stage, and probably nothing to get too worked up about, but it does reflect the Bigger Picture framing the ICANN expansion of the DNS.
During the ITU’s World Conference on International Telecommunications this December, backwards governments are expected to proposed a greater degree of government control over the internet.