Tag Archives: Philip Corwin

ICANN Board Decisions to become More Transparent by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoICA has long been an advocate for greater transparency in ICANN operations, especially in the decision-making activities of the Board. Back in May 2012, reacting to the announcement that the Board would no longer hold decisional sessions on the final day of each of the three yearly ICANN public meetings, we published a blog titled, “ICANN Board Meetings Should be Webcast Live”. Our view at that time was:

Just because all the ICANN meetings we have attended since ICA’s formation ended with a Board meeting doesn’t mean that particular scheduling is sacrosanct. But we think it’s very beneficial for the global Internet community that ICANN serves to be able to view its decision-making process – and that it’s a big plus for ICANN’s credibility and reputation to open that process to public view… Nowadays any public policy body that makes its decisions behind closed doors is going to be perceived as having something to hide… There’s a lot of U.S. DNA in the DNS. ICANN was created by the U.S. government and is a California non-profit corporation… Sessions of the U.S. House and Senate, and virtually every hearing and markup of every Congressional committee, are now Webcast in real time and then archived for future viewing.

ICANN should do no less. Every official ICANN Board meeting should be webcast in real time. When the Board is meeting telephonically then the Web audiocast should be available simultaneously. And all should be archived for future access and review. Only limited redactions should be made, such as when the Board is discussing internal personnel matters or when the proprietary and confidential information of a contracted party might be revealed, and then only if a rationale is provided. ICANN’s continued authority ultimately rests upon the consent of the networked, and in 2012 the networked expect open access to information about vital decisions with broad repercussions. And, as Supreme Court Justice Louis Brandeis once observed, sunlight is the best disinfectant.

Four years after we expressed that viewpoint, we’re happy to report that ICANN’s Board is finally taking a step toward meeting 21st Century expectations of information access. of At its meeting of May 15, 2016, ICANN’s Board adopted a Resolution on “Enhancing Openness and Transparency” that makes an overdue move toward providing transparency in regard to Board decision-making.

The operative portion of the Resolution reads as follows:

Resolved, the Board directs the President and CEO, or his designee(s), to work with the Board to develop a proposed plan for the publication of transcripts and/or recordings of Board deliberative sessions, with such plan to include an assessment of possible resources costs and fiscal impact, and draft processes to: (i) ensure the accuracy of the transcript; and (ii) for redaction of portions of the transcript that should be maintained as confidential or privileged.

Resolved, the Board expects to evaluate the plan in Helsinki, and if satisfactory to begin testing of the proposed processes relating to publication of transcripts and/or recordings of the Board’s deliberative sessions as soon as practicable after Helsinki.

The Rationale for the Resolution explains the Board’s reasons for adoption:

In support of the continued call for visibility into Board deliberations and processes, the Board has determined to make available transcripts or recordings, where appropriate, of the Board’s deliberative sessions. This effort to enhance openness is likely to also support the ICANN community in enhancing ICANN’s accountability, as it will reduce questions of how and why the Board reaches its decisions. This decision also directly supports ICANN’s previous efforts and the continued goal of operating as openly and transparently in its decision-making. ICANN is also acting consistently with the ICANN’s Bylaws, as set out in Article III, section 1 of the ICANN Bylaws, that, “ICANN and its constituent bodies shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness.” 

There will be issues before the Board for which confidentiality is still required, and that may require redaction of parts or withholding of full transcripts, and it is important that the community and the Board understand how those decisions will be taken. To that end, the Board is directing the development of a plan, which would include proposed processes by which those redaction decisions for confidentiality and privilege are to be made. That plan should be developed as soon as practicable, and should be ready for Board consideration during ICANN56 in Helsinki.

In a contemporaneous blog post, Board Chairman Steve Crocker shed a bit more light on the Resolution:

We’ve all been talking about trust lately, and the workshop gave the Board an opportunity to take a hard look at what we can do to build trust between ICANN as an organization and all of its stakeholders. This is also an ongoing discussion, and one that we all have a stake in. During the workshop, we considered concrete steps that the Board could take to increase our transparency and accountability. We agreed to post the transcripts and/or recordings of our deliberative sessions and, as a result of this discussion, passed a resolution asking Göran and his team to develop a plan for the implementation of this new procedure, also making sure that we respect confidentiality, as necessary. We know there is a lot of interest in our meetings and discussions, and we look forward to reviewing Göran’s proposal in Helsinki.

We look forward to hearing about the proposed details of the transparency plan when we attend the Helsinki meeting in a few weeks – where the community will also kick off its own discussion of Work Stream 2 accountability measures, including greater transparency within every facet of ICANN operations.

Ideally, the Board transparency measures should take effect as soon as possible, and reasons for redaction should be kept to a minimum and explained in all instances. While transcripts and audio recordings are welcome steps, especially for telephonic meetings, our preference remains for real time webcasts of all physical meetings of the Board. Public portions of the agenda could be addressed first, with anything requiring redaction left for the end of the meeting.

That would let the sunlight of transparency and the electric light of the video image illuminate all future Board decisions. ICANN and its stakeholders will be better off for the transparency this change will bring to ICANN’s most important decision-making process.

This post by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/icann-board-decisions-to-become-more-transparent/

U. S. Government Blasts China’s Draft Domain Regulations by Philip Corwin

Philip Corwin imageIn an unexpected move, the two top U.S. officials charged with the Obama Administration’s Internet policy have issued a joint statement severely criticizing draft Chinese domain policies. On May 16th, the State Department’s  Ambassador Daniel A. Sepulveda and NTIA’s Assistant Secretary for Communications and Information Lawrence E. Strickling issued an official statement titled “China’s Internet Domain Name Measures and the Digital Economy”. In it, they charge that “ the Chinese government’s recent actions run contrary to China’s stated commitments toward global Internet governance processes as well as its stated goals for economic reform”.

The focus of their ire are new proposed rules issued in March by China’s  Ministry of Industry and Information Technology. The officials describe them as:

draft measures that would require all Internet domain names in China to be registered through government-licensed service providers that have established a domestic presence in the country and would impose additional stringent regulations on the provision of domain name services …The most controversial provision of China’s draft domain name measures – article 37 – has attracted considerable international concern, as some have interpreted the article to mean that all websites with domain names registered outside China will be blocked, thereby cutting off Chinese Internet users from the global Internet.  

The statement also throws down the gauntlet in regard to China’s recent efforts to push alternative, government-centric models of Internet governance. In this regard, it states:

China’s approach to DNS management within its borders could still contravene, undermine, and conflict with current policies for managing top level domains that emerge from the Internet Corporation for Assigned Names and Numbers (ICANN), which follows a multistakeholder model in its community-based and consensus-driven policymaking approach.

While probably not affecting the content of the statement, the timing of its issuance may in part be to demonstrate a tough stance toward China’s DNS policy in advance of next Tuesday’s Senate Commerce Committee oversight hearing on the IANA transition and ICANN accountability. Committee member Ted Cruz has been peppering ICANN with questions regarding former ICANN CEO Fadi Chehade’s participation in China’s World Internet Conference (WIC) last December, and his agreement to become Co-Chair of the Advisory Committee to the 2016 WIC meeting. Many speakers at the 2015 WIC meeting defended Internet censorship and heightened government control.

Adding gasoline to the fire, the statement also lashes Chinese Internet censorship, stating in that regard:

The regulations would also appear to formalize an explicit system of online censorship by forbidding the registration of websites containing any one of nine categories of prohibited content, broadly and vaguely defined, and creating a blacklist of “forbidden characters” in the registration of domain names, adding an extra layer of control to China’s Great Firewall… What we do not accept is the exercise of aggressive authority over people’s use of the Internet or the ability of a government to prevent the world from reaching its people.  Sadly, this is exactly what Chinese authorities, through these recent measures, are trying to do. 

While such views have likely been advanced in confidential meetings between Chinese and U.S. officials, it is highly unusual to see such bold charges levied against another nation in an official statement.

China has yet to respond to the U.S. allegations, and it remains to be seen if it will moderate its position regarding the draft rules – or whether it will react to this criticism by digging in and implementing them. It is also unclear what effect implementation might have on burgeoning purchases of domain names by Chinese registrants, who have flooded the secondary domain market over the past year through high-dollar purchase of short letter and number domains, and who reportedly also account for more than half the purchases of domains originating from ICANN’s new gTLD program. The draft rules could make many registries and domain names off-limits for Chinese purchasers.

The full text of the statement follows—   

 

China’s Internet Domain Name Measures and the Digital Economy

May 16, 2016 by Ambassador Daniel A. Sepulveda and Assistant Secretary for Communications and Information Lawrence E. Strickling

Ambassador Daniel A. Sepulveda and Assistant Secretary for Communications and Information Lawrence E. Strickling

May 16, 2016

This post was cross posted to the State Department’s blog: https://blogs.state.gov/stories/2016/05/16/china-s-internet-domain-name-measures-and-digital-economy [1]

China is a force in the global digital economy and an important player in global Internet policy discussions. Today, more than 700 million people have access to the Internet in China, more than any country in the world. Several of the most valuable Internet-based companies call China home.  Global innovators and service providers from around the world, including from the United States, are eager to enter its market.

That’s why it is incredibly important that China use its power and influence in a manner that supports the continued development of the global Internet and the prosperity of its domestic digital economy.

Both of our countries participate actively in a range of international organizations and processes that discuss the global development and deployment of the Internet.  We have both argued that the current processes, which rely on the cooperation of all stakeholders including government, industry, and civil society, are working effectively for the Internet’s future development and management.

However, the Chinese government’s recent actions run contrary to China’s stated commitments toward global Internet governance processes as well as its stated goals for economic reform.

In late March 2016, China’s Ministry of Industry and Information Technology issued draft measures that would require all Internet domain names in China to be registered through government-licensed service providers that have established a domestic presence in the country and would impose additional stringent regulations on the provision of domain name services.

The regulations appear to create a barrier to access and force localization of data and domestic registration of domain names.  Whether driven by a motivation to increase control over Internet content in China or a desire to increase the quantity of Chinese-registered domain names, these regulations would contravene policies that have been established already at the global level by all Internet stakeholders (including Chinese).  If put into effect, these regulations would have potentially large and negative repercussions for everyone.

The regulations have led to expressions of concern in comments formally submitted by governments, including the United States, companies, and other stakeholders around the world that support an open and interoperable Internet.

The most controversial provision of China’s draft domain name measures – article 37 – has attracted considerable international concern, as some have interpreted the article to mean that all websites with domain names registered outside China will be blocked, thereby cutting off Chinese Internet users from the global Internet.  While Chinese authorities have clarified that the intent of the article would be to prohibit access to Chinese-registered domain names that are acquired from registries/registrars that are not in compliance with Chinese regulations, concerns remain that the language in its current form is vague and open to differing interpretations.  Even if applied to Chinese-registered domain names, China’s approach to DNS management within its borders could still contravene, undermine, and conflict with current policies for managing top level domains that emerge from the Internet Corporation for Assigned Names and Numbers (ICANN), which follows a multistakeholder model in its community-based and consensus-driven policymaking approach.

Other concerns with the measures include requirements for forced data localization and real name verification for the registration of Internet addresses.  For instance, the draft measures appear to mandate that all Internet domain name registrars, registries, root server operators, and others, maintain zone files in China, thereby compelling firms to create a system for their China operations, which is entirely separate from their global operations.  This forced localization, though not unprecedented in China, would potentially create new barriers to the free flow of information and commerce across borders and consequently infringe upon internationally recognized commitments on free expression and trade.  The regulations would also appear to formalize an explicit system of online censorship by forbidding the registration of websites containing any one of nine categories of prohibited content, broadly and vaguely defined, and creating a blacklist of “forbidden characters” in the registration of domain names, adding an extra layer of control to China’s Great Firewall.

The United States supports the open global Internet as a platform for free expression and economic and human development worldwide, and we support the growth of China’s digital ecosystem within that context. We welcome the Chinese adoption and creation of Internet-based technologies and services.

What we do not accept is the exercise of aggressive authority over people’s use of the Internet or the ability of a government to prevent the world from reaching its people.  Sadly, this is exactly what Chinese authorities, through these recent measures, are trying to do.  Such efforts will not only create undue burdens and challenges for enterprises, both Chinese and foreign, operating in China, but they will also diminish the view of China as a constructive partner in the development of the global Internet.  Furthermore, they will hinder Chinese technology and services from achieving acceptance outside of China.

We have listened to company concerns, consulted with diplomatic partners, and shared our views directly with the Chinese government, while calling for China to continue dialogue with a broad group of stakeholders as its draft regulations are revised.

The digital economy has become one of the most powerful engines for global economic growth.  If left unchanged, China’s regulations would undermine some of the most fundamental aspects of the Internet – openness, reliability, and interoperability – within China.  By creating its own rules for domain name management, China is threatening to fragment the Internet, which would limit the Internet’s ability to operate as a global platform for human communication, commerce, and creativity.

Lawrence E. Strickling [2] serves as Assistant Secretary of Commerce for Communications and Information and Administrator of the National Telecommunications and Information Administration. Ambassador Daniel A. Sepulveda [3] serves as U.S. Coordinator for International Communications and Information Policy at the U.S. Department of State.

Topics:

National Telecommunications and Information Administration
1401 Constitution Ave., NW Washington, DC 20230

commerce.gov | Privacy Policy | Web Policies | FOIA | Accessibility | usa.gov

Source URL: http://www.ntia.doc.gov/blog/2016/china-s-internet-domain-name-measures-and-digital-economy

Links:
[1] https://blogs.state.gov/stories/2016/05/16/china-s-internet-domain-name-measures-and-digital-economy
[2] http://www.ntia.doc.gov/legacy/about/bio_strickling.html
[3] http://www.state.gov/r/pa/ei/biog/bureau/209063.htm
[4] http://www.ntia.doc.gov/category/domain-name-system

This blog post by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/u-s-blasts-chinas-draft-domain-regulations/

ICANN and VeriSign Reach Deal for Ten Year .Com Agreement Extension by Philip Corwin, Internet Commerce Association

Internet Commerce Association logo: On February 11th VeriSign held its Fourth Quarter and Full-Year 2015 Earnings Call with stock analysts. In the course of the call VeriSign revealed that it had reached tentative agreement with ICANN to extend the .Com Registry Agreement (RA) by ten years, with the extension’s start coinciding with the effective date of the IANA contract transition. The current .Com RA is scheduled to terminate on November 30, 2018, with VeriSign having a presumptive right of contract renewal so long as it has effectively managed the premier gTLD and has not materially breached the RA.

Our review of the analyst call yields this preliminary analysis:

  • Verisign has negotiated an agreement with ICANN that would establish a new 10-year Root Zone Maintainer Agreement (with ICANN stepping into NTIA’s shoes) and link it to a 10-year extension of the separate .Com RA, both of which would commence on the date of the IANA transition. (So, if the transition occurs on October 1, 2016 – the date on which the current Congressional appropriations freeze on transfer of the IANA contract lapses — the expiration date of the .Com registry agreement would change from November 30, 2018 to October 1, 2026.)
  • The deal requires approval of the ICANN and VeriSign Boards, and then of the NTIA. It will be subject to public comment.
  • The deal does not lift the .Com price freeze contained in a separate Cooperative Agreement between VeriSign and NTIA. VeriSign retains its existing contract rights to petition for pricing relief if market conditions change sufficiently to restrain its .Com pricing power.

As we presently understand the situation, the Cooperative Agreement between VeriSign and the NTIA that imposed the .Com price freeze would remain unchanged and in place through late 2018, and any request by VeriSign to ease the pricing restrictions would be reviewed by NTIA and not by ICANN. That is important, because in 2012 ICANN’s Board approved a .Com renewal agreement that would have permitted four separate seven percent price increases during its six year term, and it was NTIA that imposed the price freeze urged by ICA. It’s also worth noting the near-final ICANN Accountability Proposal that will be delivered to ICANN’s Board next month restricts ICANN’s mission and core functions so that it cannot take on regulatory powers, including those of a competition authority.

ICA will carefully monitor this developing situation as it moves toward the public comment stage, when we will have an opportunity to review the actual written terms of the proposed agreement.

Our preliminary understanding of the agreement is based on the following statements made by VeriSign CEO D. James Bidzos during yesterday’s call:

ICANN and VeriSign are in the final stages of drafting the new Root Zone Maintainer Agreement to perform this Root Zone Maintainer role as a commercial service for ICANN upon the successful transition of the IANA functions… To ensure that root operations continue to perform at the same high level during the expected 10-year term of the Root Zone Maintainer Agreement, ICANN and VeriSign are in discussions to extend the term of the .com Registry Agreement to coincide with the expected 10-year term of the Root Zone Maintainer Agreement, ensuring that the terms of the two agreements are the same, will promote the stability of root operations, and will remove potential instability that might otherwise arise if the terms did not coincide…

