<div dir="ltr">Thomas, Rafik and Renata,<div><br></div><div>As I prep up for this, I would just like to congratulate all for this initiative and for combining in such a timely manner the work of the onboarding materials with the overall purpose of learning how to effectively engage in drafting a public comment. I'm sure it fills an important knowledge gap within the community.</div><div>Thanks for organizing this list and look forward to our draft.</div><div><br></div><div>Cheers!</div><div><br></div><div>Louise</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font color="#444444">Louise Marie Hurel</font></div><p style="margin:0cm 0cm 0.0001pt"><font color="#444444" face="Arial, sans-serif"><span style="font-size:11px">Cybersecurity Project Coordinator | Igarapé Institute</span></font></p><p style="margin:0cm 0cm 0.0001pt"><font face="Arial, sans-serif" color="#444444"><span style="font-size:11px">London School of Economics (LSE) Media and Communications (Data and Society)</span></font></p><div><font size="1" color="#444444">Skype: louise.dias</font></div><div><font size="1" color="#444444">+44 (0) 7468 906327</font></div><div><span style="font-size:x-small"><font color="#0000ff"><u><a href="mailto:l.h.dias@lse.ac.uk" target="_blank">l.h.dias@lse.ac.uk</a> </u></font></span><font size="1" color="#444444"><br></font></div><div><font size="1" color="#444444"><a href="mailto:louise.marie.hsd@gmail.com" target="_blank">louise.marie.hsd@gmail.com</a> </font></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2017-11-20 9:46 GMT+05:30 Dina Solveig Jalkanen <span dir="ltr"><<a href="mailto:icann@thomascovenant.org" target="_blank">icann@thomascovenant.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear fellow constituents,<br>
<br>
warmly welcome to the Comment Drafters group. This process will move on<br>
with down-to-earth guidance by me and support from Rafik (NCSG Policy<br>
Committee Chair), Renata (NCUC chair) and other experienced NCUC members.<br>
<br>
1. Introduction<br>
<br>
Why write a Public Comment? What is it? In short, it is a document<br>
commenting on an ICANN issue, a published report, proposed action.<br>
Quite often behind such a report is a working group that has put<br>
a lot of time and effort into addressing a particular issue, and<br>
is accepting feedback.<br>
<br>
I think writing a comment is a good way to participate in policy<br>
making process.<br>
<br>
Are the comments actually useful? Mostly yes, example in message below.<br>
This is not always the case. As I see it, having a track of proposed<br>
change is a good start on some subjects.<br>
<br>
Good news, everyone: you are not working on comments alone. NCUC<br>
comments I have read are well-written, produced by friendly and<br>
supportive collaboration plus NCUC readily gives advice.<br>
<br>
Take note of:<br>
<br>
"In order for the comment to be endorsed as the position<br>
of the NCSG, there should first be consultation with NCSG members, and<br>
it must be approved by the NCSG’s Policy Committee."<br>
NCUC Onboarding Program<br>
<br>
<a href="https://www.icann.org/public-comments" rel="noreferrer" target="_blank">https://www.icann.org/public-<wbr>comments</a><br>
<br>
2. Objective<br>
<br>
Our objective is to go through creating one Public Comment<br>
hands-on, so that you can continue with future Comments independently<br>
and according to your interest.<br>
<br>
3. Actions<br>
<br>
We shall read some previous comments, help with one particular comment<br>
as a group, look a bit more into the issues behind the subject and<br>
follow up on the process after.<br>
<br>
week 1 general information<br>
week 2 starting on the comment and background<br>
week 3 writing, time-frame depends on the comment<br>
week X request for review and advice<br>
week Y submission<br>
<br>
4. Week 1 task<br>
<br>
- Take a look at Public Comments submitted this year,<br>
read at least two of them, make sure you understand the topic to some<br>
extent if it's new to you:<br>
<br>
<a href="https://community.icann.org/display/gnsononcomstake/Public+Comments+-+2017" rel="noreferrer" target="_blank">https://community.icann.org/<wbr>display/gnsononcomstake/<wbr>Public+Comments+-+2017</a><br>
<br>
- What do you think about the comments you've read? Anything<br>
you really liked, anything you would improve? There's no need to post a<br>
response, but take note of your observations.<br>
<br>
- Read NCUC Onboarding Program message below<br>
<br>
This helps us to a good start. You are welcome to post questions and<br>
comments by replying to this thread - and again, thank you for<br>
contributing your time to work on this.<br>
<br>
BR,<br>
thomas<br>
<br>
--<br>
* * *<br>
Friendly geek in Amsterdam, happy FSFE and EFF member<br>
<a href="https://wiki.techinc.nl/index.php/User:Thomascovenant" rel="noreferrer" target="_blank">https://wiki.techinc.nl/index.<wbr>php/User:Thomascovenant</a><br>
<br>
<br>
Reading Week 1:<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: NCUC Onboarding Program | Overview 4 | What Policy is Set at<br>
ICANN?<br>
Date: Fri, 17 Nov 2017 15:47:52 +0000<br>
From: Maryam Bakoshi <<a href="mailto:maryam.bakoshi@icann.org">maryam.bakoshi@icann.org</a>><br>
To: <a href="mailto:onboarding@lists.ncuc.org">onboarding@lists.ncuc.org</a> <<a href="mailto:onboarding@lists.ncuc.org">onboarding@lists.ncuc.org</a>><br>
<br>
<br>
<br>
Dear NCUC Member,<br>
<br>
<br>
<br>
* *<br>
<br>
There are multiple kinds of policy within the ICANN ecosystem:<br>
<br>
1. *Domain Name System (DNS) Policies* are developed through formal<br>
policy development processes, as set forth by the ICANN Bylaws.<br>
These policies become part of the contracts signed by Registries,<br>
Registries and Registrants – part of the rules of the global Domain<br>
Name System. Examples include the New gTLD Program<br>
<<a href="http://gnso.icann.org/en/council/policy/new-gtlds" rel="noreferrer" target="_blank">http://gnso.icann.org/en/<wbr>council/policy/new-gtlds</a>>,<br>
the Inter-Registrar Transfer Policy<br>
<<a href="https://www.icann.org/en/resources/registrars/transfers/policy" rel="noreferrer" target="_blank">https://www.icann.org/en/<wbr>resources/registrars/<wbr>transfers/policy</a>>,<br>
and the Expired Registration Recovery Policy<br>
<<a href="https://www.icann.org/resources/pages/errp-2013-02-28-en" rel="noreferrer" target="_blank">https://www.icann.org/<wbr>resources/pages/errp-2013-02-<wbr>28-en</a>>, among<br>
many others. Our work in this area often focuses on protecting<br>
privacy, freedom of expression, human rights, fair use, and due<br>
process. /This is what we are primarily involved with./<br>
2. *Operational Policies* define how ICANN works as an organization.<br>
These include an array of Cross-Community Working Groups associated<br>
with enhancing ICANN’s accountability, transparency, and diversity.<br>
In addition, operational policies include those matters not subject<br>
to a formal policy development process, but where community input<br>
has been sought via public comment or other means in shaping them.<br>
Examples include a recent revision to the criteria<br>
<br>
<<a href="https://www.icann.org/public-comments/fellowship-application-process-review-2016-06-14-en" rel="noreferrer" target="_blank">https://www.icann.org/public-<wbr>comments/fellowship-<wbr>application-process-review-<wbr>2016-06-14-en</a>><br>
for<br>
awarding an ICANN Fellowship, the language services policy for<br>
determining which meetings receive translation, and the conflict of<br>
interest policy for Board members.<br>
3. *General Practices. *ICANN relies on established practices that<br>
‘just exist’ and have not necessarily gone through a formalised<br>
approval process. Examples include acceptable behaviour and conduct<br>
from community members when asking questions to Board at a public<br>
comment forum.<br>
<br>
In our world, we are mostly involved in DNS policy. These are the<br>
recommendations that are developed and refined by the ICANN community<br>
through the various Supporting Organizations and influenced by the<br>
Advisory Committees.<br>
<br>
<br>
<br>
<br>
<br>
*How is Domain Name System Policy Developed within the GNSO?*<br>
<br>
* *<br>
<br>
DNS policy is developed in different ways across the Supporting<br>
Organizations, but within the GNSO (where the NCUC sits), the process<br>
usually flows as follows:<br>
<br>
* *<br>
<br>
- Firstly, the GNSO Council or ICANN’s Board will *identify the issue*.<br>
It is up to the GNSO Council to determine whether or not the issue will<br>
result in consensus policy.<br>
<br>
* If yes, the GNSO Council will request a Preliminary Issue Report<br>
to *scope the issue*.<br>
* ICANN Staff will produce and publish the Preliminary Issue Report<br>
for public comment. Following public comment, this feedback will be<br>
reviewed and incorporated into a Final Issue Report.<br>
<br>
* *<br>
<br>
- The GNSO Council will consider the Final Issue Report and decide<br>
whether or not to *initiate the formal Policy Development Process*.<br>
<br>
* If yes, the GNSO Council will develop and adopt a charter for the<br>
Policy Development Process working group.<br>
* The GNSO Council will issue a call for volunteers to join the<br>
working group.<br>
<br>
* *<br>
<br>
- *The working group is formed. *The working group participants will<br>
meet regularly and consult with the community to develop their Initial<br>
Report. This Initial Report will be opened for public comment.<br>
<br>
* After reviews and once community consensus is reached, the working<br>
group will submit its Final Report to the GNSO Council.<br>
<br>
<br>
<br>
- The GNSO Council will* deliberate the Final Report*.<br>
<br>
* If the recommendations are adopted, the GNSO Council will submit the<br>
Final Report to the ICANN Board.<br>
<br>
* *<br>
<br>
- The ICANN Board will then consult with various Advisory Committees,<br>
and will generally put the recommendations out for comment from the<br>
wider Internet community. Taking into account the advice received,<br>
the *ICANN Board will* *vote on the Final Report recommendations.*<br>
<br>
<br>
<br>
They key thing to note, here, is that /policy development in the GNSO<br>
takes place at the working group level – so that’s where you need to be<br>
to get involved! /<br>
<br>
<br>
<br>
<br>
<br>
*What are Policy Development Process Working Groups, and What is so<br>
Exciting About them Despite their Boring Name? *<br>
<br>
<br>
<br>
There are many ways in which you can become involved in ICANN’s<br>
multistakeholder, bottom-up, consensus-driven model for policy development.<br>
<br>
The most effective way in which you can voice your position about an<br>
issue is to shape the dialogue and the deliberations of the policy<br>
topic. You can do this by joining a Working Group created by the GNSO<br>
Council.<br>
<br>
These working groups are formally chartered within the ICANN structure<br>
to address policies and other issues facing the Internet community and<br>
the various stakeholders. They are composed of interested community<br>
volunteers with various types of interests and expertise.<br>
<br>
Most working groups have a membership which is geographically dispersed,<br>
so the primary means of meeting is via teleconferences and online<br>
resources two to four times per month. The phone calls use toll-free<br>
audiobridge numbers to many countries, or the Secretariat can dial out<br>
to you. Many use the Adobe Connect platform, which is free, to<br>
participate in the meetings online.<br>
<br>
If you are new to the community, it is generally /easiest to join a<br>
working group as it is forming/, but you can also join a working group<br>
that is already in progress. Doing so requires that you catch up with<br>
the work, research, and discussion that the group has already covered.<br>
You can do so by going through the recordings, briefing and transcripts<br>
of the previous meetings. You can also reach out to an NCUC focal point<br>
who can tell you more about how to get engaged.<br>
<br>
* *<br>
<br>
*Joining the Working Group: Procedures*<br>
<br>
<br>
<br>
If you wish to join a working group, email the GNSO Secretariat<br>
at <a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a> <mailto:<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>> to indicate your<br>
interest in doing so. You must include your full name, time zone,<br>
preferred email address for correspondence, and indicate whether you<br>
wish to be a member or observer of the working group (you can change<br>
this status at any time).<br>
<br>
You will then be invited to complete a short 90-minute course with ICANN<br>
staff to learn how to use the different online resources. In this<br>
tutorial you will be introduced to ICANN Learn, an e-learning platform<br>
with a growing number of tutorials on different community topics.<br>
<br>
Shortly thereafter, you will be asked to complete a Statement of<br>
Interest (SOI) form. In this document, you publicly disclose who you<br>
work for and any other business relationships that might affect how you<br>
influence the working group. You *cannot* be disqualified from the group<br>
based on your SOI. It is posted so that others in the working group can<br>
understand what factors may influence your viewpoint. You will also be<br>
able to see the SOI of every other person in the working group.<br>
<br>
<br>
<br>
*What are my Responsibilities if I Join a Working Group? *<br>
<br>
<br>
<br>
Working groups address challenging and complex issues, and require a<br>
high level of collaboration with people from all types of backgrounds<br>
and different cultures. You will probably enjoy the work more if you<br>
stick to areas of particular interest, and seek to participate actively<br>
in only one or two working groups (at least at first).<br>
<br>
No one can force you to take on more work than you choose to – we are a<br>
community of volunteers – but for maximum impact, you will need to<br>
participate in as many of the conference calls as possible. Attendance<br>
on calls is taken by ICANN staff and is publicly posted. In addition to<br>
attending meetings, you may be asked to assist in specific tasks such as:<br>
<br>
* Developing and drafting working group documents,<br>
* Contributing ideas and knowledge to working group discussions on the<br>
mailing list,<br>
* Acting as a liaison between the working group and the NCUC and NCSG,<br>
* Ensuring that NCSG statements are developed in an informed and<br>
timely way,<br>
* Actively and constructively participating in the consensus decision<br>
making process<br>
<br>
You should be aware that working groups are normally expected to operate<br>
under the principles of transparency and openness, which means that<br>
mailing list conversations are publicly archived, meetings are normally<br>
recorded and transcribed, and the public will be able to listen to or<br>
read your contribution. This is how the public can hold the ICANN<br>
community accountable for its work.<br>
<br>
* *<br>
<br>
*What Do I Get in Return?*<br>
<br>
<br>
<br>
As a volunteer, you will gain greater insight into how domain name<br>
policy is formed; a keen awareness of near-future developments that<br>
affect millions of users worldwide; and will have the opportunity to<br>
meet volunteers of similar interest from many different countries.<br>
<br>
<br>
<br>
/“You also get to see how the multistakeholder process works in action<br>
other than just reading about it. You will form a sense of collegiality<br>
with others from our, and other, stakeholder groups. You can fight for<br>
what you believe in, and be effective in making a change (however<br>
minimal). You can fight for more transparency and accountability. You<br>
can fight for freedom of expression in domain name policies. You can<br>
build a network of people who are the top experts in their field. You<br>
can become a leader or take an official position in the constituency and<br>
feel rewarded by serving the members and the community.” /<br>
<br>
/– Farzaneh Badii, Chair of the NCUC/<br>
<br>
<br>
<br>
<br>
<br>
*I Don’t Have Time to Join a Working Group, How Can I Help?*<br>
<br>
* *<br>
<br>
Many in the community who are short on time voice their positions about<br>
issues when a working group or operational matter has a call open for<br>
public comment.<br>
<br>
The Public Comments page <<a href="http://www.icann.org/en/public-comment/" rel="noreferrer" target="_blank">http://www.icann.org/en/<wbr>public-comment/</a>> on<br>
the ICANN website lists every issue that is currently open for input<br>
from any Internet user around the world. It also has a calendar where<br>
you can find a list of upcoming issues that will be available for<br>
comment in the near future. Here you will find instructions on how to<br>
submit comments and read other comments that other stakeholders have<br>
already submitted.<br>
<br>
The NCSG, on behalf of the members of the NCUC and NPOC, work hard to<br>
prepare comments that faithfully represent our joint concerns and<br>
recommendations. In order for the comment to be endorsed as the position<br>
of the NCSG, there should first be consultation with NCSG members, and<br>
it must be approved by the NCSG’s Policy Committee. Often there is<br>
discussion on the NCSG list on the different issues, but if there is not<br>
or there is a comment that you would like to help coordinate, please let<br>
the Chair know.<br>
<br>
Throughout ICANN’s history, policy recommendations have been modified in<br>
order to incorporate the feedback received through public comments. As a<br>
recent example, the /Applicant Guidebook/ that explains how to apply for<br>
a new gTLD was posted multiple times and drew more than 1,000 comments<br>
across six revisions, until the ICANN community reached consensus on it.<br>
It is crucially important that we weigh in on issues great and small.<br>
<br>
<br>
<br>
Please reach out to us with your questions, concerns, comments, and<br>
feedback: <a href="mailto:onboarding@lists.ncuc.org">onboarding@lists.ncuc.org</a> <mailto:<a href="mailto:onboarding@lists.ncuc.org">onboarding@lists.ncuc.<wbr>org</a>>.<br>
Our mentors Ayden Férdeline, Louise Marie Hurel and Kathy<br>
Kleiman* *check this inbox periodically and are on-hand to help you<br>
assimilate into our community and into the various working groups.<br>
<br>
<br>
<br>
Best wishes,<br>
Kathy Kleiman, Ayden Férdeline, and Louise Marie Hurel<br>
NCUC Onboarding Team<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
<br>
Many thanks,<br>
<br>
<br>
<br>
*Maryam Bakoshi | *SO/AC Collaboration Services Sr. Coordinator<br>
<br>
*ICANN*| Internet Corporation for Assigned Names and Numbers<br>
<br>
*S*: Maryam.bakoshi.icann | *T*: +44 7737698036<br>
<br>
<br>
</font></span><br>______________________________<wbr>_________________<br>
Comment-drafters mailing list<br>
<a href="mailto:Comment-drafters@lists.ncuc.org">Comment-drafters@lists.ncuc.<wbr>org</a><br>
<a href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/comment-drafters" rel="noreferrer" target="_blank">https://lists.ncuc.org/cgi-<wbr>bin/mailman/listinfo/comment-<wbr>drafters</a><br>
<br></blockquote></div><br></div>