Please find the meeting information below for the Joint GRC/DT Meeting re: ccNSO GRC questions re: consulting on Special IFRs call on Monday, 15 July 2019 at 12:00 UTC for 60 minutes.


PROPOSED AGENDA


  1. Welcome and roll call
  2. Special IFR (attached:  Draft suggested timeline and questions)
  3. AOB
  4. Closure

BACKGROUND DOCUMENTS


Questions.pdf

SIFR Process Steps v 03 July 2019.pdf

RECORDINGS


Audio Recording

Zoom Recording

Chat Transcript

GNSO transcripts are located on the GNSO Calendar

PARTICIPATION


Attendance  

Apologies:  Erica Varlese, Maxim Alzoba

Notes/ Action Items


ACTION ITEMS:


Action item #1: 

Q3. David McAuley to suggest alternative language, with added flexibility.

[completed by Julie Hedlund]


Action item #2: 

Q5. David McAuley to suggest alternative language

Q5. GNSO staff to verify the guideline to ensure there is a formal reference in the guidelines to note that the work is concluded. 


Action item #3:

Julie Hedlund to update the guidelines document based on today’s discussion, and share the revised text with the GNSO DT, and GRC. Incorporate the timing into the guideline document.


Action item #4:

Staff will adjust the timeline to show the maximum and minimum timing


NOTES:


  1. Welcome and roll call

Attendance will be taken based on who is on Zoom.  Apologies from:  Alyssa Moore.  Calls will be recorded and posted on the public wiki.  Please remember to mute your phones and microphones when not speaking.


  1. Special IFR 

Julie Hedlund: questions from the previous meeting. Edits/suggestions in red by David McAuley.

David McAuley: 5 questions displayed on screen. Suggestions by David to the GNSO design team.


Q1. when to establish sIFR?

First to PTI Board, then to ICANN CEO and then to the Board.


Q2. GNSO and ccNSO councils working together. 

SICT to issue statement, and mention both councils signed off on it.

Support by Heather. Helpful to have guidelines. Flexible timing is appreciated.


Q3. even distribution of the work

Suggestion for SICT to keep duties under 5.4 and 5.6 and council deals with 5.5. (deciding whether to request a public comment period). “The councils may determine that …” More flexibility might be needed in the phrasing: avoid being too prescriptive.


Action item #1: 

Q3. David McAuley to suggest alternative language, with added flexibility.

[completed by Julie Hedlund]


Q4. other avenues to address the PTI issue

Alternative language suggested

Steve Del Bianco: It’s an excellent idea to require consideration of alternative means to address an IANA functions problem.

Bart: ICT to suggest to councils to look into alternative means to address the issue around PTI performance. When looking at the timeline, it becomes an issue.


Q5. closing down SICT if the CSC manages to fix the problem.

No alternative language suggested yet by David.

Bart: close the loop, the process to avoid unclarity on whether to proceed or not.

Heather: do we have a formal way of communicating - regardless of whether SICT has concluded its work or not?


Action item #2: 

Q5. David McAuley to suggest alternative language

Q5. GNSO staff to verify the guideline to ensure there is a formal reference in the guidelines to note that the work is concluded. 


Action item #3:

Julie Hedlund to update the guidelines document based on today’s discussion, and share the revised text with the GNSO DT, and GRC. Incorporate the timing into the guideline document.


Bart: speaks to the timeline. Starting point is when CSC sends a formal notification of the GNSO and ccNSO councils. In the meanwhile the CSC did already some actions under the Remedial Action Procedure. Min 10 days before the notification. More realistically: 30 days.

During that period, when the Board is informed by the CSC: good timing for the coordination group to be established. Do every year a reminder. Starting point (day 0): CSC notifies both councils (use a template). Review actions: how long this will take is determined by internal procedures. 3 weeks, maybe less. Inform the Board, and then the Board will call a special review to commence. Call for volunteers, run by ICANN Org. 


Action item #4:

Staff will adjust the timeline to show the maximum and minimum timing


Next steps: once the update document is being shared, GRC to review.


Absolute minimum: bylaw requirement? Flexibility not to launch a public consultation.so you can get rid of 45 days.

Critical part: how long do the councils need? 


GNSO staff to share the document by the end of the week. Suggestion to conclude the work by the end of August.


  1. AOB


  1. Closure
  • No labels