While ICANN and VeriSign are in the final stage of preparing the Root Zone Maintainer Agreement and the .com Registry Agreement extension documents, there are several important steps that still need to occur including completing the drafting of the agreements, posting them for public comment and obtaining approvals from ICANN’s and VeriSign’s Board of Directors.

Additionally, under the Cooperative Agreement, we may not enter into the contemplated extension of the .com Registry Agreement without the prior written approval of the Department of Commerce. If the department does not approve the extension, then the current .com Registry Agreement will remain unchanged. We will provide periodic updates, as appropriate, on our progress toward these objectives…

So, first of all, I think it helps to just understand that we’re not actually changing the terms of the .com Registry Agreement. And this is not a renewal. This is an extension… In order to ensure the same steady, available, uninterrupted, secure and stable environment that we’ve been providing for three decades as a Root Zone Maintainer, it is also anticipated – we are discussing – the extension of the .com Registry Agreement for 10 years.

So at that point, should all of these conditions that I described earlier, for example, approval of ICANN’s Board of Directors and VeriSign’s Board of Directors, no changes whatsoever can be made to the .com Registry Agreement without the consent of the NTIA.

So subject to those approvals and the transition occurring, then we would have 10-year concurrent terms for the Root Zone Maintainer Agreement and the .com Registry Agreement. So what you would see is essentially a change of the date, the term, of the .com Registry Agreement.

That’s essentially the change. From an investor viewpoint, instead of a renewal in 2018, you would see a 10-year term that starts with the effective date of the two changes, the Root Zone Maintainer Agreement and the extended .com Registry Agreement. So, instead of November 30, 2018, you would see a date that is 10 years from the effective date of those two…

So, again, qualifying all of this to say that if we conclude our negotiations, we get all the necessary approvals, the triggering event that marks the “effective date” would then be the IANA transition occurring… The target date is September of 2016… I would just reiterate again that what we’re contemplating here, what we’re working towards, is an extension of the .com agreement. So, the terms wouldn’t change in the .com agreement…

So let me just say that, first of all, the terms of the .com agreement will not change, and the presumptive right of renewal, of course, would remain in the .com agreement. The .com agreement doesn’t actually address pricing. That’s addressed separately in the Cooperative Agreement.

The Amendment 11 of the Cooperative Agreement is the section that describes our contractual relationship with NTIA with respect to the root zone maintainer role. And that is the portion that it’s contemplated would essentially move into a new contract, the RZMA that we’re negotiating with ICANN.

Amendment 32 is a separate part of the Cooperative Agreement that addresses pricing with respect to our ability to seek a price change if we think it’s justified by market conditions. So I certainly don’t anticipate that that would change. That would remain. So VeriSign’s right to seek relief from price controls based on market conditions that would warrant it would remain…

I think the extension means that the date changes on the agreement. But any change to the agreement requires the consent of the NTIA. And so, I can’t speak for NTIA. This is their process. The part of the process we’re involved in would be to negotiate the Root Zone Maintainer Agreement with ICANN to present that along with a .com contract that has the date extended and present that to NTIA.

This is, of course, in response to their March 2015 request for a way to transition the root zone maintainer role and to take NTIA out of that process. So that will be up to them when they see it. So I think that’s what they asked for and that’s what they’re looking for. This is not a renewal in the sense that all of the normal things that happen during a renewal would happen. So I don’t quite see it that way…

I anticipate that we would have our Amendment 32 rights to petition based on changing market conditions for price relief. And also that, certainly, the agreement calls for the ability for VeriSign to seek so-called cost-justified price increases and that includes things like cost of implementing Consensus Policies or specific threats to the DNS that are extraordinary that we have to respond to – unanticipated expenses associated with responding to threats. So I don’t see those changing at all… What we’re doing here is we’re seeking an extension to the .com Registry Agreement. The Cooperative Agreement expires in 2018, and we are not seeking any change to that. That is up to NTIA. That is their process, their contract, so I would certainly defer to them… It expires in 2018, but it’s up to NTIA to decide at that point what happens.

 (Emphasis added)

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
http://www.internetcommerce.org/ten-year-dotcom-extension/

Final RPM Report Follows ICA Comment and Sets Stage for UDRP Review by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoDomain registrants have long voiced their desire for a comprehensive review and subsequent reforms of the Uniform Dispute Resolution Policy (UDRP). That goal is now in sight, and is set to proceed in the manner recommended to ICANN by ICA.

On January 11, 2016 ICANN policy staff submitted to the GNSO Council the “Final Issue Report on a Policy Development Process to Review All Rights Protection Mechanisms in All Generic Top-Level Domains”. That Final Report is culmination of a public comment process that started last October, in which ICA actively participated, considering how a review of the rights protection mechanisms (RPMs) for the new gTLD program should be related to an unprecedented review of the UDRP, the only ICANN Consensus Policy that has never been subjected to scrutiny since its creation. Domain registrants desiring a balanced approach to their rights versus those of trademark owners have a big stake in both reviews. RPMs should recognize and protect the rights of both domains and trademarks.

In its December 1st comment letter, ICA stated its preference for a sequential review process:

ICA prefers a separate and sequential approach for the reviews and subsequent reports and recommendations, with the RPM review preceding and thereby informing the UDRP review.

ICA further explained its practical and policy reasons for that preferred two-part approach:

Both domain registrants and trademark owner complainants deserve, after nearly two decades of unexamined use, a UDRP review and reform process that is accorded adequate time for comprehensive review and development of subsequent recommendations. This review of necessity must be preceded by the RPM review, as it was the intent of the GNSO Council in 2011 that the UDRP review be informed by that of the RPMs and by any changes made to them….We fully expect that there will be substantial interest in completing the RPM review prior to the opening of any second round of new gTLDs, and that consideration provides another reason for structural separation. If the RPM and UDRP reviews were addressed together, substantial pressure could arise to truncate the UDRP portion lest it delay the timing and adoption of final RPM recommendations. As a result this first-ever UDRP review could get short shrift and inadequate attention.

That ICA suggestion was essentially adopted by ICANN staff. In this regard, the Final Report suggests the following procedure:

Following review of community feedback received regarding the three options for a RPM review that were presented in the Preliminary Issue Report for public comment, ICANN staff recommends that the GNSO Council launch a PDP in accordance with what was presented as the third option in the Preliminary Issue Report: namely, to conduct a policy review of all the RPMs in two phases. The initial phase would focus on a review only of the RPMs developed for the New gTLD Program, and the second phase would focus on a review of the UDRP. The second phase may also include any issues identified during the first phase of the PDP that are more appropriately considered during the second phase. Cumulatively, the results of both phases of the PDP would be a full review of all RPMs developed to date for all gTLDs….Staff recommends that the work in the initial phase of the RPM PDP be performed by a standalone PDP Working Group that liaises with the recently launched PDP Working Group on New gTLD Subsequent Procedures as there may be overlapping issues arising during the work of both groups that would warrant careful coordination. Staff does not recommend folding in a review of the RPMs that were developed for the New gTLD Program into the scope of work for the New gTLD Subsequent Procedures PDP due to the likely complexity and size of that PDP….Staff also recommends that, upon completion of Phase One, the PDP Working Group submits a First Initial Report to the GNSO Council that is also published for public comment….The second, subsequent phase of work in the RPM PDP would be a review of the UDRP, ideally carried out by the same PDP Working Group….Staff believes that a benefit of this two-phased approach is a better alignment of the timing of the work on reviewing the New gTLD Program RPMs with the operational reviews of the New gTLD Program17 (including the CCT Review) and the PDP on New gTLD Subsequent Procedures. (Emphasis added)

The GNSO Council has already proceeded in harmony with that suggested approach. During its meeting of January 21st, Council adopted a Charter for The New gTLD Subsequent Procedures PDP Working Group that specifically prohibits it from addressing the RPMs, stating:

Second-Level Rights Protection Mechanisms: Proposing recommendations directly related to RPMs is beyond the remit of this PDP. There is an anticipated PDP on the “current state of all rights protection mechanisms (RPMs) implemented for both existing and new gTLDs, including but not limited to the UDRP and the URS…”. Duplication or conflicting work between the New gTLD Subsequent Procedures PDP and the PDP on RPMs must be avoided. If topics related to RPMs are uncovered and discussed in the deliberations of this PDP, those topics should be relayed to the PDP on RPMs for resolution. To assure effective coordination between the two groups, a community liaison, who is a member of both Groups, is to be appointed jointly by both Groups and confirmed by the GNSO Council. (Emphasis added)

