Dear all,
As said yesterday, Sam Eisner would look at the proposed charter language included in the Initial Report. Included her findings,
Kind regards,
Bart
From: Samantha Eisner <Samantha.Eisner@icann.org>
Date: Wednesday 6 June 2018 at 23:51
To: Bart Boswinkel <bart.boswinkel@icann.org>
Cc: Trang Nguyen <trang.nguyen@icann.org>
Subject: Re: Check amended charter CSC for consistency with Bylaw and IANA Naming Function Contract Language
Hi -
I reviewed the Charter and it did not raise any concerns for me with consistency with the ICANN Bylaws.
I will note two items for potential clean up: (1) there is a reference to “IANA” as a standalone entity, but I recommend that be the IANA Functions Operator. (2) there is potential duplication between two sections where attendance requirement are now specified, however they are not inconsistent, so it’s not a big deal.
On a terminology issue, I know during the transition we said ICANN is the IFO, and then it contracts with PTI. The initial language of the CSC Charter can be read to say that PTI is the IFO, not the company contracted to perform the IANA functions. The further edits that the Charter review team made are consistent with that use of PTI as the IFO. TRANG, are we OK with leaving it, or should we recommend refinement to the terms?
Sam
—
Samantha Eisner
Deputy General Counsel, ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, California 90094
USA
Direct Dial: +1 310 578 8631
From: Bart Boswinkel <bart.boswinkel@icann.org>
Date: Wednesday, June 6, 2018 at 5:33 AM
To: Samantha Eisner <samantha.eisner@icann.org>
Cc: Trang Nguyen <trang.nguyen@icann.org>
Subject: Re: Check amended charter CSC for consistency with Bylaw and IANA Naming Function Contract Language
Hi Sam.,
Hope all is well.
The public comment period on Interim Report CSC charter review has just closed ( 1 June 2018).
This evening ( Wednesday 6 June) the RT is having a call to discuss the comments received and impact on the charter and report. I am now drafting final report and updating the proposed charter accordingly. Could you be so kind to run a consistency check over the amended charter, by the end of this week, early next week?
Thank you and kind regards,
Bart
From: Samantha Eisner <Samantha.Eisner@icann.org>
Date: Friday 20 April 2018 at 20:40
To: Bart Boswinkel <bart.boswinkel@icann.org>
Cc: Trang Nguyen <trang.nguyen@icann.org>
Subject: Re: Check amended charter CSC for consistency with Bylaw and IANA Naming Function Contract Language
Thanks Bart. Will do.
—
Samantha Eisner
Deputy General Counsel, ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, California 90094
USA
Direct Dial: +1 310 578 8631
From: Bart Boswinkel <bart.boswinkel@icann.org>
Date: Thursday, April 19, 2018 at 1:02 PM
To: Samantha Eisner <samantha.eisner@icann.org>
Cc: Trang Nguyen <trang.nguyen@icann.org>
Subject: Check amended charter CSC for consistency with Bylaw and IANA Naming Function Contract Language
Hi Sam,
Included the Initial Report of the CSC Charter review team, which was just published for public comment. It is my understanding that Donna reached out to you to ask if you could check the consistency of the proposed charter against the relevant language in Article 17 of the Bylaws and IANA Naming Function Contract. The Initial report includes the amended charter (section 6) and a comparison of the proposed and current charter). For example the RT ( and CSC itself) is struggling with when to use PTI and when the IANA Function Operator. Similarly, what to use Service Level, Service Level requirements or SLA. The Review Team will after the Public Comment update the Report including and if needed the charter will be updated.
If you could provide your input, if any, directly to the Review Team or as part of the public comment they will adjust the charter.
Thank you and kind regards,
Bart