[Gnso-bylaws-dt] REMINDER - FOR APPROVAL BY COB 11 APRIL 2019: Guidelines and Motion Templates 4.2 Community IRP & 4.3 IRP for Covered ICANN Actions

Thu Apr 4 15:55:39 UTC 2019

Dear all,

This is a reminder of the action item for consideration and approval by DT members.  See details below.

If there are no objections received in one week by COB Thursday, 11 April the document will be considered as approved by the Drafting Team.  If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them.

Thank you very much for your consideration.

With best regards,
Julie

From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces at icann.org> on behalf of Julie Hedlund <julie.hedlund at icann.org>
Date: Thursday, March 28, 2019 at 6:08 PM
To: "gnso-bylaws-dt at icann.org" <gnso-bylaws-dt at icann.org>
Subject: [Gnso-bylaws-dt] FOR APPROVAL BY COB 11 APRIL 2019: Guidelines and Motion Templates 4.2 Community IRP & 4.3 IRP for Covered ICANN Actions

Dear all,

Per the action items below, please review the attached final version of the Guidelines and Motion Templates for Sections 4.2 Community IRP and 4.3 IPR for Covered ICANN Actions.  This document reflects the accepted edits previously reviewed, as well as the revision requested at the meeting on 27 March to question 10 of the Reconsideration Request to separate the question into 10a and 10b asking for names and contact information of multiple entities.

If there are no objections received in two weeks by COB Thursday, 11 April the document will be considered as approved by the Drafting Team.  If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them.

Thank you very much for your consideration.

With best regards,
Julie
Julie Hedlund, Policy Director

From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces at icann.org> on behalf of Julie Hedlund <julie.hedlund at icann.org>
Date: Thursday, March 28, 2019 at 5:55 PM
To: "gnso-bylaws-dt at icann.org" <gnso-bylaws-dt at icann.org>
Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 27 March 21:00 UTC

Dear all,

Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 27 March 2019 (21:00-22:00 UTC).  Staff have posted to the wiki space the action items and notes.  Please note that these are high-level notes and are not meant as a substitute for the recording, chat room, or transcript. The recording, AC chat, transcript and attendance records are posted on the wiki at: https://community.icann.org/pages/viewpage.action?pageId=105383460.

Best Regards,
Julie
Julie Hedlund, Policy Director

ACTIONS & NOTES:

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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_annex-2D3-2Dinput-2Dprocess-2Dmanual-2D18jun18-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=VTAJdtLMkvUT9bfmr7KeEF99S4rkchPeXPMyJLuYuLY&s=VyZKr_fwCqgVrYp_SmkIy1OR9bF6i8s6NPV47i2xs7M&e=> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-bylaws-dt/attachments/20190404/3b1ebd76/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 28 March 2019 FINAL.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 28904 bytes
Desc: GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 28 March 2019 FINAL.docx
URL: <http://mm.icann.org/pipermail/gnso-bylaws-dt/attachments/20190404/3b1ebd76/GUIDELINESMOTIONTEMPLATESArticle4AccountabilityandReview4.2CommunityIRP4.3IRP28March2019FINAL-0001.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 28 March 2019 FINAL.pdf
Type: application/pdf
Size: 81456 bytes
Desc: GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 28 March 2019 FINAL.pdf
URL: <http://mm.icann.org/pipermail/gnso-bylaws-dt/attachments/20190404/3b1ebd76/GUIDELINESMOTIONTEMPLATESArticle4AccountabilityandReview4.2CommunityIRP4.3IRP28March2019FINAL-0001.pdf>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://mm.icann.org/pipermail/gnso-bylaws-dt/attachments/20190404/3b1ebd76/ATT00001-0001.txt>