That means that review of all the new gTLD RPMs—the Trademark Clearinghouse (TMCH) and related Sunrise and Trademark Claims service periods; Uniform Rapid Suspension System (URS); and Post-Delegation Dispute Resolution Procedures (PDDRPs) — should be the sole preserve of a new Working Group (WG) on all RPMs in all gTLDs. Following that review, it will proceed to review the UDRP and consider whether it should be reformed.

The GNSO Council will likely take up a Motion to establish that RPM WG, as well as adopt its Charter, at its next meeting scheduled to take place on February 18th.

Once Council takes that next step, ICA intends to fully engage in the review of the new gTLD RPMs and, of course, the UDRP review. ICA will advocate an approach that, while fully respecting the legitimate rights of trademark owners, brings greater balance to the exercise of all the RPMs and that helps to make the application of the UDRP a more consistent and predictable process in the future. We will of course keep our members comprehensively informed as the reviews proceed, and will solicit their feedback and guidance as critical questions emerge.

This article was sourced with permission from the Internet Commerce Association website here.

ICA Tells ICANN That Comprehensive UDRP Review Should Follow RPM Analysis by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoOn November 30th ICA filed its comment letter regarding the “Preliminary Issue Report on a GNSO Policy Development Process to Review All Rights Protection Mechanisms in All gTLDs” that was published for public comment on October 9, 2015.

ICA’s complete comment can be viewed at forum.icann.org/lists/comments-rpm-prelim-issue-09oct15/msg00021.html, and all 24 filed comments are available at forum.icann.org/lists/comments-rpm-prelim-issue-09oct15/index.html.

The principal question raised by the Report was whether the review and possible adjustment of new gTLD RPMs and the review and potential reform of the UDRP should be combined or separated. On that key decision, our comment letter said that the RPMs should be addressed prior to the UDRP review for these reasons:

We believe that the RPM review and the UDRP review each constitutes a highly complex array of interrelated questions and judgments, and that trying to combine the two into a single mega-review will tax any Working Group (WG) inordinately.

In particular, the UDRP review will constitute the first comprehensive inquiry into ICANN’s oldest Consensus Policy. It may address structural issues; such as whether ICANN should enter into uniform contractual agreements with all UDRP providers, whether there should be clear boundaries to prevent individual dispute providers’ Supplementary Rules from influencing decisional outcomes, and whether an internal appeals procedure should provide an avenue for a ‘UDRP Supreme Court’ to address and reconcile disparate decisions by different providers on nearly identical fact patterns.

…Both domain registrants and trademark owner complainants deserve, after nearly two decades of unexamined use, a UDRP review and reform process that is accorded adequate time for comprehensive review and development of subsequent recommendations. This review of necessity must be preceded by the RPM review, as it was the intent of the GNSO Council in 2011 that the UDRP review be informed by that of the RPMs and by any changes made to them. Further, as staff notes at page 8 of the Report, one result of “this approach is the fact that community consideration of the more general overarching issue concerning the comprehensiveness of all the RPMs as a set of aggregate protections for trademark holders in all gTLDs, as well as the issue of whether any of the new RPMs should be considered Consensus Policies like the UDRP, will necessarily be postponed to the second phase of work”. Unlike staff, we do not view that consideration as a drawback but as a far more responsible approach than considering integration of any of the new gTLD RPMs in legacy gTLD without knowing whether or in what manner they may be altered.

We agree with staff that “One benefit of this two-pronged approach is better alignment of the timing of the work on reviewing the new RPMs with the operational reviews of the New gTLD Program (including the CCT Review) and, conceivably, a new PDP on New gTLD Subsequent Procedures”. We fully expect that there will be substantial interest in completing the RPM review prior to the opening of any second round of new gTLDs, and that consideration provides another reason for structural separation. If the RPM and UDRP reviews were addressed together, substantial pressure could arise to truncate the UDRP portion lest it delay the timing and adoption of final RPM recommendations. As a result this first-ever UDRP review could get short shrift and inadequate attention.

Many of the other groups and individuals who filed comments also took the view that the RPM and UDRP reviews should be separate, with the RPMs teed up first.

What did surprise us was the reluctance of the trademark community to even contemplate a review of the UDRP, much less consider any changes based on nearly twenty years of experience with it.

The International Trademark Association (INTA) asserted that it is “is strongly opposed to opening the Uniform Dispute Resolution Policy (UDRP) to review as the UDRP has been functioning efficiently and well for over fifteen years. It is important to maintain this effective mechanism which combats the most blatant instances of cybersquatting within the domain name system. Any review or subsequent modifications could jeopardize the benefits that the UDRP is intended to provide to trademark owners.” Having attended INTA conferences along with thousands of others, and seen the money invested in global branding as well as the sector’s political influence, it strains credulity to believe that trademark owners could be “rolled’ in the course of a UDRP review.

ICANN’s Intellectual Property Constituency (IPC) warned “that the complexity of any review would be immense and the drain on resources considerable, with a risk of creating new problems via an overly complicated review process… the IPC has a serious concern that if a review were to be carried out, there is a risk of a polarization of views into two camps – each with a fear that the other camp would either dilute or overly strengthen the UDRP. Improvements sought by one side would be seen as potentially abusive to registrants, improvements sought by the other as potentially diluting the effectiveness of a mechanism for resolving disputes efficiently… if a review of the UDRP as a policy is to be considered, an “Expert Group” should be assembled to carry out this review.” For ICA’s part, we think that, just like war is too important to just be left to the generals, UDRP review and reform is too important to just be left to “experts” and must include participation by those with broader views of the UDRP’s impact on domain registrants and free expression, among other key considerations.

And UN agency and accredited UDRP provider the World Intellectual Property Organization (WIPO) opined that “the UDRP continues to function as intended. In its harmonized criteria and universal application, this anti-cybersquatting mechanism has come to be recognized as an international policy success… Destabilization of the predictable UDRP framework may have a range of unintended consequences. It would disrupt the body of precedent carefully developed by hundreds of panelists from across jurisdictions in tens of thousands of cases… Each day, the UDRP demonstrates the flexibility to meet the demands of an evolving DNS; it does not need system-wide updates that would imprudently limit this flexibility”. To the contrary, domain investors would respond that this “flexibility” is code for a lack of any binding precedent that makes the UDRP more of a casino game in a world of proliferating UDRP providers.

We are pleased that ICANN’s Business Constituency, of which ICA is a member, took a more balanced approach, stating, “While the BC believes that the UDRP is working well overall, it now seems timely to engage in a review of its performance with an eye toward considering possible improvements, so long as that UDRP review commences after completion of the RPM review.”

In response to the trademark community’s message of opposition and excessive caution, ICA added this final point to our comment’s Executive Summary, to wit:

Finally, we have strong disagreement with the view expressed by a minority of commenters that the UDRP review anticipated by the GNSO Council’s Resolution of December 15, 2011 should not proceed at all, and that any such undertaking would be unduly arduous and dangerous. The UDRP is the only ICANN Consensus Policy that has never been reviewed. Like any human undertaking, it is not perfect and was drafted by individuals who could not have known how it would be implemented in practice. Any UDRP review should of course be fully informed by the actual record of UDRP practice and experience of participants, and should proceed carefully. But we are confident that a good faith UDRP review that considers the legitimate rights and interests of both registrants and complainants, as well as related public policy issues, can produce a more balanced and consistent system that preserves the fundamental virtues of the UDRP while yielding modifications that benefit all affected parties.

ICA looks forward to participating in both the RPM and UDRP reviews. ICANN staff is scheduled to deliver a Report summarizing comments and suggesting next steps by December 10th. Following receipt of that report, the GNSO Council will decide on a way forward and, if ICA’s and other commenters’ proposed procedure is followed, will consider a draft Charter for an RPM review working group in the initial months of 2016.

Throughout the coming review processes, ICA will be an active participant seeking to protect the legitimate rights and interests of domain investors and developers and to bring greater balance between trademark and domain rights.

Here’s the rest of our comment letter’s Executive Summary:

Executive Summary

  • ICA prefers a separate and sequential approach for the reviews and subsequent reports and recommendations, with the RPM review preceding and thereby informing the UDRP review.
  • ICA reiterates all of the points made and views expressed in our prior RPM comment letter of April 30, 2015.
  • ICA believes that the URS has been largely effective in achieving its intended goals. We would strongly oppose any alterations that could make it a substitute for, rather than a narrow supplement to, the UDRP. In addition, the initiation of a PDP to determine whether the URS and other new gTLD RPMs should become Consensus Policies for all gTLDs, and the full consideration of the multiple transitional issues accompanying any such decision, illustrates again that the decision of GDD staff to seek imposition of the URS in contract renewal negotiations with legacy gTLDs was a direct and impermissible intrusion into the policy realm reserved to GNSO Council by ICANN’s Bylaws. ICANN’s Board should therefore instruct GDD staff to cease and desist from any such attempts during the time that these PDPs are open and active, and should refuse to approve any legacy gTLD renewal contract that contains any provision of new gTLD RPMs.
  • The language of Trademark Claims notices may deter legitimate noninfringing domain registrations at new gTLDs. This situation can be partly but not completely addressed by providing more comprehensive information in the notice to the prospective registrant, and also clarifying under what circumstances the post-notice registration of a domain will be considered to constitute “bad faith” for UDRP and URS purposes.
  • Labels that generate a Trademark Claims notice should not be expanded beyond the present system of exact matches of the trademark, plus domain labels recovered in UDRP or court actions under the ‘Trademark-plus-fifty’ implementation measure.
  • The right of first refusal for a premium domain name during or after the sunrise period should be conditioned on whether the trademark is unique or a dictionary word, and if a dictionary word whether the gTLD label is related to the goods and services for which it is registered.
  • Our responses to the report’s UDRP questions emphasize the need for a mechanism, perhaps via an optional internal appeal, to establish greater predictability and consistency in decisions dealing with similar facts; better protection for free speech, especially legitimate noncommercial criticism; more equitable time periods for respondents to choose counsel and draft answers; a fairer means of allocating cases among UDRP providers and their panelists; and establishment of a uniform laches policy barring complaints in defined circumstances.
  • Our additional comments on the UDRP address the need for clear guidelines and meaningful penalties to determine and deter attempted Reverse Domain Name Hijacking; greater transparency requirements for UDRP providers; and establishment of an ICANN-maintained centralized database of UDRP decisions and other relevant information.

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
http://www.internetcommerce.org/rpm-udrp-review/

The TPP and the DNS by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoOn November 5, 2015 the Office of the U.S. Trade Representative (USTR) released the official text of the Trans-Pacific Partnership (TPP). That text consists of 30 separate Chapters totaling more than 2,000 pages, and is accompanied by four additional Annexes and dozens of Related Instruments. Only those who negotiated it are likely to have a detailed understanding of all its provisions, and even that probably overstates reality.

The TPP’s intellectual property (IP) provisions are contained in Chapter 18, which runs for a mere 74 pages. While the majority of these provisions address patents, copyrights, and trademarks, Article 18.28 deals with Domain Names (its full text is reproduced at the end of this article). While of direct relevance to the domain name industry as well as the trademark sector, these provisions were not deemed sufficiently important to merit a single word of explanation in the IP Rights issue paper or fact sheet issued by USTR.

There are twelve signatory nations to the TPP – Australia, Brunei Darussalam, Canada, Chile, Japan, Malaysia, Mexico, New Zealand, Peru, Singapore, Vietnam, and the United States. Article 18.28 requires each of them to do two things with regard to domain names:

  1. Make available for its country code top level domain (ccTLD) a dispute resolution procedure, modeled upon the principles of ICANN’s Uniform Dispute Resolution Policy (UDRP), that is designed to provide expeditious and low cost resolution, is fair and equitable, is not overly burdensome, and does not bar access to judicial redress; and
  2. Provide online public access to a reliable and accurate database of domain registrants in its ccTLD in accordance with each nation’s laws and relevant administrative policies regarding privacy and personal data protection.

Neither of these provisions is earth-shattering, and to some degree they are even positive for the domain sector. Most major ccTLDs already provide access to non-judicial dispute resolution between trademark rights holders and domain registrants, and some even go beyond TPP’s requirements. The .US ccTLD, for example, which had already adopted the UDRP, announced in June 2104 that it was adopting the Uniform Rapid Suspension (URS) procedure which was developed for ICANN’s new gTLD program but is not yet a Consensus Policy applicable to legacy gTLDs. Further, the .US versions of both UDRP and URS require the rights holder to only demonstrate that “the domain name(s) were registered or are being used in bad faith”, while the ICANN versions require evidence of both bad faith registration and use. From a registrant’s point of view, the most positive element of the TPP language is its emphasis on a “fair and equitable” process and its preservation of court access.

As for online access to registrant data, the TPP’s deference to law and policy regarding privacy and personal data protection does not appear to attempt to influence the ongoing attempt by ICANN stakeholders to fashion a new database policy to replace WHOIS. Nor does it require ccTLDs to prohibit the use of privacy and proxy services (which are permitted, for example, by the .AU registry).

So Article 18.28 seems to at least satisfy the “do no harm” standard.

These provisions do not take effect until a signatory nation take the additional steps required under its law to formally adopt the TPP. In the U.S. that requires Congressional approval. President Obama’s November 5th letter to the House and Senate leaders concludes with this statement:

“Consistent with the Trade Priorities Act, I am sending this notification at least 90 days in advance of signing the TPP Agreement.  My Administration looks forward to working with the Congress in developing appropriate legislation to approve and implement this TPP Agreement.”

The TPP faces stiff political opposition within the U.S. Most Democrat members of Congress are opposed to it due to strong resistance from unions and other interest groups.

While we don’t see them as being in the camp of either U.S. political party, the Electronic Frontier Foundation (EFF) recently declared that the publication of TPP’s IP provisions “confirms our worst fears about the agreement, and dashes the few hopes that we held out that its most onerous provisions wouldn’t survive to the end of the negotiations”. EFF took a far more jaundiced view than our own regarding the domain name provisions, observing that it “requires countries to adopt an equivalent to ICANN’s flawed Uniform Domain-Name Dispute Resolution Policy (UDRP), despite the fact that this controversial policy is overdue for a formal review by ICANN” (Note: Such UDRP review is expected to commence in the first half of 2016.)

With the U.S. elections just a year away, U.S. Presidential and Congressional electoral politics are converging to bear on the TPP’s prospects. Presidential Contender Bernie Sanders is a long-time and highly vocal detractor of the pact. His official position states that he:

“Opposed NAFTA, CAFTA, permanent normal trade relations (PNTR) with China, the TPP, and other free-trade agreements. These deals kill American jobs by shifting work overseas to nations which fail to provide worker protections and pay extremely low wages.”

Meanwhile, Hillary Clinton, who pronounced the TPP to be the “gold standard” of modern trade deals while serving as Secretary of State in the Obama Administration, reversed that stance on October 7th, shortly after the final text was published on WikiLeaks, stating:

“As of today, I am not in favor of what I have learned about it. I have said from the very beginning that we had to have a trade agreement that would create good American jobs, raise wages and advance our national security. I still believe that’s the high bar we have to meet. I’ve been trying to learn as much as I can about the agreement, but I’m worried. I appreciate the hard work that President Obama and his team put into this process and recognize the strides they made. But the bar here is very high and, based on what I have seen, I don’t believe this agreement has met it.”

That position, alleged by some to constitute a “flip-flop “, caused the Washington Post to opine in an editorial:

“Bowing to pressure from the Democratic Party’s ascendant protectionist wing, would-be presidential nominee Hillary Clinton has come out against President Obama’s freshly negotiated Trans-Pacific Partnership (TPP) trade agreement. The most hopeful thing to be said about this deeply disappointing abandonment of the president she served, and the internationalist tendency in Democratic ideology she once embodied, is that it is so transparently political… To be sure, Ms. Clinton salted her anti-TPP statement with qualifiers: “What I know about it.” “As of today.” “I am not in favor of what I have learned about it.” And so on. In other words, there is still a chance that later on, if or when she’s president, and it is to her advantage, she may discover some decisive good point in the TPP that would let her take a different position without, technically, contradicting herself. Cynical? Perhaps, but as we said, that’s the hope.”

On the Republican side, leading Presidential contender Donald Trump has made his TPP opposition clear, stating inimitably in a November 9th interview, ““The deal is insanity. That deal should not be supported and it should not be allowed to happen.” While Jeb Bush has voiced support for TPP, others vying for the GOP nomination do not appear to be eager to take a hard position that could antagonize an already disaffected and generally anti-establishment voter base, particularly within its “Tea Party” contingent. More establishment Republican corporate interests tend to favor the TPP, but even in that camp there are notable industries and major companies with strong concerns about various aspects of the agreement.

Congress voted in June 2015 to give the President “fast track” trade promotion authority for the TPP, but that does not mean that a vote will come quickly — just that the TPP text cannot be amended by Congress. The earliest Congress might vote on TPP is Spring 2016. But given that 2016 will be a politically charged year with control of the House, Senate, and White House all theoretically up for grabs, neither party is anxious to take a vote that could alienate millions of potential voters. So there’s a good chance that the final decision on TPP will be left to the next President and Congress sometime in 2017.

The TPP’s signatory nations do not include the largest economic power on the western shore of the Pacific, China, and that omission is to some extent meant to deliberately counter that nation’s economic designs for the Pacific Rim. As former U.S. Treasury Secretary Lawrence Summers just described that strategy:

“The Council on Foreign Relations, hardly a source of xenophobic or radical ideas, recently issued a report drafted by leading U.S. diplomats condemning this country’s efforts to build up China within the international economic order and calling for a “balancing strategy” that includes “new preferential trading arrangements. . .that consciously exclude China.” No small part of the case being made by the Obama administration for the Trans-Pacific Partnership (TPP) trade deal involves the idea that it will promote competitiveness vis-a-vis China and reduce China’s influence in determining global trade rules.”

But global investment flows route around trade policies just like the Internet routes around obstacles, and Chinese investors are today taking actions that may elevate the status of domain names in future trade agreements. Domain name registrations have recently been hitting record levels and, as reported in The Domains, most of the demand seems to be coming from purchasers in China who want to diversify out of equities and real estate and now view domains as an asset class with multiple valuable attributes, including good price appreciation potential.

That changing economic role for domains gives hope that, when the next multinational trade pact is under development, the domain investment industry will be well positioned to make its own case that domains must be viewed not just through the prism of potential trademark infringement but as a valuable intangible asset unto itself, and one that is equally deserving of uniform international recognition and protections.

 

***

Domain Name Provisions of the TPP:

 

Article 18.28: Domain Names

  1. In connection with each Party’s system for the management of its country-code top-level domain (ccTLD) domain names, the following shall be available:

(a) an appropriate procedure for the settlement of disputes, based on, or modelled along the same lines as, the principles established in the Uniform Domain-Name Dispute-Resolution Policy, as approved by the Internet Corporation for Assigned Names and Numbers (ICANN) or that:

(i) is designed to resolve disputes expeditiously and at low cost;

(ii) is fair and equitable;

(iii) is not overly burdensome; and

(iv) does not preclude resort to judicial proceedings; and

(b) online public access to a reliable and accurate database of contact information concerning domain-name registrants,

in accordance with each Party’s law and, if applicable, relevant administrator policies regarding protection of privacy and personal data.

  1. In connection with each Party’s system for the management of ccTLD domain names, appropriate remedies17 shall be available at least in cases in which a person registers or holds, with a bad faith intent to profit, a domain name that is identical or confusingly similar to a trademark.

17 The Parties understand that such remedies may, but need not, include, among other things, revocation, cancellation, transfer, damages or injunctive relief.

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
http://www.internetcommerce.org/the-tpp-and-the-dns/

ICA Asks ICANN BGC to Reconsider Approval of Legacy gTLD Registry Agreements Containing URS by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoOn October 13th ICA filed a formal Reconsideration Request (RR) asking ICANN’s Board Governance Committee (BGC) to rethink The Board’s approval of the renewal registry agreements (RAs) for .Travel, .Cat and .Pro. All three renewal agreements contain Uniform Rapid Suspension (URS) and other rights protection mechanisms (RPMs) drawn from the new gTLD program. Those RPMs are in the contracts largely because staff of ICANN’s Global Domain Division (GDD) started the RA renewal process by proposing their inclusion “to increase the consistency of registry agreements across all gTLDs”. ICA had previously filed comments on all three proposed RAs protesting the inclusion of the URS, as did the large majority of all those who commented.

The explanations of the Board Resolutions approving the three RAs, accomplished with no formal vote on the Consent Agenda of its September 28th meeting, contains the comforting words that “the Board’s approval of the Renewal Registry Agreement is not a move to make the URS mandatory for any legacy TLDs, and it would be inappropriate to do so”. However, it also includes the highly questionable assertion that the inclusion of the URS in the Renewal RAs is based on the bilateral negotiations between ICANN and the Registry Operator, where Registry Operator expressed their interest to renew their registry agreement based on the new gTLD Registry Agreement…and transitioning to the new form of the registry agreement would not violate established GNSO policy“.

There are two major problems with that reasoning:

  • First, there is no equality of bargaining position between a registry that needs its contract renewed, and that often is seeking to obtain beneficial amendments to its prior RA, and GDD staff who take RPM inclusion as their starting point and insist on that throughout the negotiation process as the price of reaching a deal. The assertion that these Registry Operators “expressed their interest” in adopting the URS is a convenient fiction when, by their own admission, GDD staff proposed it at the start of negotiations. The very fact that all three of these registries adopted the RPMs is circumstantial evidence that the action was coerced and hardly voluntary.
  • Second, and more important for preserving ICANN’s multistakeholder bottom-up policy development process, GDD staff subverted it by making what is incontrovertibly a policy decision on a critical question that has not yet been addressed by the community. Now that the Board has condoned this GDD staff initiative they are free to pursue the same RPMs end with every legacy gTLD when their contracts come up for renewal – including .Org, .Net and .Com.

As ICA explained in its RR:

“We believe that this attempt by ICANN contracting staff to create de facto Consensus Policy via individual registry contract, absent a relevant Policy Development Process (PDP), is a glaring example of the type of top down, unaccountable action that should be targeted by enhanced accountability measures accompanying the IANA transition proposal. Contracts with legacy gTLDs can contain and enforce Consensus Policy, but it is an impermissible violation of ICANN’s Bylaws for contracts to attempt to create Consensus Policy.

… We further note that ICANN staff has just issued, on October 9th, the “Preliminary Issue Report on a GNSO Policy Development Process to Review All Rights Protection Mechanisms in All gTLDs”. This report will be considered by the GNSO Council and the ICANN community at the upcoming ICANN 54 meeting in Dublin, Ireland and, following a public comment period scheduled to end on November 30th, will result in a Final Staff report being issued on or about December 10th.

That Final Report will probably provide the foundation for the initiation of one or more Policy Development Processes (PDP) addressing whether the new gTLD RPMs should be adjusted and, more relevant to this reconsideration request, whether they should be adopted as Consensus Policy and applied to legacy gTLDs and/or integrated with the UDRP. Indeed, the Preliminary Issue Report notes (at pp.22-23):

“These [potential] issues would be specific topics to be addressed as part of their Charter by the PDP Working Group, in addition to the more general, overarching issues such as:

  • Whether any of the new RPMs (such as the URS) should, like the UDRP, be Consensus Policies applicable to all gTLDs, and the transitional issues that would have to be dealt with as a consequence.”

This passage of the Preliminary Issue Report constitutes further and new material evidence, provided directly by ICANN policy staff, that the question of whether the URS should become a Consensus Policy applicable to all gTLDs is an overarching policy matter, and that it is wholly inappropriate for GDD staff to seek imposition of it on legacy gTLDs as the starting point for registry renewal agreement negotiations because doing so creates de facto consensus policy via contract. It also identifies the presence of “transitional issues” that have in no way been considered in pressing for the inclusion of the URS in the three renewal agreements that are the focus of this reconsideration request.

Unless and until the URS is adopted as a Consensus Policy for all gTLDs, ICANN staff should not be initiating the registry agreement renewal process with any legacy gTLD by suggesting that new gTLD RPMs be the starting point for contract negotiation as, given the inequality in bargaining power, this can have the effect of making the URS a de facto Consensus Policy notwithstanding the fact that the regular order PDP outlined in and required by the Bylaws has not been followed. Such GDD staff actions make a mockery of and undermine the integrity of the GNSO’s upcoming PDP review of RPMs.ICA will continue to use all available means to assure that the policies imposed on the registrants of more than 100 million legacy gTLD domains are determined through the policymaking process mandated by ICANN’s Bylaws and not set by the whims and coercive pressure of GDD staff.

BGC action on a RR is generally supposed to take place within 30 days of its filing. The RR process is constructed in a manner to provide multiple procedural grounds for summary dismissal without ever reaching the merits of the situation. While that unfortunate avoidance tactic could be utilized, we are hopeful that the importance of this precedent-setting situation, as well as the fact that a similar RR was jointly filed by ICANN’s Business Constituency (BC) and Non-Commercial Stakeholder Group (NCSG), will convince the BCG to do the right thing and address the RRs on their substantive merits.

