[Call] Final Proposed Agenda GNSO Council Meeting - 30 January 2018 at 22:00 UTC

Sun Jan 21 02:45:12 EET 2018

Hi all,

Please find below the council call agenda for the 30th Jan . You can listen
to the call streaming at this linkhttp://stream.icann.org:8000/stream01.m3u
.
We will also have our regular NCSG call this wednesday at 12:00UTC
(invitations were sent with remote participation details) .

Best,

Rafik
---------- Forwarded message ----------

Councilors,

Please below find the final proposed agenda for the GNSO Council Meeting on
30 January 2018 at 22:00 UTC. This has been posted on the GNSO Council
meeting wiki page and on the GNSO master calendar[gnso.icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar-23nov&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=pFQxlozYAm_b-YkKiVmz0XwG6RINxE6YaQNRIiF1UXc&s=lr5kHa3FU6cRqwx-VE_M9ndjoPs8Dve2w19gnTIL_u8&e=>.

 *Final proposed agenda 30 January 2018*

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/bgCfB <https://community.icann.org/x/bgCfB> *

This agenda was established according to the GNSO Operating Procedures
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_op-2Dprocedures-2D01sep16-2Den.pdf&d=DQMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=U4IBJYYYko8geLjSlTyOXbvtmoVER-_lK-PAQ64rKHs&m=55oYi9y1UeIL5juaxAkqpioz33PyWq>
v3.2,
updated on 01 September 2016.

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.

Coordinated Universal Time: 22:00 UTC: https://tinyurl.com/y8v2lryd

14:00 Los Angeles; 17:00 Washington; 22:00 London; (Wednesday 31 January)
03:00 Islamabad; 07:00 Tokyo; 09:00 Hobart

*GNSO Council Meeting Audio Cast*
To join the event click on the link: http://stream.icann.org:8000/
stream01.m3u

Councilors should notify the GNSO Secretariat in advance if they will not
be able to attend and/or need a dial out call.

*___________________________________*

*Item 1. Administrative Matters (5 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/en/meetings/minutes-council-30nov17-en.pdf>
of the GNSO Council meeting on the 30 November were posted on 21 November
2017.

Minutes <https://gnso.icann.org/en/meetings/minutes-council-21dec17-en.pdf>
of the GNSO Council meeting on the 21 December 2017 were posted on 8
January 2018.

*Item 2. Opening Remarks / Review of Projects & Action List (10 mins)*

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 (0 min)*

None

*Item 4: COUNCIL VOTE – Adoption of the Revisions to GNSO Operating
Procedures and Recommendations for Amendments to ICANN Bylaws (15 minutes)*

On 27 May 2016, the ICANN Board adopted
<https://www.icann.org/resources/board-material/resolutions-2016-05-27-en#1.a>
a
set of new ICANN Bylaws which became effective upon the expiration the IANA
Functions Contract between ICANN and NTIA. Accordingly, on 30 June 2016,
the GNSO Council established
<https://gnso.icann.org/en/council/resolutions#201606> a Drafting Team to
identify all the new or additional rights and responsibilities that the
GNSO has under the revised Bylaws. On 12 October 2016, the Drafting
Team submitted
its Final Report
<http://mm.icann.org/pipermail/gnso-bylaws-dt/2016-October/000145.html> to
the GNSO Council.

On 01 December 2016, the GNSO Council accepted
<https://gnso.icann.org/en/council/resolutions#201612> the recommendations
in the Drafting Team’s Final Report and directed staff to draft proposed
language for any necessary modifications or additions to the GNSO Operating
Procedures and, if applicable, those parts of the ICANN Bylaws pertaining
to the GNSO.

On 19 June 2017, ICANN staff published
<https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en> its
proposed changes to the GNSO Operating Procedures and ICANN Bylaws to
implement the DT recommendations for public comment. Public comment closed
on 10 August 2017 and staff published the Report of Public Comments
<https://www.icann.org/en/system/files/files/report-comments-gnso-op-procedures-31aug17-en.pdf>
.

The proposed changes were discussed on the GNSO Council’s 20 September 2017
meeting and again during the GNSO Council’s Strategic Planning sessions on
26 January 2018.

Here, the Council will vote to adopt the proposed revisions to the GNSO
Operating Procedures and the recommended amendments to the ICANN Bylaws.

4.1 – Presentation of motion (Heather Forrest)

4.2 – Council discussion

4.3 – Council vote (voting threshold: simple majority)

*Item 5: COUNCIL VOTE – Adoption of the Charter related to the next steps
for the ICANN Procedure of Handling WHOIS conflicts with Privacy Law (15
minutes) *

As a result of community input and the work of the Implementation Advisory
Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy
Law Procedure
<https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-privacy-law>
on 18 April 2017 to better accommodate issues where WHOIS requirements
conflict with applicable laws.

As requested by this GNSO Council, ICANN published a paper
<https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedure-03may17-en.pdf>
for public comment
<https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> to
provide analysis and solicit community input on the practicality and
feasibility of the triggers identified in the revised WHOIS Conflicts with
Privacy Law Procedure. The public comment period was also intended to
collect suggestions for moving forward with the review. The public comment
period closed on 7 July 2017 and the staff report of public comments
<https://www.icann.org/en/system/files/files/report-comments-whois-privacy-law-28jul17-en.pdf>
was published on 28 July 2017.

On 1 August 2017, the Council received a letter
<https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en.pdf>
from Akram Atallah providing a collection of possible options for
proceeding with the review, and offering to discuss those options or others
identified by Council. On 24 August 2017, the Council received an update
from GDD staff and discussed possible options for moving forward with the
review of the Procedure for Handling WHOIS Conflicts with Privacy Law.

A small group of Councilors have prepared a Charter (including guidelines
and parameters around scope, deliverables, composition, operating
procedures, etc.) pursuant to which a subsequent group will operate as it
deliberates and provides suggested next steps and/or recommendations.

Here, the Council will vote to approve the Charter.

5.1 – Presentation of motion (TBD)

5.2 – Council Discussion

5.3 – Council vote (voting threshold: simple majority)

*Item 6: COUNCIL DISCUSSION – Update on potential FY19 GNSO Additional
Budget Requests (15 minutes) *

On 5 December 2017, ICANN launched
<https://www.icann.org/news/announcement-2017-12-05-en> the FY19 SO/AC
Additional Budget Request Process, with a due date of 31 January 2018 for
community requests. During the FY18 cycle, the GNSO requested and was
granted two Additional Budget Requests: 1) GNSO Council Strategic Planning
Session Pilot Project; and 2) GNSO PDP WG Chairs Support Pilot Project.

