Decisions Reached
Decisions reached on plenary meetings & calls are reported in the table below:
Meeting # | Date | Decision Reached |
IFRT #20 | 26-Jan-2021 | Final Report approved by team through lack of any objections |
IFRT #19 | 15-Dec-20 | On Final Report, a) include on a note that Recs 1 & 2 are complete b) Based on the reviewing the Public Comments received no changes are required to the Final Report. c) IFRT will add an Appendix regarding the Comments received |
via email | 02-Oct-2020 | Initial Report approved; no dissents |
IFRT #18 | 15-Sep-20 | In order to prevent additional Public Comments besides for the Initial Report and Final Report, do required/Best Practice consultations with PTI, the Board, the CSC, g & cctld operators for the Recommendation that will require an IANA Naming Functions Contract amendment. PTI has already been consulted; the co-chairs will send a letter to the Board; Amy & James will discuss with CSC during their monthly meeting; the co-chairs will conduct a community webinar for communication with c & gtld operators. The Initial Report Public Comment will also highlight the contract amendment recommendation so that this Public Comment acts also a Public Comment for contract amendments. |
IFRT #18 | 15-Sep-20 | Reword the "FINDINGS" on .int. See Meeting Notes for details on this decision. |
IFRT #18 | 15-Sep-20 | Removed the Recommendation on .int. See Meeting Notes for details on this decision. |
IFRT #17 | 01-Sep-20 | Removed the Recommendation on Publishing “past” CCOP Test Results. It was pointed out there was only a single set of test results from 2019 because the contract only called for annual testing if necessary. ICANN & PTI were satisfied not to do annual testing because there had been no changes to the CCOP that would require it. PTI did post the 2019 test results within 90 days. |
IFRT #17 | 01-Sep-20 | Removed Recommendation on improving IANA related user materials It was determined to remove this requirement from the Initial Report because on re-reviewing the materials and the sub-group call which covered this subject it was determined that the materials met the contract requirements and there were no other major issues with it. |
IFRT #17 | 01-Sep-20 | Recommendation on designating an entity in charge of policy for .int It was determined that re-writing is necessary to provide more clarity for what actions the IFRT expects. Peter and Suzanne will discuss through email to suggest new text. |
IFRT #10 | 28-Apr-20 | Decision on what constitutes the Community Outreach required for the review and determined that the following outreach opportunities would capture the most pertinent information from the largest amount of reachable IANA services customers:
Further Outreach would cause large delays in the review without reaching additional IANA services customers or obtaining new information. |
IFRT #10 | 28-Apr-20 | Team agreed to verbal attestations from ICANN, PTI, GNSO Councils, etc. in regards to attesting that sections of the IANA contract have been met |
IFRT #6 | 18-Feb-20 | Work Plan approved; full consensus |
IFRT #5 | 04-Feb-20 | Scope of Work approved; full consensus |
IFRT #3 | 7-Jan-20 | Rules of Engagement Approved; full consensus |