Public Forum: Open Discussion ICANN Meeting - Cairo Thursday, 6 November 2008 >> We would like our ICANN members to take the stage, please, so we can begin our public forum. Again, if the ICANN board members could take their places on the stage, our chairman would like to begin the second portion of a public forum. Again, would the ICANN board please take their seats at the head table so that we can begin our portion of the public forum. Thank you. Welcome again, chairman, board of directors, ICANN, Peter Dengate Thrush. >>PETER DENGATE THRUSH: Thank you. Could you turn the microphone up. Thank you, thank you. Welcome back. I hope the coffee was sustaining you, we now have a short period until lunch and to make it easier for public comment, we are dispensing with any further reporting. The reports of staff are available on the Web site. You've had many conversations with them during the course of the afternoon sessions anyway so I'm declaring the public comment period open. We have a roving microphone delivered by staff if you have a comment about any topic, you have a chance. I see Andy Van Couvering (phonetic) wishing to make a comment. >> Thank you, thank you, Peter, thank you, what portion of the board is here. I've been very interested in the new gTLD process and I thank the staff for the enormous amount of work they've done and I'm very pleased to see that we're finally moving forward on this. I also appreciate that this is in many ways an objective process so that if you do complete the application properly, your TLD will be approved. However, at the core of this process is one of the most subjective process -- one of the most subjective decisions that can be made which is that your application is evaluated by a panelist. We do not know who that panelist is. We do not know his or her qualifications, and we do not know his or her instructions from the staff. So for instance, with regard to financial stability, do you have the foundation to actually do this. I represent NYC, I have three budgets that I take to the investors. One is the rice and beans budget. One is the reasonable budget. One is the fully loaded budget that I would give to venture capitalists. Which one do I submit to ICANN? How does this panelist know that this is reasonable? How do I have any expectation of success or knowledge of whether my application will succeed based from this one panelist, especially with no communication back and forth, a single chance for review, and I could spend a lot of money and a lot of time and face a rejection. So I think this is highly subjective, and I would like to see some more clear criteria around this. I think it's a big risk, I think it's -- I know that more than $185,000, this is scaring people away. There's simply no way to communicate surety to an investor. Thank you. >>PETER DENGATE THRUSH: Thank you, Andrew. The question, as I take it, we'll try to get an answer if we could get one quickly. The question seemed to be what are the evaluation criteria used in the evaluations. Kurt, are you able to give us sort of a five-line answer to that. Microphone, 1, please. microphone 1, please. >>KURT PRITZ: Yes, very briefly, because we don't have time -- and I'd be happy to take any questions offline -- is that ICANN certainly -- ICANN intends to post a public tender to solicit the dispute resolution providers and that will be a public process so those who are retained to evaluate applications also, so the evaluation process tender process will be very public, and those who are providing the service will be known to the applicants. The second point is certainly the evaluation is a balancing between very objective criteria, which cannot scale with business models, in an attempt to create scalable criteria to accommodate different business models and different economic situations. We think essentially the evaluation and passing the evaluation is, you know, not a very high bar and that the applicant should have a high degree of surety going in whether its application will be accepted. >>PETER DENGATE THRUSH: Thanks, Kurt. Can we move next. >> Number 4. >>AIZU IZUMI: Hello. My name is Aizu Izumi. I'm the outgoing member of the At-Large Advisory Committee after five years, and it's been a real interesting challenge with the Mr. Hamadoun Touré, secretary-general, mentioning the interesting process of the civil society, because I was there in Tokyo when he talked about this NGO. I would like to make some friendly amendment to the fact what he's mentioned. It was not the government of Taiwan who was claiming as an NGO. That was not a dispute at all. The comment with China asked the adoption of the U.N. rules and procedures and requested NGOs be by the Taiwanese government. It wasn't the rule of the Chinese government to do so when they went to negotiation. I was there to be the part of the negotiation and finally reached a compromise. So, but all in all, the civil society [inaudible] and elsewhere have made a great effort to make the process a really multistakeholder event. And it was an uphill battle. And we tried to make something similar to what we exercise here at ICANN, that in the end, perhaps the civil society obtained somewhat a similar place or role within this, just like the GAC in ICANN. I don't think we still have a level playing field. Just one comment on the ccTLD item again. Being a member of the individual users committee, I would like to ask all the people involved during the distribution of the organization, the registration of the governments or the users, to please listen to the individual users' voices in your own countries in the process of selecting the registry or how to operate that. In Japan, as I mentioned already, the government are starting the formal procedure to discuss these and make an open sort of process that the trade associations, the business associations, as well as the consumer groups and academia and experts all invited in public process with public comments to reach a consensus with next year's introduction. And I think something similar could be shared, even though it's under the sovereignty of each nation. I think the users, among others, have the right and obligation to participate into the processes. Thank you very much. >>PETER DENGATE THRUSH: Thanks. Could we go down here, please, number two. >>STEPHEN KELLEY: My name is Stephen Kelley, I'm here on behalf of Far Further, a U.S. organization and a gTLD initiative. We are immensely grateful for the opportunity that ICANN is carefully and cautiously orchestrating. We have to acknowledge that without your effort and that of your staff, this room would likely be empty and we would be pursuing other initiatives and opportunities that may be less exciting and less financially appropriate than what we have here before us today. However, among our investors, among our constituents, our council, even our employees, we, among others, share a great concern over the current and proposed draft guidebook and certain financial ambiguities and operational instances that are stated within it. As hard as you have worked to bring us here, we have worked very hard for a number of years to follow you here. And we want to continue doing that within, as we all acknowledge, a difficult and ever-changing global economic environment. As that changes, it is even more important that we establish something within this organization that is consistent, that we can rely upon, and not worry about any change tomorrow. As you report to your people, we report to our people. And to do so with ever-changing ideas and concepts, a different and perhaps delayed schedule makes it difficult on those organizations, we -- to do exactly in this marketplace for ICANN and global Internet community that ICANN seeks. So we would like to present to you a compelling argument, simply by our presence here, that we need to move forward, without further delay, with a clean and unambiguous document that favors the end result that we all want to reach. And do so in a very efficient and prudent economic fashion. And that, to us, means no further delay in the process implementing or accepting applications within the soonest or the earliest possible quarter, without the risk of it being delayed another quarter or another two quarters. Having said that, we want to leave you with our best wishes and greatest regards. >>PETER DENGATE THRUSH: Thank you for that. And thank you for coming and taking part in the process. We tend to hear a lot from people who want the process to be slow on -- we'll keep going down that line for a while. >>MARCUS FAURE: Marcus Fauve, CORE. Sorry for my untimely comment earlier. Like others here, I would like to talk about the draft RFP. We've heard that there's some concern regarding numbers. I would not like to concentrate so much on the 185 application fee, although we think it's an issue. It's more about the 75 recurring annual fee that is the minimum payment that ICANN has envisioned. CORE is convinced that although a limit of this magnitude will only allow two kinds of applicants. >>PETER DENGATE THRUSH: Just speak up a little. Get the microphone a little bit closer. Thank you. >>MARCUS FAURE: CORE is convinced that those kind of minimum yearly payment will only allow two kinds of applicants. One applicant with a hail Mary bank roll, and, B, copies of the dot com model. As the rest of the document clearly addresses a larger variety of models, this point should be made consistent as well. So we have taken the initiative to develop a model that addresses this. I don't want to go into the details here, but the basic idea is that as long as the registry has an income of less than $1 million, it should be considered to be in survival mode, and ICANN should only charge its costs that are directly related to TLD operations, such as the IANA function. When it crosses this line, ICANN should also be allowed to consider its overhead costs, such as meetings like this one. Doug Brent has given us a bit of his time which we have used to present our model. And he said that at first glance, what we developed seems to make sense. And, therefore, I would like to propose that ICANN allows us to work directly with the staff to achieve a viable and timely solution for this question. We at CORE to like to avoid a situation where people feel that after five years, the result of the new gTLD process is just a monetary shootout or, looking at our meeting schedule, a Mexican standoff. CORE is, like ICANN, a nonprofit organization with the aim to improve the TLD space. And we would be eager to work with you and offer our help to add a little registry perspective to the process. So I'm asking for your kind consideration of our proposal. Thank you. >>PETER DENGATE THRUSH: Thank you. And behind you, sir. >>MASON COLE: Thank you very much. My name is Mason Cole. I represent oversee.net, a U.S.-based company in the domain name space. We have over 200 employees. I have a general comment about a growing concern that I and some of the other in the room have with ICANN policy development process. For companies that are in our industry, ICANN has effectively, even though it's not intended, to become a regulator. ICANN created our industry. It's encouraged competition in our industry. And as a result, ICANN has a responsibility to our industry. But increasingly, unfortunately, ICANN has sought to enact rules that, if implemented, would dramatically impact our and other businesses, often without significant metrics or without any basic research or evidence to support the effort. The -- Excuse me. The problem behind these proposals is invariably a perception of harm that may or may not actually exist. So, surely, community members who are interested in changing policy owe it to the companies and the registrants to do some basic research to have fact-based rather than opinion-based policy development. So in creating competition in the industry, I would encourage that ICANN continue to allow the latitude for competition to exist in our industry. Thank you very much. >>PETER DENGATE THRUSH: Thank you. And behind you. >>PAUL STAHURA: I am Paul Stahura, the founder of eNOM. And I have four brief points about new TLDs. Number one, many of you know me, and that I've been waiting ten years to operate a TLD. So you know I will be an applicant. And I'm also a backend provider for more applications. Number two, we think the RFP is a strong and well-prepared document. It reflects more than 18 months of community input and discussion. It's 98% of the way there. Number three, our applications will respect and protect I.P. rights. Number four, our biggest concern is that the application window slips past Q2, 2009. Subsequent to the Paris meeting, global business and community awareness and interest is very high. There are many backend providers like eNOM spreading the word. So we, the Internet community, have done a great job to get applicants back to the starting line. Our engines are running. Don't let us run out of gas before you start the race. Open the application window in Q2, 2009. Thank you. [ Applause ] >>PETER DENGATE THRUSH: Sir. >>DIRK KRISCHENOWSKI: My name is Dirk Krischenowski, and I'm founder of the dot Berlin initiative. We are here for the 11th meeting on -- in a row, ICANN meeting. And I'm hopeful every time, since the timeline ICANN publishes before the ICANN meeting looks very promising to us and others. But with us, also the community of Berliners is looking forward to acquire its top-level domain, dot Berlin. But every time we are going back to our community in Germany, we are disappointed, disappointed about the three- to six-months delay in the new TLD process, which makes up nine months from now before the next round actually opens. I call this a consecutive pregnancy of ICANN. And what is usually done when a pregnancy will not end naturally is cesarean section is the method of choice for both saving the life of, in our case, I would say, the new TLD applicants, and ICANN. I'm also speaking on behalf of the city TLD stakeholder alliance, the city TLD initiatives of Barcelona, Berlin, Hamburg, New York City, and Paris have formed on Tuesday. Our interest group is planning to become part of ICANN's structure and framework. And we invite others to join our group. And we are happy to do cooperation and collaboration with them. Besides the timeline, our group is also concerned about the 75,000 annual fees for city TLDs. This amount is unfair in comparison to the ccTLDs and existing gTLDs. It also endangers the business models of the city TLDs seriously. Therefore, and for these reasons, I would appreciate if the board will not allow ICANN to further postpone the introduction of the new top-level domain names. Please help to give birth to the new top-level domain names finally. [ Applause ] >>PETER DENGATE THRUSH: Thank you. Congratulations on the formation of your city TLD association. That seems a classic example of bottom-up self-organizing. Can we go over to this side. Number three, please, microphone three. The name then we'll come to 4. >> Okay. Sorry, my name is (saying name), from Nigeria, the TLD managers. This is actually my first ICANN meeting. I came here with quite a lot of expectation. But I have seen something quite different. I have seen quite a lot of rows and grouses and infighting, if I would say, the Gs on one side, the CCs, the GAC. And there is so much suspicion and distrust. And the bottom line, really, is that everybody's talking and nobody's listening. The fallout I see already, with witness in AfriNIC being moved from, I think, Ethiopia to Mauritius because of suspicion of involvement in dot Africa. I also see it in the new gTLD, which I do not believe serves the interest of the user, is it competition that's our goal? Is it transparency that is our goal? Or should be a subset, what really are we driving at in this new process? My submission is that each is saying something, and we need to pause to hear each person. The ccTLD space, with its sovereignty issues, is talking about governments having the right to decide how to populate their domains and have a basic right to ensure that their citizens have access to what they will call a (inaudible). It is not the same space as the gTLDs. They are also saying they need an avenue to propagate their ideas. I am thinking with this new process, we will be able to true up the dot tels and the dot mobis that I feel are very innovative, with the new process, would these great innovations have happened or would they have been stifled? So we need to sit back and listen to each other and need to realize that we need to walk together to achieve a desired aim, which is to make the Internet better for the end user, not for the registries or the registrars. There are tools in the process. But we need to make it better. And I feel that the new process, its pricing, its system, will stifle innovation by all parameters and will not be in the best interest of the Internet community. Thank you. >>PETER DENGATE THRUSH: Thank you very much. Can we come down to number 4 on this side. >> Thank you very much for convening this conference here in Cairo and giving us the opportunity of participating. [ Applause ] >> The ICT in Egypt and in the Arab world is following with tremendous attention everything that is being done. I will give the rest of my remarks in English. My name is (saying name). I'm CEO of (No audio)-- I understood very little of what they discussed. (No audio) But I was astonished to see that something very important was not discussed there, how offering ccTLDs and gTLD (inaudible) worldwide. From everything I've heard, ccTLDs will be offering IDN domains much sooner than the current gTLDs, were I in business today. Does it make sense to ensure that at least the current gTLDs are allowed to operate on the same timetable as ccTLDs? (inaudible) Arabic language version of my domain. I know how it is to deal with different governments. And I certainly do not want to go to 20 different governments to acquire 20 different versions of my name. I can't even fit 20 different ccTLD domains on my business card. Until now, I have gotten the very answer that maybe gTLDs will be there in time. Maybe not, though. Now, my question, dear board. And I would like to point out that this is a question, not only a remark. My question: How can I make sure that this threatening problem for the business world is not only maybe, but definitely solved? Or, in other words, as one of the businesses very much affected by your decision, can you guarantee me that both the current gTLDs and the ccTLDs will be offering IDNs on the same timeline? >>PETER DENGATE THRUSH: Thank you. Down back to the center line. >> Dear board -- >>PETER DENGATE THRUSH: I'm sorry. I thought it was -- we don't have time to engage in a debate at this stage. We're not giving answers to all of the questions. What we could do is take each question and provide a long, full, detailed answer. There is a lot to the questions that you posed. We think it is more important to hear you at this stage than to debate with you. >> Thank you. >>PETER DENGATE THRUSH: I thought I had made it clear. We're recording that you will and there will be answered published. Back to the center line. Nii, nice to see you. >>NII QUAYNOR: Yeah, I'm very pleased to be back. I'm convenor of AfriNOG. I'm here to make a comment on what appears to be a side effect. Recently, there's been news reports, both in Africa and in Europe, about a registry meeting, AfriNIC meeting, policy meeting in Ethiopia being banned because Ethiopia had an interest in hosting a names registry, dot Africa. This is surprising to me, because, you know, a (inaudible) registry is a registry. And there's, therefore, no real relationship to a names registry. So I'm actually here to sort of apologize and ask that you bear with us while we try to build a real consensus. Of course, we dislike politics or, you know, national situations affecting our technical policy development. We also don't believe that commercial interests should do the same. So I'm actually -- since it's evident that the action was engendered from the community, I'm asking that we be, you know, given some chance to try and regroup in the normal way, as we are doing right now in a bottom-up way, such that we are able to acquire the relevant know-how in terms of technical registry operation and be able to help our name services in general in the region advance. So it's more one of that kind of statement that I intend to make. So thank you very much. >>PETER DENGATE THRUSH: Thank you, Nii. Now, just before we carry -- just to let you know, the housekeeping arrangements, this session now needs to finish. We can extend it until 1:15. We will not finish the line. We are looking now for some additional time in the timetable. And as soon as we have that sorted, we will let you know. So. >>YOUNG EUM LEE: Young Eum Lee from dot KR. I'm in the ccNSO. I'd like to talk about the issue of geographical diversity, not with new gTLDs or IDNs. I'd like to point out that ICANN's core value number 4 focuses on geographic and cultural values at all levels. This value has been repeatedly emphasized in the D.O.C.'s midterm review of the JPA as well. I would first like to acknowledge the efforts of ICANN to adhere to this value by adopting the geographical diversity principle to its board and various committees, as well as the decision to hold the meetings in a rotating fashion in the five geographical regions. At the same time, however, I would like to point out some areas which I believe requires continued effort. Specifically, in the distribution of ICANN staff. According to the figures on the ICANN site, out of the 73 staff members and those of you in the audience, try to remember your region's figures, if you're from Latin America, you should know that there are no members, staff members, from Latin America. >> Sorry, I am. >>YOUNG EUM LEE: According to the site, there wasn't. I'm going -- okay. One. Okay. Four from Africa. 13 from Europe. And 45, or 62% of staff members which are -- are from the North American region, of which 41 are from the United States. In the case of the AP region, six staff members are from Australia, one from the Middle East, and four are from the rest of Asia, 32 countries. And although I think that the ccNSO chair, Chris Disspain, the president of ICANN, Paul Twomey, and a significant member of the board, Bruce Tonkin -- all from Australia -- and ICANN board chair, Peter Dengate Thrush -- from New Zealand -- are doing a fabulous job, and I have only the highest admiration for them -- [ Applause ] >>YOUNG EUM LEE: -- and personally have the warmest feelings, especially for Peter and Chris, I would hesitate to fully agree that the truly Asian perspective, which constitutes 40% of all Internet users in the world -- and I think this room is a reflection of some of that -- is represented by their presence on those important positions. I would like to point out that in terms of geographically diversity, ICANN still has some way to go in terms of reflecting the truly Asian perspective, and would like to publicly make an appeal to ICANN to consider this in the future, for example, in selecting the venue for its meetings and in hiring new staff members. And I would like to conclude that I have a secure day job. I am not in the job market. Thank you. [ Applause ] >>PETER DENGATE THRUSH: Thank you for drawing those statistics to our attention, Dr. Lee. Let's keep going down the line. Thank you. >>SUSAN REYNOLDS: Susan Reynolds speaking on behalf of dot gal, an initiative in favor of a domain for the Galician language and culture. Right now, we have the draft applicant guidebook, and we thank you for this. We appreciate it, because we know it's been hard work for you. But, still, the whole new gTLDs has taken a long, long time. In the international meeting in Paris, the expected timeline indicated that the process would be open around May 2009. Now we have to wait a few more months, maybe September 2009. We don't know; you don't know. Our community is awaiting the launch of the gTLD dot gal, dot CYM, et cetera. And in order to have a more democratic, multicultural, and global Internet, we need the process to be open as soon as possible. Because the sooner, the better. Communities -- community-based TLDs have well-defined characters. So we think the process will be easier for these type of communities. We are ready. We think other community-based TLDs should be ready. So we really ask you to open the process as soon as possible. And we're also concerned about the $185,000 fee. We think about the different possibilities of paying this fee, and we think we could do it. But what about small initiatives, small communities? What about them? Isn't it far too high? What is far too high is the $75,000 annual fee. We really ask ICANN to think about this. Thank you. [ Applause ] >>PETER DENGATE THRUSH: Thank you for that. Go down to microphone number 4. >>KIEREN McCARTHY: Yes, hello. It's -- I have a comment here from the online chat room which I wanted to read out from Danny Younger. He says, had Jon Postel been approached with the possibility of a name space devoted to the language and cultures of indigenous peoples, he would probably have said, "Good idea. You can have dot IP," and the name space would have come into being with no cost, no hassle, and no paperwork, just simplicity and trust. The pursuit of the noble should not require $185,000 entry fee. Why stifle innovation and worthy products by imposing this rather significant barrier to entry? >>PETER DENGATE THRUSH: I other aspects of life 15 years ago people yearn to go back to. In the middle. >>OLIVIER CREPIN-LEBLOND: Thank you. My name is Olivier Crepin-Leblond. I'm speaking as an individual, a bit like Mr. Joe average, Joe plumber of the Internet. [ Laughter ] >>OLIVIER CREPIN-LEBLOND: I have a statement which I've written earlier. And I was comforted in delivering it after I heard Secretary-General Touré's performance a bit earlier on. First of all, I would like to congratulate ICANN about the amount of work which has been done so far and the pace at which ICANN is changing, evolving and maturing. I would like to talk specifically about IPv4 and IPv6, call it migration, transition, cohabitation. I don't want to get into arrangements here. It's about the fact that IPv4 address space has been depleted. It is the fact that IPv6 opens the door to a huge amount of address space and can therefore be seen as the main solution about IPv4 space depletion. In the past few days, I have spoken to several people in the ICANN board and the ICANN community. There is clear consensus -- there's no clear consensus, sorry, about what should be done. Previously, I consulted several RIRs, and through their mailing list, and I know the RIRs are working hard on this subject. What transpires, though, is that there is a real need to coordinate all those efforts to promote IPv6. This is such a hot issue in the rest of the world, yet while several sessions touched on this, on this subject in Paris, there was no -- well, there was a total lack of any session about v4 and v6 here in Cairo. ICANN has done a huge amount of work with regard to names. I would therefore like more focus on the second end of ICANN, the numbers, which at the moment look like the poor child in the ICANN family. Until now, ICANN has been reactive on this subject. It needs to become proactive because if nothing is done and it fails its core function, its core mission to ensure the stability of the Internet, the very fact that so little was done in time will be taken against ICANN. I therefore suggest more IPv6-related sessions in the future conference in Mexico, and I also suggest a special cross-constituency fast-track working group to identify, evaluate, and implement everything that ICANN could do or should do to promote IPv6 and to coordinate these efforts with the RIRs and NROs. Come on, ICANN, you can do it. Thank you for listening. [ Applause ] >>PETER DENGATE THRUSH: We sure can. Ron. >>RON ANDRUFF: Good morning. Thank you, Mr. Chairman. Ron Andruff, member of the business constituency, but speaking in my individual capacity. I would like to echo the comments of many here that the staff has created a very workable document. But there are some edges that still need to be knocked off, and I would like to put a sharper point on a couple of those elements. The first is with regard to the registry operation fee, that 75,000 that's talked about. I just would like to make sure that the staff and the board understand that if, in fact, there is such a large number, that would have to be recouped in the wholesale cost to the registrars who would then mark the place up considerably higher than it normally would be, meaning that ultimately the end registrant or consumer would pay a higher price. And of course none of us want that. The second point I would like to speak about is Module 4, and that's the section 4.2.3, the comparison evaluation chart. The operator must score 11 of 12 points or 92% to be declared a clear winner. And this doesn't account for human fallibility. And I speak as someone who has founded a company, a registry, in dot travel, and we had gathered the travel and tourism community, 22 sectors, as they determined and we were told that we did not represent community. So human fallibility has to be factored in, and therefore we would like to recommend that at least 10 of 12 points, or 83% as an example, be somewhat of a measure. The third point is transliteration. The notion that every label should have $185,000 fee attached to it is incongruous with ICANN's cost recovery concept. Should an applicant pass all the criteria and be awarded the right to manage a string on behalf of a particular community or simply a generic TLD, the additional cost of $185,000 simply to review the transliteration of that name is unconscionable. How much could it cost to review the transliteration into Cyrillic, Arabic, or Kanji characters? $5,000 per review is probably still too much, but the fact is it would take that kind of number as opposed to 185. Secondly, one could argue that allowing a second entity to lay claim to a transliterated name of another applicant contravenes the confusingly similar element of the RFP. And that is to say, it forces an applicant to spend further financial resources on the challenge process for no valid reason to defend its global IDN-based string that is the transliteration of its ASCII string. That money would be better spent in development of the TLD. Third, ICANN's responsibility, stability and integrity of the net and allowing two registry operators to run what effectively is the same string is willingly creating huge potential for resolution collisions and user issues that are completely unnecessary. Finally, allowing applicants to gain authority over their respective ASCII and IDN names -- that is, all transliterated names requested and approved -- would allow a registrant -- a registry to offer registrants a combination of both ASCII and IDN names they wish to registry without concern for any collision in the DNS. The last issue I would like to raise is that of the four-month awareness campaign. We have heard from many in this line and I'm sure we will see many comments online in the respective places, but as pointed out by Kurt Pritz this week, the awareness campaign is already happening. What is the rationale for suspending the process once the RFP is ready to go. Clearly, no entity that sincerely wishes to manage a registry can prepare an application in four months. Speaking from experience, at minimum, one year of preparatory work is necessary, and perhaps two, and therefore the notion that a new potential applicant can hear about a new gTLD and then 16 weeks later deliver a well thought through application has zero merit. I encourage the board to instruct the staff to move forward with the four-month campaign in January 2009to ensure that applications can be submitted in Q2 2009 as originally suggested. Finally, with regard to improving the contract terms so that agreements are fair and equitable to all parties, I leave that to the lawyers and the ICANN community to comment on, but clearly that also needs to be redressed. Thank you very much. >>PETER DENGATE THRUSH: Thank you for the clarity and brevity of those submissions, Ron. Mr. Palage. >>MICHAEL PALAGE: Thank you. Two points briefly. The first is with regard to the document that was leased earlier this week regarding the board review. I have done a quick cursory review of the document, and the one issue that I believe has not been addressed that should is the issue of term limits for the CEO. I believe that term limits are an important safety mechanism to prevent ICANN, the organization, from becoming too closely aligned with the personality of its CEO. Term limits are an important mechanism. There are term limits for most ICANN -- for the ICANN board. The GNSO, in its recent review, imposed term limits on council members. If you look at the IGOs, there are generally two term limits for the Secretary-Generals. So I think term limits for the CEO is something that should potentially be added to the board review document. Second point, and it has to do with some of the comments from the ITU Secretary-General Touré. During his discussion earlier today, he made a point several times of talking about how the ITU did not get involved in operational issues. And I think one of the important things ICANN needs do, whether it's viewed as a technical coordinating body or a regulator, it needs to stay out of operational issues. And I think that that's a line that continues to blur. ICANN, notwithstanding provisions in its bylaws, does operate the dot INT and dot ARPA registry, it operates a root server, and with its most recent proposal to sign the root, we see ICANN becoming more and more involved in operational issues. I think there needs to be a clear bifurcation between operational issues and oversight issues. Thank you. >>PETER DENGATE THRUSH: Thank you, Mike. >>MICHAEL PALAGE: One final point. Just let the people speak, everybody in the line. It would help. >>PETER DENGATE THRUSH: Thank you. [ Applause ] >>PETER DENGATE THRUSH: Next. >>ARLENE PAREDES: Thank you. My name is Arlene Paredes. I am from NETPIA. We are an ICANN registrar in South Korea, but we do have an office in Manila, Philippines, so I will probably see some of you in Manila next year. I have three points and it is based on the beautiful words on the gTLD program side which are openness, change and innovation. After reading the RFP, sad to say the openness is not there, at least not yet. We are hoping it would be more open in terms of details, as the draft comes to progress and is finalized. From the point of view of an investor, we don't know yet what we're getting into, how much refunds would be there in case refunds would happen, as, of course, an application progresses. And in terms of the registry fee, which is at $75,000, we don't know if that's for everyone, if it's been decided, and if every kind or every diverse kind of applicant has been considered. And having said that, I will go into innovation and change. I would just like to remind ICANN that not all great innovators have deep pockets and even the most amazing change can be deterred by unreasonable cost. That's all and thank you. >>PETER DENGATE THRUSH: Thank you. Just a warning. This may be the last one before we take a break. But we are coming back and you will all be heard. >>MICKEY BEYER-CLAUSEN: My name is Mickey Beyer-Clausen and I am the founder of Pervasive Media. First of all, I would like to applaud ICANN for recognizing and promoting the potential of domain names to lay the groundwork for better Internet. And for the great foundation found in the very well-written draft RFP. However, representing a new entity intending to apply for new gTLDs, it is critical for funding and planning purposes to have short deadlines and no delays. We need to be able to trust announcements from ICANN. It is my hope that ICANN will seriously consider pushing the new gTLD process through as fast as possible with no further delays. If not, ICANN would be favoring established entities with other revenue streams that have time to wait. New entities are fragile to changes and delays, especially in this financial climate. My second request is that ICANN reconsider the annual maintenance fee. ICANN already receives 185,000 application fee covering the cost for this new gTLD process. $75,000, or 5%, whichever is highest, is an exceptionally high fee to pay to ICANN for compliance, registry liaison, and possibly increased registrar activity. Thank you. >>PETER DENGATE THRUSH: Thank you. Okay. We are going to stop now for lunch. Sorry we got just to there but we have to stop somewhere. Here is the proposed timetable for this afternoon. We will take a break now for lunch until 2:15. We will then have a very shortened President's Strategy Committee report and workshop from 2:15 to 2:45. If you are not interested in the President's Strategy Committee, you can take a longer lunch. We will then come back to this public forum from 2:45 to 3:30. 2:45 to 3:30, and the board has obligations involving its international visitors from 3:30 onwards. >> Peter can I just at for those are fretting in the line, we will take your names, in order so that you haven't invested all that time in waiting. So don't worry about that. >>PETER DENGATE THRUSH: So your place in the queue is preserved. Thank you, Paul. So that's it. We'll stop for lunch. Just those times again. Lunch until 2:15. President's Strategy Committee until 2:45. And then the forum until 3:30. Thank you all. [ Lunch break ]