And we will of course comment upon the recently issued Preliminary Report on Rights Protection Mechanisms in All gTLDs and participate in any subsequent policy development process (PDP) to ensure that RPM Consensus Policies are balanced, and respectful of the procedural and substantive due process rights of domain registrants.

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/rr-on-urs/

ICANN Staff Publish Summary of Public Comments on URS at .Travel by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoOn July 31st ICANN staff finally published the Report of Public Comments regarding the Proposed Renewal of .TRAVEL Sponsored TLD Registry Agreement, after missing the July 5th due date by more than three weeks.

The Report accurately reflects that all but two of the many comments filed on the proposal opposed imposition of Uniform Rapid Suspension (URS) by contract upon a legacy gTLD, and took the view that new gTLD rights protection mechanisms (RPMs) should only be implemented at legacy gTLDs through a standard policy development process (PDP) that made them a Consensus Policy.

In defense of the inclusion of the URS in the proposed .Travel Registry Agreement and other RAs, the report says:

Although the URS was developed and refined through the process described here, including public review and discussion in the GNSO, it has not been adopted as a consensus policy and ICANN staff has no ability to make it mandatory for any TLDs other than those subject to the new gTLD registry agreement. Accordingly, ICANN staff has not moved to make the URS mandatory for any legacy TLDs, and it would be inappropriate for staff to do so. In the case of .TRAVEL and other legacy TLD registry agreement renewals (.JOBS) and proposed renewals for .CAT and .PRO registry agreements, inclusion of the URS was developed as part of the proposal in bilateral negotiations between the registry operator and ICANN. It should also be noted that there are no restrictions on Registry Operators to impose further rights protection mechanisms, such as the URS, which could also be included in the Registry Agreement in other ways, such as through the RSEP process. However, due to the approaching expiration date of the .TRAVEL Registry Agreement and the interest of the Registry Operator to renew their Registry Agreement based on the new gTLD Registry Agreement, the proposed renewal language is similar to the new gTLD Registry Agreement except for the provisions stated above and also explained in detail in the public comment announcement. (Emphasis added)

The notion that .Travel and other incumbent gTLDs agreed to the URS voluntarily is belied by the original request for comments, which clearly states that, “ICANN has proposed that the renewal agreement be based on the approved new gTLD Registry Agreement as updated on 9 January 2014.”(Emphasis added) Contracted parties have told us that ICANN staff takes a very hard line in these closed door negotiations and that they must pretty well go along with whatever provisions staff insist upon.

As for “Next Steps” for the .Travel RA, the Report says:

After taking into consideration the public comments received (see summary and analysis below), some revisions to the proposed renewal of .TRAVEL Registry Agreement are proposed.

