AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
ALAC Liaisons and Representatives
At-Large Review Implementation Plan Development
Page History
...
Applicants from developing economies requiring relief (#10): ALAC has long been of firm belief that ICANN should offer a beneficial pricing to applicants who need a rigid criteria regarding location, community service and financial need. We continue to charter and encourage the "JAS" working group to explore ways to reduce barriers within the ICANN application framework and advocate cost reduction for worthy applicants. We reject the role, envisioned by some ICANN stakeholders, that would establish a subsidy fund and/or engage in external fundraising. The effort of ICANN to empower applications from all parts of the world must not be one of charity, it must not pit applicants against each other to demonstrate who is most "worth" for a limited pool of subsidy funds.ICANN staff's refusal to even discuss the concept of differential pricing has hampered attempts to research potential areas of cost saving within the current application framework. And while the Board response to Scorecard # 10 is to await the final work of the JAS, it has already explicitly rejected early JAS appeals for lowered pricing at a previous meeting. We strongly endorse the GAC's effort to request the ICANN Board to reconsider this regressive and anti-competitive position. And we encourage ongoing monitoring of the costs to administer the gTLD program to determine where price reductions may be enabled for these applicants while maintaining over general principles of overall cost-recovery (see Theme 4 below).
Theme 4: Operational Readiness and Scalability
Scorecard
...
item 3
...
ALAC shares all of the GAC concerns and recommendations related to ICANN's readiness to expand the Root Zone, sufficiently to accommodate the large expansion of gTLDs envisioned by the number of current applications-in-waiting. We would note that only the vested interests within ICANN are pushing for a massive round of simultaneous applications and approvals. We would advise a more staggered approach, with a steady timetable of approvals and delegations. Doing so would allow for the kind of careful technical monitoring (and appropriate compensation) demanded by the GAC recommendations, and would also have the side-benefit of providing more precise cost calculations for administering the approval/delegation process. Such calculations will be of great value to the efforts to determine what cost reductions are possible for applicants to whom current pricing is an unreasonable obstacle to entry (Scorecard #10, Theme 3 above).
Theme 5: Business and Market Considerations
Scorecard items 4, 5
Regarding market and economic impact (Scorecard #4): ALAC believes that the market and the public interest is best served by a variety of (well regulated) strings and business models. ICANN should not be in the business of evaluating business models beyond the sustainability of the plans (which are an Internet stability issue). Applications much have contingency plans of what to do in case of registry failure, and ICANN must have similar default plans that result in minimal disruption for owners of domains in financially failing TLDs. However, we believe that "public benefit" declarations within TLD applications will be of dubious benefit, and in any case subject to substantial modification (and difficulty of enforcement) post-delegation. We have already seen registries such as .pro significantly alter their business models from what existed at launch -- while perhaps unfortunate, such market-driven practice cannot and should not be unduly constrained. The only exception to this are self-declared community applications, in which we support the GAC call for "Due diligence or other operating restrictions to ensure that Community-based gTLDs will in fact serve their targeted communities".
Regarding cross-ownership between registries and registrars (Scorecard #5): The At-Large Community was an active participant in the ICANN Vertical Integration Working Group. Our participants in that group were as split in their opinions as the working group was in general when it failed to reach a consensus recommendation.
The above notwithstanding, ALAC wishes to re-iterate its general consensus on a number of points that should be considered regardless of the final cross-ownership regime:
- It is essential that there be mechanisms in place to ensure that cultural and IDN TLDs are not disadvantaged by the rules. Specifically, there is a fear that under some regimes, the requirement to use ICANN accredited registrars and to not self-distribute could jeopardize TLDs that will have a specific regional focus or those using less common scripts or languages. The lack of registrar interest or registrar capability could potentially impact the viability of just those new TLDs that we most want to succeed.
- There should be viable ways for single registrant TLDs to operate effectively. In such a single registrant TLD, all 2nd level domains are used by the registry itself (or its corporate parent) and are not made available to outsiders. The registry controls, and is legally responsible for, all 2nd level domains. The largest
Theme 5: Business and Market Considerations
Scorecard items 4, 5
Regarding market and economic impact (Scorecard #4): ALAC believes that the market and the public interest is best served by a variety of (well regulated) strings and business models. ICANN should not be in the business of evaluating business models beyond the sustainability of the plans (which are an Internet stability issue). Applications much have contingency plans of what to do in case of registry failure, and ICANN must have similar default plans that result in minimal disruption for owners of domains in financially failing TLDs. However, we believe that "public benefit" declarations within TLD applications will be of dubious benefit, and in any case subject to substantial modification (and difficulty of enforcement) post-delegation. We have already seen registries such as .pro significantly alter their business models from what existed at launch -- while perhaps unfortunate, such market-driven practice cannot and should not be unduly constrained. The only exception to this are self-declared community applications, in which we support the GAC call for "Due diligence or other operating restrictions to ensure that Community-based gTLDs will in fact serve their targeted communities".
Regarding cross-ownership between registries and registrars (Scorecard #5): The At-Large Community was an active participant in the ICANN Vertical Integration Working Group. Our participants in that group were as split in their opinions as the working group was in general when it failed to reach a consensus recommendation.
The above notwithstanding, ALAC wishes to re-iterate its general consensus on a number of points that should be considered regardless of the final cross-ownership regime:
- It is essential that there be mechanisms in place to ensure that cultural and IDN TLDs are not disadvantaged by the rules. Specifically, there is a fear that under some regimes, the requirement to use ICANN accredited registrars and to not self-distribute could jeopardize TLDs that will have a specific regional focus or those using less common scripts or languages. The lack of registrar interest or registrar capability could potentially impact the viability of just those new TLDs that we most want to succeed.
- There should be viable ways for single registrant TLDs to operate effectively. In such a single registrant TLD, all 2nd level domains are used by the registry itself (or its corporate parent) and are not made available to outsiders. The registry controls, and is legally responsible for, all 2nd level domains. The largest projected use is for corporations where the TLD relates to a trademark, but it could also be used for not-for-profits, charities and NGOs. The specific issue is that if there is no demonstrable added value to registrar involvement (since there is no consumer and no competitive issues), such intermediaries should not be required. The benefit to the gTLD eco-system of such gTLDs is that they will serve to acclimatize users to the concept of new gTLDs and will facilitate their acceptance in the general case.
- Compliance will be a critical part of gTLD deployment. It is essential that the rules surrounding the new gTLDs be sufficiently clear and reasonably enforceable; and that ICANN put in place mechanisms to ensure reasonable compliance. The enforcement mechanisms must be sufficiently public that third-party scrutiny and whistle-blowers are welcomed to augment official investigative efforts.
Theme 6: Legal Considerations
Scorecard items 9, 11
Additional theme: Timing Considerations
...
( TO BE ADDED -- PLEASE HELP)
...
Proposal by Alan Greenberg:
...