Hi,

As you know I disagree.  I think leaving the grandfathering to the
processes we have is the right thing to do.  I do not think the CCWG is
the pplace to start messing about with Registry and Registrar contracts.

But I won't argue with you on the CCWG list.  If I am alone in my belief
that this is the right way to handle it given the plan we sent forward
and in adherence to the bottom up methodologies of the GNSO and if the
NCSG PC, after sufficient member review decides to send in a SG comment
when it comes time to do SG comments (which this pass isn't), I will ask
to append a minority statement to the NCSG statement.  But in the CCWG,
I will leave the battle in CCWG  to Becky who knows the contractual
environment better than I ever will.

I make sure this gets an open discussion in the gTLD subsequent
procedures WG.  PICs are most definitely on the docket and it will be
close to 10 years before the issue comes to the fore as a practical matter.

avri

On 06-Apr-16 13:39, Mueller, Milton L wrote:
>> -----Original Message-----
>> From the discussion on the CCWG call we just had, it sounds like the solution
>> is for the base contract for gTLDS and the RAA to be changed.
>> In terms of the gTLD contract this is something that the current gTLD
>> subsequent procedures should take up as a policy issue.
> That is NOT a "solution". That is a way for the mission limitations to be eradicated for most of the industry. If the GNSO has to specifically make a policy that changes the RA and the RAA then those who want ICANN to stray from its mission win. The default value should be that THEY have to pass policies 
>
>> If the PDP decides to change the base contract and PICS are outside of the
>> mission, then the contract that the PDP recommends could not include PICS.
>>
>> Not sure how to handle the change to the RAA in this case, but it sounds like
>> that would need to be changed , so the next time a new RAA was
>> introduced, then the grandfathering would end.
> This is unacceptable. 
>



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus