Re: [CCG] Fwd: Proposed Changes to License Agreements between ICANN and IETF Trust

John Curran <jcurran@arin.net> Sun, 12 November 2017 13:54 UTC

Return-Path: <jcurran@arin.net>
X-Original-To: ccg@ietfa.amsl.com
Delivered-To: ccg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEF4129438; Sun, 12 Nov 2017 05:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LxkbYgNStae; Sun, 12 Nov 2017 05:54:28 -0800 (PST)
Received: from smtp1.arin.net (smtp1.arin.net [192.136.136.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAC01200F1; Sun, 12 Nov 2017 05:54:28 -0800 (PST)
Received: by smtp1.arin.net (Postfix, from userid 323) id F00EB10A84C3; Sun, 12 Nov 2017 08:54:27 -0500 (EST)
Received: from ASHEDGE02.corp.arin.net (ashedge02.corp.arin.net [199.43.0.123]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTPS id 96D3110A84D2; Sun, 12 Nov 2017 08:54:24 -0500 (EST)
Received: from CAS02ASH.corp.arin.net (10.4.30.63) by ASHEDGE02.corp.arin.net (199.43.0.123) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sun, 12 Nov 2017 08:54:05 -0500
Received: from CAS01ASH.corp.arin.net (10.4.30.62) by CAS02ASH.corp.arin.net (10.4.30.63) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 12 Nov 2017 08:54:05 -0500
Received: from CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6]) by CAS01ASH.corp.arin.net ([fe80::4803:bd5b:dc93:20f6%18]) with mapi id 15.00.1210.000; Sun, 12 Nov 2017 08:54:06 -0500
From: John Curran <jcurran@arin.net>
To: Kaveh Ranjbar <kranjbar@ripe.net>
CC: CCG PTI <ccg@ietf.org>, Trustees <trustees@ietf.org>
Thread-Topic: [CCG] Fwd: Proposed Changes to License Agreements between ICANN and IETF Trust
Thread-Index: AQHTW27QAs6vh7sFKEahh7KX4OeEZqMRGHwA
Date: Sun, 12 Nov 2017 13:54:05 +0000
Message-ID: <B119875A-77F2-4752-B1AA-3C7A54A7E51F@arin.net>
References: <149373262717.9880.7516296670939349912.idtracker@ietfa.amsl.com> <6576F76C-CCBF-478F-8AEF-B39FC4FA8947@ripe.net>
In-Reply-To: <6576F76C-CCBF-478F-8AEF-B39FC4FA8947@ripe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [199.43.0.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_E30ADD0D-40E5-4B0D-9148-AE784FC8004B"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccg/Snfb86ieNySPcUsyV-q7VtfRDdY>
Subject: Re: [CCG] Fwd: Proposed Changes to License Agreements between ICANN and IETF Trust
X-BeenThere: ccg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IANA IPR Community Coordination Group <ccg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccg>, <mailto:ccg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccg/>
List-Post: <mailto:ccg@ietf.org>
List-Help: <mailto:ccg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccg>, <mailto:ccg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Nov 2017 13:54:31 -0000

Kaveh -

  Thank you for the update!

/John

Chair, Number Resource Organization


> On 11 Nov 2017, at 11:26 PM, Kaveh Ranjbar <kranjbar@ripe.net>; wrote:
> 
> Dear CCG Members,
> 
> Here is an status update on the process of transferring the IANA domains to the IETF Trust from ICANN using CSC as the registrar. We are at the point where we are executing the CSC contract (step <g> in the original announcement, quoted below).
> 
> Next step would be transfer of iana.net <http://iana.net/> domain (IANA has three: iana.com <http://iana.com/>;, iana.net <http://iana.net/> and iana.org <http://iana.org/>;, all pointing to iana.org <http://iana.org/>) to CSC and then try to make a simple administrative change and test CSC’s response.
> 
> FYI, the IANA IPR license agreement amendments to support these changes have been signed earlier in the October and you can find a copy of them attached for the record.
> 
> I will keep you posted on the progress.
> 
> All the best,
> 
> Kaveh Ranjbar,
> Chair, IETF Trust.
> 
> 
> <IANA IPR License Agreement for IANA Numbers Services_Amendment One.pdf>
> <IANA IPR License Agreement for IANA Names Services_Amendment One.pdf>
> <IANA IPR License Agreement for IANA Protocol Parameter Services_Amendment One.pdf>
> 
>> Begin forwarded message:
>> 
>> From: The IETF Trust <ietf-trust@ietf.org <mailto:ietf-trust@ietf.org>>
>> Subject: [CCG] Proposed Changes to License Agreements between ICANN and IETF Trust
>> Date: 2 May 2017 at 21:43:47 GMT+8
>> To: "IETF Announcement List" <ietf-announce@ietf.org <mailto:ietf-announce@ietf.org>>
>> Reply-To: trustees@ietf.org <mailto:trustees@ietf.org>
>> 
>> 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 IANA IPR
>> License Agreements’ Exhibit E Domain Name Registrar Requirements.
>> Exhibit E is the same in each of the three IANA IPR License
>> Agreements between the Trust and ICANN, specifically the licenses
>> for the IANA Names Services, the IANA Numbers Services and the IANA
>> Protocol Parameter Services.
>> 
>> The implementation of the domain name registrar requirements needed
>> additional details than in the current Exhibit E. These details have
>> been worked out with ICANN, reviewed by the CCG and approved by the
>> IETF Trust for this review by the community.
>> 
>> Specifically the proposed changes affect the following: 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 (Trust)
>> 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, to prohibit
>> deletions, and to remove the configuration to renew the domain
>> automatically.
>> 
>> A markup of the License Agreement Exhibit E reflects those proposed
>> details and can be found here as Proposed Amendment to License
>> Agreements 1 May 17: https://trustee.ietf.org/iana.html <https://trustee.ietf.org/iana.html>
>> 
>> CSC has agreed that it can implement the proposed changes.
>> 
>> It is believed the next steps are:
>> 
>>  a.  Community Review
>>  b.  Acceptance of proposed changes to Exhibit E by the Trust
>>  c.  Trust and ICANN execute amendments to the three License
>> 	Agreements
>>  d.  Incorporate the changes in CSC Agreement Schedule A
>> 	(Schedule A is the same as Exhibit E of the License Agreements)
>>  e.  Trust puts Schedule A of the CSC Agreement out for Community
>> 	Review
>>  f.  Community Review
>>  g.  Trust executes CSC Agreement
>>  h.  CSC Test of conformance to the requirements
>>  i.  All IANA domains transferred upon successful test
>> 
>> Your feedback by 17 May 2017 on the proposed amendments to Exhibit E
>> of the IANA IPR License Agreements and the next steps are
>> appreciated.
>> 
>> Thanks.
>> 
>> Kaveh Ranjbar
>> Chair
>> IETF Trust
>> 
>> _______________________________________________
>> CCG mailing list
>> CCG@ietf.org <mailto:CCG@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ccg
> 
> _______________________________________________
> CCG mailing list
> CCG@ietf.org
> https://www.ietf.org/mailman/listinfo/ccg