Date: Fri, 29 Mar 2024 07:37:02 +0000 (UTC) Message-ID: <1498472800.2626.1711697822825@community1.lax.icann.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2625_1900156466.1711697822824" ------=_Part_2625_1900156466.1711697822824 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Please note that all documents referenced in the agenda ha= ve been gathered on a Wiki page for convenience and easier access: <= a href=3D"https://community.icann.org/x/jgxACQ" rel=3D"nofollow">http= s://community.icann.org/x/jgxACQ
This agenda was established according to the GNSO Opera= ting Procedures v3.5, updated on 24 October 2019
For convenience:
GNSO Council meeting held 17:30 UTC (12:30 local time)
Coordinated Universal Time: 17:30 UTC: https:/= /tinyurl.com/2dc33d7k
10:30 Los Angeles; 13:30 Washington; 17:30 London; 18:30 Paris; 20= :30 Moscow; (Thursday) 04:30 Melbourne
GNSO Council Meeting Remote Participation:
Councilors should notify the GNSO Secretariat in advance if they w= ill not be able to attend and/or need a dial out call.
___________________________________
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 of the GNSO Council meeting on 21 Janua= ry 2021 were posted on 4 February 2021.
Minutes of the GNSO Council meeting on 18 Febru= ary 2021 were posted on 4 March 2021.
Item 2: Opening Remarks / Review of Projects & Action List (= 0 minutes)
2.1 - Review focus areas and provide updates on specific key theme= s / topics, to include review of Projects = List and Action Item List.
Item 3: Consent Agenda (5 minutes)
Item 4: COUNCIL VOTE - IANA Naming Functions Contract Amendment = (10 minutes)
The Internet Assigned Numbers Authority (IANA) Naming Function Rev= iew Team (IFRT) Final Report contains a recommendation that requires GNSO C= ouncil action. The IFR is an evaluation of Public Technical Identifiers (PT= I) performance of the IANA naming function against the contractual requirem= ents in the IANA Naming Function Contract and the IANA Naming Functio= n SOW. The IFR Review Team's Recommendation 4 (page 5 of t= he IFR Final Report [PDF, 2.2= MB]) calls for an amendment to Article 7, Section 7.1 (a) of the IANA Namin= g Function Contract. Pursuant to ICANN Bylaws Article 18.6 (iv), there = must be "public comment on the amendments= that are under consideration by the IFRT through a public comment period t= hat complies with the designated practice for public comment periods within= ICANN." In addition, Article 18.6 (b) requires that in o= rder for the recommendation of the IFRT that amends the IANA Naming Functio= n Contract or IANA Naming Function SOW to become effective, one of the requ= irements is for GNSO approval by a Supermajority.
The IANA Naming Function Contract currently states at= Article VII, Section 7.1 (a): Audits:
=E2=80=9CContractor shall generate and publish via the IANA Websit= e a monthly audit report identifying each root zone file and root zone =E2= =80=9CWHOIS=E2=80=9D database change request and its status. The relevant p= olicies under which the changes are made shall be noted within each monthly= report. Such audit report shall be due to ICANN no later than 15 calendar = days following the end of each month.=E2=80=9D
The IFRT recommends that this statement, "The relevant policies un= der which the changes are made shall be noted within each monthly report" b= e removed from the contract.
Per the letter f= rom the Co-chairs of the IANA Naming Function Review (IFR), =E2=80=9CThis s= ection refers to the Root Operations Audit Reports (https://www.iana.org/performance/root-audit) w= hich is published monthly by PTI. This statement, carried over from the con= tract between ICANN and NTIA, is no longer required; further, implementatio= n of this requirement has long been recognised as being operationally impra= cticable, as a single change request cannot be traced back to a single rele= vant policy. The IFRT is satisfied that there is no value to this statement= remaining in the IANA Naming Function Contract, as the referenced line add= s no value to the reports.=E2=80=9D
Here, the Council will vote to approve the IFRT Recommendation 4.<= /span>
4.1 =E2=80=93 Presentation of the Motion (Tom= slin Samme-Nlar)
4.2 =E2=80=93 Council discussion
4.3 =E2=80=93 Council vote (voting threshold: supermajority)
Taking this action is within the GNSO=E2=80=99s remit as outli= ned in ICANN=E2=80=99s Bylaws, as a GNSO Supermajority is one of the requir= ed elements to allow for an amendment to either the IANA Naming Function Co= ntract, IANA Naming Function SOW or CSC Charter, as set forth in these Byla= ws=E2=80=99 (Art.18.6).
Item 5: COUNCIL VOTE - Charter for the Transfer Policy PDP (10 m= inutes)
During its February Council meeting, the GNSO Council resolved to initiate = a PDP on the Transfer Policy, while also determining that further time was = needed to draft the charter. The Preliminary Issue Report included a draft = charter, which was included in the public comment proceeding. That draft ch= arter is also included in the Fi= nal Issue Report, Annex A. Comment on the dra= ft charter was solicited from Councilors via a pre-recorded webinar prior to this Council meeting. A small team of Councilors wa= s convened to refine the charter, focusing primarily on the membership stru= cture. After receiving input from various communities, the small team propo= sed a representative structure that it believes allows for appropriate leve= ls of participation.
Here, the Council will vote to approve the Charter.
5.1 =E2=80=93 Presentation of the Motion (Pam= Little, GNSO Council Vice-Chair) Presentation Slide Deck
5.2 =E2=80=93 Council discussion
5.3 =E2=80=93 Council vote (voting threshold: an affirmative vote = of more than one-third (1/3) of each House or more than two-thirds (2/3) of= one House)
Taking this action is within the GNSO=E2=80=99s remit as outli= ned in ICANN=E2=80=99s Bylaws as the GNSO =E2=80=98shall be responsible for= developing and recommending to the Board substantive policies relating to = generic top-level domains and other responsibilities of the GNSO as set for= th in these Bylaws=E2=80=99 (Art.11.1). Furthermore, this action complies w= ith the requirements set out in Annex A: GNSO Policy Development Process of= the ICANN Bylaws.
Item 6: COUNCIL DISCUSSION - Nominating Committee Outreach Subco= mmittee Outreach (10 minutes)
The Nominating Committee (NomCom) initiated its application process on 25 Janua= ry 2021 (with the deadline ext= ended to 29 March 2021). For this cycle, the NomCom will b= e selecting two members of the GNSO Council, one representing the Contracte= d Parties House and one representing the Non-Contracted Parties House. The = GNSO Council provided updated criteria to the NomCom in = January 2021.
Here, the NomCom Outreach Subcommittee will provide information ab= out the NomCom panel, about the positions being filled for the GNSO Council= , and answer questions that the Council might have.
6.1 - Introduction of topic (NomCom Outreach Subcommittee: Adetola Sogbesan & Wo= lfgang Kleinwaechter) Presentation Slide Deck<= /p>
6.2 =E2=80=93 Council discussion
6.3 =E2=80=93 Next steps
Item 7: COUNCIL DISCUSSION =E2=80=93 Status Update Regarding EPD= P Phase 2A (20 minutes)
On 21 October 2020, the GNSO Council approved the initiation of EPDP Phase= 2A, to examine the topics of legal/natural and feasibility of unique conta= cts. In doing so, the Council required that:
"[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 Cou= ncil on the status of deliberations. Based on this report, which is expecte= d to include an update on progress made and the expected likelihood of cons= ensus recommendations, the GNSO Council will decide on next steps, which co= uld include providing additional time for the EPDP to finalize its recommen= dations or termination of the EPDP if it is clear that no progress is being= made or consensus is unlikely).=E2=80=9D
Here, the Chair of the EPDP Team and GNSO Council Liaison to the E= PDP will provide an update to the Council.
7.1 =E2=80=93 Introduction of topic (EPDP Team Chair, Keith Drazek= and GNSO Council Liaison to the EPDP, Philippe Fouquart) Presentation slide deck
7.2 =E2=80=93 Council discussion
7.3 =E2=80=93 Next steps
Item 8: Council Discussion - Debrief on the Consultation with th= e ICANN Board on the Financial Sustainability of the SSAD (20 minutes)
In the adoption= span> of the Expedited Policy Development Process (EPDP) on the T= emporary Specification Phase 2 Final Report and Recommendations, the Counci= l resolved that:
=E2=80=9CNoting some of the questions surrounding the financial su= stainability of SSAD and some of the concerns expressed within the differen= t minority statements, the GNSO Council requests a consultation with the IC= ANN Board as part of the delivery of the GNSO Council Recommendations Repor= t to the ICANN Board to discuss these issues, including whether a further c= ost-benefit analysis should be conducted before the ICANN Board considers a= ll SSAD-related recommendations for adoption.=E2=80=9D
The GNSO Council communicated its Recommend=
ations Report to the Board 29 October 2020, in which the Council proposed, =
=E2=80=9Cto form a small team consisting of GNSO Council and ICANN Board me=
mbers to develop a proposed approach and agree on expectations in relation =
to this consultation.=E2=80=9D The ICANN Board responded on 1 December 2020, stating that it believed the Operational Design Ph=
ase (ODP) it envisioned, will help facilitate the consultation with the Cou=
ncil. The Council responded on 22 Januar=
y 2021, suggesting that it is more important to agree upon the elements of =
the operational impact assessment, rather than relying on the ODP framework=
exclusively.
That consultation between the Board and the GNSO Coun= cil took place on 22 February 2021. The Council will meet with the Board ag= ain, connected with ICANN70, on 1 April 2021. There, the Operational Design= Phase for the SSAD will be one of the topics for discussion. A small team = of Councilors is preparing a letter to be sent to the Board, in advance of = the 1 April 2021 meeting, which is expected to be available for this 24 Mar= ch Council meeting.
Here, the Council will hold a debrief on the 22 February consultat= ion and plan for the 1 April meeting.
8.1 =E2=80=93 Introduction of topic (Council Leadership)
8.2 =E2=80=93 Council discussion
8.3 =E2=80=93 Next steps
Item 9: COUNCIL UPDATE - EPDP Phase 1 Rec 27 (Wave 1.5) (5 minut= es)
Recommendation 27 from the EPDP Phase 1 Final Report, =E2=80=9C... recommends that as= part of the implementation of these policy recommendations, updates are ma= de to the following existing policies / procedures, and any others that may= have been omitted, to ensure consistency with these policy recommendations= as, for example, a number of these refer to administrative and/or technica= l contact which will no longer be required data elements.=E2=80=9D In suppo= rt of this recommendation, ICANN org prepared the Wave 1 report, an updated= version of which was shared with the Council on 19 February 2020. ICANN or= g has performed additional analysis for recommendation 27, resulting in the= Wave 1.5 Report that f= ocuses on Privacy and Proxy Services Accreditation Issues (PPSAI) and Trans= lation and Transliteration of Contact Information (T/T) policy recommendati= ons, for which implementation has been started but not completed.
For the Wave 1 Report, the staff s= upport team conducted a first analysis of the report, identifying possible = next steps for Council consideration that the Council subsequently reviewed= to determine next steps. The Council may elect to follow a si= milar approach to the Wave 1.5 Report, to determine appropriate next steps.=
Here, the Council will discuss the Wave 1.5 Report.
9.1 =E2=80=93 Introduction of topic (Council Leadership)
9.2 =E2=80=93 Council discussion
9.3 =E2=80=93 Next steps
Item 10: COUNCIL DISCUSSION - Introduction to the Briefing Paper= on Accuracy Requirements and Programs from ICANN=E2=80=99s Global Domains = & Strategy (GDS) (5 minutes)
On 4 November 2020, the GNSO Council wrote = to ICANN org, requesting the preparation of a briefing document outlining b= oth the existing accuracy requirements and programs as well as the impact t= hat GDPR has had on implementing and enforcing the identified requirements = and programs. This briefing is intended to inform an accuracy scoping team = that the GNSO Council envisioned initiating , which would be tasked with fu= rthering the community=E2=80=99s understanding of the issue and assist in s= coping and defining the issue. On 10 December 2020, ICANN org respond= ed to confirm its understanding of the request and to comm= it to delivering that briefing by 26 February 2021. ICANN org delivered the= briefing paper on the 26th. In addition to the= briefing providing an overview of accuracy requirements and programs, ICAN= N org included a suggestion that a study to measure accuracy of registratio= n data might be beneficial. In parallel to the request for the briefing, IC= ANN SO/AC/SG/Cs were requested to start thinking about whether their groups= would be interested to participate in a scoping team once created. To date= , the BC, ISPCP, RySG and GAC have expressed an interest and identified pot= ential volunteers with relevant knowledge and expertise.
Here, the Council will discuss next steps as it relates to the bri= efing as well as the scoping team.
10.1 =E2=80=93 Introduction of topic (Council Leadership)= p>
10.2 =E2=80=93 Council discussion
10.3 =E2=80=93 Next steps
Item 11: COUNCIL DISCUSSION - GNSO Council Consideration of SAC1= 14 (5 minutes)
On 15 February 2021, the SSAC shared SAC114 wi= th the GNSO Council, which are the Security and Stability Advisory Committe= e (SSAC)=E2=80=99s comments on the New gTLD Subsequent Procedures PDP=E2=80= =99s Draft Final Report, but are directed at the ICANN Board for its consid= eration. While the comments are directed at the ICANN Board, they pertain t= o the work of the GNSO and as a result, the Council may benefit from consid= ering SAC114 and formulating its impressions of the recommendations.=
Here, the Council will consider SAC114 and discuss next steps, if = any.
11.1 =E2=80=93 Introduction of topic (Council Leadership)= p>
11.2 =E2=80=93 Council discussion
11.3 =E2=80=93 Next steps
Item 12: COUNCIL DISCUSSION - GNSO Framework for Continuous Impr= ovement (5 minutes)
The GNSO Council has sought an approach to address work that focus= es on GNSO structural, procedural and process improvement related work. The= proposal from Council leadership is to create a GNSO Framework for Continu= ous Improvement that will help provide structure to manage the numerous non= -PDP related efforts residing on the Council=E2=80=99s Action Decision Rada= r (ADR). An overview= was developed and shared on 20 January 2021.
Based on initial feedback from Councilors and other GNSO stakehold= ers, a much more detailed draft document was prepared and shared on 2 March 20= 21, which provides additional information about the structure and potential= work assignments. Input was sought from the Council and SG/C Chairs.
Here, the Council will consider whether the framework serves as an= appropriate path forward, as well as relevant next steps.
12.1 =E2=80=93 Introduction of topic (Council Leadership)= p>
12.2 =E2=80=93 Council discussion
12.3 =E2=80=93 Next steps
Item 13: ANY OTHER BUSINESS (10 minutes)
13.1 - Open Microphone
_______________________________
Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article = 11, Section 11.3(i))
See h= ttps://www.icann.org/resources/pages/governance/bylaws-en/#article11= .
Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operatin= g Procedures, Section 4.4)
See https://gnso.icann.org/sites/default/files/file/fie= ld-file-attach/op-procedures-30jan18-en.pdf
References for Coordinated Universal Time of 17:30 UTC
Local time between November and March Winter in the NORTHERN hemis= phere
------------------------------------------------------------------= ----------
California, USA (PDT) UTC-7 10:30
San Jos=C3=A9, Costa Rica (CST) UTC-6 11:30
New York/Washington DC, USA (EDT) UTC-4 13:30
Buenos Aires, Argentina (ART) UTC-3 14:30
Rio de Janeiro, Brazil (BRST) UTC-3 14:30
London, United Kingdom (GMT) UTC+0 17:30
Kinshasa, Democratic Republic of Congo (WAT) UTC+1 18:30
Paris, France (CEST) UTC+1 18:30
Moscow, Russia (MST) UTC+3 20:30
Singapore (SGT) (+1 day) UTC+8 01:30
Melbourne, Australia (AEDT)(+1 day) UTC+11 04:30
------------------------------------------------------------------= ----------
DST starts/ends on Sunday 28 March 2021, 2:00 or 3:00 local time (= with exceptions) for EU countries and on Sunday 14 March 2021 for the US.= span>
------------------------------------------------------------------= ----
For other places see http://www.timeanddate.com= and https://tinyurl.com/2dc33d7k