[Gnso-newgtld-wg-wt4] Work Track 4 agenda for 4 May 2017

Rubens Kuhl rubensk at nic.br
Tue May 9 21:37:20 UTC 2017

> On May 9, 2017, at 9:44 PM, Aikman-Scalese, Anne <AAikman at lrrc.com> wrote:
> Thanks Rubens.  I do not think that these specific TLD strings have to be specifically mentioned in our Charter.  They simply fall under the category of name collisions, clearly within scope.  As you point out, it is not because something became an issue in the first round that it falls outside our remit. 

The topic should have been mentioned, not the specific strings. Like "Closed Generics" were mentioned applying to the 2012-round, even though not mentioning specific strings. This is what we have in the charter:

"Name	collisions:	How	should	name	collisions	be	incorporated	into	future	new	gTLD	rounds?	What	measures	may	be	needed	to	manage	risks	for	2012-round	gTLDs	beyond	their	2	year	anniversary	of	delegation,	or	gTLDs	delegated	prior	to	the	2012	round?"

So, for 2012-round gTLDs, we can only look at measures for delegated gTLDs. At least with the charter as it is now. 

> Don’t we say it’s the GNSO that makes policy, not the Board?  You said that as to new applications for very risky names,
> “That's one of the policy questions I mentioned.”
> It makes no sense to me that cases of very risky name collision strings going forward are within the scope of Sub Pro but that very risky name collision issues identified with .home, .corp, and .mail are dealt with directly by the Board.  Shouldn’t the same consistent policy (developed according to a Multi-Stakeholder bottom-up process with ample opportunity for public comment) apply to very risk name collision strings regardless of application date?

The next procedures might have very different application rules, depending on the outcome of this PDP; those applications were made with the 2012 rules, and unless for topics specifically punted for this PDP (like closed generics), they are the ones in force, not what we discuss here. Same applies for other contentious issues like community applications, where some 2012 applications are still pending but will be judged against the 2012 criteria. 

>  Why would the Board be in charge of name collision mitigation policy for very risky names in connection with 2012 round applications, while  Sub Pro and GNSO are in charge of name collision mitigation policy for very risky names not yet applied for?

Actually, the Board acted within what was specified in the 2007 GNSO Policy for such issues. 
Principle D: "A set of technical criteria must be used for assessing a new gTLD registry applicant to minimise the risk of harming the operational stability, security and global interoperability of the Internet."
Recommendation 4: "Strings must not cause any technical instability."

We might have disagreements with the implementation, specially since it at least contradicted principle A (predictability), but we didn't have in 2012 the implementation oversight mechanisms that are mandated since September 2015, output of a work that started exactly due to implementation issues seen in the 2012-round. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4/attachments/20170509/dd55429e/attachment.html>

More information about the Gnso-newgtld-wg-wt4 mailing list