ICANN ICANN Email List Archives

[gnso-igo-ingo]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-igo-ingo] Consolidated Draft of Initial Report for IGO/INGO PDP WG

  • To: Avri Doria <avri@xxxxxxx>, "GNSO IGO INGO (gnso-igo-ingo@xxxxxxxxx)" <gnso-igo-ingo@xxxxxxxxx>
  • Subject: RE: [gnso-igo-ingo] Consolidated Draft of Initial Report for IGO/INGO PDP WG
  • From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Date: Wed, 5 Jun 2013 14:47:38 +0000

Thanks Avri.  That change seems fine to me.

Chuck

-----Original Message-----
From: owner-gnso-igo-ingo@xxxxxxxxx [mailto:owner-gnso-igo-ingo@xxxxxxxxx] On 
Behalf Of Avri Doria
Sent: Wednesday, June 05, 2013 10:34 AM
To: GNSO IGO INGO (gnso-igo-ingo@xxxxxxxxx)
Subject: Re: [gnso-igo-ingo] Consolidated Draft of Initial Report for IGO/INGO 
PDP WG 



On 5 Jun 2013, at 10:14, Gomes, Chuck wrote:

> For the most part, Avri's suggestions seem pretty reasonable to me. I don't 
> understand AD72.  Also, I think that AD86 was covered elsewhere but it is 
> okay to mention it again. 


thanks.

the problem with 72 is that my comment is garbled.

I am recommending replacing

unacceptably vulnerable
 
with

are as vulnerable

- the point is that they should be included because they claim they are 
similarly vulnerable to other names that have received special considerations.  
We have not defined vulnerability nor a mark of what is acceptable and what 
isn't acceptable.




<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy