From dave at davecake.net  Mon Feb  1 10:51:08 2021
From: dave at davecake.net (David Cake)
Date: Mon, 1 Feb 2021 16:51:08 +0800
Subject: [NCSG-PC] Engagement on DNS Abuse
In-Reply-To: <CAM8DdeWLXks-AKF3ScvLUwLJCmZ8kF63epj3MpzcRjoFkYBXqg@mail.gmail.com>
References: <a446240dc4e24916af1369da0094855d@verisign.com>
 <CADAEEV3hi2MDshEjHT8S2s+5Q1NV033AJ-FORk41tHRv5vt=ZA@mail.gmail.com>
 <CAM8DdeWLXks-AKF3ScvLUwLJCmZ8kF63epj3MpzcRjoFkYBXqg@mail.gmail.com>
Message-ID: <695D3530-5973-49DB-8C32-43127CAF22DB@davecake.net>

I agree we need an internal group to establish a position - this is a complex history with a lot of history. I agree it is a good opportunity for newer volunteers work alongside old hands. 

I would be interested in both being part of an internal discussion group, and engaging with the CPH once we have had that discussion.

It is worth noting that now that Amr is in the CPH he could be a useful sounding board, as he still has close links with many of us, and understands the issues from both sides. 

David

> On 27 Jan 2021, at 2:48 am, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:
> 
> Thank you Bruna for sharing this. 
> 
> I agree we need a small group to discuss and form an official NCSG position on DNS abuse. This will both guide our members who volunteer to the CPH WG and how we engage in general with the rest of the community on this topic. A spelled out position will also enable us to have non-experienced volunteers be a bit confident to work on the topic along-side experienced volunteers. Forming an opinion on how NCSG views a specific issue is often a big challenge for non-experienced volunteers and newcomers. This will go a long way in helping more people get involved and it is our job as policy committee to lead this.
> 
> I would be interested in a call with CPH on this topic once we are in sync internally on what our position is.
> 
> Tomslin
> 
> 
> 
> On Tue, 26 Jan 2021 at 16:51, Bruna Martins dos Santos <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
> Dear PC, 
> 
> I just shared the CPH WG on DNS Abuse on the list, but am sharing Keith's email below with you all. It would be really important for us to form a little group to discuss whether we can achieve a NCSG position on the topic and engage with the community about it. 
> 
> This is an issue that Rafik has brought to our attention to before but we never really managed to set forth. Last year we were even planning on organizing a webinar on this topic, maybe this is something we can bring back to our plans in anticipation for icann 70. 
> 
> Apart from the webinar, I would kindly ask you to  let me know if you would be interested in setting a call with the CPH WG. 
> 
> best, 
> Bruna 
> 
> ---------- Forwarded message ---------
> From: Drazek, Keith <kdrazek at verisign.com <mailto:kdrazek at verisign.com>>
> Date: Fri, Jan 22, 2021 at 5:44 PM
> Subject: Engagement on DNS Abuse
> To: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com> <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>>
> Cc: Brian F. Cimbolic <BCimbolic at pir.org <mailto:BCimbolic at pir.org>>, Jim Galvin <jgalvin at afilias.info <mailto:jgalvin at afilias.info>>, Graeme Bunton <gbunton at tucows.com <mailto:gbunton at tucows.com>>
> 
> 
> Hello Bruna,
> 
>  
> 
> I hope you?re doing well and staying healthy and safe. I am reaching out to you on behalf of the Contracted Party House DNS Abuse Working Group as we look ahead to ICANN 70 and the rest of 2021.
> 
>  
> 
> The Contracted Party House (CPH) DNS Abuse Group is conducting outreach to our friends in other SO/AC/SG/Cs regarding DNS Abuse. As previously noted by the CPH, DNS Abuse <https://rrsg.org/wp-content/uploads/2020/10/CPH-Definition-of-DNS-Abuse.pdf> comprises five categories: phishing, pharming, malware, botnets, and spam when it acts as a delivery mechanism for one of the other forms of DNS Abuse.
> 
>  
> 
> We want to open a more direct dialogue to understand pain points, hear suggestions and identify common ground where we can work together to mitigate DNS Abuse.  Is there a subset of the NCSG focusing on DNS Abuse questions that would be able to join the CPH DNS Abuse group on a call to discuss this topic? We want to encourage frank and productive discussions  on the topic that lead to really informing our dialogues and actions.
> 
>  
> 
> As a starting point, we propose the following questions to guide our discussion.  Are there any questions NCSG would like discuss?:
> 
>  
> 
> What information do you use and how do you use it to assess DNS Abuse levels?
> 
>  
> 
> What are the NCSG?s pain points regarding DNS Abuse?
> 
>  
> 
> Are you seeing practices from registrars or registries you find helpful?
> 
>  
> 
> Please let us know if a subgroup of the NCSG would be willing to join us.  Our group meets regularly on Tuesdays at 1500 UTC.  If so, please propose a Tuesday when you are available.
> 
>  
> 
> Best regards,
> 
> Keith
> 
>  
> 
> Keith Drazek
> 
> Vice President, Public Policy & Government Relations
> 
> Verisign, Inc.
> 
> +1-571-377-9182
> 
> Kdrazek at verisign.com <mailto:Kdrazek at verisign.com>
>  
> 
>  
> 
> 
> 
> -- 
> Bruna Martins dos Santos 
> 
> Skype ID: bruna.martinsantos
> @boomartins
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> _______________________________________________
> 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/20210201/0ecd60c0/attachment.htm>

From brenda.brewer at icann.org  Mon Feb  1 17:24:20 2021
From: brenda.brewer at icann.org (Brenda Brewer)
Date: Mon, 1 Feb 2021 15:24:20 +0000
Subject: [NCSG-PC] NCSG Policy Call - transcript, attendees, replay,
 chat - 19 January 2021
Message-ID: <50D94549-762D-4139-971E-76A07909025D@icann.org>

Good day all,

Please find attached the transcript for the 19 January 2021 NCSG Policy Call.  Thank you!

Kind regards,
Brenda

From: Brenda Brewer <brenda.brewer at icann.org>
Date: Wednesday, January 20, 2021 at 8:13 AM
To: NCSG List <NCSG-DISCUSS at LISTSERV.SYR.EDU>, "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
Cc: Maryam Bakoshi <maryam.bakoshi at icann.org>, Brenda Brewer <brenda.brewer at icann.org>
Subject: NCSG Policy Call - attendees, replay, chat - 19 January 2021

Dear All,

Please find attendees, replay, and chat details for the monthly NCSG Policy Call held on Tuesday, 19 January 2021 at 11:30 UTC.

Kind regards,
Brenda & Maryam


Attendees:  Abdias Zambrano, Avri Doria, Bruna Martins dos Santos, Bukola Oronti, Daniel Dasig Jr., Ephraim Percy Kenyanito, Farell Folly, Grace Githaiga, GZ Kabir, Iona Stupariu, Juan Manuel Rojas, Kathryn Kleiman, Lavish Mawuena Mensah, Lia Hern?ndez P?rez, Manju Chen, Nadira Al-Araj, Ol?vi? Kouami, Olga Kyryliuk, Oreoluwa Lesi, Pedro de Perdig?o Lana, Poncelet Ileleji, Rafik Dammak, Raoul Plommer, Raymond Mamattah, Shah Rahman, Shavkat Sabirov, Stephanie Perrin, Stephen Dakyi, Taiwo Peter Akinremi, Tatiana Tropina, Tomslin Samme-Nlar, Vernatius Okwu Ezeama, Vrikson Acosta  |  ICANN org:  Brenda Brewer, Carlos Reyes  |  Apologies:  Raphael Beauregard-Lacroix

Zoom Replay:  https://icann.zoom.us/rec/play/IQlb4D2ZrkQ2lc_wbEl9DDLx2j0RatP2K4AT7EQIuDCh6WVSJ240Tui7aljPa2c2myuqwsIBOjXu3BCt.P0Q2MsI4h8lRMbLd

Zoom Chat:  See attached

Zoom Transcript:  will be sent upon receipt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210201/21fe677a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Transcript_NCSG Policy_19Jan2021.pdf
Type: application/pdf
Size: 250044 bytes
Desc: Transcript_NCSG Policy_19Jan2021.pdf
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210201/21fe677a/attachment.pdf>

From mesumbeslin at gmail.com  Thu Feb  4 06:13:14 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 4 Feb 2021 15:13:14 +1100
Subject: [NCSG-PC] PC Vice-Chair Election Results
Message-ID: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>

Dear PC,

I would like to announce that the NCSG Policy Committee elected vice-chair
is  - Akinremi Peter Taiwo.

I wish Akinremi good luck in the role and I look forward to working with
him.

Cheers,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210204/14fe9ae6/attachment.htm>

From bruna.mrtns at gmail.com  Thu Feb  4 08:36:36 2021
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Thu, 4 Feb 2021 04:36:36 -0200
Subject: [NCSG-PC] PC Vice-Chair Election Results
In-Reply-To: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
References: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
Message-ID: <CADAEEV0NL7DW4xJP-oxhBHgyALZkN0AAWMYKX1JyxXcR0hNHsg@mail.gmail.com>

Congrats, Akinremi!

On Thu, Feb 4, 2021 at 2:13 AM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear PC,
>
> I would like to announce that the NCSG Policy Committee elected vice-chair
> is  - Akinremi Peter Taiwo.
>
> I wish Akinremi good luck in the role and I look forward to working with
> him.
>
> Cheers,
> Tomslin
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>


-- 
*Bruna Martins dos Santos *

Skype ID: bruna.martinsantos
@boomartins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210204/542a6dc0/attachment.htm>

From wisdom.dk at gmail.com  Thu Feb  4 11:47:57 2021
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Thu, 4 Feb 2021 09:47:57 +0000
Subject: [NCSG-PC] PC Vice-Chair Election Results
In-Reply-To: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
References: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
Message-ID: <CAAU+vPH_m20S1H8kro3vK=Qxy2_C4yETSYb8FzmhGTJWFPtBSw@mail.gmail.com>

Congratulations Peter.

On Thursday, February 4, 2021, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear PC,
>
> I would like to announce that the NCSG Policy Committee elected vice-chair
> is  - Akinremi Peter Taiwo.
>
> I wish Akinremi good luck in the role and I look forward to working with
> him.
>
> Cheers,
> Tomslin
>
>


-- 
*WISDOM DONKOR*
President & CEO
Africa Open Data and Internet Research Foundation
P.O. Box CT 2439, Cantonments, Accra | www.aodirf.org  / www.afrigeocon.org
Tel: +233 20 812 8851
Skype: wisdom_dk | Facebook: kwasi wisdom |  Twitter: @wisdom_dk
_____________________________________________________________________________
ICANN GNSO Council Member | UN IGF MAG Member | World Bank Independent
Consultant | AU AFIGF Member
___________________________________________________________
Specialization:
E-government Network Infrastructure and E-application, Internet
Governance,  Open Data policies platforms & Community Development, Cyber
Security,  Domain Name Systems, Software Engineering, Event Planning &
Management,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210204/029af6bc/attachment.htm>

From farell at benin2point0.org  Thu Feb  4 12:01:10 2021
From: farell at benin2point0.org (Farell FOLLY)
Date: Thu, 4 Feb 2021 11:01:10 +0100
Subject: [NCSG-PC] PC Vice-Chair Election Results
In-Reply-To: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
References: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
Message-ID: <85B08989-41F1-48CC-9901-2EB7D15D6D9E@benin2point0.org>

Congrats Peter.

@__f_f__

Best regards
____________________________________

Lt-Colonel Farell FOLLY, Ir
GNSO Councillor
linkedin.com/in/farellf 






> On 4 Feb 2021, at 05:13, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:
> 
> Dear PC, 
> 
> I would like to announce that the NCSG Policy Committee elected vice-chair is  - Akinremi Peter Taiwo. 
> 
> I wish Akinremi good luck in the role and I look forward to working with him.
> 
> Cheers,
> Tomslin
>    
> _______________________________________________
> 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/20210204/2d1243d2/attachment.htm>

From oreoluwa at wtec.org.ng  Thu Feb  4 19:23:25 2021
From: oreoluwa at wtec.org.ng (Oreoluwa Lesi)
Date: Thu, 4 Feb 2021 18:23:25 +0100
Subject: [NCSG-PC] PC Vice-Chair Election Results
In-Reply-To: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
References: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
Message-ID: <F0440588-5B5C-4D34-B2D2-9E9D0AF38C63@wtec.org.ng>

Congratulations in your new role, Peter.

-- 
Oreoluwa Lesi
Executive Director, Women's Technology Empowerment Centre (W.TEC)
+234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng | @wteconline 




> On 4 Feb 2021, at 5:13 AM, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:
> 
> Dear PC, 
> 
> I would like to announce that the NCSG Policy Committee elected vice-chair is  - Akinremi Peter Taiwo. 
> 
> I wish Akinremi good luck in the role and I look forward to working with him.
> 
> Cheers,
> Tomslin
>    
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc



From compsoftnet at gmail.com  Thu Feb  4 20:41:10 2021
From: compsoftnet at gmail.com (Akinremi Peter Taiwo)
Date: Thu, 4 Feb 2021 19:41:10 +0100
Subject: [NCSG-PC] PC Vice-Chair Election Results
In-Reply-To: <F0440588-5B5C-4D34-B2D2-9E9D0AF38C63@wtec.org.ng>
References: <CAM8DdeX0VoZjQE3ZcjStBuEUHNSzfhGvtGJKL08_Tisf141R9g@mail.gmail.com>
 <F0440588-5B5C-4D34-B2D2-9E9D0AF38C63@wtec.org.ng>
Message-ID: <CAGK4d09eJnhgWTNa4s5vs6aO6w2-3znrzsvrmoNVBaunr8vKUw@mail.gmail.com>

Thank you all for the wishes

Looking forward to working with everyone.

Regards

On Thu, 4 Feb. 2021, 6:23 pm Oreoluwa Lesi, <oreoluwa at wtec.org.ng> wrote:

> Congratulations in your new role, Peter.
>
> --
> Oreoluwa Lesi
> Executive Director, Women's Technology Empowerment Centre (W.TEC)
> +234.803.621.1307, +234.813.339.9999 | www.wtec.org.ng | @wteconline
>
>
>
>
> > On 4 Feb 2021, at 5:13 AM, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
> >
> > Dear PC,
> >
> > I would like to announce that the NCSG Policy Committee elected
> vice-chair is  - Akinremi Peter Taiwo.
> >
> > I wish Akinremi good luck in the role and I look forward to working with
> him.
> >
> > Cheers,
> > Tomslin
> >
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
> _______________________________________________
> 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/20210204/2be238f2/attachment.htm>

From mesumbeslin at gmail.com  Tue Feb  9 09:39:54 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 9 Feb 2021 18:39:54 +1100
Subject: [NCSG-PC] Fwd: [council] Final Proposed Agenda | GNSO Council
 Meeting 18 February 2021 at 19:00 UTC
In-Reply-To: <67AB3ACA-5A8C-44F8-ACA2-588B286250FB@icann.org>
References: <67AB3ACA-5A8C-44F8-ACA2-588B286250FB@icann.org>
Message-ID: <CAM8DdeV0TOwfeXXDQz2Jq+yfLibUTgZc0TwycDFGvXB9Bz3Tjw@mail.gmail.com>

Dear all,

Please find below the final proposed agenda for the February Council
meeting.

Cheers,
Tomslin


---------- Forwarded message ---------
From: Nathalie Peregrine <nathalie.peregrine at icann.org>
Date: Tue., 9 Feb. 2021, 10:17
Subject: [council] Final Proposed Agenda | GNSO Council Meeting 18 February
2021 at 19: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 18
February 2021 at 19:00 UTC.
Draft GNSO Council Agenda 18 February 2021

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/QwtACQ



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 19:00 UTC



Coordinated Universal Time: 19:00 UTC: https://tinyurl.com/yxdh3opz



11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 22:00
Moscow; (Friday) 06:00 Melbourne



GNSO Council Meeting Remote Participation:

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 (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-17dec20-en.pdf.pdf>
of the GNSO Council meeting on 17 December 2020 were posted on 3 January
2021.

Minutes of the GNSO Council meeting on 21 January 2021 were posted on 4
February 2021.



*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 (5 minutes) *

3.1 - Confirmation of of SSC selection processes:

   - Confirmation of Philippe Fouquart to serve as the GNSO Council liaison
   to the EPDP 2A.
   - Non-objection from the Council for the EPDP Team to appoint a non-EPDP
   Team member as vice-chair.
   - Confirmation of the Recommendations Report [LINK TO BE ADDED UPON
   RECEIPT] to the ICANN Board regarding adoption of all recommendations from
   the Phase 1 Final Report of the Review of All Rights Protection Mechanisms
   (RPMs) in All gTLDs PDP.
   - Per the incoming letter [LINK TO BE ADDED UPON RECEIPT] from the IANA
   Naming Function Review Team (IFRT), approval of the IFRT?s Recommendation
   that would require an amendment to the IANA Naming Function Contract.



*Item 4: COUNCIL VOTE - Approval to Initiate a Two-Phased Policy
Development Process on the Transfer Policy (15 minutes)*

The GNSO Council established a Transfer Policy Review Scoping Team to
provide recommendations on the approach to a potential review and future
policy work related to the Transfer Policy, including composition of the
review team or PDP working group and scope of the review. The Transfer
Policy Review Scoping Team delivered a Transfer Policy Initial Scoping Paper
<https://gnso.icann.org/sites/default/files/file/field-file-attach/transfer-policy-review-scoping-team-06apr20-en.pdf>
on April 6, 2020 in which it recommended the GNSO Council instruct ICANN
Policy staff to draft a Preliminary Issue Report. On 24 June 2020, the
Council requested the preparation of a Preliminary Issue Report. The
Preliminary Issue Report was published for public comment on 12 October
2020 and after the report was adjusted to take into account public comments
as appropriate, the Final Issue Report
<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-issue-report-pdp-transfer-policy-review-12jan21-en.pdf>
was delivered to the GNSO Council on 12 January 2021.

The Final Issue Report includes a recommendation that the GNSO Council
proceed with a two-phased Policy Development Process (PDP) that will
address the following topic areas in sequence:

   - Phase 1(a): Form of Authorization (including Rec. 27, Wave 1 FOA
   issues) and AuthInfo Code
   - Phase 1(b): Change of Registrant (including Rec. 27, Wave 1 Change of
   Registrant issues)
   - Phase 2: Transfer Emergency Action Contact and reversing
   inter-registrar transfers, Transfer Dispute Resolution Policy (including
   Rec. 27, Wave 1 TDRP issues), NACKing transfers, ICANN-approved transfers

The General Counsel of ICANN has indicated that the topics recommended for
review are properly within the scope of the ICANN policy process and the
GNSO. On 1 February 2021, policy staff shared a  pre-recorded webinar
<https://community.icann.org/x/J4FeCQ> to help Councilors prepare for this
agenda item.

Here, the Council will vote to initiate a two-phased PDP to review the
Transfer Policy, as recommended in the Final Issue Report.

4.1 - Presentation of motion <https://community.icann.org/x/SAtACQ> (TBD)

4.2 ? Council discussion

4.3 ? 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?s remit as outlined in ICANN?s
Bylaws as the GNSO ?shall 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 forth in these Bylaws?
(Art.11.1). Furthermore, this action complies with the requirements set out
in Annex A: GNSO Policy Development Process of the ICANN Bylaws.*



*Item 5: COUNCIL VOTE - Final Report and Outputs From the New gTLD
Subsequent Procedures PDP (20 minutes)*

The New gTLD Subsequent Procedures (SubPro) PDP was chartered in January
2016  to review the 2012 New gTLD Program round to determine what, if any
changes may need to be made to the existing 2007 Introduction of New
Generic Top-Level Domains policy recommendations. After extensive WG
deliberations and a number of community consultations, the WG
delivered its Final
Report
<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf>
to the GNSO Council on 18 January 2021. Because of the volume of
outputs(e.g., affirmations, recommendations, implementation guidance, etc.)
and length of the report, the PDP Co-Chairs believed that similar to the
Final Report for the All Rights Protection Mechanisms (RPMs) in All gTLDs
PDP WG, a preliminary briefing would be beneficial and therefore, scheduled
a briefing during the January 2020 Council meeting.

Subsequently, and again similar to the RPMs PDP, the GNSO Council liaison
to the PDP and the Co-Chairs held a detailed webinar and discussion on the
report, to better prepare the Council for a vote during a subsequent
Council meeting.

Here, the Council will vote to adopt the Final Report of the SubPro WG.

5.1 - Presentation of motion <https://community.icann.org/x/SAtACQ> (GNSO
Council liaison to the PDP, Flip Petillion)

5.2 ? Council discussion

5.3 ? Council vote (voting threshold: supermajority)

*Taking this action is within the GNSO?s remit as outlined in ICANN?s
Bylaws as the GNSO ?shall 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 forth in these Bylaws?
(Art.11.1). Furthermore, this action complies with the requirements set out
in Annex A: GNSO Policy Development Process of the ICANN Bylaws.*



*Item 6: COUNCIL DISCUSSION ? Charter for the Transfer Policy PDP (20
minutes)*

In connection to item 4, if the Council initiates a PDP on the Transfer
Policy, it will subsequently need to adopt a charter. The Preliminary Issue
Report included a draft charter, which was included in the public comment
proceeding. That draft charter is also included in the Final Issue Report.
Comment on the draft charter was solicited from Councilors via a
pre-recorded webinar <https://community.icann.org/x/J4FeCQ>prior to this
Council meeting.

Here, the Council will discuss whether there are substantive changes needed
for the draft charter and determine next steps as appropriate.

6.1 ? Introduction of topic (Council leadership)

6.2 ? Council discussion

6.3 ? Next steps



*Item 7: COUNCIL UPDATE - Update from the Internationalized Domain Names
(IDNs) EPDP Charter Drafting Team (15 minutes)*

During the Council?s October 2020 meeting, the Council agreed to launch a
call for volunteers and to establish a drafting team to develop a draft
charter and an EPDP initiation request for the IDN Policy Track 2. That
drafting team met for the first time on 5 January 2021 and since then has
steadily made progress, recently agreeing for the most part to a set of
principles and underlying assumptions to help make its work more efficient.
Previous to that agreement, making progress was challenging, resulting in
an extension of the expected completion date from the March Council meeting
to the May Council meeting (see workplan here
<https://docs.google.com/spreadsheets/d/1mD0soQAd-OfPQCiY5aHls3HVltq0CtSu8aAlZ5zQlAk/edit#gid=0>
).

Here, the Council will receive an update from the drafting team.

7.1 ? Introduction of topic (Chair of the drafting team, Dennis Tan)

7.2 ? Council discussion

7.3 ? Next steps


*Item 8: ANY OTHER BUSINESS (20 minutes)*

8.1 - EPDP-P2A Project and Work Plan commitment

8.2 - Update from the GNSO Council liaison to the GAC, including his
discussion with the GAC point of contact to the GNSO, Jorge Cancio.

8.3 - ICANN70 GNSO sessions



_______________________________

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 19:00 UTC

Local time between November and March Winter in the NORTHERN hemisphere

----------------------------------------------------------------------------

California, USA (PDT) UTC-8 11:00

San Jos?, Costa Rica (CST) UTC-6 13:00

New York/Washington DC, USA (EDT) UTC-5 14:00

Buenos Aires, Argentina (ART) UTC-3 16:00

Rio de Janeiro, Brazil (BRST) UTC-3 16:00

London, United Kingdom (GMT) UTC+0 19:00

Kinshasa, Democratic Republic of Congo (WAT) UTC+1 20:00

Paris, France (CEST) UTC+1 20:00

Moscow, Russia (MST) UTC+3 22:00

Singapore (SGT) (+1 day) UTC+8 03:00

Melbourne, Australia (AEDT)(+1 day) UTC+11 06:00

----------------------------------------------------------------------------

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.

----------------------------------------------------------------------

For other places see http://www.timeanddate.com and
https://tinyurl.com/yxdh3opz




_______________________________________________
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-pc/attachments/20210209/1b7fe452/attachment.htm>

From farell at benin2point0.org  Tue Feb  9 11:12:05 2021
From: farell at benin2point0.org (Farell FOLLY)
Date: Tue, 9 Feb 2021 10:12:05 +0100
Subject: [NCSG-PC] PC-related tasks improvements
In-Reply-To: <90506FE9-D5EE-4D00-9CBB-A10D8477F935@benin2point0.org>
References: <35ABCEC3-AFC3-4CE9-8FC4-C45284F78FD2@benin2point0.org>
 <8AEF9566-0DE6-4A4D-892E-826159A657B4@benin2point0.org>
 <59E97394-4B1F-4176-B0BE-6B80ADD0AB5C@benin2point0.org>
 <90506FE9-D5EE-4D00-9CBB-A10D8477F935@benin2point0.org>
Message-ID: <402EA991-E2B2-4586-94C2-D2987D496867@benin2point0.org>

Dear all,


I think we can now close this issue, at least by now, and move forward. I will sum up my constations around the following points:

There are some improvements needed regarding the way we engage with the membership
There are some improvements needed regarding how we handle the drafting of public comments and how we organise ourselves
There are some suggestions to improve the archive and our online presence.


I will let the new PC leadership decide the way they would like to approach these issues. As far I am concerned, I will work with some key members to build a roaster, basically  an SME database, that could help support newcomers or members that have to draft Public comments. Then, whenever a new call for Public comment is issued, volunteers can know upfront who can help them quickly to have the right information, give them the background and the NCSG historical position on the issue.

I wish you all a nice day.



@__f_f__

Best regards
____________________________________

Lt-Colonel Farell FOLLY, Ir
GNSO Councillor
linkedin.com/in/farellf 






> On 27 Jan 2021, at 19:57, Farell FOLLY <farell at benin2point0.org> wrote:
> 
> Dear All,
> 
> 
> It?s now been a little while since and I  have seen many interesting comments on the document. Surely it looks like there are ways for improvements. At least, I saw nobody against the suggestions. There are suggestions that are straightforward and some that would probably require explicit consent from the wider membership.
> 
> I invite this who wanted to comment but didn?t have the opportunity yet.. I will let the document open for a while before drafting a summary thereof.
> 
> 
> @__f_f__
> 
> Best regards
> ____________________________________
> 
> Lt-Colonel Farell FOLLY, Ir
> GNSO Councillor
> linkedin.com/in/farellf <http://linkedin.com/in/farellf> 
> 
> 
> 
> 
> 
> 
>> On 28 Dec 2020, at 09:54, Farell FOLLY <farell at benin2point0.org <mailto:farell at benin2point0.org>> wrote:
>> 
>> Dear All,
>> 
>> I hope you are all doing well. This is gentle reminder to comment on the document for improvements about our policy-related activities. I already saw some interesting inputs.
>> 
>> Season?s greetings. Stay safe!
>> 
>> 
>> @__f_f__
>> 
>> Best regards
>> ____________________________________
>> 
>> Farell FOLLY
>> GNSO Councillor
>> linkedin.com/in/farellf <http://linkedin.com/in/farellf> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On 16 Dec 2020, at 19:14, Farell FOLLY <farell at benin2point0.org <mailto:farell at benin2point0.org>> wrote:
>>> 
>>> Dear all,
>>> 
>>> Following our recent policy meeting held on 14th of December, I would like to share with you the following document <https://docs.google.com/document/d/1HLRUXMoLMPQrqF0rQdk3lnD7ZfKpDJS7-ED5G1IXMps/edit?usp=sharing> where you can put your thoughts and suggestions on the matter named in this e-mail?s subject. There is a brief notice at the beginning of the document that explains the purpose and what is expected.
>>> 
>>> In sum:
>>> 
>>> ?>  given the very low and decreasing engagement of our membership, I was suggesting during the meeting that we should improve some of the ways we engage with them (members)  for policy-related tasks, especially for public comments drafting, documents archiving and materials sharing. This document gives the opportunity to all PC members to opine on this matter.
>>> 
>>> ?> Currently, most of the recurrent routines of the Policy Committee is to share information from other ICANN stakeholders to the members, leading and coordinate the drafting of public comments, liaise with and follow the WG PDPs, just to name a few. 
>>> 
>>> ?> Therefore, a minimalistic list of areas of improvements could be: how we coordinate public comment draftings, how we share and manage information and resources.
>>> 
>>> Although it is not very urgent, it would be good if people react on this asap or anytime before next year so that we can collect all opinions in order to make a decision.
>>> 
>>> The document is available at: https://docs.google.com/document/d/1HLRUXMoLMPQrqF0rQdk3lnD7ZfKpDJS7-ED5G1IXMps/edit?usp=sharing <https://docs.google.com/document/d/1HLRUXMoLMPQrqF0rQdk3lnD7ZfKpDJS7-ED5G1IXMps/edit?usp=sharing> 
>>> 
>>> All the best for Christmas and the season.
>>> 
>>> 
>>> @__f_f__
>>> 
>>> Best regards
>>> ____________________________________
>>> 
>>> Farell FOLLY
>>> GNSO Councillor
>>> linkedin.com/in/farellf <http://linkedin.com/in/farellf> 
>>> 
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>> 
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> 
> _______________________________________________
> 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/20210209/13ea9b86/attachment.htm>

From mesumbeslin at gmail.com  Tue Feb  9 11:59:12 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 9 Feb 2021 20:59:12 +1100
Subject: [NCSG-PC] PC-related tasks improvements
In-Reply-To: <402EA991-E2B2-4586-94C2-D2987D496867@benin2point0.org>
References: <35ABCEC3-AFC3-4CE9-8FC4-C45284F78FD2@benin2point0.org>
 <8AEF9566-0DE6-4A4D-892E-826159A657B4@benin2point0.org>
 <59E97394-4B1F-4176-B0BE-6B80ADD0AB5C@benin2point0.org>
 <90506FE9-D5EE-4D00-9CBB-A10D8477F935@benin2point0.org>
 <402EA991-E2B2-4586-94C2-D2987D496867@benin2point0.org>
Message-ID: <CAM8DdeWtEXFi-HrTvQEZA4cteZzC+Sbifa5OwMU5XbhtWUeS1w@mail.gmail.com>

Hi Farell,

Thank you for the summary. I think keeping  confluence updated is a low
hanging fruit which we can quickly work on too.
In the last meeting, someone volunteered to help with this. PC leadership
will reach out to them.

Cheers,
Tomslin


On Tue., 9 Feb. 2021, 20:12 Farell FOLLY, <farell at benin2point0.org> wrote:

> Dear all,
>
>
> I think we can now close this issue, at least by now, and move forward. I
> will sum up my constations around the following points:
>
>
>    1. There are some improvements needed regarding the way we engage with
>    the membership
>    2. There are some improvements needed regarding how we handle the
>    drafting of public comments and how we organise ourselves
>    3. There are some suggestions to improve the archive and our online
>    presence.
>
>
>
> I will let the new PC leadership decide the way they would like to
> approach these issues. As far I am concerned, I will work with some key
> members to build a roaster, basically  an SME database, that could help
> support newcomers or members that have to draft Public comments. Then,
> whenever a new call for Public comment is issued, volunteers can know
> upfront who can help them quickly to have the right information, give them
> the background and the NCSG historical position on the issue.
>
> I wish you all a nice day.
>
>
>
> @__f_f__
>
> Best regards
> ____________________________________
>
> Lt-Colonel Farell FOLLY, Ir
> GNSO Councillor
> linkedin.com/in/farellf
>
>
>
>
>
>
> On 27 Jan 2021, at 19:57, Farell FOLLY <farell at benin2point0.org> wrote:
>
> Dear All,
>
>
> It?s now been a little while since and I  have seen many interesting
> comments on the document. Surely it looks like there are ways for
> improvements. At least, I saw nobody against the suggestions. There are
> suggestions that are straightforward and some that would probably require
> explicit consent from the wider membership.
>
> I invite this who wanted to comment but didn?t have the opportunity yet..
> I will let the document open for a while before drafting a summary thereof.
>
>
> @__f_f__
>
> Best regards
> ____________________________________
>
> Lt-Colonel Farell FOLLY, Ir
> GNSO Councillor
> linkedin.com/in/farellf
>
>
>
>
>
>
> On 28 Dec 2020, at 09:54, Farell FOLLY <farell at benin2point0.org> wrote:
>
> Dear All,
>
> I hope you are all doing well. This is gentle reminder to comment on the
> document for improvements about our policy-related activities. I already
> saw some interesting inputs.
>
> Season?s greetings. Stay safe!
>
>
> @__f_f__
>
> Best regards
> ____________________________________
>
> Farell FOLLY
> GNSO Councillor
> linkedin.com/in/farellf
>
>
>
>
>
>
> On 16 Dec 2020, at 19:14, Farell FOLLY <farell at benin2point0.org> wrote:
>
> Dear all,
>
> Following our recent policy meeting held on 14th of December, I would like
> to share with you the following document
> <https://docs.google.com/document/d/1HLRUXMoLMPQrqF0rQdk3lnD7ZfKpDJS7-ED5G1IXMps/edit?usp=sharing> where
> you can put your thoughts and suggestions on the matter named in this
> e-mail?s subject. There is a brief notice at the beginning of the document
> that explains the purpose and what is expected.
>
> In sum:
>
> ?>  given the very low and decreasing engagement of our membership, I was
> suggesting during the meeting that we should improve some of the ways we
> engage with them (members)  for policy-related tasks, especially for public
> comments drafting, documents archiving and materials sharing. This document
> gives the opportunity to all PC members to opine on this matter.
>
> ?> Currently, most of the recurrent routines of the Policy Committee is to
> share information from other ICANN stakeholders to the members, leading and
> coordinate the drafting of public comments, liaise with and follow the WG
> PDPs, just to name a few.
>
> ?> Therefore, a minimalistic list of areas of improvements could be: how
> we coordinate public comment draftings, how we share and manage information
> and resources.
>
> Although it is not very urgent, it would be good if people react on this
> asap or anytime before next year so that we can collect all opinions in
> order to make a decision.
>
> The document is available at:
> https://docs.google.com/document/d/1HLRUXMoLMPQrqF0rQdk3lnD7ZfKpDJS7-ED5G1IXMps/edit?usp=sharing
>
>
> All the best for Christmas and the season.
>
>
> @__f_f__
>
> Best regards
> ____________________________________
>
> Farell FOLLY
> GNSO Councillor
> linkedin.com/in/farellf
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
>
> _______________________________________________
> 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/20210209/294fad9b/attachment.htm>

From stephanie at digitaldiscretion.ca  Wed Feb 10 18:10:40 2021
From: stephanie at digitaldiscretion.ca (Stephanie E Perrin)
Date: Wed, 10 Feb 2021 11:10:40 -0500
Subject: [NCSG-PC] transfer policy amendments
Message-ID: <86defb83-a56d-1bad-012b-00d8efae764b@digitaldiscretion.ca>

Members may have heard discussion of the amendments to the transfer 
policy,? We should probably discuss at a PC meeting in a more fulsome 
manner.? In the meantime, review of the current document is homework for 
the IRT members, who meet today in an hour.? Just posting the link to 
the google doc for those who are interested in this topic. 
https://docs.google.com/document/d/1-IOK0R1T8ecn1eBS5rHjvkU1C5ASnSww/edit#heading=h.gjdgxs

Frequently people ask team members to send a digest of what is going on 
to the list.? I usually push back, and this is a good example of why.? 
It is a 26 page document, I will barely get it reviewed in time for the 
meeting, let alone write up a summary. Suggestions welcome, but shadow 
members of working groups would be great.

Cheers Stephanie Perrin



From mesumbeslin at gmail.com  Wed Feb 10 22:53:59 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Thu, 11 Feb 2021 07:53:59 +1100
Subject: [NCSG-PC] transfer policy amendments
In-Reply-To: <86defb83-a56d-1bad-012b-00d8efae764b@digitaldiscretion.ca>
References: <86defb83-a56d-1bad-012b-00d8efae764b@digitaldiscretion.ca>
Message-ID: <CAM8DdeXWDkuKJZC1sSCSBpeuBM7OBSKJ+pHaq=9n2C3Q2dYtpQ@mail.gmail.com>

Hi Stephanie,

Thanks for bringing this to the list. We can include it for discussion in
our meeting next week. I also noticed the google doc requires authenticated
access. Any chance you could forward a copy to the list so that more
members can have access to it?

Cheers,
Tomslin



On Thu, 11 Feb 2021 at 03:10, Stephanie E Perrin <
stephanie at digitaldiscretion.ca> wrote:

> Members may have heard discussion of the amendments to the transfer
> policy,  We should probably discuss at a PC meeting in a more fulsome
> manner.  In the meantime, review of the current document is homework for
> the IRT members, who meet today in an hour.  Just posting the link to
> the google doc for those who are interested in this topic.
>
> https://docs.google.com/document/d/1-IOK0R1T8ecn1eBS5rHjvkU1C5ASnSww/edit#heading=h.gjdgxs
>
> Frequently people ask team members to send a digest of what is going on
> to the list.  I usually push back, and this is a good example of why.
> It is a 26 page document, I will barely get it reviewed in time for the
> meeting, let alone write up a summary. Suggestions welcome, but shadow
> members of working groups would be great.
>
> Cheers Stephanie Perrin
>
> _______________________________________________
> 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/20210211/5a536ac0/attachment.htm>

From stephanie at digitaldiscretion.ca  Thu Feb 11 07:01:09 2021
From: stephanie at digitaldiscretion.ca (Stephanie Perrin)
Date: Thu, 11 Feb 2021 00:01:09 -0500
Subject: [NCSG-PC] transfer policy amendments
In-Reply-To: <CAM8DdeXWDkuKJZC1sSCSBpeuBM7OBSKJ+pHaq=9n2C3Q2dYtpQ@mail.gmail.com>
References: <CAM8DdeXWDkuKJZC1sSCSBpeuBM7OBSKJ+pHaq=9n2C3Q2dYtpQ@mail.gmail.com>
Message-ID: <C688E695-8551-4E40-B808-F89E1F3446CC@digitaldiscretion.ca>

Sorry, i did not notice this and if it is not visible to non- members, i find that to be a concern.  Our deliberations are supposed to be publicly archived.
Stephanie 

Sent from my iPhone

> On Feb 10, 2021, at 15:54, Tomslin Samme-Nlar <mesumbeslin at gmail.com> wrote:
> 
> ?
> Hi Stephanie,
> 
> Thanks for bringing this to the list. We can include it for discussion in our meeting next week. I also noticed the google doc requires authenticated access. Any chance you could forward a copy to the list so that more members can have access to it?
> 
> Cheers,
> Tomslin
> 
> 
> 
>> On Thu, 11 Feb 2021 at 03:10, Stephanie E Perrin <stephanie at digitaldiscretion.ca> wrote:
>> Members may have heard discussion of the amendments to the transfer 
>> policy,  We should probably discuss at a PC meeting in a more fulsome 
>> manner.  In the meantime, review of the current document is homework for 
>> the IRT members, who meet today in an hour.  Just posting the link to 
>> the google doc for those who are interested in this topic. 
>> https://docs.google.com/document/d/1-IOK0R1T8ecn1eBS5rHjvkU1C5ASnSww/edit#heading=h.gjdgxs
>> 
>> Frequently people ask team members to send a digest of what is going on 
>> to the list.  I usually push back, and this is a good example of why.  
>> It is a 26 page document, I will barely get it reviewed in time for the 
>> meeting, let alone write up a summary. Suggestions welcome, but shadow 
>> members of working groups would be great.
>> 
>> Cheers Stephanie Perrin
>> 
>> _______________________________________________
>> 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/20210211/cc34f0e7/attachment.htm>

From mesumbeslin at gmail.com  Fri Feb 12 12:08:34 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Fri, 12 Feb 2021 21:08:34 +1100
Subject: [NCSG-PC] Fwd: [Public Comment] Call for volunteers - FY22-26
 Operating & Financial Plan and Draft FY22 Operating Plan & Budget
In-Reply-To: <CAPZSw-q1DGCs+v_-vO1UcUFCs3b1-Q9yFLNXtgmp46QeTaZNdg@mail.gmail.com>
References: <CAM8DdeWKFQnW4f6GE03Xb=KVKfPFOR21y+UvqwQNT0ytKtmyZg@mail.gmail.com>
 <CAPZSw-q1DGCs+v_-vO1UcUFCs3b1-Q9yFLNXtgmp46QeTaZNdg@mail.gmail.com>
Message-ID: <CAM8DdeXwAjh4u6+hFztmQpREg2r26+NOjmMBkqD15suerjaKNA@mail.gmail.com>

Dear PC,

Could you please review the below comment? I will be sending it off on
Monday morning to the comments team.

Cheers,
Tomslin


---------- Forwarded message ---------
From: Raphael Beauregard-Lacroix <rbeauregardlacroix at gmail.com>
Date: Thu., 11 Feb. 2021, 02:36
Subject: Re: [Public Comment] Call for volunteers - FY22-26 Operating &
Financial Plan and Draft FY22 Operating Plan & Budget
To: Tomslin Samme-Nlar <mesumbeslin at gmail.com>
Cc: NCSG-DISCUSS at LISTSERV.SYR.EDU <NCSG-DISCUSS at listserv.syr.edu>


Hi all,

Please find below the draft comment for your consideration.

Given the upcoming deadline, in order to ensure that the PC has enough time
for its consideration, please provide your own comments and edits by *tomorrow
Thursday 23:59 UTC. *

https://docs.google.com/document/d/11DszoVkoE4-yHTutHpsTn1BPPZgLL3EfPgxrqmZiGq4/edit

Thank you,

On Mon, Dec 21, 2020 at 9:47 PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear members,
>
> ICANN has just published the FY22-26 Operating & Financial Plan and Draft
> FY22 Operating Plan & Budget for public comment.
>
> The Policy Committee is calling for volunteers to draft an NCSG comment to
> the draft plan and budget. Please let me know off-list if you'd like to
> volunteer for the comment drafting. It'll be nice to have more than one
> volunteers, including new-commers who can use this as an opportunity to
> learn and be familiar with policy work.
>
> More information about the draft plan and budget can be found here :
> https://www.icann.org/public-comments/draft-opplan-budget-fy22-26-2020-12-17-en
>
> A draft Google doc for the comment can be found here:
> https://docs.google.com/document/d/11DszoVkoE4-yHTutHpsTn1BPPZgLL3EfPgxrqmZiGq4/edit?usp=sharing
>
> You can find previous NCSG comments here:
> https://community.icann.org/m/mobile.action#page/40928144
>
> See below some best practices for the penholder:
>
>    - Provide the first draft on the mailing list in by day 21 of the
>    comment period
>    - Try to resolve the comments throughout the duration of comment
>    period
>    - Make sure that the commenter has seen how comment has been resolved
>    (contact them directly if necessary)
>
> Regards,
> Tomslin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210212/d0251449/attachment.htm>

From mesumbeslin at gmail.com  Sat Feb 13 00:07:09 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 13 Feb 2021 09:07:09 +1100
Subject: [NCSG-PC] Fwd: [council] Motion SubPro WG Final Report
In-Reply-To: <1F096BF4-D11F-475E-A387-FDC89608B99B@petillion.law>
References: <8C87F37C-C189-4E4F-A952-D484DDABD01B@petillion.law>
 <685B333D-8A37-436D-9F81-DDD028C1E58A@petillion.law>
 <1F096BF4-D11F-475E-A387-FDC89608B99B@petillion.law>
Message-ID: <CAM8DdeXanzbcuqQrmke=drvd1_W_jZ+MSJX5JK313jT=gJ5vaQ@mail.gmail.com>

Dear members,

The SubPro WG final report is up for vote in the next week's council
meeting and below and attached is the motion and approach that will be
taken by the council.

For those who've read the report or have followed the discussion, you'll
know that while most of the items deliberated by the WG had some form of
consensus, recommendations 35.2 and 35.4 only had strong support but
significant opposition.

Please let the PC know if you have any questions or concerns.

Cheers,
Tomslin


---------- Forwarded message ---------
From: Flip Petillion <fpetillion at petillion.law>
Date: Sat., 13 Feb. 2021, 03:40
Subject: [council] Motion SubPro WG Final Report
To: GNSO Council List <council at gnso.icann.org>




Dear Councilors,



Attached please find an amendment to the Motion of the Policy Development
Process on New gTLD Subsequent Procedures Final Report.



As the motion proposer and noting that there is no seconder as yet for the
motion, I deem those amendments to be friendly.



I attach a version with and a version without track changes.



Respectfully submitted,



Flip





Flip Petillion

fpetillion at petillion.law

+32484652653

www.petillion.law



<https://www.petillion.law/>



  Attorneys ? Advocaten ? Avocats





*From: *Flip Petillion <fpetillion at petillion.law>
*Date: *Friday, 5 February 2021 at 22:00
*To: *GNSO Council List <council at gnso.icann.org>
*Subject: *Motion SubPro WG Final Report



Dear Councilors,



Attached please find a Motion to Adoption of the Policy Development Process
on New gTLD Subsequent Procedures Final Report.



The motion is structured in such a way that the Council will be voting on
the Final Report as one package.  That said, because two of the hundreds of
Outputs had strong support but significant opposition, we have bifurcated
the resolved clauses to (a) recommend the implementation of those Outputs
that had either consensus or full consensus designations and (b) *consider* the
Outputs that have strong support but significant opposition as well as the
associated rationale in the report and the minority statements.



We believe that providing the entire report to the Board for its
consideration is important for the Board to understand how we arrived at
where we are and to give those very few areas without consensus some
context.  We are not stating that the Board MUST implement those elements
that did not have consensus, but we are giving them full information so
that either they can make a decision on how to proceed on those, or ask for
future work.



Although there are these couple Outputs that did not attain at least
Consensus, and one Output (Closed Generics) where there is consensus that
there is no agreement, we do not believe that a Council substantive
discussion on these issues or remanding it back to the Working Group, would
result in a different result.  There are good arguments on all sides of
these issues and the Working Group spent  a number of years trying to come
up with compromise proposals without success. These are areas where we
believe that guidance from the Board will be necessary to make further
progress on these issues.



Should you have questions, I am at your disposal for a call to discuss
these. I would appreciate it should you share your questions in the list
beforehand.



Respectfully submitted,



Flip



Flip Petillion

fpetillion at petillion.law

+32484652653

www.petillion.law



[image: id:image001.png at 01D3691D.DA7539C0] <https://www.petillion.law/>



  Attorneys ? Advocaten ? Avocats


_______________________________________________
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-pc/attachments/20210213/62390f96/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7396 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/62390f96/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7397 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/62390f96/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 21 02 12 SubPro Final Report Motion Friendly amendment NO TRACK CHANGES.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 52852 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/62390f96/attachment.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 21 02 12 SubPro Final Report Motion Friendly amendment.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 40297 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/62390f96/attachment-0001.docx>

From mesumbeslin at gmail.com  Sat Feb 13 02:26:25 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sat, 13 Feb 2021 11:26:25 +1100
Subject: [NCSG-PC] Fwd: Meeting Invite: GNSO Council/Board Discussion on the
 SSAD - 22 Feb 2021 - 19:00 UTC
In-Reply-To: <F44A101C-91E4-4481-AEA4-B97F86E4DB26@icann.org>
References: <F44A101C-91E4-4481-AEA4-B97F86E4DB26@icann.org>
Message-ID: <CAM8DdeUFE0kqYY5RQyBATu=Gj6=1OfNehENrgyvmgMhYrcMA7w@mail.gmail.com>

Dear members and PC,

I am forwarding this invite of a meeting between the Council and ICANN
board to discuss the Standardized System for Access/Disclosure (SSAD) for
22 February at 19:00 UTC / 11am PST.

The purpose of whish is "for the Board to explain how it envisions
conducting the ODP and to the extent possible, showing how the elements
flagged in the Council?s letter should more or less be captured already in
the Board?s concept of the Operational Design Phase (ODP)."

I understand observers are welcomed, so feel free to dial-in.

Cheers,
Tomslin


---------- Forwarded message ---------
From: Julie Bisland <julie.bisland at icann.org>
Date: Wed., 10 Feb. 2021, 03:53
Subject: Meeting Invite: GNSO Council/Board Discussion on the SSAD - 22 Feb
2021 - 19:00 UTC
To: ntfy-gnso-council at icann.org <ntfy-gnso-council at icann.org>
Cc: gnso-secs at icann.org <gnso-secs at icann.org>


Dear all,



Pursuant to the Doodle poll we have scheduled the GNSO Council / Board
discussion on the Standardized System for Access/Disclosure (SSAD) for 22
February at 19:00 UTC / 11am PST.



   - The purpose of the meeting is for the Board to explain how it
   envisions conducting the ODP and to the extent possible, showing how the
   elements flagged in the Council?s letter [gnso.icann.org]
   <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/field-file-attach/gnso-council-to-icann-board-22jan21-en.pdf__;!!PtGJab4!rWd3pPgwCu3CgOXjpsLjnubArudnusETEEo6cIsE8QCRBKFtSwaUw5-qeFCWv0RDOJLPbkd1nA$>
    should more or less be captured already in the Board?s concept of the
   Operational Design Phase (ODP).
   - The meeting is open to all Board and GNSO Council members; attendance
   is optional.



Connection details are provided below.



*Join Zoom Meeting*

https://icann.zoom.us/j/99226501836?pwd=NUwzN09VTVJFd3hIVC95M3VBTU1sdz09
[icann.zoom.us]
<https://urldefense.com/v3/__https:/icann.zoom.us/j/99226501836?pwd=NUwzN09VTVJFd3hIVC95M3VBTU1sdz09__;!!PtGJab4!rWd3pPgwCu3CgOXjpsLjnubArudnusETEEo6cIsE8QCRBKFtSwaUw5-qeFCWv0RDOJIKXWDAdw$>



Zoom Meeting ID: 992 2650 1836

Zoom Passcode: GNSO at 2021#



*Audio only:*

One tap mobile

+16699006833,,99226501836#,,,,*7835608785# US (San Jose)



Telephone Only: find your local number: https://icann.zoom.us/u/auBUdeXT0
[icann.zoom.us]
<https://urldefense.com/v3/__https:/icann.zoom.us/u/auBUdeXT0__;!!PtGJab4!rWd3pPgwCu3CgOXjpsLjnubArudnusETEEo6cIsE8QCRBKFtSwaUw5-qeFCWv0RDOJLsfhP4Gw$>

Meeting ID: 992 2650 1836

Telephone Only Passcode: 7835608785



Thank you,

Board Operations








_______________________________________________
Ntfy-gnso-council mailing list
Ntfy-gnso-council at icann.org
https://mm.icann.org/mailman/listinfo/ntfy-gnso-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-pc/attachments/20210213/828897e7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3668 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/828897e7/attachment.ics>
-------------- next part --------------
_______________________________________________
Gnso-chairs mailing list
Gnso-chairs at icann.org
https://mm.icann.org/mailman/listinfo/gnso-chairs
_______________________________________________
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://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!PtGJab4!rWd3pPgwCu3CgOXjpsLjnubArudnusETEEo6cIsE8QCRBKFtSwaUw5-qeFCWv0RDOJIyaB2Mow$ ) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!PtGJab4!rWd3pPgwCu3CgOXjpsLjnubArudnusETEEo6cIsE8QCRBKFtSwaUw5-qeFCWv0RDOJJrjVCDLw$ ). 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 --------------
A non-text attachment was scrubbed...
Name: GNSO Council-Board Discussion on the SSAD.ics
Type: application/ics
Size: 3751 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210213/828897e7/attachment.bin>

From mesumbeslin at gmail.com  Sat Feb 13 15:28:10 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 14 Feb 2021 00:28:10 +1100
Subject: [NCSG-PC] February Policy call proposed Agenda
Message-ID: <CAM8DdeXdx7WmgP=a7sp1MDmcCWZ-syMMw2b02-600LR_J3y89w@mail.gmail.com>

Dear PC,

Here below is the proposed agenda for our February meeting. Could you let
me know if you'd like an item added please?


   1. Introduction
   2. Updates from the GNSO Council Action Decision Radar (ADR)
   3. GNSO Council Call Preparation
      - Council agenda can be found here:
      https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+GNSO+Council+Agenda+18+February+2021
   4. Policy Updates
      - Transfer policy amendments
      - Current calls for volunteers (public comments)
   5. Any other business & Admin matters


Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210214/bc5602fd/attachment.htm>

From mesumbeslin at gmail.com  Sun Feb 14 14:31:10 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 14 Feb 2021 23:31:10 +1100
Subject: [NCSG-PC] Fwd: [gnso-igo-wt] IGO WT - Preparation for our first
 call on 22 Feb at 1600 UTC
In-Reply-To: <9D558E12-0FEB-4A7F-8921-40B3B59F4872@gmail.com>
References: <2EE5AADD-5A15-4755-9B02-D3BD4C1500FC@disspain.uk>
 <9D558E12-0FEB-4A7F-8921-40B3B59F4872@gmail.com>
Message-ID: <CAM8DdeXUqabsdGsMWuh+RpuSwk-u4r6c3+smXxgwtes28E=VVw@mail.gmail.com>

Dear PC,
FYI

Cheers,
Tomslin


---------- Forwarded message ---------
From: Kris Seeburn <seeburn.k at gmail.com>
Date: Sat., 13 Feb. 2021, 12:44
Subject: Re: [gnso-igo-wt] IGO WT - Preparation for our first call on 22
Feb at 1600 UTC
To: Chris Disspain <chris at disspain.uk>
Cc: <gnso-igo-wt at icann.org>, <gnso-secs at icann.org>


Hi Chris,

The document is fine and to me does not push for any clarifications. But in
hindsight I will say we need to do some real work for ICANN and our
community as well as the community at large.

I think it has become a time that things become not a jungle as it is but
clear stipulation of what we think and should help the community ar large.

I?ll explain them point wise and we will discuss same when we do
- we need to absolutely sign a working agreement with WIPO
- on the governmental grounds and for ICANN business model there is need
for more work to go in. Creating the ccNSO was a good thing as a derivative
and this could lead to a proper working of the ccNSO and the main 3
domains, org,net,com - I say this because we need to resonate and ensure
clarity in the domain name business such as asia, Africa etc., but I would
like to raise something important that I think should be reviewed. The
three original domains were past but we are now in a new world, I see too
many businesses being ripped apart an people make you payloads of money to
get your domain back.
- now the point I want to make is that we need to push the whole model in a
very different way, it does not mean if you have a .com or .org like what
happened to Red Cross and so many examples we can cite. I think the need to
make a different move altogether, meaning that we should push  any company
formally registered in a country to adopt and go the country code name
since Govt knows the validity of a company, their should be no open box to
just buy a .com etc unless it is a company registered internationally. And
also on WIPO list. I am not cutting loose the fact that those already
owning a .com .org etc., should be suffering a consequential issue but we
need to present a solid case for those to happen and to also ensure GAC is
happier and that makes a good business model case and the reason the ccNSO
was created and many countries are still fighting to make this work, reason
is simple the cost of a country level code depends has a cost variance from
country to country so the cheapest is a .com when we are looking to have a
site.
- Now another debate that has been going on very deeply is the Amazon
jungle and the Jeff bests Amazon company. Now for me there is a clear
distinction for Amazon.com the international company registered in the WIPO
books. Amazon as a river and community that falls between a few South
American countries could clearly adopt a .org or the creation of .South
America for example.
_ believe me it would make things easier to search for.....
- I know my colleagues will most likely not necessarily like what am
proposing but when things go south , a framework of mind change and model
is required to change. For example a company which is international can
have a .com if they prove that they are international , look at ebay for
example there is .com which is mostly the American business and then eBay
Also has the country level code registered. Why can?t Amazon have an
umbrella that is.com but business done or represented in America should be
.US for example.
- Now it is practice for any company duels registered to go to court but at
this stage we need to ensure that GAC walks the line in goof faith so that
there is a clear spot for businesses or personal ones. Some who do not get
.com ruminate but also adopt the .co domain.

I have loads to sat, but the way forward is a bit dodgy as the convincing
and clearing need to happen. A music band could adopt the .music for
example. The litmus test was put to test but it failed as people still say
if you are a company you buy a .com or .co and so on.

The idea is to create a path and clearly mitigated risk based issues that
would end up in spending more money that en#uring a clear path to move
forward and ensuring we put in place a mechanism that we need to rollback
what we have into a more clearer understanding of issues, like amazon the
company is a .com the Amazon the community in South America should be an
.org plus a .South America if needs be. We need to separate things now more
than ever. .gov for example is restricted to the US government. Or .edu etc
needs good and clear demarcation....

I also as I said it might and must be the most important thing is that we
have WIPO on with us on the work track as we need their take as well as
well as AFrican union, European Union , ASEAN  all these. Are key players
in making a clear path.


So just some stuff to digest on before the meetings take place, I see the
document also ask for clear defined timeliness etc., it is of course a
clear definition for all of us to be able to discuss but a unanimous
consent is necessary to make it work.

Things to put on the agenda, but talking of agenda, I see a document from
staff explaining the role of this WT but I would like to see clear agendas
for meetings and I hope to see one coming our way for the first meeting. I
am unfortunately methodical in how I see things.

KRIS for NCUC





On 11 Feb 2021, at 18:25, Chris Disspain <chris at disspain.uk> wrote:

?
Greetings,

Thank you all for your patience. We now have our first call scheduled for
22 February and, as promised, I attach a briefing paper with thanks to Mary
Wong and Steve Chan for all the work to put it together. I hope you find it
useful and please send any questions or clarification requests to this list.

You will see from the briefing paper that the scope and boundaries of the
work of this group is very limited and I would like to specifically draw
your attention to the paragraph at the top of page 3 which states:

"As such, the Work Track may wish to consider an early discussion as to the
likelihood of it reaching *consensus on an appropriate policy solution
within the above framework that is also likely to be acceptable to the GNSO
Council and the GAC, such as to be a solution that can be adopted by the
Board as being in the best interests of ICANN or the ICANN community* (as
required under the Bylaws)."

It would help in our work if each of us could consider possible policy
solutions that we think fit within the scope and boundaries provided by the
GNSO and bring those ideas to our first meeting. We can then list of those
possible solutions, add others that may arise in the group discussions and
then test them for group consensus and consider the likelihood of wider
acceptance. At this early brainstorm stage, there are no bad ideas, only
useful contributions to get our work started.

I am very much looking forward to working with you all and will see you on
zoom on the 22nd.



Cheers,

Chris Disspain
chris at disspain.uk

+44 7880 642456




_______________________________________________
gnso-igo-wt mailing list
gnso-igo-wt at icann.org
https://mm.icann.org/mailman/listinfo/gnso-igo-wt

_______________________________________________
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-pc/attachments/20210214/1b547f01/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.tiff
Type: image/tiff
Size: 12586 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210214/1b547f01/attachment.tiff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IGO Work Track Briefing Paper - DRAFT - 11 Feb 2021.pdf
Type: application/pdf
Size: 163516 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210214/1b547f01/attachment.pdf>

From tatiana.tropina at gmail.com  Sun Feb 14 15:28:43 2021
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Sun, 14 Feb 2021 14:28:43 +0100
Subject: [NCSG-PC] Fwd: [gnso-igo-wt] IGO WT - Preparation for our first
 call on 22 Feb at 1600 UTC
In-Reply-To: <CAM8DdeXUqabsdGsMWuh+RpuSwk-u4r6c3+smXxgwtes28E=VVw@mail.gmail.com>
References: <2EE5AADD-5A15-4755-9B02-D3BD4C1500FC@disspain.uk>
 <9D558E12-0FEB-4A7F-8921-40B3B59F4872@gmail.com>
 <CAM8DdeXUqabsdGsMWuh+RpuSwk-u4r6c3+smXxgwtes28E=VVw@mail.gmail.com>
Message-ID: <CADxLtgcEA4SC17sd=nuwyZ0+P0q9fTcWzBe6zU1JeY4nVfxFmw@mail.gmail.com>

Was this position agreed or discussed with NCUC/NCSG?!
Tanya

On Sun 14. Feb 2021 at 13:31, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Dear PC,
> FYI
>
> Cheers,
> Tomslin
>
>
> ---------- Forwarded message ---------
> From: Kris Seeburn <seeburn.k at gmail.com>
> Date: Sat., 13 Feb. 2021, 12:44
> Subject: Re: [gnso-igo-wt] IGO WT - Preparation for our first call on 22
> Feb at 1600 UTC
> To: Chris Disspain <chris at disspain.uk>
> Cc: <gnso-igo-wt at icann.org>, <gnso-secs at icann.org>
>
>
> Hi Chris,
>
> The document is fine and to me does not push for any clarifications. But
> in hindsight I will say we need to do some real work for ICANN and our
> community as well as the community at large.
>
> I think it has become a time that things become not a jungle as it is but
> clear stipulation of what we think and should help the community ar large.
>
> I?ll explain them point wise and we will discuss same when we do
> - we need to absolutely sign a working agreement with WIPO
> - on the governmental grounds and for ICANN business model there is need
> for more work to go in. Creating the ccNSO was a good thing as a derivative
> and this could lead to a proper working of the ccNSO and the main 3
> domains, org,net,com - I say this because we need to resonate and ensure
> clarity in the domain name business such as asia, Africa etc., but I would
> like to raise something important that I think should be reviewed. The
> three original domains were past but we are now in a new world, I see too
> many businesses being ripped apart an people make you payloads of money to
> get your domain back.
> - now the point I want to make is that we need to push the whole model in
> a very different way, it does not mean if you have a .com or .org like what
> happened to Red Cross and so many examples we can cite. I think the need to
> make a different move altogether, meaning that we should push  any company
> formally registered in a country to adopt and go the country code name
> since Govt knows the validity of a company, their should be no open box to
> just buy a .com etc unless it is a company registered internationally. And
> also on WIPO list. I am not cutting loose the fact that those already
> owning a .com .org etc., should be suffering a consequential issue but we
> need to present a solid case for those to happen and to also ensure GAC is
> happier and that makes a good business model case and the reason the ccNSO
> was created and many countries are still fighting to make this work, reason
> is simple the cost of a country level code depends has a cost variance from
> country to country so the cheapest is a .com when we are looking to have a
> site.
> - Now another debate that has been going on very deeply is the Amazon
> jungle and the Jeff bests Amazon company. Now for me there is a clear
> distinction for Amazon.com the international company registered in the WIPO
> books. Amazon as a river and community that falls between a few South
> American countries could clearly adopt a .org or the creation of .South
> America for example.
> _ believe me it would make things easier to search for.....
> - I know my colleagues will most likely not necessarily like what am
> proposing but when things go south , a framework of mind change and model
> is required to change. For example a company which is international can
> have a .com if they prove that they are international , look at ebay for
> example there is .com which is mostly the American business and then eBay
> Also has the country level code registered. Why can?t Amazon have an
> umbrella that is.com but business done or represented in America should
> be .US for example.
> - Now it is practice for any company duels registered to go to court but
> at this stage we need to ensure that GAC walks the line in goof faith so
> that there is a clear spot for businesses or personal ones. Some who do not
> get .com ruminate but also adopt the .co domain.
>
> I have loads to sat, but the way forward is a bit dodgy as the convincing
> and clearing need to happen. A music band could adopt the .music for
> example. The litmus test was put to test but it failed as people still say
> if you are a company you buy a .com or .co and so on.
>
> The idea is to create a path and clearly mitigated risk based issues that
> would end up in spending more money that en#uring a clear path to move
> forward and ensuring we put in place a mechanism that we need to rollback
> what we have into a more clearer understanding of issues, like amazon the
> company is a .com the Amazon the community in South America should be an
> .org plus a .South America if needs be. We need to separate things now more
> than ever. .gov for example is restricted to the US government. Or .edu etc
> needs good and clear demarcation....
>
> I also as I said it might and must be the most important thing is that we
> have WIPO on with us on the work track as we need their take as well as
> well as AFrican union, European Union , ASEAN  all these. Are key players
> in making a clear path.
>
>
> So just some stuff to digest on before the meetings take place, I see the
> document also ask for clear defined timeliness etc., it is of course a
> clear definition for all of us to be able to discuss but a unanimous
> consent is necessary to make it work.
>
> Things to put on the agenda, but talking of agenda, I see a document from
> staff explaining the role of this WT but I would like to see clear agendas
> for meetings and I hope to see one coming our way for the first meeting. I
> am unfortunately methodical in how I see things.
>
> KRIS for NCUC
>
>
>
>
>
> On 11 Feb 2021, at 18:25, Chris Disspain <chris at disspain.uk> wrote:
>
> ?
> Greetings,
>
> Thank you all for your patience. We now have our first call scheduled for
> 22 February and, as promised, I attach a briefing paper with thanks to Mary
> Wong and Steve Chan for all the work to put it together. I hope you find it
> useful and please send any questions or clarification requests to this list.
>
> You will see from the briefing paper that the scope and boundaries of the
> work of this group is very limited and I would like to specifically draw
> your attention to the paragraph at the top of page 3 which states:
>
> "As such, the Work Track may wish to consider an early discussion as to
> the likelihood of it reaching *consensus on an appropriate policy
> solution within the above framework that is also likely to be acceptable to
> the GNSO Council and the GAC, such as to be a solution that can be adopted
> by the Board as being in the best interests of ICANN or the ICANN community*
> (as required under the Bylaws)."
>
> It would help in our work if each of us could consider possible policy
> solutions that we think fit within the scope and boundaries provided by the
> GNSO and bring those ideas to our first meeting. We can then list of those
> possible solutions, add others that may arise in the group discussions and
> then test them for group consensus and consider the likelihood of wider
> acceptance. At this early brainstorm stage, there are no bad ideas, only
> useful contributions to get our work started.
>
> I am very much looking forward to working with you all and will see you on
> zoom on the 22nd.
>
>
>
> Cheers,
>
> Chris Disspain
> chris at disspain.uk
>
> +44 7880 642456
>
>
>
>
> _______________________________________________
> gnso-igo-wt mailing list
> gnso-igo-wt at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-igo-wt
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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/20210214/eb792140/attachment.htm>

From mesumbeslin at gmail.com  Sun Feb 14 21:37:02 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Mon, 15 Feb 2021 06:37:02 +1100
Subject: [NCSG-PC] Fwd: [gnso-igo-wt] IGO WT - Preparation for our first
 call on 22 Feb at 1600 UTC
In-Reply-To: <CADxLtgcEA4SC17sd=nuwyZ0+P0q9fTcWzBe6zU1JeY4nVfxFmw@mail.gmail.com>
References: <2EE5AADD-5A15-4755-9B02-D3BD4C1500FC@disspain.uk>
 <9D558E12-0FEB-4A7F-8921-40B3B59F4872@gmail.com>
 <CAM8DdeXUqabsdGsMWuh+RpuSwk-u4r6c3+smXxgwtes28E=VVw@mail.gmail.com>
 <CADxLtgcEA4SC17sd=nuwyZ0+P0q9fTcWzBe6zU1JeY4nVfxFmw@mail.gmail.com>
Message-ID: <CAM8DdeUt-ee8LpEgW6Lxt6r6mfxG_DWt0=+NfSM48-y0nQYxnw@mail.gmail.com>

Hi Tanya,

It wasn't agreed, which is why I am bringing it to the attention of the PC
so that we decide what to do with it.

Cheers,
Tomslin


On Mon., 15 Feb. 2021, 00:28 Tatiana Tropina, <tatiana.tropina at gmail.com>
wrote:

> Was this position agreed or discussed with NCUC/NCSG?!
> Tanya
>
> On Sun 14. Feb 2021 at 13:31, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
> wrote:
>
>> Dear PC,
>> FYI
>>
>> Cheers,
>> Tomslin
>>
>>
>> ---------- Forwarded message ---------
>> From: Kris Seeburn <seeburn.k at gmail.com>
>> Date: Sat., 13 Feb. 2021, 12:44
>> Subject: Re: [gnso-igo-wt] IGO WT - Preparation for our first call on 22
>> Feb at 1600 UTC
>> To: Chris Disspain <chris at disspain.uk>
>> Cc: <gnso-igo-wt at icann.org>, <gnso-secs at icann.org>
>>
>>
>> Hi Chris,
>>
>> The document is fine and to me does not push for any clarifications. But
>> in hindsight I will say we need to do some real work for ICANN and our
>> community as well as the community at large.
>>
>> I think it has become a time that things become not a jungle as it is but
>> clear stipulation of what we think and should help the community ar large.
>>
>> I?ll explain them point wise and we will discuss same when we do
>> - we need to absolutely sign a working agreement with WIPO
>> - on the governmental grounds and for ICANN business model there is need
>> for more work to go in. Creating the ccNSO was a good thing as a derivative
>> and this could lead to a proper working of the ccNSO and the main 3
>> domains, org,net,com - I say this because we need to resonate and ensure
>> clarity in the domain name business such as asia, Africa etc., but I would
>> like to raise something important that I think should be reviewed. The
>> three original domains were past but we are now in a new world, I see too
>> many businesses being ripped apart an people make you payloads of money to
>> get your domain back.
>> - now the point I want to make is that we need to push the whole model in
>> a very different way, it does not mean if you have a .com or .org like what
>> happened to Red Cross and so many examples we can cite. I think the need to
>> make a different move altogether, meaning that we should push  any company
>> formally registered in a country to adopt and go the country code name
>> since Govt knows the validity of a company, their should be no open box to
>> just buy a .com etc unless it is a company registered internationally. And
>> also on WIPO list. I am not cutting loose the fact that those already
>> owning a .com .org etc., should be suffering a consequential issue but we
>> need to present a solid case for those to happen and to also ensure GAC is
>> happier and that makes a good business model case and the reason the ccNSO
>> was created and many countries are still fighting to make this work, reason
>> is simple the cost of a country level code depends has a cost variance from
>> country to country so the cheapest is a .com when we are looking to have a
>> site.
>> - Now another debate that has been going on very deeply is the Amazon
>> jungle and the Jeff bests Amazon company. Now for me there is a clear
>> distinction for Amazon.com the international company registered in the WIPO
>> books. Amazon as a river and community that falls between a few South
>> American countries could clearly adopt a .org or the creation of .South
>> America for example.
>> _ believe me it would make things easier to search for.....
>> - I know my colleagues will most likely not necessarily like what am
>> proposing but when things go south , a framework of mind change and model
>> is required to change. For example a company which is international can
>> have a .com if they prove that they are international , look at ebay for
>> example there is .com which is mostly the American business and then eBay
>> Also has the country level code registered. Why can?t Amazon have an
>> umbrella that is.com but business done or represented in America should
>> be .US for example.
>> - Now it is practice for any company duels registered to go to court but
>> at this stage we need to ensure that GAC walks the line in goof faith so
>> that there is a clear spot for businesses or personal ones. Some who do not
>> get .com ruminate but also adopt the .co domain.
>>
>> I have loads to sat, but the way forward is a bit dodgy as the convincing
>> and clearing need to happen. A music band could adopt the .music for
>> example. The litmus test was put to test but it failed as people still say
>> if you are a company you buy a .com or .co and so on.
>>
>> The idea is to create a path and clearly mitigated risk based issues that
>> would end up in spending more money that en#uring a clear path to move
>> forward and ensuring we put in place a mechanism that we need to rollback
>> what we have into a more clearer understanding of issues, like amazon the
>> company is a .com the Amazon the community in South America should be an
>> .org plus a .South America if needs be. We need to separate things now more
>> than ever. .gov for example is restricted to the US government. Or .edu etc
>> needs good and clear demarcation....
>>
>> I also as I said it might and must be the most important thing is that we
>> have WIPO on with us on the work track as we need their take as well as
>> well as AFrican union, European Union , ASEAN  all these. Are key players
>> in making a clear path.
>>
>>
>> So just some stuff to digest on before the meetings take place, I see the
>> document also ask for clear defined timeliness etc., it is of course a
>> clear definition for all of us to be able to discuss but a unanimous
>> consent is necessary to make it work.
>>
>> Things to put on the agenda, but talking of agenda, I see a document from
>> staff explaining the role of this WT but I would like to see clear agendas
>> for meetings and I hope to see one coming our way for the first meeting. I
>> am unfortunately methodical in how I see things.
>>
>> KRIS for NCUC
>>
>>
>>
>>
>>
>> On 11 Feb 2021, at 18:25, Chris Disspain <chris at disspain.uk> wrote:
>>
>> ?
>> Greetings,
>>
>> Thank you all for your patience. We now have our first call scheduled for
>> 22 February and, as promised, I attach a briefing paper with thanks to Mary
>> Wong and Steve Chan for all the work to put it together. I hope you find it
>> useful and please send any questions or clarification requests to this list.
>>
>> You will see from the briefing paper that the scope and boundaries of the
>> work of this group is very limited and I would like to specifically draw
>> your attention to the paragraph at the top of page 3 which states:
>>
>> "As such, the Work Track may wish to consider an early discussion as to
>> the likelihood of it reaching *consensus on an appropriate policy
>> solution within the above framework that is also likely to be acceptable to
>> the GNSO Council and the GAC, such as to be a solution that can be adopted
>> by the Board as being in the best interests of ICANN or the ICANN community*
>> (as required under the Bylaws)."
>>
>> It would help in our work if each of us could consider possible policy
>> solutions that we think fit within the scope and boundaries provided by the
>> GNSO and bring those ideas to our first meeting. We can then list of those
>> possible solutions, add others that may arise in the group discussions and
>> then test them for group consensus and consider the likelihood of wider
>> acceptance. At this early brainstorm stage, there are no bad ideas, only
>> useful contributions to get our work started.
>>
>> I am very much looking forward to working with you all and will see you
>> on zoom on the 22nd.
>>
>>
>>
>> Cheers,
>>
>> Chris Disspain
>> chris at disspain.uk
>>
>> +44 7880 642456
>>
>>
>>
>>
>> _______________________________________________
>> gnso-igo-wt mailing list
>> gnso-igo-wt at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-igo-wt
>>
>> _______________________________________________
>> 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.
>>
>> _______________________________________________
>> 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/20210215/4ca29f00/attachment.htm>

From tatiana.tropina at gmail.com  Sun Feb 14 21:53:06 2021
From: tatiana.tropina at gmail.com (Tatiana Tropina)
Date: Sun, 14 Feb 2021 20:53:06 +0100
Subject: [NCSG-PC] Fwd: [gnso-igo-wt] IGO WT - Preparation for our first
 call on 22 Feb at 1600 UTC
In-Reply-To: <CAM8DdeUt-ee8LpEgW6Lxt6r6mfxG_DWt0=+NfSM48-y0nQYxnw@mail.gmail.com>
References: <2EE5AADD-5A15-4755-9B02-D3BD4C1500FC@disspain.uk>
 <9D558E12-0FEB-4A7F-8921-40B3B59F4872@gmail.com>
 <CAM8DdeXUqabsdGsMWuh+RpuSwk-u4r6c3+smXxgwtes28E=VVw@mail.gmail.com>
 <CADxLtgcEA4SC17sd=nuwyZ0+P0q9fTcWzBe6zU1JeY4nVfxFmw@mail.gmail.com>
 <CAM8DdeUt-ee8LpEgW6Lxt6r6mfxG_DWt0=+NfSM48-y0nQYxnw@mail.gmail.com>
Message-ID: <CADxLtgerN5V-yDjgxvLqn=pH1sNbxzo25DFThWKEEpGdQu5oJw@mail.gmail.com>

Thanks Tomslin. I asked just in case, it would have been surprising if this
was agreed upon.
As someone who was against adding people with no experience related to IGO
to this work track just for sake of encouraging volunteers, I want to say
straight at the beginning that I?d like the PC to reflect on this for the
future in addition to doing something with this particular email.

Cheers
Tanya

On Sun 14. Feb 2021 at 20:37, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> Hi Tanya,
>
> It wasn't agreed, which is why I am bringing it to the attention of the PC
> so that we decide what to do with it.
>
> Cheers,
> Tomslin
>
>
> On Mon., 15 Feb. 2021, 00:28 Tatiana Tropina, <tatiana.tropina at gmail.com>
> wrote:
>
>> Was this position agreed or discussed with NCUC/NCSG?!
>> Tanya
>>
>> On Sun 14. Feb 2021 at 13:31, Tomslin Samme-Nlar <mesumbeslin at gmail.com>
>> wrote:
>>
>>> Dear PC,
>>> FYI
>>>
>>> Cheers,
>>> Tomslin
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Kris Seeburn <seeburn.k at gmail.com>
>>> Date: Sat., 13 Feb. 2021, 12:44
>>> Subject: Re: [gnso-igo-wt] IGO WT - Preparation for our first call on 22
>>> Feb at 1600 UTC
>>> To: Chris Disspain <chris at disspain.uk>
>>> Cc: <gnso-igo-wt at icann.org>, <gnso-secs at icann.org>
>>>
>>>
>>> Hi Chris,
>>>
>>> The document is fine and to me does not push for any clarifications. But
>>> in hindsight I will say we need to do some real work for ICANN and our
>>> community as well as the community at large.
>>>
>>> I think it has become a time that things become not a jungle as it is
>>> but clear stipulation of what we think and should help the community ar
>>> large.
>>>
>>> I?ll explain them point wise and we will discuss same when we do
>>> - we need to absolutely sign a working agreement with WIPO
>>> - on the governmental grounds and for ICANN business model there is need
>>> for more work to go in. Creating the ccNSO was a good thing as a derivative
>>> and this could lead to a proper working of the ccNSO and the main 3
>>> domains, org,net,com - I say this because we need to resonate and ensure
>>> clarity in the domain name business such as asia, Africa etc., but I would
>>> like to raise something important that I think should be reviewed. The
>>> three original domains were past but we are now in a new world, I see too
>>> many businesses being ripped apart an people make you payloads of money to
>>> get your domain back.
>>> - now the point I want to make is that we need to push the whole model
>>> in a very different way, it does not mean if you have a .com or .org like
>>> what happened to Red Cross and so many examples we can cite. I think the
>>> need to make a different move altogether, meaning that we should push  any
>>> company formally registered in a country to adopt and go the country code
>>> name since Govt knows the validity of a company, their should be no open
>>> box to just buy a .com etc unless it is a company registered
>>> internationally. And also on WIPO list. I am not cutting loose the fact
>>> that those already owning a .com .org etc., should be suffering a
>>> consequential issue but we need to present a solid case for those to happen
>>> and to also ensure GAC is happier and that makes a good business model case
>>> and the reason the ccNSO was created and many countries are still fighting
>>> to make this work, reason is simple the cost of a country level code
>>> depends has a cost variance from country to country so the cheapest is a
>>> .com when we are looking to have a site.
>>> - Now another debate that has been going on very deeply is the Amazon
>>> jungle and the Jeff bests Amazon company. Now for me there is a clear
>>> distinction for Amazon.com the international company registered in the WIPO
>>> books. Amazon as a river and community that falls between a few South
>>> American countries could clearly adopt a .org or the creation of .South
>>> America for example.
>>> _ believe me it would make things easier to search for.....
>>> - I know my colleagues will most likely not necessarily like what am
>>> proposing but when things go south , a framework of mind change and model
>>> is required to change. For example a company which is international can
>>> have a .com if they prove that they are international , look at ebay for
>>> example there is .com which is mostly the American business and then eBay
>>> Also has the country level code registered. Why can?t Amazon have an
>>> umbrella that is.com but business done or represented in America should
>>> be .US for example.
>>> - Now it is practice for any company duels registered to go to court but
>>> at this stage we need to ensure that GAC walks the line in goof faith so
>>> that there is a clear spot for businesses or personal ones. Some who do not
>>> get .com ruminate but also adopt the .co domain.
>>>
>>> I have loads to sat, but the way forward is a bit dodgy as the
>>> convincing and clearing need to happen. A music band could adopt the .music
>>> for example. The litmus test was put to test but it failed as people still
>>> say if you are a company you buy a .com or .co and so on.
>>>
>>> The idea is to create a path and clearly mitigated risk based issues
>>> that would end up in spending more money that en#uring a clear path to move
>>> forward and ensuring we put in place a mechanism that we need to rollback
>>> what we have into a more clearer understanding of issues, like amazon the
>>> company is a .com the Amazon the community in South America should be an
>>> .org plus a .South America if needs be. We need to separate things now more
>>> than ever. .gov for example is restricted to the US government. Or .edu etc
>>> needs good and clear demarcation....
>>>
>>> I also as I said it might and must be the most important thing is that
>>> we have WIPO on with us on the work track as we need their take as well as
>>> well as AFrican union, European Union , ASEAN  all these. Are key players
>>> in making a clear path.
>>>
>>>
>>> So just some stuff to digest on before the meetings take place, I see
>>> the document also ask for clear defined timeliness etc., it is of course a
>>> clear definition for all of us to be able to discuss but a unanimous
>>> consent is necessary to make it work.
>>>
>>> Things to put on the agenda, but talking of agenda, I see a document
>>> from staff explaining the role of this WT but I would like to see clear
>>> agendas for meetings and I hope to see one coming our way for the first
>>> meeting. I am unfortunately methodical in how I see things.
>>>
>>> KRIS for NCUC
>>>
>>>
>>>
>>>
>>>
>>> On 11 Feb 2021, at 18:25, Chris Disspain <chris at disspain.uk> wrote:
>>>
>>> ?
>>> Greetings,
>>>
>>> Thank you all for your patience. We now have our first call scheduled
>>> for 22 February and, as promised, I attach a briefing paper with thanks to
>>> Mary Wong and Steve Chan for all the work to put it together. I hope you
>>> find it useful and please send any questions or clarification requests to
>>> this list.
>>>
>>> You will see from the briefing paper that the scope and boundaries of
>>> the work of this group is very limited and I would like to specifically
>>> draw your attention to the paragraph at the top of page 3 which states:
>>>
>>> "As such, the Work Track may wish to consider an early discussion as to
>>> the likelihood of it reaching *consensus on an appropriate policy
>>> solution within the above framework that is also likely to be acceptable to
>>> the GNSO Council and the GAC, such as to be a solution that can be adopted
>>> by the Board as being in the best interests of ICANN or the ICANN community*
>>> (as required under the Bylaws)."
>>>
>>> It would help in our work if each of us could consider possible policy
>>> solutions that we think fit within the scope and boundaries provided by the
>>> GNSO and bring those ideas to our first meeting. We can then list of those
>>> possible solutions, add others that may arise in the group discussions and
>>> then test them for group consensus and consider the likelihood of wider
>>> acceptance. At this early brainstorm stage, there are no bad ideas, only
>>> useful contributions to get our work started.
>>>
>>> I am very much looking forward to working with you all and will see you
>>> on zoom on the 22nd.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Chris Disspain
>>> chris at disspain.uk
>>>
>>> +44 7880 642456
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> gnso-igo-wt mailing list
>>> gnso-igo-wt at icann.org
>>> https://mm.icann.org/mailman/listinfo/gnso-igo-wt
>>>
>>> _______________________________________________
>>> 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.
>>>
>>> _______________________________________________
>>> 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/20210214/d9799999/attachment.htm>

From PolicyCalendar at icann.org  Mon Feb 15 17:08:55 2021
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Mon, 15 Feb 2021 15:08:55 +0000
Subject: [NCSG-PC] REMINDER: NCSG Monthly Policy call | 16 February | 11:30
 UTC
Message-ID: <55015bf4b7cd4990b39bd288879cd51d@icann.org>

Please join the NCSG Monthly Policy call on Tuesday, 16 February 2021 at 11:30 UTC.&nbsp; Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG+Policy+Call&iso=20210216T1130&p1=1440&ah=1&am=30>.



Join Zoom Meeting:&nbsp; https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09



Meeting ID: 988 7818 9584

Passcode: i!y7.qx+11



One tap mobile

+16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)

+12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)





PHONE ONLY DETAILS:

Find your local number: https://icann.zoom.us/u/ayKmeftWg

Meeting ID: 988 7818 9584

Phone only Passcode: 7740925615


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210215/22c3d798/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2489 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210215/22c3d798/attachment.ics>

From brenda.brewer at icann.org  Mon Feb 15 17:21:07 2021
From: brenda.brewer at icann.org (Brenda Brewer)
Date: Mon, 15 Feb 2021 15:21:07 +0000
Subject: [NCSG-PC] REMINDER: NCSG Monthly Policy call | 16 February | 11:30
 UTC
Message-ID: <62B3EF66-CD42-484C-B26E-D3EBE3ED9712@icann.org>

Good day all!

Please find below the call details for NCSG Monthly Policy call on Tuesday, 16 February @ 11:30 UTC for 90 minutes.
Also note, calendar invites have been sent and .ics is attached.

Kind regards,
Brenda & Maryam
  _____________________________________________

Join Zoom Meeting:  https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09__;!!PtGJab4!rPiXg0kaXKwasfz7peL05WmV9GH8oZkhQy-7TKy4yjYED8i1r1v7vx1fVQuMUq-FlN9uBzH3$>

Meeting ID: 988 7818 9584
Passcode: i!y7.qx+11

One tap mobile
+16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)
+12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)

PHONE ONLY DETAILS:
Find your local number: https://icann.zoom.us/u/ayKmeftWg
Meeting ID: 988 7818 9584
Phone only Passcode: 7740925615


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210215/924e8594/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: REMINDER-  NCSG Monthly Policy call  16 February  11-30 UTC.ics
Type: text/calendar
Size: 2492 bytes
Desc: REMINDER-  NCSG Monthly Policy call  16 February  11-30 UTC.ics
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210215/924e8594/attachment.ics>

From PolicyCalendar at icann.org  Tue Feb 16 13:09:40 2021
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Tue, 16 Feb 2021 11:09:40 +0000
Subject: [NCSG-PC] REMINDER: NCSG Monthly Policy call | 16 February | 11:30
 UTC
Message-ID: <d037a82f0c734adbb84f7968f8e88d31@icann.org>

Reminder, this call starts in 20 minutes.&nbsp; Thank you!



Please join the NCSG Monthly Policy call on Tuesday, 16 February 2021 at 11:30 UTC.&nbsp; Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG+Policy+Call&iso=20210216T1130&p1=1440&ah=1&am=30>.



Join Zoom Meeting:&nbsp; https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09



