Page History

Notes/ Action Items

Actions:

1. Meeting Timing: Staff will send a Doodle to see whether the current time is still preferable or whether a new time will encourage more attendance.
2. Article 4 Accountability and Review – Sections 4.2 & 4.3: Staff will a) develop a new draft with David McAuley and b) circulate to the DT for review.
3. Section 18.12 Special IFRs – GNSO Input Process: Staff to put text of GNSO Input Procedure into a Google document for DT members to edit as possible Special IFR procedures/guidelines.

Notes:

1.Updates to Statements of Interest (SOIs): No updates provided.

2. Revised Draft of Guidelines/Templates for Article 4 Accountability and Review – Sections 4.2 & 4.3:

Comments from David McAuley:

-- Page 2 and 3: References to 4.2 and 4.3 -- highlight the fact that one is in annex D and one is in the main body of the Bylaws.

-- Page 3, para 4, change to "request or support"

-- Page 4, Add language/template for whether and when the GNSO wants to support an IRP (not covered by the Reconsideration Request form).

ACTION ITEM: Staff will 1) develop a new draft with David McAuley and 2) circulate to the DT for review.

3. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs):

Questions for Consideration:

ia. GNSO Input Process: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at: https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.pdf  

-- Is it useful, is anything missing -- a gap analysis.  Should help to identify any GNSO-specific items.  If we do need something else suggest what that could be.

Discussion:

-- Note that changes to GNSO Operating Procedures need to go out for public comment and be approved by the Council.

-- Could consider referencing the GIP or using another process.

-- GIP seems to be fairly broad with flexibility.

-- Link back to a Special IFR -- doesn't seem to quite fit.  Doesn't arise to the level of seriousness of a Special IFR.

-- Could use the form of the GIP but adjust it to a Special IFR.

-- Impossible to know in advance what is necessary.

-- Not sure we need to add points to the GIP -- could it be sufficient; rather than redrafting the GIP produce guidance for using the GIP for a Special IFR.

ACTION ITEM: Put GIP language in a Google doc to customize for Special IFRs as a guidance document.  Highlight what we think is necessary for the Special IFR.  Can note time requirements for specific steps.

iib. Coordination with the ccNSO Guidelines Review Committee: DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision.

Discussion:

-- Might want a formal process based on the seriousness of the subject matter.

-- Having some sort of a record that the GNSO and ccNSO have discussed whether or not to bring a Special IFR.  Such as a letter.

4. Next Meeting:

-- The next meeting is in 3 weeks on 01 May.

-- The Sub Team will take up the question of coordination with ccNSO.