The proposed renewal of .TRAVEL Registry Agreement includes substantial and material changes to the original .TRAVEL Registry Agreement, which are based on the existing New gTLD Registry Agreement terms (as described above). Similarly, .JOBS Registry Agreement, another Sponsored TLD, was renewed on 20 February 2015 (see: https://www.icann.org/resources/agreement/jobs-2015-02-20-en).

As a next step, ICANN intends to consider the renewal proposal taking into account the comments. (Emphasis added)

That really doesn’t make clear whether the URS will stay in the final contract.

ICA has told ICANN, via its written comments as well as its presentation to the Board at the Buenos Aires Public Forum, that the Board should have the final word on this RA if the URS stays in, and should thereby take direct responsibility for the final agreement. There’s no assurance that the Board will take that step and be accountable, but we shall continue to monitor this situation.

*****

This is how the Report summarized ICA’s comments:

ICA also raised their concern that “The potential addition of these RPMs to legacy gTLDs through this inappropriate avenue will have a substantial and deleterious effect on ICANN’s policy making process going forward, will create a new and dangerous precedent whereby de facto Consensus Policy can be created by contractual fiat in violation of ICANN Bylaws, and will substantially and adversely affect third parties around the world consisting of the existing registrants of more than one hundred million legacy gTLD domains.”, adding that “the RPMs could be imposed on legacy gTLDs only after their impact and efficacy was fully assessed, and then only via a standard PDP to create new Consensus Policy in conformity with ICANN Bylaws. ”… While BC stated that their concern is not in regards to the adoption of new gTLD RPMs for legacy TLDs, BC, ICA and NCSG expressed their objection to the decision by ICANN staff to take the new gTLD registry agreement as the starting point for renewal RAs for legacy gTLDs since it has the effect of transforming the PDDRP and the URS into de facto Consensus Policies without following the procedures laid out in ICANN’s Bylaws for their creation… Both BC and ICA indicated in their comment that their comments also apply to similar proposed renewal of .CAT and .PRO Registry Agreements currently under public comment period… Both BC and ICA also raised their concern on ICANN staff’s seeking to insert specific new gTLD program RPMs in legacy gTLD renewal RAs when ICANN policy staff have yet to define the issues they implicate, and the GNSO has yet to receive the Issues Report that may be the basis of one or more PDPs; including one addressing whether they should become Consensus Policies applicable to all gTLDs… One of the comments suggested that “if the decision is made by staff to retain these RPMs in the .Travel renewal RA following the close of the public comment period, we believe that the proposed final contract must be forwarded to, reviewed by, and voted upon by the ICANN Board.” (ICA)

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/urs-travel-comments-report/

ICANN Opens “IANA Stewardship and Accountability Public Comment Periods” by Philip Corwin, Internet Commerce Association

Internet Commerce Association logoOver the past week ICANN has opened dual comment periods on the interrelated proposals for transitioning oversight of the IANA root zone functions form the U.S. government to the multistakeholder ICANN community, and for significantly enhancing that community’s ability to hold ICANN’s Board and staff accountable. When the final proposals are implemented they will mark the biggest changes in ICANN’s oversight and operations since its start seventeen years ago.

The comment period on the fully integrated (names, numbers and protocols) proposal from the IANA Stewardship Transition Coordination Group (ICG) closes on September 8th, while the one on the second draft CCWG proposal on Enhancing ICANN Accountability closes on September 12. Once the public comments are taken into account a final proposal on the transition and accountability will likely be presented to the ICANN Board at the October meeting in Dublin, Ireland, or soon thereafter.

As of now the projected date on which the NTIA would be informed that the plan, including all Work Stream One pre-transition accountability measures and Bylaws amendments, has been implemented would be July 2016. That would kick off a period in which NTIA, and likely Congress, would carefully review and consider whether the final plan met all necessary requirements. If it passes that hurdle the transition could be completed around September 2016.

As explained by the ICG:

In parallel with the process [for development of the transition proposal]…, the Cross Community Working Group on Enhancing ICANN Accountability (CCWG) has developed a proposal to ensure ICANN’s continued accountability in the absence of contractual oversight by the U.S. government. This accountability proposal does not deal directly with the governance of the IANA functions, but nevertheless must have broad public support in order for the IANA transition to proceed. The domain names component of the transition proposal, about which the ICG is seeking comment here, is significantly dependent and expressly conditioned on the implementation of specific ICANN-level accountability mechanisms by the CCWG.

According to the CCWG:

The CCWG-Accountability requests community feedback on its 2nd Draft Proposal of proposed enhancements to ICANN’s accountability framework it has identified as essential to happen or be committed to before the IANA Stewardship Transition takes place (Work Stream 1). Community input will help the CCWG-Accountability improve its proposal and carry on with next steps, including Chartering Organizations’ endorsement of the CCWG-Accountability output before it is submitted to the ICANN Board of Directors during or after ICANN54…This 40-day comment period is an opportunity for the community to make its voice heard and to shape the outcome of the CCWG-Accountability work.

In an August 4th blog titled “Let Your Voice be Heard on IANA Transition”, NTIA head Larry Strickling wrote:

The IANA transition will advance our commitment to ensuring that the Internet remains an engine for global economic growth, innovation and free speech… I urge all parties with an interest in the IANA transition to review these proposals and provide feedback to the working groups. This is the best way to make your voice heard and make a difference. It is particularly important that stakeholders everywhere evaluate whether these plans meet the criteria that we have said must be part of the transition.

We echo Secretary Stickling’s sentiments. If you are involved in the domain name sector – or even if you just utilize the Internet and want to assure its continued reliability as a platform for free expression and innovation – it’s worth taking the time to review the plans and submitting a comment. Besides, this chance won’t come again.

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/icann-transition-accountability-comments-open/

Majority Comments say “No URS by Contract at .Cat & .Pro” – While Staff Report on .Travel Comments is Two Weeks Past Due by Philip Corwin, Internet Commerce Association

Philip Corwin imageOnce again, as it was with .Travel, the vast majority of comments on the proposed renewal Registry Agreements (RAs) for the legacy .Cat and .Pro gTLDs are united in their opposition to imposition of Uniform Rapid Suspension (URS) and other new gTLD rights protection mechanisms (RPMs) by contract, arguing that this is a consensus policy decision that can only be fairly made through the policy development process (PDP).

Comments following this general line of reasoning were filed on .Cat by, among others, the Electronic Frontier Foundation, IP Justice, ICANN’s Business Constituency (BC) and Non-Commercial Stakeholders Group (NCSG) — and of course the ICA along with individual comments filed by ICA Board member Nat Cohen and ICA members Jay Chapman and Greg McNair.

As we saw with the comments on .Travel, the only commenters supporting URS by contract at legacy gTLDs were ICANN’s Intellectual Property Constituency (IPC) and new gTLD portfolio registry operator Donuts.

An identical list of commenters and positions appears at the comment forum for .Pro.

A Staff Report on the .Cat and .Pro comments is scheduled to be filed on July 21st. But odds are that these will be late, given that the due date for the staff report on .Travel comments was July 5th but all that appears at its website is this – “Report Overdue”. It’s difficult to understand why it is taking staff so long to complete and post that document, because that Staff Report is supposed to be an objective compilation and summary of the comments received – and not a defense brief to justify the staff action of proposing the inclusion of URS in these renewal RAs that has drawn such broad criticism and opposition.

We will continue to monitor the .Travel website, along with those for .Cat and .Pro, to see when those Staff Reports are filed and what they say.

Meantime, here is what ICA said in the additional comments we filed on both .Cat and .Pro:

This comment by the Internet Commerce Association incorporates by reference and supplements the comment letter we filed in regard to the proposed renewal registry agreement (RA) for .Travel on June 21st.

The issues are essentially identical, in that:

  • The proposed RAs for. .Cat and .Pro are completely identical to .Travel in regard to incorporating the URS in Section 2 of Specification 7.
  • .Cat and .Pro are legacy gTLDs created before and for which the URS is a non-relevant implementation detail of the current new gTLD program, and is not a Consensus Policy enforceable against all gTLDs and contracted parties.
  • The notice published by ICANN regarding the proposed renewal RA clearly states that “ICANN has proposed” that the new gTLD RA be the starting point for contract renewal discussion and negotiation.

This issue of staff creation of de facto Consensus Policy arose several times at the just concluded ICANN 53 meeting held in Buenos Aires. At its opening session on Sunday morning, June 21st ICANN’s GNSO Council met with senior staff of ICANN’s Global Domains Division (GDD). Many Council members raised their own strong concerns about the staff action and its destructive impact on the GNSO’s role in making gTLD policy. GDD staff provided the weak response that “we did not push anyone to accept” the URS, maintaining that .Travel, .Pro, and .Cat registry operators had all “volunteered” to include it in their proposed renewal agreements. That justification strains credulity given that GDD staff proposed its inclusion as the starting point for registry agreement renewal.

As we stated in our comment letter regarding .Travel–

There can be no doubt that this is a staff attempt to create de facto Consensus Policy, as is clearly documented by the fact that the same objectionable provision appears in the proposed renewal RAs for .Cat and .Pro, both released for comment on May 28th. This evidences a deliberate and illegitimate attempt by contracting staff to create a series of precedents that would lead inevitably to the imposition of the URS on major legacy gTLDs such as .Org, .Net and .Com when they come up for renewal, despite the fact that the URS is not an ICANN Consensus Policy.

GDD staff also said they would change their position if the GNSO told them not to seek to impose new gTLD RPMs on legacy gTLDs – which is not only an impossibility for this proposed renewal RA, given the time required for the GNSO to establish policy via the standard PDP, but completely misunderstands and reverses the proper relationship between the stakeholders and staff. It is stakeholders who create ICANN policies through a bottom up process, which are subsequently administered by staff – not staff given free rein to initiate policy in a top down and unaccountable manner via contract negotiations until the stakeholders stop them.

The same concerns were raised when the Council met with the ICANN Board on the afternoon of June 21st, where they received a far more sympathetic reception. Several Board members agreed that staff should not initiate policy changes.

In addition to the concerns raised by Council members, and at community members at the Public Forum in Buenos Aires, the comments filed on .Travel ran overwhelmingly against incorporation of the URS in the renewal RA.

Only two comments supported the action by GDD staff to propose it as a starting point:

  • The Intellectual Property Constituency (IPC) stated that it “encourages Registry Operators to voluntarily go above and beyond the minimum rights protections. Whether adding new restrictions against abusive registrations, implementing blocking or creating new dispute procedures, those best practices should be encouraged and do not require a PDP for TLD Operators to implement”. We strongly disagree that there is anything voluntary about a process in which a supplicant registry in need of having its contract renewed must negotiate with ICANN staff who propose that inclusion of specific RPMs be the starting point for negotiations.
  • We therefore believe that legacy gTLD registry operators are not free to create and adopt new RPMs that alter the rights of existing registrants at the time of contract renewal because there is no one in the negotiating room to speak for the due process rights of their registrants. Indeed, such negotiations take place behind closed doors and are not transparent to affected stakeholders.
  • Further, the IPC’s claim that “there is clearly no requirement that an RPM must become consensus policy before it can be adopted by a registry. We have already learned that from Donuts and Rightside Registry, both of whom adopted a form of “blocking” as an RPM, which was also not consensus policy” completely misunderstands the critical difference between revenue-generating blocking policies promulgated by portfolio gTLD operators and dispute resolution policies. Blocking policies prevent domains from being registered in the first place and therefore have no impact on existing registrants, while alterations in dispute resolution policies can result in an existing registrant having its domain suspended, extinguished or transferred.
  • The IPC also fails to recognize the difference between a new gTLD, in which potential registrants have clear notice of any supplementary RPMs, and a legacy gTLD in which registrants should expect that additional RPMs will be adopted through a standard PDP that creates Consensus Policy.
  • The new gTLD portfolio operator Donuts, which maintained that the STI-RT that created the URS “never considered” whether it “should not be included in legacy TLDs”. All we can say is that Donuts’ recollection is quite different from ours, as we recall this question being raised multiple times and receiving assurances from STI-RT participants and others involved in the development of the new gTLD RPMs that they would not and could not be imposed on legacy gTLDs absent a subsequent review, followed by a PDP which adopted them as Consensus Policy.

In closing, we repeat the conclusion of our comment letter regarding .Travel —

Consensus Policy regarding RPMs must be vetted within the community to assure a proper balancing of the interests and rights of both trademark owners and domain registrants.

In order to assure that balance two indispensable steps are necessary:

  • The attempt to impose new gTLD RPMs on legacy gTLDs by contract must be withdrawn in recognition that such action is in violation of ICANN Bylaws. If staff is unwilling to retreat on this initiative then ICANN’s Board must assume responsibility and review all the issues at play, including compliance with the Bylaws, before any legacy gTLD RA with such a provision is made final.
  • Any further modification of the new gTLD RPMs must be considered within the context of a full PDP. We are far past the implementation phase of the new gTLD program. Further, it is clear that the applicability of the RPMs to legacy gTLDs is now primed for discussion. Unless both RPM modifications and legacy gTLD applicability are considered within the PDP framework there is a substantial risk of a bait-and-switch policy process, in which RPMs are made applicable to legacy gTLDs and then substantially altered via a backdoor, non-PDP process.

In addition, we repeat the request that ICA made directly to ICANN’s Board at the Buenos Aires Public Forum –

First, we need a commitment that any further alterations of the new gTLD RPMs will be made through a standard PDP. We are far past the implementation details stage and it is now crystal clear that these decisions will implicate legacy gTLDs as well.

Second, if GDD staff ignores the overwhelming weight of comments and retains the URS in the final RAs for legacy gTLDs, you need to vote up and down on those RAs. You need to “own” that decision and in that way indicate whether you believe this GDD staff action is or is not acceptable.

We hope that GDD staff will recognize that they have overreached on these legacy gTLD contracts and that the proper action is to strike the RPMs adopted from the new gTLD program from them and leave that decision to the multistakeholder community.

If staff does not do the right thing then we will press for an up and down Board vote on this and the other affected contracts before they take effect.

 

Sincerely,

Philip S. Corwin

Counsel, Internet Commerce Association

This article by Philip Corwin from the Internet Commerce Association was sourced with permission from:
www.internetcommerce.org/no-urs-at-cat-and-pro/