Public Comment

Public Comment is a vital part of our multistakeholder model. It provides a mechanism for stakeholders to have their opinions and recommendations formally and publicly documented. It is an opportunity for the ICANN community to effect change and improve policies and operations.

Ce contenu est uniquement disponible en

  • English

Name: Alexander Levit
Date: 30 Sep 2024
Affiliation: Dynadot Inc
1. Please choose your level of support for Recommendation #1:
No Opinion
1. Please choose your level of support for Recommendation #2:
No Opinion
1. Please choose your level of support for Recommendation #3:
No Opinion
1. Please choose your level of support for Recommendation #3:
No Opinion
1. Please choose your level of support for Recommendation #5:
No Opinion
1. Please choose your level of support for Recommendation #6:
No Opinion
1. Please choose your level of support for Recommendation #7:
No Opinion
1. Please choose your level of support for Recommendation #8:
No Opinion
1. Please choose your level of support for Recommendation #9:
No Opinion
1. Please choose your level of support for Recommendation #10:
No Opinion
1. Please choose your level of support for Recommendation #11:
No Opinion
1. Please choose your level of support for Recommendation #12:
No Opinion
1. Please choose your level of support for Recommendation #13:
No Opinion
1. Please choose your level of support for Recommendation #14:
No Opinion
1. Please choose your level of support for Recommendation #15:
No Opinion
1. Please choose your level of support for Recommendation #16:
No Opinion
1. Please choose your level of support for Recommendation #17:
No Opinion
1. Please choose your level of support for Recommendation #18:
Recommendation should be deleted

2. If your response requires an edit or deletion of Recommendation #18, please indicate the revised wording and rationale here.

Recommendation 18 was presented as Preliminary Recommendation 17 in the WG's initial Group 1(a) recommendations and purported to remedy problems related to: the failure of the Transfer Policy to meet the expectations of RNHs, credit card fraud and domain name theft in registrars' operations, and gaps in the integrity of the UDRP process. No empirical evidence was presented to support the existence of these problems. In its comment to the initial report, Dynadot requested that the WG obtain evidence sufficient to demonstrate that these problems are material enough to support changes to the Transfer Policy that contradict its very purpose, which is identified in its preamble as the imperative to enhance domain name portability and transferability between registrars. The amended Group1(a) recommendations again present no empirical evidence to support these assertions. Legislators across the world are proposing legislation aimed at discouraging market practices that restrict users’ rights to port their digital services among competing platforms. Adopting Recommendation 18 would result in the ICANN model adopting a policy that runs counter to global legislators' imperatives, and to boot it will be in the absence of a balancing of any evidence showing the value the industry gained by the transfer restriction as against the value lost by it. Although Dynadot supports the carveout provided for a subset of registrants whose circumstances meet the requirements for removal of the lock, it notes that even a qualified transfer restriction requires evidence supporting departure from the default position that a registrant would find herself absent adoption of this recommendation at all. In the absence of supporting evidence, policies that contradict the very purpose of the Transfer Policy should be deleted. Thank you for considering Dynadot’s comment.

1. Please choose your level of support for Recommendation #19:
No Opinion
1. Please choose your level of support for Recommendation #20:
No Opinion
1. Please choose your level of support for Recommendation #21:
No Opinion
1. Please choose your level of support for Recommendation #22:
No Opinion
1. Please choose your level of support for Recommendation #23:
No Opinion
1. Please choose your level of support for Recommendation #24:
No Opinion
1. Please choose your level of support for Recommendation #25:
No Opinion
1. Please choose your level of support for Recommendation #26:
No Opinion
1. Please choose your level of support for Recommendation #27:
No Opinion
1. Please choose your level of support for Recommendation #28:
No Opinion
1. Please choose your level of support for Recommendation #29:
No Opinion
1. Please choose your level of support for Recommendation #30:
No Opinion
1. Please choose your level of support for Recommendation #31:
No Opinion
1. Please choose your level of support for Recommendation #32:
No Opinion
1. Please choose your level of support for Recommendation #33:
No Opinion
1. Please choose your level of support for Recommendation #34:
No Opinion
1. Please choose your level of support for Recommendation #35:
No Opinion
1. Please choose your level of support for Recommendation #36:
No Opinion
1. Please choose your level of support for Recommendation #37:
No Opinion
1. Please choose your level of support for Recommendation #38:
No Opinion
1. Please choose your level of support for Recommendation #39:
No Opinion
1. Please choose your level of support for Recommendation #40:
No Opinion
1. Please choose your level of support for Recommendation #41:
No Opinion
1. Please choose your level of support for Recommendation #42:
No Opinion
1. Please choose your level of support for Recommendation #43:
No Opinion
1. Please choose your level of support for Recommendation #44:
No Opinion
1. Please choose your level of support for Recommendation #45:
No Opinion
1. Please choose your level of support for Recommendation #46:
No Opinion
1. Please choose your level of support for Recommendation #47:
No Opinion