[NCSG-PC] Fwd: [Gnso-bylaws-dt] FOR FINAL REVIEW: Revised Guidelines & Motion Template - Section 1.3 Approval Action Community Forum (11 July 2019)

Rafik Dammak rafik.dammak at gmail.com
Tue Jul 16 03:13:59 EEST 2019


Thanks Stephanie for sharing this.
while this will come to council for adoption, it is critical to review and
make changes at DT level. I would like ask everyone to review and see if
there is any area of concern.

Rafik

Le lun. 15 juil. 2019 à 22:37, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca> a écrit :

>
> I must confess that I have missed the last couple of meetings on this
> issue.  As you can see, the final draft is nearly ready, we need to comment
> asap.  Please, folks who participated more closely in the IANA review, take
> a look.  Or tell me who I should forward this to to take a look.
> cheers Steph
> -------- Forwarded Message --------
> Subject: [Gnso-bylaws-dt] FOR FINAL REVIEW: Revised Guidelines & Motion
> Template - Section 1.3 Approval Action Community Forum (11 July 2019)
> Date: Thu, 11 Jul 2019 21:04:56 +0000
> From: Julie Hedlund <julie.hedlund at icann.org> <julie.hedlund at icann.org>
> To: gnso-bylaws-dt at icann.org <gnso-bylaws-dt at icann.org>
> <gnso-bylaws-dt at icann.org>
>
> Dear DT members,
>
>
>
> Per action item 2 below from the meeting on 10 July, please review the
> revised version of the GUIDELINES & MOTION TEMPLATE: SECTION 1.3 APPROVAL
> ACTION COMMUNITY FORUM DRAFT (11 July 2019) at:
> https://docs.google.com/document/d/1v5qtCO0Ocrbkk6o2YVrsuIWwjTQsprdEmWBYD35OH6o/edit?usp=sharing.
> The document also is attached in Word with redlines.
>
>
>
> The document will be on the agenda *for finalization/approval *at the
> next meeting on *Wednesday, 24 July at 21:00 UTC*.  In the meantime, DT
> members are encouraged to make suggested edits and comments in the Google
> document or in the Word document.
>
>
>
> Thank you very much for your consideration.
>
>
>
> Kind regards,
>
> Julie
>
> Julie Hedlund, Policy Director
>
>
>
> *From: *Gnso-bylaws-dt <gnso-bylaws-dt-bounces at icann.org>
> <gnso-bylaws-dt-bounces at icann.org> on behalf of Julie Hedlund
> <julie.hedlund at icann.org> <julie.hedlund at icann.org>
> *Date: *Thursday, July 11, 2019 at 4:59 PM
> *To: *"gnso-bylaws-dt at icann.org" <gnso-bylaws-dt at icann.org>
> <gnso-bylaws-dt at icann.org> <gnso-bylaws-dt at icann.org>
> *Subject: *[Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting
> 10 July 21:00 UTC
>
>
>
> Dear all,
>
>
>
> Please see below the action items and notes captured by staff from the GNSO
> Drafting Team meeting held on 10 July 2019 (21:00-22:00 UTC).  Staff have
> posted these to the wiki space.  *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=111387729.
>
>
>
> Please note that all versions of the guidelines may be found on the wiki
> at:
> https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Depository.
>
>
>
>
> Best Regards,
>
> Julie
>
> Julie Hedlund, Policy Director
>
>
>
> *Actions Items:*
>
>
>
>    1. *Joint ccNSO/GNSO Initiation of a Special IFR*: Staff will check on
>    the status of questions to ICANN Legal, specifically on whether the GNSO
>    and ccNSO can jointed initiate a Special IFR. (DONE – see response in
>    separate message.)
>    2. *Section 1.3 Approval Action Community Forum*: Staff will accept
>    the grammatical edits in the document from Heather Forrest and generate a
>    new version with the flagged issues/comments called out for DT
>    consideration (see below), including a timeline for the GNSO Council
>    actions. (DONE – see documents for review in separate message.)
>    3. *Preparation for 24 July Meeting*: Staff will circulate for DT
>    review the draft of Section 2.2 Petition Process for Specified Actions and
>    Section 2.3 Rejection Action Community Forum. (DONE – see documents for
>    review in separate message.)
>
>
>
> *Notes:*
>
>
>
> 1. Updates to Statements of Interest (SOIs): None provided.
>
>
>
> 2. Section 18.12 Special IFRs -- Brief Update re: 15 July joint GRC/DT
> meeting on Guidelines for GNSO-ccNSO Consultation on Initiating a Special
> IFR:https://docs.google.com/document/d/1ol8461abkOqzXSahZKkuLL-7GxDWklmA0wnK1CKwfgY/edit?usp=sharing
> [docs.google.com]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1ol8461abkOqzXSahZKkuLL-2D7GxDWklmA0wnK1CKwfgY_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=RfYmWnCQSyLL0EsBnWmD6gb5eu50atShEcYcuw1NcLg&s=aQxrVGGlnlFIhJqK6BXgA3NWGE0zel27UR03KM5AROE&e=>
>
>
>
> -- What do we expect from the meeting on 15 July and how do we move
> forward?  Could the GRC be satisfied from the call on Monday, or would
> there be additional deliberations?
>
> -- Expectation that it is a matter of clarification and coming to a common
> understanding of the questions.  The GRC and DT can finish their documents
> and they would have two common approaches.
>
>
>
> *ACTION ITEM:* *Staff will check on the status of questions to ICANN
> Legal, particularly as to whether the GNSO and ccNSO can jointly initiate a
> Special IFR.*
>
>
>
> 3. Discussion/Edits re: Section 1.3 Approval Action Community Forum:
> https://docs.google.com/document/d/1tR6YeATOl-_6ig7XKKluR3jwY8cLPYKoLCB-t6GhVNc/edit?usp=sharing
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1tR6YeATOl-2D-5F6ig7XKKluR3jwY8cLPYKoLCB-2Dt6GhVNc_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=sbkfLm_KS_6kkvPCW33WPWzEqKV0o0RQ_pxSldlvwrw&s=b2S5eYTIFBKQ9F6ZQVRjv1LGZuYnfgHf-hFZ_XSd5uU&e=>
>
>
>
> -- Staff and David McCauley noted that there is a real-time example of the
> anticipated use of the Approval Action Community Forum to consider the
> ccNSO’s request for a Fundamental Bylaws Amendment regarding the IANA
> Naming Function Review Team's Composition.  See: https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-2019-06-10-en
> [icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_bylaws-2Damend-2Diana-2Dnaming-2Dfunction-2D2019-2D06-2D10-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=5VHwARxTSP3PsyJJ-5TsXhC-aJ7h8NXUJdIjfi89Kpg&s=Yb4Kf5QFfGYTcUVHIKbC6T3MT0aMgQq4CKR8jzUp-lg&e=>
> .
>
> -- Staff also noted that the EC Administration has accordingly requested,
> per the Bylaws, that an Approval Action Community Forum should be scheduled
> to take place during ICANN66 in Montreal.
>
>
>
> Edits/Comments for DT Consideration in the Google Doc (as called out in
> the revised version dated 11 July):
>
>
>
>    1. Noting that although the current representative to the EC
>    Administration is the GNSO Council Chair, there is nothing to prevent the
>    GNSO Council from choosing a different person as its representative.  Thus,
>    it is suggested that references to the GNSO Council Chair in the document
>    should be changed to GNSO Representative to the EC Administration (see page
>    4 and onward).  Maxim Alzoba also inserted a comment relating to this
>    issue, so we request that he should review this suggested edit.
>    2. 4.3.1 Consultation Mechanism:
>
> a.      Change “If such a consultation is scheduled” to “If such a
> consultation occurs”.
>
> b.      In response to a point made by David McCauley about ensuring that
> the GNSO Council can meet the decision deadline of 21 days as specified in
> the Bylaws, add to the last sentence, “and in no event later than the
> 21-day Approval Action Decision Period per Section 1.4 Annex D of the
> Bylaws.”
>
>    1. 4.3.2 GNSO Council Decision and Informing the EC Administration:
>
> a.      The DT discussed how to ensure that the GNSO Council’s actions to
> decide on whether to support, object to, or abstain from the Approval
> Action are completed within the above-mentioned 21-day period.  Staff
> suggested adding a timeline showing the timing of the activities.  In
> addition, staff has added the excerpt from the Bylaws with the relevant
> details.
>
> b.      On 11 July Wolf-Ulrich Knoben suggested edits to combine sections
> 4.3.2 and 4.3.3 into one section.  Staff has included those edits in the
> version dated 11 July.
>
>    1. Staff also accepted all of the grammatical changes provided by
>    Heather Forrest.
>
>
>
> *ACTION ITEM: Staff will accept the grammatical edits in the document from
> Heather Forrest and generate a new version with the flagged issues/comments
> called out for DT consideration, including a timeline for the GNSO Council
> actions.*
>
>
>
> 4. Next Meeting: 24 July:  The DT will finalize its review of Section 1.3,
> and begin review of Section 2.2 Petition Process for Specified Actions and
> Section 2.3 Rejection Action Community Forum.
>
>
>
> *ACTION ITEM: Staff will circulate for DT review the draft of Section 2.2
> Petition Process for Specified Actions and Section 2.3 Rejection Action
> Community Forum. *
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20190716/fe78f54c/attachment.htm>


More information about the NCSG-PC mailing list