Re: [CCG] Proposed Changes to License Agreements

[CW Mail <[e-mail]>]

Good afternoon:

On this occasion I can confirm my agreement to the amendments to and the current text of Exhibit E, as proposed below.

More generally, however, and for future reference, I would like CCG to be associated more thoroughly with any issues or texts that arise in this context.
For instance, I have no record of CCG having been associated with the development of the final IANA IPR Licence Agreement, whereas I had pointed out some time ago that in the international context it would not be appropriate to grant a monopoly to the AAA Rules in the event of unresolved disputes. But this appears to have been ignored.

Regards

Christopher Wilkinson

PS:	 I was disappointed that there was no opportunity to meet during ICANN58 in Copenhagen.


On 09 Mar 2017, at 19:54, CW Mail <[e-mail]> wrote:
> Dear Tobias Gordon:
> 
> Thankyou. I shall also review the document and respond in good time for your schedule.
> I would like to clarify how exactly the envisaged Community Reviews would be conducted.
> 
> May I suggest that those of us who are in Copenhagen next week might  meet briefly and informally to establish personal contact.
> 
> Best regards
> 
> Christopher Wilkinson
> 
> On 01 Mar 2017, at 16:39, Tobias Gondrom <[e-mail]> wrote:
> 
>> Dear all,
>>  
>> We are in the process of transferring the IANA domains to the Trust
>> from ICANN using CSC as the registrar.
>>  
>> The agreement with CSC requires the incorporation of the License
>> Agreements’ Exhibit E Domain Name Registrar Requirements.  Exhibit E
>> is the same in each of the three license agreements between the
>> Trust and ICANN.
>>  
>> The implementation of the requirements needed additional details
>> than in the current Exhibit E. These details have been worked out
>> with ICANN and approved by the IETF Trust for review and acceptance
>> by the CCG.
>>  
>> Specifically, under the circumstance where the Administrative and
>> Technical Contacts must approve the change to the Technical Contact
>> the Registrar must provide notice of a receipt of a request to each to
>> change the Technical Contact.
>>  
>> Additionally, under the circumstance where the Registrant can
>> override the need for the other parties to approve a change to the
>> Technical Contact, the Registrant must provide documentation that
>> notice of the change was provided to both the Administrative and
>> Technical Contacts and that no response was received after a period
>> of no less than ten business days.
>>  
>> These conditions are also incorporated under the circumstances where
>> the domain is set to prohibit registrar transfers and to prohibit
>> deletions.
>>  
>> A markup of the attached License Agreement Exhibit E reflects those
>> proposed details.
>>  
>> CSC has stated that it can implement the proposed changes.
>>  
>> Section 3.2 e (ii) of the Community Agreement provides that each
>> Operational Community accepts the “Initial License Agreement”, which
>> was done.
>>  
>> The Trust, together with the current Operator, propose changes to the
>> License Agreement and requests that the Operational Communities
>> accept these changes.
>>  
>> Following acceptance of these proposed changes it is believed the
>> next steps to be:
>>  
>>   a.  Community Review
>>   b.  Trust and ICANN execute amendments to the three License Agreements
>>   c.  Incorporate the changes in CSC Agreement Schedule A
>>             (Schedule A is the same as Exhibit E of the License Agreements)
>>   d.  Trust puts Schedule A of the CSC Agreement out for Community Review 
>>   e.  Community Review
>>   f.  Trust executes CSC Agreement
>>   g.  CSC Test of conformance to the requirements 
>>   h.  All IANA domains transferred upon successful test
>>  
>> Your feedback by 20 March 2017 on the proposed amendments to the
>> License Agreements and the next steps are appreciated.
>>  
>> Best regards,
>>  
>> Tobias Gondrom
>> Chair
>> IETF Trust
>>  
>> <Exhibit E Domain Name Registrar Requirements Markup -00.pdf>_______________________________________________
>> CCG mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/ccg
>