For FY19, the GNSO Council is proposing to again request those two
successful items, along with a third request to fund a Working Group
sign-up and management tool.

Here, the Council will discuss the proposed Additional Budget Requests for
FY19.

6.1 – Presentation of discussion topic (Council Leadership)

6.2 – Council Discussion

6.3 – Next Steps

*Item 7: COUNCIL DISCUSSION – GNSO Council Public Comment to the Proposed
Incremental Changes to the ICANN Meetings Strategy (10 minutes)*

On 02 February 2013, the ICANN Board resolved
<https://www.icann.org/resources/board-material/resolutions-2013-02-02-en#2.a>
to
establish the Multi-Stakeholder Meeting Strategy Working Group (MSWG),
allowing community members and the Board to work together to develop a
meeting strategy that aligns with community needs.

On 25 February 2014, the MSWG published its report
<https://meetings.icann.org/en/mswgrecommendations-icannfuturemeetingsstrategyfinalv119jun14.pdf>
and
recommendations for public comment. The recommendations of the MSWG led to
the current structure now in place (i.e., Meeting A, B, and C).

Many in the community are generally supportive of the new and now existing
structure, but still see room for improvement. On 17 August 2017, community
leaders and ICANN staff held a discussion
<https://community.icann.org/display/soaceinputfeedback/Event+Calendar>
regarding
possible changes to ICANN meetings and the venue selection process. The
potential changes envisioned are generally considered adjustments to the
existing meeting strategy rather than a wholesale change to that meeting
strategy. On 14 December 2017, the Proposed Incremental Changes to the
ICANN Meetings Strategy was published for public comment
<https://www.icann.org/public-comments/proposed-changes-meetings-strategy-2017-12-14-en>
.

A small group of Councilors have prepared a draft public comment response.
Here, the Council will discuss the potential response and ensure that there
are no objections to the submission of the public comment.

7.1 - Presentation of discussion topic (Council leadership)

7.2 – Council discussion

7.3 – Next steps

*Item 8: COUNCIL DISCUSSION – GNSO Council Public Comment to the Operating
Standards for ICANN’s Specific Reviews (10 minutes)*

Under ICANN’s Bylaws
<https://www.icann.org/resources/pages/governance/bylaws-en>, four specific
reviews are required: Competition, Consumer Trust and Consumer Choice
Review, the Security, Stability, and Resiliency of the DNS Review, the
Accountability and Transparency Review, and the Registration Directory
Service Review. Section 4.6
<https://www.icann.org/resources/pages/governance/bylaws-en#article4.6> of
the Bylaws further calls for Operating Standard for these Specific Reviews,
which are intended to provide consistency, clarity, and transparency around
the reviews.

On 17 October 2017, ICANN published a draft set of Operating Procedures
<https://www.icann.org/en/system/files/files/draft-operating-standards-specific-reviews-17oct17-en.pdf>
for public comment
<https://www.icann.org/public-comments/reviews-standards-2017-10-17-en>,
seeking feedback in particular on scoping and review team composition.

A small group of Councilors have prepared a draft public comment response.
Here, the Council will discuss the potential response and ensure that there
are no objections to the submission of the public comment.

8.1 - Presentation of discussion topic (Council leadership)

8.2 – Council discussion

8.3 – Next steps

*Item 9: COUNCIL DISCUSSION – Review of Second Security, Stability, and
Resiliency (SSR2-RT) Letter from GNSO Council to SO/AC leadership (10
minutes)*

The Security, Stability, and Resiliency Review, mandated by the ICANN
Bylaws, assembled its review team and began administrative and step steps
in early 2017.  During ICANN60 in Abu Dhabi, the ICANN Board paused the
second community-driven review of ICANN’s Security, Stability, and
Resiliency Review Team (SSR2-RT
<https://community.icann.org/display/SSR/SSR2+Review>).

Following ICANN60, the SSR2-RT members prepared a matrix of members’ skills
and expertise and an evaluation of the scope of the review.

As there is no established process by which to re-start the SSR2-RT, the
SO/AC leaders have been collaborating since ICANN60 on the process to
re-starting this important review effort. The GNSO Council will discuss the
issue with a view to sharing its findings with the SO/AC leaders through
the Council Chair. In order to inform the wider community of the GNSO
Council’s intentions, a small group of Councilors have drafted a letter to
be shared with SO/AC leaders.

Here, the Council will discuss the draft letter and ensure that there are
no objections to the transmission of the letter to SO/AC leaders.

9.1 - Presentation of discussion topic (Council leadership)

9.2 – Council discussion

9.3 – Next steps

*Item 10: ANY OTHER BUSINESS (0 minutes)*

*10.1 – Planning for ICANN61*

*________________________________*

*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/en/council/op-procedures-01sep16-en.pdf.

*References for Coordinated Universal Time of 22:00 UTC  *Local time
between March and October Summer in the NORTHERN hemisphere
----------------------------------------------------------------------------
California, USA (PDT) UTC-8 14:00
San José, Costa Rica (CST) UTC-6 15:00
New York/Washington DC, USA (EDT) UTC-5 17:00
Buenos Aires, Argentina (ART) UTC-3 19:00
Rio de Janeiro, Brazil (BRST) UTC-2 20:00
London, United Kingdom (GMT) UTC 22:00

Paris, France (CEST) UTC+1 23:00
Kinshasa, Democratic Republic of Congo (WAT) UTC+1 23:00

Islamabad, Pakistan (PKT) UTC+5 (+ 1 day) 03:00
Singapore (SGT) UTC+8 (+ 1 day) 06:00
Tokyo, Japan (JST) UTC+9 (+ 1 day) 07:00
Sydney/Hobart, Australia (AEDT) UTC+11 (+ 1 day) 09:00
----------------------------------------------------------------------------

DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with
exceptions) for EU countries.
----------------------------------------------------------------------
For other places see http://www.timeanddate.com and https://tinyurl.com/
y8v2lryd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20180121/dfd77744/attachment.htm>