Please find the meeting information below for the GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Community call on Wednesday, 27 March 2019 at 21:00 UTC for 60 minutes.

14:00 PDT, 17:00 EDT, 22:00 Paris CET, (Thursday) 02:00 Karachi PKT, (Thursday) 06:00 Tokyo JST, (Thursday) 08:00 Melbourne AEDT

For other times: https://tinyurl.com/y4e9a8lv

PROPOSED AGENDA


 

  1. Review Agenda
  2. Updates to Statements of Interest (SOIs)
  3. Review and approval of Draft Timeline (attached)
  4. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3 (attached in Word and PDF)
  5. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs)
  6. AOB

BACKGROUND DOCUMENTS


GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 05 March 2019 DRAFT.pdf

Timeline_ Development of Guidelines & Templates for GNSO Role in the Empowered Community.pdf

RECORDINGS


mp3

AC recording

GNSO transcripts are located on the GNSO Calendar

PARTICIPATION

Attendance & AC chat

Apologies:  Juan Manuel Rojas, Erica Varlese

Notes/ Action Items


Actions:

ACTION ITEM re: Timeline -- Heather will communicate the timeline to the GNSO Council leadership (DONE 27 March by Heather – final is attached)

ACTION ITEMS re: Sections 4.2 and 4.3 Guidelines and Templates

1. Staff will revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. (DONE 28 March by staff and attached in Word and PDF)

2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. (DONE 28 March by staff)

ACTION ITEMS re: Section 18.12 Special IFRs

1. 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 and attached in Word and PDF.  (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED)

-- 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.

-- Can we focus on just how to coordinate on just the consultation process.  How formal do we need to be with that consultation process?  Could be informal during development, but more formal for approval which you can enter into via the respective chairs.

2. Coordination with the ccNSO Guidelines Review Committee:

-- Staff is checking with ccNSO support staff on timing.  (ONGOING)

-- David McAuley will check with Katrina Sataki, ccNSO Chair. (ONGOING)

-- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED)

 

Notes:

 

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

 

2. Review and approval of Draft Timeline:

-- Discussion on 18.12 Special IFRs will include a need to coordinate with the ccNSO.

-- Three-call rotation to complete/approve documents.

-- Substantive work done by end of May.

-- Package would go to the Council in time for the June document deadline (16 June).  Suggest putting this on the agenda as a discussion item.

-- One of us to attend the June meeting (Heather volunteers).

-- Gives the time to go back to SGs and Cs.

-- Proposed vote in the July GNSO Council meeting.

ACTION ITEM: Heather will communicate the timeline to the GNSO Council leadership.

 

3. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3:

-- Page 7, Question 10: on whether we can ask if you are bringing this Reconsideration Request on behalf -- insert a 10a include the names/contact on whose behalf you are bringing this request.

-- Question 6, re: Question 10 -- could we identify others in this question?  The responses to the questions are slightly different.

-- If people disagree that you are bringing the claim on behalf of them then the claim is invalid.  ICANN should confirm.

-- What if it can't be verified?  This would be so rare I don't think we have to anticipate that this would happen.

-- Question 10 asked if you are bringing it on behalf of multiple entities, but we haven't asked if it is on behalf of a single entity.  If there is even one more the question would be accurate.

-- Informal feedback to staff: the form is not as clear as it could be.  Once we've used it more in practice it might be further improved.

-- A single entity can represent multiple entities.

ACTION ITEMS:

1. Revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities.

2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text.

 

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

-- Bringing an IFR outside of the IFR process (a "Special IFR" and only in two instances.

-- Where a remedial action has already taken place but has not resolved the problem.

-- These are very limited circumstances.

-- The GIP GIP is proposed, but as a suggestion for the DT to consider.  There might be other options, such as a small group within the Council, for example, or a drafting team.

-- Consider not reinventing the wheel.

-- Might require additional time, but perhaps allow for consultation with experts, research, etc.

-- Might be necessary given the IANA function.

-- ccNSO Guidelines Review Committee: May need a bit more time than in the GNSO.

 

ACTION ITEMS:

1. GNSO Input Process: The DT member review the GIP and in the context of the initiation of a Special IFR on the IANA function.  Staff will provide a link to the document.  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.

-- Can we focus on just how to coordinate on just the consultation process.  How formal do we need to be with that consultation process?  Could be informal during development, but more formal for approval -- which you can enter into via the respective chairs.

2. Coordination with the ccNSO Guidelines Review Committee. 

-- Staff is checking with ccNSO support staff on timing. 

-- David McAuley will check with Katrina Sataki, ccNSO Chair. 

-- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision.

 

6. AOB: Next meeting Wednesday, 10 April 2019 at 21:00 UTC.


  • No labels