[council] Final Proposed Agenda | GNSO Council Meetings part 1 and 2 | 21 October 2020 at 13:00 CET / 11:00 UTC
Rafik Dammak
rafik.dammak at GMAIL.COM
Sun Oct 11 18:40:06 EEST 2020
hi all,
please find below the proposed agenda for next GNSO Council meetings next
week. As it is during the Annual General Meeting (AGM), there will be 2
parts, with the 2nd part for the new council to elect the GNSO chair.
We will discuss it at the NCSG Policy committee meeting which is open to
all this Thursday 15th Oct, 12:00UTC (you can find details here
https://69.schedule.icann.org/)
Best,
Rafik
---------- Forwarded message ---------
De : Nathalie Peregrine <nathalie.peregrine at icann.org>
Date: lun. 12 oct. 2020 à 06:13
Subject: [council] Final Proposed Agenda | GNSO Council Meetings part 1 and
2 | 21 October 2020 at 13:00 CET / 11:00 UTC
To: council at gnso.icann.org <council at gnso.icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>
Dear all,
Please find below the final proposed agenda for the GNSO Council Meeting on 24
September 2020 at 12:00 UTC.
Draft GNSO Council Agenda 21 October 2020 - Part I
Please note that all documents referenced in the agenda have been gathered
on a Wiki page for convenience and easier access:
https://community.icann.org/x/OAebC
This agenda was established according to the GNSO Operating Procedures
<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-24oct19-en.pdf>
v3.5, updated on 24 October 2019
For convenience:
- An excerpt of the ICANN Bylaws defining the voting thresholds is
provided in Appendix 1 at the end of this agenda.
- An excerpt from the Council Operating Procedures defining the absentee
voting procedures is provided in Appendix 2 at the end of this agenda.
GNSO Council meeting held 13:00 CET (Hamburg time)
Coordinated Universal Time: 11:00 UTC: https://tinyurl.com/y3nxs8rf
04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Moscow; 20:00
Tokyo; 22:00 Melbourne
GNSO Council Meeting Remote Participation: Not available until 24 hours
before.
___________________________________
*Item 1: Administrative Matters (10 mins)*
1.1 - Roll Call
1.2 - Updates to Statements of Interest
1.3 - Review / Amend Agenda
1.4 - Note the status of minutes for the previous Council meetings per the
GNSO Operating Procedures:
Minutes
<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso-council-20aug20-en.pdf>of
the GNSO Council meeting on 20 August 2020 were posted on 04 Sep 2020.
Minutes
<https://gnso.icann.org/sites/default/files/policy/2020/minutes/minutes-gnso-council-24sep20-en.pdf>
of the GNSO Council meeting on the 24 September 2020 were posted on 9
October 2020.
*Item 2: Opening Remarks / Review of Projects & Action List (10 minutes)*
2.1 - Review focus areas and provide updates on specific key themes /
topics, to include review of Projects List
<https://gnso.icann.org/en/council/project>and Action Item List.
<https://community.icann.org/x/RgZlAg>
*Item 3: Consent Agenda (10 minutes) *
3.1 - Action Decision Radar
<https://community.icann.org/download/attachments/40175174/program_management_tool_20200924.pdf?version=1&modificationDate=1599834261000&api=v2>
- *Next Steps for WHOIS Conflicts Procedure Implementation Advisory Group*
The GNSO Council has considered the proposed immediate actions and
subsequent steps as outlined in the WHOIS Conflicts Procedure IAG (WHOIS
IAG) Small Team’s proposal
<http://mm.icann.org/pipermail/council/attachments/20201006/2a0c0c3e/SummaryofWHOISConflictsProcedureIAGSmallTeamProposal-0001.docx>.
The proposal outlines recommended next steps to consider with respect to
modifying the implementation of the WHOIS Conflicts Procedure, in light of
public comments received and changes to data protection law that may have
affected the implementation of the Procedure. Specifically, the GNSO
Council requests:
1. ICANN org, in consultation with contracted parties, to draft a
proposal for a modification to the existing Procedure based on its past
experience with both the WHOIS Conflicts Procedure and the registrar data
retention waiver process. In formulating the draft proposal, the GNSO
Council recommends that ICANN org consider changes to data protection law
that may have affected the previous implementation of this Procedure in
light of the contractual requirements, e.g., the General Data Protection
Regulation. For example, should the identification of a new trigger to
activate the procedure be considered given potential financial penalties
under GDPR?
2. Following receipt of the proposal from ICANN org, the GNSO Council
will consider the proposal and assess next steps, including seeking input
from the community, if appropriate, given the substance of the proposal.
Following the GNSO Council’s consideration, the GNSO Council may choose to
adopt the proposal.
3. If the GNSO Council does not deem the proposal appropriate:
a. the GNSO Council will recommend a small group of
Council volunteers to review the WHOIS IAG draft charter
<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-icann-procedure-whois-conflicts-iag-23jan18-en.pdf>
and confirm it is still fit for purpose; and
b. Following confirmation of the Charter by the GNSO
Council, the GNSO Council recommends launching the call for volunteers for
the WHOIS IAG, taking into consideration the GNSO Council’s upcoming
workload. For example, the call for volunteers may need to be postponed if
no community bandwidth is available to immediately consider the issues. In
the meantime, ICANN org, in conjunction with the EPDP Phase 1 IRT, will
need to update relevant terminology pursuant to EPDP Phase 1, Rec. 27.
1. Should the GNSO Council consider the outcome developed from the WHOIS
IAG unacceptable, the GNSO Council will consider initiating an EPDP to
either change or repeal the Consensus Policy.
3.2 - Action Decision Radar
<https://community.icann.org/download/attachments/40175174/program_management_tool_20200924.pdf?version=1&modificationDate=1599834261000&api=v2>
- Per the rationale circulated on 11 October 2020, Council agrees to launch
a call for volunteers for a small team to develop both a draft charter and
an EPDP scoping document for the IDN Policy Track 2.
3.3 - Following the GNSO Council’s consideration of the proposed immediate
actions and subsequent steps as outlined here
<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-priority-2-items-10sep20-en.pdf>,
the GNSO Council directs:
*EPDP Phase 2a – Legal/natural and feasibility of unique contacts*
1. The GNSO Policy Support Team communicate to the groups that have
appointed members to the EPDP Team that the Council is expected to instruct
the EPDP Team to further consider the topics of legal/natural and
feasibility of unique contacts per the instructions above, as well as the
expected timeframe, provided herein for reference, “[a]t the latest 3
months after reconvening, the Chair of the EPDP Team and GNSO Council
Liaison to the EPDP will report back to the GNSO Council on the status of
deliberations. Based on this report, which is expected to include an update
on progress made and the expected likelihood of consensus recommendations,
the GNSO Council will decide on next steps, which could include
providing additional time for the EPDP to finalize its recommendations or
termination of the EPDP if it is clear that no progress is being made or
consensus is unlikely). Request groups to:
a. Commence process of confirming members availability
and/or re- appointing members to work on these topics. Proposed deadline:
15 November.
b. Start developing proposals to address these topics,
factoring in deliberations to date, that will allow the EPDP Team to
kickstart deliberations on these topics when it reconvenes.”
1. The Council leadership to initiate an Expression of Interest Process
to identify a new Chair.
The EPDP Team shall recommence its deliberations upon selection and
confirmation of a new Chair; however, should no suitable candidates be
found or should the appointment process require significant time, Council
leadership will inform the Council accordingly and recommend commencement
of deliberations under the leadership of the GNSO Council liaison to the
EPDP Team.
*Accuracy:*
1. The GNSO Policy Support Team communicates to GNSO SG/Cs, as well as
ICANN Advisory Committees that have expressed an interest in the topic of
accuracy, the intent of the GNSO Council to launch a scoping team on this
topic. Request groups to:
a. Start thinking about members that have relevant
knowledge and expertise that should join this effort once the scoping team
launches.
b. Start compiling relevant information and suggestions
that would allow kickstarting the discussions on 1. and 2. once the scoping
team is formed (see here
<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-priority-2-items-10sep20-en.pdf>
for resources already identified).
1. Council leadership to request ICANN Org to develop a briefing
document that outlines both (i) existing accuracy requirements and programs
and (ii) the corresponding impact that GDPR has had on implementing /
enforcing these requirements and programs. The document, once delivered,
will be provided to the scoping team to inform its deliberations.
2. GNSO Council to consider in the context of the Council Action /
Decision Radar, the appropriate starting time for this effort, factoring in
other projects that are in the pipeline.
3.4 - Confirmation of the Recommendations Report
<https://gnso.icann.org/sites/default/files/file/field-file-attach/draft-epdp-phase-2-report-08oct20-en.pdf>
to the ICANN Board regarding adoption of recommendations 1-22 contained in
the Final Report from the EPDP Temporary Specification for gTLD
Registration Data – Phase 2.
3.5 - Appointment of the GNSO Liaison to the Governmental Advisory
Committee (motion <https://community.icann.org/x/OgebC>)
*Item 4: COUNCIL DISCUSSION - Discuss Draft Motion to Affirm intent of EPDP
Phase 1 Recommendation 7 and Initiation of the Thick WHOIS Transition
Policy EPDP (25 minutes)*
In adopting the Expedited Policy Development Process (EPDP) on the
Temporary Specification Final Report and Recommendations, the Council
requested that an informal Implementation Review Team (IRT) be established,
which was done. After the recommendations were approved by the ICANN Board,
the informal IRT transitioned to a formal IRT and has diligently been
working to implement the policy recommendations. Within the IRT, there are
diverging views amongst some IRT members on how to implement recommendation
7, especially in relation to the Thick WHOIS Transition Policy for .COM,
.NET, and .JOBS
The ICANN Board, taking note of the potential impasse, sent a letter
<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/botterman-to-drazek-2-11mar20-en.pdf__;!!PtGJab4!oQwV9HCMGhXBS5EtU3aOkRxs-f4RQKkHbMUNsLes--FAx9ODzxL57AybmR5oXmWG2uZ2OXw$>
to the GNSO Council on 11 March 2020. The Council considered the letter and
agreed that recommendation 7 did not explicitly overturn the Thick Whois
Transition Policy; to do so will require the GNSO Council to initiate
policy development. The Council sent a response
<https://urldefense.com/v3/__https:/www.icann.org/en/system/files/correspondence/little-dammak-to-botterman-29may20-en.pdf__;!!PtGJab4!oQwV9HCMGhXBS5EtU3aOkRxs-f4RQKkHbMUNsLes--FAx9ODzxL57AybmR5oXmWGbazEgkk$>
to the ICANN Board on 29 May 2020. The IRT has continued to try and
implement recommendation 7 but has still been unable to reach agreement. As
such and per the Council’s letter, the Council requested a briefing from,
”the GNSO Council liaison detailing the precise nature of the impasse so
that the GNSO Council can make an informed determination on how to
proceed.” During its September Council meeting, the Council received a
briefing from the GNSO Council liaison to the IRT, Sebastien Ducos. The
Council agreed to convene a small team of Councilors that was charged with
establishing a path forward to try and resolve the impasse. That small team
met to determine what the best practical path forward may be.
Here, the Council will consider a draft motion that would do two things 1)
Affirm the intent of EPDP Phase 1 Recommendation 7; and 2) initiate an EPDP
on the Thick WHOIS Transition Policy.
4.1 - Introduction of topic (Council Vice-Chair, Pam Little)
4.2 – Council discussion
4.3 – Next steps
*Item 5: COUNCIL DISCUSSION - Draft Operational Design Phase for gTLD
Policy Implementation (15 minutes)*
During the 23 September SO/AC Leaders call, the concept of an "Operational
Design Phase" was introduced by Goran. The SO/AC Leaders had a preliminary
discussion on the topic and Goran indicated that ICANN would produce a
paper for community consideration and feedback. That paper
<http://mm.icann.org/pipermail/council/attachments/20201005/2000130c/Design-Phase-Concept-Draft-1oct20-0001.pdf>
was prepared and was shared with the Council on 5 October 2020.
The objective for this new proposed design phase is to better prepare the
Board by providing operational and resourcing information before making
decisions on GNSO-approved policy recommendations. The paper notes that
while the GNSO Council is the manager of the PDP and gTLD policy
development is within the GNSO's remit, consensus policy making involves
all stakeholders (including ACs who give advice to the Board). Further, the
paper seeks to be clear that this design phase concept doesn't affect
policy development or the Consensus Policy Implementation Framework. It
recognizes that if policy issues are impacted, they rightfully go back to
the GNSO for its consideration, rather than permitting ICANN Org or Board
to make unilateral changes.
The Stakeholder Groups and Constituencies were invited and encouraged to
provide feedback to the paper. In addition, on a 6 October GNSO Council
pre-ICANN working session, Karen Lentz from ICANN org provided additional
information and rationale for the new concept.
Here, Councilors will be invited to share their initial thoughts on the
concept and the paper.
5.1 - Introduction of topic (Council leadership)
5.2 - Council discussion
5.3 - Next steps
*Item 6: COUNCIL DISCUSSION - Board Consultation Regarding **Questions
Surrounding the financial Sustainability of the System for Standardized
Access and Disclosure (20 minutes)*
On 24 September 2020, the GNSO Council adopted the recommendations
contained in the Expedited Policy Development Process (EPDP) on the
Temporary Specification Phase 2 Final Report
<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf>.
Resolved clause 1b. states:
*b. [if 1a. is adopted] Noting some of the questions surrounding the
financial sustainability of SSAD and some of the concerns expressed within
the different minority statements, the GNSO Council requests a consultation
with the ICANN Board as part of the delivery of the GNSO Council
Recommendations Report to the ICANN Board to discuss these issues,
including whether a further cost-benefit analysis should be conducted
before the ICANN Board considers all SSAD-related recommendations for
adoption.*
The request for a consultation with the ICANN Board is not usually an
element of the transition of GNSO-approved recommendations from the GNSO
Council to the ICANN Board. As such, the Council will need to consider how
best to engage with the Board in seeking this consultation.
Here, the Council will discuss next steps as it relates to resolved clause
1b, including whether the draft Transmittal Letter
<https://gnso.icann.org/en/drafts/draft-transmittal-letter-icann-board-08oct20-en>
accurately captures the agreed-upon approach of the Council.
6.1 - Introduction of topic (Council leadership)
6.2 - Council discussion
6.3 - Next steps
*Item 7: COUNCIL DISCUSSION - ADR Item - Council to Consider Delay of the
Request for the Policy Status Report for the Expiration Policy(ies) (10
minutes)*
As indicated on the Action Decision Radar
<https://community.icann.org/display/gnsocouncilmeetings/Action+Items?preview=/40175174/147849802/GNSO_Council_Program_ADR_20200924.pdf>,
the GNSO Council is to consider when to request a Policy Status Report to
conduct a review of the two Expiration Policies, the Expired Domain
Deletion Policy
<https://www.icann.org/resources/pages/registars/accreditation/eddp-en>
(EDDP) and the Expired Registration Recovery Policy
<https://www.icann.org/resources/pages/errp-2013-02-28-en> (ERRP). Given
the concerns about capacity, along with the circumstances that no known
issues have presented themselves, Council leadership is suggesting that the
request for Policy Status Reports for these two Consensus Policies can be
delayed by a period of 24 months, assuming no substantive issues arise
during that time. This would have the effect of deferring the request for a
Policy Status Report on the EDDP and ERRP until at least November 2022,
where it would then be discussed again to determine if a request is timely.
Here, the Council will consider whether it agrees with this suggestion and
if so, agree to include on the November consent agenda.
7.1 - Introduction of topic (Council leadership)
7.2 - Council discussion
7.3 - Next steps
*Item 8: ANY OTHER BUSINESS (20 minutes)*
8.1 - Farewell to outgoing Councilors (Elsa Saade, Erika Mann, James
Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and
Scott McCormick.)
8.2 - Open microphone
_______________________________
Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11,
Section 11.3(i))
See https://www.icann.org/resources/pages/governance/bylaws-en/#article11.
Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating
Procedures, Section 4.4)
See
https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf
References for Coordinated Universal Time of 11:00 UTC
Local time between March and October Summer in the NORTHERN hemisphere
----------------------------------------------------------------------------
California, USA (PDT) UTC-7 04:00
San José, Costa Rica (CST) UTC-6 06:00
New York/Washington DC, USA (EDT) UTC-4 07:00
Buenos Aires, Argentina (ART) UTC-3 08:00
Rio de Janeiro, Brazil (BRST) UTC-3 08:00
London, United Kingdom (GMT) UTC+1 12:00
Kinshasa, Democratic Republic of Congo (WAT) UTC+1 12:00
Paris, France (CEST) UTC+2 13:00
Moscow, Russia (MST) UTC+3 14:00
Singapore (SGT) UTC+8 19:00
Tokyo, Japan (JST) UTC+9 20:00
Melbourne, Australia (AEDT) UTC+11 22:00
----------------------------------------------------------------------------
DST starts/ends on Sunday 25 of October 2020, 2:00 or 3:00 local time (with
exceptions) for EU countries and on Sunday 01 of November 2020 for the US.
----------------------------------------------------------------------
For other places see http://www.timeanddate.com and h
ttps://tinyurl.com/y3nxs8rf
Final GNSO Council Agenda 21 October 2020 - Part II (Admin)
Please note that *all documents *referenced *in the agenda have been
gathered on a Wiki page for convenience and easier access:*
https://community.icann.org/x/OAebC
This agenda was established according to the GNSO Operating Procedures
<https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-24oct19-en.pdf>
v3.5 updated on 24 October 2019
For convenience:
- An excerpt of the ICANN Bylaws defining the voting thresholds is
provided in *Appendix 1* at the end of this agenda.
- An excerpt from the Council Operating Procedures defining the absentee
voting procedures is provided in *Appendix 2* at the end of this agenda.
GNSO Council meeting held 15:15 CET (Hamburg time)
Coordinated Universal Time: 13:15 UTC: https://tinyurl.com/yyor7bfj
06:15 Los Angeles; 09:15 Washington; 14:15 London; 16:15 Moscow; 22:15
Tokyo; (Thursday 22 October) 00:15 Melbourne
GNSO Council Meeting Remote Participation: Not available until 24 hours
before.
*___________________________________*
*Item 1. Seating of the 2020 / 2021 Council (20 mins)*
1.1 - Roll Call
1.2 - Statements of Interest
INCOMING COUNCILORS:
Kurt Pritz: SOI <https://community.icann.org/display/gnsosoi/Kurt+Pritz+SOI>
Registries Stakeholder Group
Kristian Ørmen - SOI
<https://community.icann.org/pages/viewpage.action?pageId=66081213>
Registrars Stakeholder Group
Mark Datysgeld: SOI
<https://community.icann.org/display/gnsosoi/Mark+Datysgeld+SOI> Business
Constituency
Stephanie Perrin: SOI
<https://community.icann.org/display/gnsosoi/Stephanie+Perrin+SOI>
Non-Commercial Stakeholder Group
Wisdom Donkor: SOI
<https://community.icann.org/display/gnsosoi/Wisdom+Donkor+SOI>
Non-Commercial Stakeholder Group
Tomslin Samme-Nlar - SOI
<https://community.icann.org/display/gnsosoi/Tomslin+Samme-Nlar+SOI>
Non-Commercial Stakeholder Group
Olga Cavall- SOI
<https://community.icann.org/display/gnsosoi/Olga+Cavalli+SOI> - Non-Voting
NomCom Appointee
Jeffrey Neuman - SOI
<https://community.icann.org/display/gnsosoi/Jeff+Neuman+SOI> - GNSO
Council Liaison to the GAC
*Thank you again to outgoing Councilors: Elsa Saade, Erika Mann, James
Gannon, Julf Helsingius, Keith Drazek, Michele Neylon, Rafik Dammak and
Scott McCormick. *
1.3 - Review / Amend Agenda
*Item 2. Election of the Chair (20 mins)*
One nomination was received for this position from Philippe Fouquart of the
Non Contracted Party House. The GNSO reviewed the candidate statement
<https://gnso.icann.org/sites/default/files/file/field-file-attach/fouquart-statement-20sep20-en.pdf>
and held a question & answer session with the candidate on 24 September
2020. Here the GNSO Council will proceed to hold the election for its Chair
for 2020-2021, according to the GNSO Operating Procedures (note Section 2.2
of the GNSO Operating Procedures on Officer Elections: Chair and
Vice-Chairs (see Appendix 1 below)).
*Item 3. Any Other Business (0 min)*
None
*Appendix 1: Excerpt from GNSO Operating Procedures (Section 2.2)*
2.2 https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf
Officer
Elections: Chair and Vice-Chairs
The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows:
1. The GNSO Chair shall be elected by a 60 percent vote of each house.
2. Each house will be allowed to nominate one candidate for GNSO Council
Chair. Each house is responsible for determining how to nominate its
candidate. A candidate for GNSO Council Chair does not need to be a member
of a house, but must be a current or incoming member of the GNSO Council.
Should a Chair be elected from outside of the houses that Chair will be a
non-voting Chair.
a. All ballots will include the “none of the above”
option. In the event that a 60 percent vote of each house selects the
“none of the above” option, each house will commence a new nomination
period of not longer than 15 days. An election for the new nominees will be
scheduled for no sooner than 30 days after the unsuccessful vote.
b. In the case of a tie for the most votes between the
two candidates, or between a candidate and “none of above,” a second
election will be held no sooner than 30 days. The candidates shall remain
the same for this second election. In the case this second election also
results in a tie, each house will commence a new nomination period of not
longer than 15 days. An election for the new nominees will be rescheduled
for no sooner than 30 days after the unsuccessful vote.
c. The leading candidate will be defined as the one with
the highest score. The score is calculated by adding together the voting
percentages attained from each house. The highest percentage attainable in
each house is 100. Thus, the maximum score a candidate can achieve is 200
as a result of attaining 100 percent of the votes from the contracted party
house and 100 percent from the non-contracted party house (100 percent +
100 percent = score of 200). In case neither candidate reaches the 60
percent of each house threshold, a second ballot will be held between the
leading candidate and “none of the above.”
d. In case neither candidate reaches the 60 percent of
each house threshold and the candidates do not tie, a second runoff ballot
will be held between the leading candidate and “none of the above.”
e. If the single candidate does not reach the 60 percent
of each house threshold in the runoff ballot, then each house will commence
a new nomination period of not longer than 15 days. An election for the
new nominees will be rescheduled for no sooner than 30 days after the
unsuccessful runoff ballot.
1. Each house shall select a Council Vice-Chair from within its
respective house.
2. A Chair may not be a member of the same Stakeholder Group of either
of the Vice-Chairs.
3. The Chair and Vice-Chairs shall retain their votes (if any) in their
respective houses (if any).
4. In the event that the GNSO Council has not elected a GNSO Council
Chair by the end of the previous Chair’s term, the Vice-Chairs will serve
as Interim GNSO Co- Chairs to jointly oversee the new Chair election and
conduct Council business until a successful election can be held. In the
event that one or both Vice-Chairs’ terms ends concurrently with the term
of the previous Chair, the procedures described in Section 2.2.1 below
shall apply.
5. The Council shall inform the Board and the Community appropriately
and post the election results on the GNSO website within 2 business days
following each election and runoff ballot, whether successful or
unsuccessful.
*Appendix 2: GNSO Council Voting Thresholds (**ICANN Bylaws,*
<https://www.icann.org/resources/pages/governance/bylaws-en/#article11>*
Article 11, Section 3)*
(i) Except as otherwise specified in these Bylaws, *Annex A*, *Annex A-1*
or *Annex A-2* hereto, or the GNSO Operating Procedures, the default
threshold to pass a GNSO Council motion or other voting action requires a
simple majority vote of each House. The voting thresholds described below
shall apply to the following GNSO actions:
(i) Create an Issues Report: requires an affirmative vote of more than
one-fourth (1/4) vote of each House or majority of one House.
(ii) Initiate a Policy Development Process ("*PDP*") Within Scope (as
described in *Annex A*): requires an affirmative vote of more than
one-third (1/3) of each House or more than two-thirds (2/3) of one House.
(iii) Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO
Supermajority (as defined in *Section 11.3(i)(xix)*).
(iv) Approve a PDP Team Charter for a PDP Within Scope: requires an
affirmative vote of more than one-third (1/3) of each House or more than
two-thirds (2/3) of one House.
(v) Approve a PDP Team Charter for a PDP Not Within Scope: requires an
affirmative vote of a GNSO Supermajority.
(vi) Changes to an Approved PDP Team Charter: For any PDP Team Charter
approved under (iv) or (v) above, the GNSO Council may approve an amendment
to the Charter through a simple majority vote of each House.
(vii) Terminate a PDP: Once initiated, and prior to the publication of a
Final Report, the GNSO Council may terminate a PDP only for significant
cause, upon a motion that passes with a GNSO Supermajority Vote in favor of
termination.
(viii) Approve a PDP Recommendation Without a GNSO Supermajority: requires
an affirmative vote of a majority of each House and further requires that
one GNSO Council member representative of at least 3 of the 4 Stakeholder
Groups supports the Recommendation.
(ix) Approve a PDP Recommendation With a GNSO Supermajority: requires an
affirmative vote of a GNSO Supermajority,
(x) Approve a PDP Recommendation Imposing New Obligations on Certain
Contracting Parties: where an ICANN contract provision specifies that "a
two-thirds vote of the council" demonstrates the presence of a consensus,
the GNSO Supermajority vote threshold will have to be met or exceeded.
(xi) Modification of Approved PDP Recommendation: Prior to Final Approval
by the Board, an Approved PDP Recommendation may be modified or amended by
the GNSO Council with a GNSO Supermajority vote.
(xii) Initiation of an Expedited Policy Development Process ("*EPDP*"):
requires an affirmative vote of a GNSO Supermajority.
(xiii) Approve an EPDP Team Charter: requires an affirmative vote of a GNSO
Supermajority.
(xiv) Approval of EPDP Recommendations: requires an affirmative vote of a
GNSO Supermajority.
(xv) Approve an EPDP Recommendation Imposing New Obligations on Certain
Contracting Parties: where an ICANN contract provision specifies that "a
two-thirds vote of the council" demonstrates the presence of a consensus,
the GNSO Supermajority vote threshold will have to be met or exceeded.
(xvi) Initiation of a GNSO Guidance Process ("*GGP*"): requires an
affirmative vote of more than one-third (1/3) of each House or more than
two-thirds (2/3) of one House.
(xvii) Rejection of Initiation of a GGP Requested by the Board: requires an
affirmative vote of a GNSO Supermajority.
(xviii) Approval of GGP Recommendations: requires an affirmative vote of a
GNSO Supermajority.
(xix) A "*GNSO Supermajority*" shall mean: (A) two-thirds (2/3) of the
Council members of each House, or (B) three-fourths (3/4) of the Council
members of one House and a majority of the Council members of the other
House.
https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf
Appendix 1 GNSO Council Voting Results table
*Absentee Voting Procedures *
*https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf*
<https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf>
*4.4 Absentee Voting*
4.1.1 * Applicability*
Absentee voting is permitted for the following limited number of Council
motions or measures.
1. Initiate a Policy Development Process (PDP);
2. Approve a PDP recommendation;
3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN
Bylaws;
4. Fill a Council position open for election.
4.1.2 Absentee ballots, when permitted, must be submitted within the
announced time limit, which shall be 72 hours from the meeting’s
adjournment. In exceptional circumstances, announced at the time of the
vote, the Chair may reduce this time to 24 hours or extend the time to 7
calendar days, provided such amendment is verbally confirmed by all
Vice-Chairs present.
4.1.3 The GNSO Secretariat will administer, record, and tabulate
absentee votes according to these procedures and will provide reasonable
means for transmitting and authenticating absentee ballots, which could
include voting by telephone, e- mail, web-based interface, or other
technologies as may become available.
4.1.4 Absentee balloting does not affect quorum requirements.
_______________________________________________
council mailing list
council at gnso.icann.org
https://mm.icann.org/mailman/listinfo/council
_______________________________________________
By submitting your personal data, you consent to the processing of your
personal data for purposes of subscribing to this mailing list accordance
with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
the website Terms of Service (https://www.icann.org/privacy/tos). You can
visit the Mailman link above to change your membership status or
configuration, including unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20201011/f1734f3f/attachment.htm>
More information about the Ncsg-discuss
mailing list