Meeting ID: 988 7818 9584

Passcode: i!y7.qx+11



One tap mobile

+16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)

+12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)





PHONE ONLY DETAILS:

Find your local number: https://icann.zoom.us/u/ayKmeftWg

Meeting ID: 988 7818 9584

Phone only Passcode: 7740925615


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/9e3c27d0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2560 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/9e3c27d0/attachment.ics>

From mesumbeslin at gmail.com  Tue Feb 16 13:21:37 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 16 Feb 2021 22:21:37 +1100
Subject: [NCSG-PC] [Public Comment] Call for volunteers - EPDP Phase 2
 Policy Recommendations for Board Consideration (SSAD)
Message-ID: <CAM8DdeW3kB5jC+mYJ6st8D+ntfG8V8dEdbViPqEcO5y-DHz7pw@mail.gmail.com>

 Dear members,

A public comment period is now open for the EPDP Phase 2 Policy
Recommendations for Board Consideration. In particular, this one seeks
input on a set of final recommendations that relate to a proposed System
for Standardized Access/Disclosure to non-public registration information
("SSAD").
You can read more her:
https://www.icann.org/public-comments/epdp-2-policy-recs-board-2021-02-08-en

Due on 30 March 2021, the Policy Committee is calling for volunteers to
draft an NCSG comment. Please let me know off-list if you'd like to
volunteer for the comment drafting. It'll be nice to have more than one
volunteers, including new-commers who can use this as an opportunity to
learn and be familiar with policy work.

A draft Google doc for the comment can be found here:
https://docs.google.com/document/d/1QAUa2nT2a9YGGhK0r603EJCXfa58elXd9kPh3DH0DrU/edit

You can find previous NCSG comments here:
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2021

See below some best practices for the penholder:

   - Provide the first draft on the mailing list in by day 21 of the
   comment period
   - Try to resolve the comments throughout the duration of comment period
   - Make sure that the commenter has seen how comment has been resolved
   (contact them directly if necessary)

Regards,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/8fd4dc03/attachment.htm>

From brenda.brewer at icann.org  Tue Feb 16 13:22:02 2021
From: brenda.brewer at icann.org (Brenda Brewer)
Date: Tue, 16 Feb 2021 11:22:02 +0000
Subject: [NCSG-PC] FW: REMINDER: NCSG Monthly Policy call | 16 February |
 11:30 UTC
In-Reply-To: <62B3EF66-CD42-484C-B26E-D3EBE3ED9712@icann.org>
References: <62B3EF66-CD42-484C-B26E-D3EBE3ED9712@icann.org>
Message-ID: <7B16F824-E34C-4A6C-8DDE-8819CC505A95@icann.org>

Kind reminder of call starting in 10 minutes.  Join details are below and also attached.  See you soon!
Thank you!
Brenda & Maryam

From: Brenda Brewer <brenda.brewer at icann.org>
Date: Monday, February 15, 2021 at 9:21 AM
To: NCSG List <NCSG-DISCUSS at LISTSERV.SYR.EDU>, "ncsg-pc at lists.ncsg.is" <ncsg-pc at lists.ncsg.is>
Cc: Brenda Brewer <brenda.brewer at icann.org>, Maryam Bakoshi <maryam.bakoshi at icann.org>, Carlos Reyes <carlos.reyes at icann.org>
Subject: REMINDER: NCSG Monthly Policy call | 16 February | 11:30 UTC

Good day all!

Please find below the call details for NCSG Monthly Policy call on Tuesday, 16 February @ 11:30 UTC for 90 minutes.
Also note, calendar invites have been sent and .ics is attached.

Kind regards,
Brenda & Maryam
  _____________________________________________

Join Zoom Meeting:  https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09__;!!PtGJab4!rPiXg0kaXKwasfz7peL05WmV9GH8oZkhQy-7TKy4yjYED8i1r1v7vx1fVQuMUq-FlN9uBzH3$>

Meeting ID: 988 7818 9584
Passcode: i!y7.qx+11

One tap mobile
+16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)
+12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)

PHONE ONLY DETAILS:
Find your local number: https://icann.zoom.us/u/ayKmeftWg
Meeting ID: 988 7818 9584
Phone only Passcode: 7740925615


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/a7bc219c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: REMINDER-  NCSG Monthly Policy call  16 February  11-30 UTC.ics
Type: text/calendar
Size: 2492 bytes
Desc: REMINDER-  NCSG Monthly Policy call  16 February  11-30 UTC.ics
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/a7bc219c/attachment.ics>

From mesumbeslin at gmail.com  Tue Feb 16 14:58:41 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Tue, 16 Feb 2021 23:58:41 +1100
Subject: [NCSG-PC] [Public Comment] Call for volunteers - Second Security,
 Stability, and Resiliency (SSR2) Review Team Final Report
Message-ID: <CAM8DdeXsZAxMugAUBcNuoecumC2=C=CHkjVhoWW287c2SKd+gg@mail.gmail.com>

 Dear members,

The public comment period on the *Second Security, Stability, and
Resiliency (SSR2) Review Team Final Report* is in progress.

The Policy Committee is calling for volunteers to draft an NCSG comment for
this proceeding which is due on *9 Mar 2021* . Please let me know off-list
if you'd like to volunteer for the comment drafting. It'll be nice to have
more than one volunteers, including new-commers who can use this as an
opportunity to learn and be familiar with policy work.

More information about the SSR2 Review Team Final Report can be found here
: https://www.icann.org/public-comments/ssr2-final-report-2021-01-28-en

A draft Google doc for the comment can be found here:
https://docs.google.com/document/d/1Hn_yguSzCZK9cnsS_J5XF3Atg6XpiYmZlYy_Nbc7K_I/edit

You can find previous NCSG comments here:
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2021

See below some best practices for the penholder:

   - Provide the first draft on the mailing list in by day 21 of the
   comment period
   - Try to resolve the comments throughout the duration of comment period
   - Make sure that the commenter has seen how comment has been resolved
   (contact them directly if necessary)

Regards,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210216/57c3e7e8/attachment.htm>

From mesumbeslin at gmail.com  Wed Feb 17 12:19:29 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 17 Feb 2021 21:19:29 +1100
Subject: [NCSG-PC] [Public Comment] Call for volunteers - Additional
 Reference Label Generation Rulesets for the Second Level
Message-ID: <CAM8DdeU8C-e1E90oUK1vHqzj7nSiNZZd1-rx7pwQMPu9YShyEA@mail.gmail.com>

 Dear members,

The public comment proceeding for *Additional Reference Label Generation
Rulesets (LGRs) for the Second Level* is currently in progress and the
Policy Committee would like to call for volunteers to draft an NCSG comment
for this.

The comment period ends on *11* *Mar 2021*.

Please let me know off-list if you'd like to volunteer for the comment
drafting. It'll be nice to have more than one volunteers, including
new-commers who can use this as an opportunity to learn and be familiar
with policy work.

More information can be found here :
https://www.icann.org/public-comments/lgr-additional-reference-2021-01-28-en

A draft Google doc for the comment can be found here:
https://docs.google.com/document/d/1bhiYGs_MGHNGkaCfaItvY3tpVMWYL5-U7_oS72UD8x4/edit

You can find previous NCSG comments here:
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2021

See below some best practices for the penholder:

   - Provide the first draft on the mailing list in by day 21 of the
   comment period
   - Try to resolve the comments throughout the duration of comment period
   - Make sure that the commenter has seen how comment has been resolved
   (contact them directly if necessary)


Regards,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210217/11b7a620/attachment.htm>

From mesumbeslin at gmail.com  Wed Feb 17 12:24:44 2021
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 17 Feb 2021 21:24:44 +1100
Subject: [NCSG-PC] [Public Comment] Call for volunteers - Recommendation for
 an IANA Naming Function Contract Amendment
Message-ID: <CAM8DdeVD=i70RKxjxBcBZ6w_3Qm7He+2PF=G_GTi9KX46P5iLQ@mail.gmail.com>

 Dear members,

The Policy Committee would like to call for volunteers to draft an NCSG
comment for *IANA Naming Function Review: Recommendation for an IANA Naming
Function Contract Amendment*.

The comment period ends on *22* *Mar 2021*.

Please let me know off-list if you'd like to volunteer for the comment
drafting. It'll be nice to have more than one volunteers, including
new-commers who can use this as an opportunity to learn and be familiar
with policy work.

More information on the public comment can be found here :
https://www.icann.org/public-comments/iana-naming-function-contract-amend-2021-02-10-en

A draft Google doc for the comment can be found here:
https://docs.google.com/document/d/1xY_0i6dR0L90JDqZ69BKgsGrt9m1WPlYdeDl8b8d1a0/edit

You can find previous NCSG comments here:
https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2021

See below some best practices for the penholder:

   - Provide the first draft on the mailing list in by day 21 of the
   comment period
   - Try to resolve the comments throughout the duration of comment period
   - Make sure that the commenter has seen how comment has been resolved
   (contact them directly if necessary)


Regards,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210217/b627775b/attachment.htm>

From bruna.mrtns at gmail.com  Wed Feb 24 07:05:24 2021
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Wed, 24 Feb 2021 02:05:24 -0300
Subject: [NCSG-PC] NCSG Board Meeting
Message-ID: <CADAEEV34V5ROPnGND_wKGFNb=Xk2Bwt5a9-in0mdi7OQ7gyu9g@mail.gmail.com>

Dear NCSG PC and EC,

I need to provide our talking points for the NCSG meeting with the ICANN
Board by Feb. 26th, the latest. On that note, I would like to ask if any of
you would like to suggest and/or lead any of these discussions.

For the ones not familiar with our Joint meeting with the Board at ICANN
meetings, this is a 1h meeting where both the NCSG and ICANN Board will
prepare their talking points for each other. We normally go with 2 to 3
talking points and its also nice to see our community leaders leading the
discussions, so feel free to send your suggestions here and we can start
working on the discussion agenda.

For my 1:1 meeting with the CEO that happened this week I chose to ask the
following questions, but I would like to hear from you whether you think
its good to repeat them:

*SSAD and Content Moderation*


   - *On a recent communication that was sent to the Board and to you, we
   asked a few questions regarding an "ICANN Org Comments on the
   Recommendations 01/2020 on Measures That Supplement Transfer Tools to
   Ensure Compliance With the EU Level of Protection of Personal Data". NCSGs
   letter was seeking clarification about an specific part of the statement
   that highlighted that SSAD was "instrumental for stopping and preventing
   the dissemination of illegal content and in order to avoid related societal
   harms". On that note, I would like to ask you how the development of a new
   System for Standardized Access/Disclosure falls within the realm of
   instruments for preventing the dissemination of illegal content ?*
   - *When the document mentions the prevention of the dissemination of
   illegal content and societal harm, does it relate to factors other than the
   access to information object of legitimate requests by legal authorities
   and/or related to investigations ? *

*DNS Abuse and the DNS Security Facilitation Initiative Technical Study
Group*


   - *Do you believe ICANN is not working toward security and stability and
   fighting with abuse as much as its mission allows? Why do you think that ?*
   - *NCSG would also like to know more about the DNS Security Facilitation
   Initiative Technical Study Group. Where does this technical study group
   fall within ICANNs strategy for dealing with DNS abuse? *



Looking forward to hearing back from you!

Best,

-- 
*Bruna Martins dos Santos *

Skype ID: bruna.martinsantos
@boomartins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210224/65b5a421/attachment.htm>

From PolicyCalendar at icann.org  Wed Feb 24 22:46:06 2021
From: PolicyCalendar at icann.org (ICANN Policy Calendar)
Date: Wed, 24 Feb 2021 20:46:06 +0000
Subject: [NCSG-PC] NCSG Monthly Policy call | 16 March | 11:30 UTC
Message-ID: <953bf3d7145743248ae1538008021550@icann.org>

Please join the NCSG Monthly Policy call on Tuesday, 16 March 2021 at 11:30 UTC.&nbsp; Additional time zone support here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NCSG+Policy+Call&iso=20210316T1130&p1=1440&ah=1&am=30>.



Join Zoom Meeting:&nbsp; https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09



Meeting ID: 988 7818 9584

Passcode: i!y7.qx+11



One tap mobile

+16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose)

+12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma)





PHONE ONLY DETAILS:

Find your local number: https://icann.zoom.us/u/ayKmeftWg

Meeting ID: 988 7818 9584

Phone only Passcode: 7740925615




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210224/1cce93c6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 2473 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20210224/1cce93c6/attachment.ics>