Résultats de l’appel:

Le contenu discuté lors de cet appel est destiné à informer la finalisation du RRDRP. Tous les commentaires seront pris en compte et, le cas échéant, des révisions peuvent être apportées au RRDRP, qui seront publiées avec le Guide de candidature.

Session:

Le meeting se tiendra par téléconférence le 13 avril 2011 à 19:00 UTC (http://timeanddate.com/s/208b), pour une durée prévue de 60 minutes.

Participation:

Si vous désirez participer, veuillez soumettre votre nom à registry-liaison@icann.org, et les informations sur l’appel vous seront communiquées.

ICANN performs these functions pursuant to a procurement contract that is scheduled to expire on 30 September 2011. NTIA indicates that it will consider public comments in the procurement process to award a new IANA functions contract.

The NOI is available [PDF, 64 KB] for anyone to read and comment upon. The deadline for submission of comments is 31 March 2011.

ICANN would like to announce that the transition of the technical management function for the IN-ADDR.ARPA zone from ARIN to ICANN has been completed. ICANN would also like to thank ARIN for carrying out the DNS zone maintenance function for IN-ADDR.ARPA since 1997 and their cooperation during this transition period.

For more details on the history of this transition please see the project web page.

The Internet has boomed in the intervening years and exceeded all our expectations. It now has a fundamental place in the economies of nations around the globe. The boom has gone so far that on February 3rd I allocated the last five blocks of IPv4 addresses from IANA’s central pool to the Regional Internet Registries (RIRs). The RIRs will allocate those IPv4 addresses to the networks in their regions in the coming months and maybe years.

The Internet uses IP addresses for its infrastructure, for the content we access and for the connections of ordinary Internet users. Recent studies indicate that approximately 2 billion people around the world have access to the Internet. And many of those 2 billion people may use 2 or more devices (computers, mobile phones, cable modems) that require an Internet address to deliver the service they want. The few billion addresses in IPv4 are barely enough for the services offered to 2 billion people much less for a world with a population of almost 7 billion.

There will be a period of transition and it will take time for the primary IPv4 infrastructure of the Internet to be replaced by IPv6 infrastructure. That transition will happen though because using the Internet has become an economic driver in all parts of the world.

I want to repeat the call I made in 1995 today because unique addresses are still good. And I urge everyone who anticipates building new Internet services, equipment and connections to provide support for globally unique IPv6 addresses. Having the wealth of unique addresses that IPv6 offers removes constraints that were placed upon innovation by the restricted availability of essential Internet addresses. IPv6 will enable the Internet’s future growth and there will be new opportunities for those already using the Internet as well as for those who will soon begin using it.

The peaks in IPv6 access, which is shown in red on the graph, closely correlate with ICANN meetings. IPv6 connectivity is provided as standard at ICANN meetings and lots of meeting attendees have been using it without knowing while using the free WiFi.

So, as the graph shows, we have had peaks in IPv6 access alongside the October 2009 ICANN meeting in Seoul, the March 2010 ICANN meeting in Nairobi and June’s ICANN meeting in Brussels. There was also a peak in January 2010, which we believe is associated with the IANA Business Continuity Exercise that took place on the 19^th of January, thus users were preferring the IPv6 transport while IPv4 provision was in flux.

What is perhaps more heartening than the peaks associated with the ICANN meetings, is that the troughs in April and May 2010 are far less shallow than those seen in December 2009 and February 2010. There is growth in IPv6 traffic! While at the start of the process we had to use a magnifying lens to see the changes, they are definitely becoming more obvious.

ICANN will continue to assess the adoption of IPv6 worldwide and make reports at regular intervals. ICANN also encourages all organizations to make sure they are – or will be – implementing IPv6 on their networks.

Nonetheless, there are a lot of addresses and lots of new things to learn if you are only familiar with an IPv4 environment. But as we implement IPv6 across our networks we will see IPv6 addresses popping up in mail headers, system logs, traceroutes and all sorts of other places where IPv4 used to be used exclusively. Knowing quickly whether an address is part of your own network or someone else’s; whether an address is intended for private use or Internet use; and knowing whether an address is used by a transition mechanism or a native connection will help save lots of time.

Last year, ICANN staff worked with the staff at APNIC and the RIPE NCC to produce a single sheet that identified the key address groups, explained what they were and gave IPv4 examples of IPv4 equivalents where they existed. This year we have updated the sheet and you can grab a copy of the updated reference from here.

This reference will be useful for anyone working on an abuse desk, in a Network Operations Centre or a corporate IT department. Even if you don’t plan to roll out IPv6 on your own network in the next few months, you are likely to see it appearing on other networks. Using our cheat sheet can help bring you up to speed quickly and identify where to look for an address faster than by just consulting the on-line registries.

We want this reference guide to be as useful and current as possible, so as things change in the future we will produce further updates for you to use.

Today, we are pleased to provide a test version of the new WHOIS server for you to experiment with and provide feedback on. It is online at new.whois.iana.org. Here is a sample:

Here are some of the things worth noting with this WHOIS server:

• New format. The first thing that one would notice comparing the output is that we have adopted a new RPSL-style output format. It is a more predictable format that is commonly used by other WHOIS services, and also is easier to parse with a predictable “key: value” format.
• IDN support. We’ve improved the IDN support in this WHOIS server, so that we accept both the ASCII-based wire-format (i.e. prefixed with xn--) and the Unicode presentation format (encoded in UTF-8) as arguments to the WHOIS server. For IDNs, we return both formats in the result, with the U-label under the domain: key, and the A-label under the domain-ace: key.
• IP addresses. One of the great new features is IP address support. We maintain the global address space for both IPv4 and IPv6 and maintains the authoritative top-level delegation of address blocks. You can now query for any IP address and either get the top-level allocation (e.g. to a Regional Internet Registry), or its reserved status. This works for AS numbers too.
• Referrals. When a domain name or an IP address block is delegated to a more specific registry (i.e. either a top-level domain registry, or an RIR), and we have information on a WHOIS server that has more specific information, we’ll first return a refer: key and the WHOIS server with the more specific information. This effectively allows you to query IANA’s WHOIS service for any domain, IP address or AS number to determine the best place to look.

So, give it a try and let us know what you think. We only ask that you please not hardcode the new.whois.iana.org host into anything as this is temporary while we experiment. Ultimately the WHOIS server is anticipated to replace what is used today. Incidentally the existing WHOIS server is one of the oldest pieces of code still in service in ICANN so retiring it will be a pleasure for all concerned.

What you should be seeing is something like the following:

It even works on a mobile phone:

The three new top-level domains are السعودية. (“Al-Saudiah”), امارات. ( “Emarat”) and مصر. (“Misr”). All three are Arabic script domains, and will enable domain names written fully right-to-left. Expect more as we continue to process other applications using the “fast track” methodology.

ICANN staff are still finishing the processing of these domain’s delegations, but now that they are visible in the root zone it is fair to say these are mostly formalities. The remaining tasks include final technical verifications, updating the IANA WHOIS database and publishing the delegation reports.

Now the hard work happens in the countries which have their new IDN ccTLDs. They will now commence their own processes to launch the domains in a way that gives their communities access to put them to day-to-day use.

The ICANN meeting in Seoul was my first meeting as CEO, and coincided with the kickoff of the ICANN Strategic planning process, an essential basis for ICANN’s operational and budget planning process. Based on my experience with other organizations and Boards, I was interested in taking the planning processes of past years, and evolving it into an approach that identified key strategic focus areas that captured ICANN’s mission and mandate, namely:

• DNS stability and security;
• Consumer choice, competition and innovation;
• IANA and core operations and
• A healthy Internet eco-system.

These four focus areas were the building blocks used to identify strategic objectives, key strategic projects and perhaps most importantly, the tremendous community and staff work that will be undertaken in the next few years.

Underlying these four strategic areas are key values, or enablers, that cut across all of ICANN’s work. These are essential to ICANN succeeding in all of its challenges, and an important reflection of the principles by which the organization operates. These are:

• Multi-stakeholder;
• Collaborative;
• International;
• Transparent;
• Accountable.

In developing the plan we used the traditional stakeholder engagement processes and also added online survey tools, which allowed community members from around the world to vote on proposed strategic plan items during the live sessions in Seoul.

I would like to personally thank all of you who contributed to this year’s Strategic planning process. Your input and engagement is an important part of ensuring that the organization’s future truly reflects a bottom up, multi-stakeholder process. We look forward to your input to the implementation of the Strategic plan into the operational planning and budget preparations.

Warmly,

Rod

Rod Beckstrom
CEO and President
ICANN
22 February 2010

• We have been in contact with the administrators of .HT and they are alive and well, although understandably overwhelmed dealing with the tragedy there. Other ICANN fellows in the country have been contacted and accounted for. Regrettably, some have lost their homes and are impacted heavily by the tragedy.

• Some of the name servers for .HT are not reachable from outside Haiti due to significant damage to the local telecommunications infrastructure. Work is underway to re-establish Haiti’s links to the world through the Dominican Republic.

• Despite some of the DNS infrastructure not working as expected, the DNS is a highly resilient protocol, and the .HT domain continues to function through a number of sites located outside of Haiti. Haiti’s name server partners are aware of the situation and also taking additional measures so that should technical reachability of Haiti deteriorate, function of .HT can continue uninterrupted.

Functioning telecommunications can make a real difference in recovering from a major natural disaster. The naming and numbering infrastructure is just a small piece of this, but we want to be sure it continues to function so that it is not the obstacle that prevents people communicating. We’d like to thank all our friends and partners, particularly those in Haiti, who have been working the last couple of days to ensure we can best help the community emerge from this disaster.