Internet Corporation for Assigned Names and Numbers

Директор Координационного центра домена RU Андрей Колесников избран в правление Организации поддержки общих имен (GNSO Council).

Я задал ему три вопроса:

1. Почему ты решил подать свою кандидатуру в gNSO Council?
Сначала я подал свою кандидатуру в ccNSO council и указал, что gNSO мне тоже интересно. В связи с территориальными квотами, были маленькие шансы пройти в ccNSO, поэтому я решил номинироваться в gNSO.

2. Есть ли в России интерес по запуску новых корневых доменов gTLD?
Безусловно есть. Россия в этом плане не сильно отличается от других государств. Во-первых у нас есть очень большие и известные бренды. Думаю .gazprom и .газпром и .роснефть будут весьма интересны для этих компаний. Во-вторых, есть серьезные веб порталы. Например .яндекс.

3. Какой будет твой вклад в работу GNSO?
Я вижу свою роль в работе по внедрению IDN gTLD и считаю, что можно использовать мои знания для разработки общих платформ и договоренностей между gTLD и ccTLD сообществ в части разработки принципов, которые являются универсальными для всех типов доменов. Например защита
торговых марок, описания принципов стоп-листов, проблемы возврата администраторов, срок действия доменов которых закончен. Также мне крайне интересна идея которая находится между cc и g миром: например домены для федеральных образований внутри страны (пример – Татарстан в России) и домены для крупных городов (.москва, .самара)

{ 1 comment }

At the joint meeting of ICANN’s advisory committees and supporting organizations in Sydney, a number of core issues and corresponding possible solutions were discussed and pulled into a summary document.

We have put that document out in a radically different public comment period to allow for as much community discussion and collaboration as possible.

The comment period uses Jive software which allows for simple interaction and discussion between community members. It is an experiment we are running from now until 24 September. You can view everyone’s responses, clearly broken down into different areas, and if you register post your own thoughts and responses. As well as vote in polls, write blog posts, and so on.

[read the rest…]

{ 4 comments }

It’s not every day that ICANN comes to town. As an employee of Tucows, the third largest ICANN accredited registrar, I’m a little more tuned in to what’s going on with ICANN than the average person. But in my nearly three years at the company, I’ve never attended an ICANN meeting in the flesh. Instead, it’s been a case of tuning into the odd stream from the International Meeting, or hearing about the goings on from Adam Eisner, our Director of Domain Services at Tucows.

Not having been to an ICANN event, I didn’t know what to expect from the “Regional Gathering of ICANN-Accredited Registrars and gTLD Registries” when it came to Toronto last week. A check of the agenda had me wondering if some of the material would be over my head. The subject matter included security, compliance, data escrow and the Registrar Accreditation Agreement among other things. As I said, I try to stay up on what’s happening with ICANN, so at least I was familiar with most of topics being discussed.

The first session I attended was probably not the best introduction to the inner workings of ICANN. I had heard that there was a tendency to use acronyms to excess, so I came armed with a BlackBerry and the link to the ICANN website glossary. Despite my efforts, I still found myself leaning over on a number of occasions to ask my more experienced neighbours what the ALAC was and why the New gTLD AG3 was all about.

[read the rest…]

{ 4 comments }

Variant top-level domains (TLDs) and how they are managed is one of the most hotly discussed topics we are facing at the moment. What are variant TLDs, you ask? Well, that’s where the discussion begins…

ICANN’s staff is currently producing implementation plans for both the IDN ccTLD Fast Track Process and the New gTLD Process. What guides that process for the topic of variants, is three things:

1. Following the direction of policy advice already provided
2. Taking broader community needs into consideration, and
3. Ensuring the continued stability of the DNS and the namespace in general

In the course of doing this for the issue of variant TLDs there were two different proposals.

[read the rest…]

{ 4 comments }

One particularly important aspect of ICANN’s launch of new generic top-level domains (gTLDs) will be the availability of Internationalized Domain Names (IDNs) at the top level. That eagerly anticipated enhancement to Internet participation has also raised some issues.

For example, current practice dictates that gTLDs contain at least three characters – two-character Latin TLDs are reserved for country-code top-level domains (ccTLDs). However, in certain languages (you probably can think of more than one) one or two characters commonly express a complete word – and they would not be confused with present-day ccTLDs.

Prohibiting the registration of names of less than three characters in certain languages may hobble IDN use in certain languages but it is difficult to fashion a uniform set of rules to govern a potential relaxation of this requirement that works universally.

ICANN’s approach to this issue is similar to its approach on many issues regarding implementation of the policy for the introduction of new gTLDs.

[read the rest…]

{ 2 comments }

One of the consistent pieces of feedback I receive as ICANN’s Chief Financial Officer is that people want to know what it is that the organization is spending its money on. We have been been working hard to come up with ways of showing this clearly, especially so over the past year.

ICANN is a public benefit not-for-profit company and we recognize that you, as a community, need to be kept informed about our finances so that we remain accountable.

So here is a rundown of what we have produced with respect to finances. The hope is that you can follow the budget process all the way through from the strategic planning to the draft budget stage and through to seeing where the money comes from and where it goes to.

You should also, by the time you reach the end of this post, know how and when you can provide input into that process and so directly influence the budgeting process.

[read the rest…]

{ 6 comments }

In the past few days, we have been receiving a large number of emails and phonecalls about the web address YouTubeIslam.com, and a dispute over its ownership.

Because we coordinate the domain name system, ICANN is sometimes wrongly seen as the ultimate authority over anything that happens with the domain name system. The reality is quite different, so this blog post explains ICANN’s role and relates that to this particular issue.

While ICANN does ultimately set the rules by which domain names are registered, it does not possess the power to overturn decisions that are made within the rules. Why? Because ICANN, through its bottom-up policy development, seeks to provide distributed, independent decision making that is placed in the hands most suited toward making these sorts of decisions.

[read the rest…]

{ 43 comments }

This briefing note is also published on the Sydney meeting site at http://syd.icann.org and linked to on the front page of that site.

What was it?

ICANN’s 35th international public meeting is the first of three held annually to conduct policy development and outreach. It was hosted by ICANN (the Internet Corporation for Assigned Names and Numbers), AusRegistry International, operator of Australia’s dot-au register, and auDA (.au Domain Administration), the policy authority and industry self-regulatory body for the dot-au domain space.

The meeting was opened by New South Wales’ premier Nathan Rees, and Senator Stephen Conroy, Minister for Broadband Communications and the Digital Economy.

Premier Rees spoke about the impact and importance of the digital revolution, the important role that ICANN plays with the Internet, and the possibilities that new generic top-level domains will open up.

[read the rest…]

Some IPv4 /8s have been used to number IP networks in an unofficial and improper way. That is, they have been used without being properly allocated and registered in a public Whois database. In most cases these networks are mostly private, used internally in their organization, and so the addresses are not seen in the Internet’s routing system. The organizations using these addresses have relied on the overall availability of IPv4 addresses so that there was no pressing need to allocate all of the /8s that IANA manages. With the decreasing IANA free pool of unallocated IPv4 addresses, it is now clear that every last one of them will ultimately be allocated to the RIRs.

The networks using these officially unallocated addresses are intended to be private, not visible to the global Internet. Nonetheless, their use can be detected when the private parts of networks connect to their public Internet facing connections, such as the connections to their service providers. The addresses leak in e-mail message headers, DNS queries and other random traffic. In some cases, this unofficial use can cause operational problems.

[read the rest…]

{ 2 comments }