[Gnso-newgtld-wg] On copy-pasting applications

[lists at christopherwilkinson.eu]

Dear Rubens, Dear All:

The whole discussion about copy-pasting into applications seems to presuppose that there will be applicants who intend to apply for multiple TLDs, not excluding very large numbers of applications.
If that happens again, it would defeat the objectives of consumer choice, competitive DNS offerings and linguistic and geographical diversity.  Furthermore, - in the present DNS market conditions - those TLD delegations would be primarily directed towards warehousing and speculation with a view to future profitable sales. Such an outcome would discredit ICANN in ways that I would prefer not to.

May I suggest that Subsequent Procedures starts to discuss ways of preventing or radically discouraging multiple applications. Obviously a minimalist starting point would be to prevent ‘copy-pasting’.

Regards

CW




> On 25 Mar 2019, at 20:15, Rubens Kuhl <rubensk at nic.br> wrote:
> 
> 
> 
> Hi folks. 
> 
> On the theme whether there should be an ability for applicants to replicate responses among application, I believe we are mixing two different things:
> 1) If the application should or must have this feature
> 2) If applications should have dissimilarities among them from a policy perspective
> 
> On (1), I believe the relevant WT, comments and SG analysis should base the WG discussion, notably the alert by ICANN Org that more features equal more time and cost. But we shouldn't conflate that discussion with whether copy-pasting, even if done by the applicant on its own, should be discouraged or disallowed. 
> 
> On (2), I believe the relevant WG, comments and SGs already established that when the point of non-scored questions was analysed, and the full WG should consider that. But one thing that could help those reviewing the applications would be a comparative analysis. And regardless whether policy forbids such or not, that would be a useful aid for groups reviewing large number of applications. I only discourage making that a requirement, but expressing the usefulness of such a tool in the final report would at least allow someone at Org to argue for it to be contracted/created. 
> 
> 
> Rubens
> 
> 
> _______________________________________________
> Gnso-newgtld-wg mailing list
> Gnso-newgtld-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg