<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thanks Kathy for raising those concerns alongside all the solid arguments. I could not have done better.<br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class="Apple-interchange-newline">@__f_f__<br class=""><br class="">Best Regards<br class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">____________________________________</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">(Ekue) Farell FOLLY</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">NCUC Rep. to the NCSG Policy Committee</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><a href="http://linkedin.com/in/farellf" class="">linkedin.com/in/farellf</a> <br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><br class="Apple-interchange-newline"></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></div></div></div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 27 Aug 2018, at 05:20, Kathy Kleiman <<a href="mailto:kathy@KATHYKLEIMAN.COM" class="">kathy@KATHYKLEIMAN.COM</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hi Elsa,</p><p class="">With the deadline still pending last week, I went ahead, printed
off the 300 page report, and spent hours digging into it. I also
participated in Subgroup 2 -- Legal and Regulatory -- and was
dismayed by the lack of data, systematic analysis, or serious
consideration of views other than those being directly represented
by members of the subgroup (nearly all active members representing
large, incumbent New gTLD Registries who want to register hundreds
(or more) New gTLDs). <br class="">
</p><p class="">I remember our goals in the first Applicant Guidebook in the late
2000's -- how excited we were to see Internationalized Domain
Names, and our great hope that Applicants for New gTLDs would be
from countries and regions underrepresented (and, in some cases,
completely unrepresented) as registries in the existing (legacy)
gTLDs. In this next round (or the many next rounds the SubPro
Working Group envisions), I see many of these hopes being dashed
and am very concerned. <br class="">
</p><p class="">The devil is in the details -- in the very procedural rules they
are setting out. I am deeply concerned that with insufficient
notice and guidance, smaller and more diverse entities will not be
able to apply. I'm equally concerned that with no limits to
applications, or even the proposed "first-come, first-served"
system (which I'll rename "the all you can gobble" approach),
there will be no time for the Global South to catch up --
everything could well be given away by then.</p><p class="">Extensive comments! More can be added, particularly on the
issues you and Bruna highlighted. If you can link these
principles and important discussion to specific sections of the
Initial Report in which they are discussed, it will help to ensure
that our comments, and your important thoughts, will receive the
credit they deserve when comments are compiled by staff into a
report.</p><p class="">I'm out of the office for this last week of summer, but otherwise
around. Best, Kathy<br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 8/25/2018 8:53 PM, Elsa S wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAHFwYbfYNgZLBKx=GtM2bqypR6zmbLHT0QJnrU==J2VeMgg-XA@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
<div class="">
<div dir="auto" class="">Hi all,</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Any chance we could meet this coming week to fix
the document? I’ll touch base with Robin and maybe Kathy to
see if they could join us to answer some of our questions on
the doc. In the meantime, I’ll be reviewing the doc and seeing
if we could add any further points.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Let me know if interested! I can set up a google
doc.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">E.</div>
<div dir="auto" class="">—</div>
<br class="">
<div class="gmail_quote">
<div class="">On Thu, Aug 23, 2018 at 7:27 PM Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" moz-do-not-send="true" class="">rafik.dammak@gmail.com</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">Thanks Farzaneh, that is good for us.
<div class="">I touched base few days ago with Elsa and Bruna
regarding the status of our draft and we are currently
progressing. I think Kathy is also helping for the
review and Robin will be consulted too.</div>
<div class="">as reminder we organized few weeks ago a NCSG webinar
(<a href="https://community.icann.org/display/gnsononcomstake/NCSG+Webinars" target="_blank" moz-do-not-send="true" class="">https://community.icann.org/display/gnsononcomstake/NCSG+Webinars</a>)
on the report presented by Robin where she highlighted
the most important and relevant topics for us, I advice
everyone to listen to it. while the report is 300 pages
(there are appendices etc), it can be easier to listen
to the webinar and check the spreadsheet made by the WG
with all the recommendations and questions organized by
topic.</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class=""><br class="">
</div>
<div class="">Rafik<br class="">
<br class="">
</div>
</div>
<div class="">
<div class="">
<div class="gmail_quote">
<div class="">Le ven. 24 août 2018 à 01:31, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank" moz-do-not-send="true" class="">farzaneh.badii@gmail.com</a>>
a écrit :<br class="">
</div>
</div>
</div>
</div>
<div class="">
<div class="">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="">
<div style="font-family:verdana,sans-serif" class="">we got
some time for this huge document to comment on.
A big Phew.</div>
<div style="font-family:verdana,sans-serif" class=""><br class="">
</div>
<div class="">
<div class="m_-5051817785915982835gmail-m_2506395340310723665gmail_signature">
<div class="">
<div class=""><font face="verdana, sans-serif" class="">Farzaneh
</font></div>
</div>
</div>
</div>
<br class="">
<br class="">
<div class="gmail_quote">
<div class="">---------- Forwarded message ---------<br class="">
From: <strong class="gmail_sendername" dir="auto">Emily Barabas</strong> <br class="">
</div>
<br class="">
<br class="">
<div lang="EN-US" class="">
<div class="m_-5051817785915982835gmail-m_2506395340310723665m_2047545855745330147WordSection1"><p class="MsoNormal"><span style="font-size:11pt" class="">Dear Farzaneh,</span></p><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11pt" class="">We are writing to
let you know that the
<a href="https://www.icann.org/public-comments/gtld-subsequent-procedures-initial-2018-07-03-en" target="_blank" moz-do-not-send="true" class="">
public comment period</a> for the New
gTLD Subsequent Procedures PDP WG
Initial Report has been extended. Public
comments will now be accepted through
<b class="">26 September 2018</b>. Can you kindly
assist in sharing this information with
the relevant members of your group?</span></p><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Best regards,</span></div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Cheryl Langdon-Orr
and Jeff Neuman (WG Co-Chairs)</span></div><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
solid rgb(181,196,223);padding:3pt 0cm
0cm" class=""><p class="MsoNormal"><b class=""><span style="" class="">From: </span></b><span style="" class="">Nathalie Peregrine
<<a href="mailto:nathalie.peregrine@icann.org" target="_blank" moz-do-not-send="true" class="">nathalie.peregrine@icann.org</a>><br class="">
<b class="">Date: </b>Wednesday, 4 July 2018
at 04:50<br class="">
<b class="">To: </b>farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank" moz-do-not-send="true" class="">farzaneh.badii@gmail.com</a>><br class="">
<b class="">Cc: </b>"<a href="mailto:jeff.neuman@comlaude.com" target="_blank" moz-do-not-send="true" class="">jeff.neuman@comlaude.com</a>"
<<a href="mailto:jeff.neuman@comlaude.com" target="_blank" moz-do-not-send="true" class="">jeff.neuman@comlaude.com</a>>,
Cheryl Langdon-Orr <<a href="mailto:langdonorr@gmail.com" target="_blank" moz-do-not-send="true" class="">langdonorr@gmail.com</a>>,
Steve Chan <<a href="mailto:steve.chan@icann.org" target="_blank" moz-do-not-send="true" class="">steve.chan@icann.org</a>>,
Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank" moz-do-not-send="true" class="">julie.hedlund@icann.org</a>>,
Emily Barabas <<a href="mailto:emily.barabas@icann.org" target="_blank" moz-do-not-send="true" class="">emily.barabas@icann.org</a>>,
Maryam Bakoshi <<a href="mailto:maryam.bakoshi@icann.org" target="_blank" moz-do-not-send="true" class="">maryam.bakoshi@icann.org</a>>,
"<a href="mailto:gnso-secs@icann.org" target="_blank" moz-do-not-send="true" class="">gnso-secs@icann.org</a>"
<<a href="mailto:gnso-secs@icann.org" target="_blank" moz-do-not-send="true" class="">gnso-secs@icann.org</a>><br class="">
<b class="">Subject: </b>New gTLD Subsequent
Procedures PDP WG Initial Report -
Public Comment</span></p>
</div>
<div class=""><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div>
</div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Dear</span>
Farzaneh,
</div><p style="margin:0cm 0cm 0.0001pt" class=""> </p><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">We write to you as
the Co-Chairs of the GNSO’s New gTLD
Subsequent Procedures Working Group
(WG), which is tasked with calling upon
the community’s collective experiences
from the 2012 New gTLD Program round to
consider potential changes that may be
needed to the existing 2007 Introduction
of New Generic Top-Level Domains policy
recommendations and implementation. We
are pleased to share that the Working
Group has reached an important milestone
by publishing its <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_gtld-2Dsubsequent-2Dprocedures-2Dinitial-2D2018-2D07-2D03-2Den&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=4gYyCwhtEI98RlWT6m_3FasU_W94CPJVbYvXvdaDxws&s=TwT7TfmDQ6Na2XFI7TKEFTn4pi5z-7JSXypjqAP6rRE&e=" target="_blank" moz-do-not-send="true" class="">
Initial Report for Public Comment
[icann.org]</a>. We would like to
strongly encourage you to review this
report and provide feedback through
public comment on the draft preliminary
recommendations, options, and questions
for community feedback. Your input is
essential to the success of this PDP.</span></div><p style="margin-right:0cm;margin-left:36pt;margin-bottom:0.0001pt" class="">
<b class=""><span style="" class="">1. <span class="m_-5051817785915982835gmail-m_2506395340310723665m_2047545855745330147apple-tab-span">
</span>Background on the New gTLD
Subsequent Procedures PDP WG</span></b></p><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">The GNSO’s New gTLD
Subsequent Procedures Working Group
(WG), which was chartered by the GNSO
Council to conduct a Policy Development
Process (PDP), is seeking to determine
what, if any, changes may need to be
made to the existing</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issues_new-2Dgtlds_pdp-2Ddec05-2Dfr-2Dparta-2D08aug07.htm&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=4gYyCwhtEI98RlWT6m_3FasU_W94CPJVbYvXvdaDxws&s=fAYAOAlC7DqbvB0WyYMiIOXAkUC6kzqPgR62nsJhHCQ&e=" target="_blank" moz-do-not-send="true" class=""><span style="" class="">
</span><i class=""><span style="color:rgb(17,85,204)" class="">Introduction
of New Generic Top-Level Domains</span></i>
[gnso.icann.org]</a><i class=""><span style="" class="">
</span></i><span style="" class="">policy
recommendations from 8 August 2007 as
well as the final</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_en_applicants_agb&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=4gYyCwhtEI98RlWT6m_3FasU_W94CPJVbYvXvdaDxws&s=iK3CVAc8mCe_CJRGZTBv2B_bDcoekw7F1Tg2uNLpbsI&e=" target="_blank" moz-do-not-send="true" class=""><span style="" class="">
</span><span style="color:rgb(17,85,204)" class="">Applicant
Guidebook</span> [newgtlds.icann.org]</a><span style="" class=""> dated June 2012. As
the original policy recommendations as
adopted by the GNSO Council and ICANN
Board have “been designed to produce
systemized and ongoing mechanisms for
applicants to propose new top-level
domains,” those policy recommendations
remain in place for subsequent rounds of
the New gTLD Program unless the GNSO
Council would decide to modify those
policy recommendations via a policy
development process. The PDP WG created
5 Work Tracks that are responsible for
considering the subjects within its
charter. The PDP WG sought community
input through two community comment
periods. The Working Group has produced
its Initial Report, which includes
material from the full Working Group and
Work Tracks 1-4. Work Track 5, focused
on Geographic Names at the Top-Level,
was established later than the other
Work Tracks and will produce a separate
Initial Report.</span></div><div class=""> <br class="webkit-block-placeholder"></div><p style="margin-right:0cm;margin-left:36pt;margin-bottom:0.0001pt" class="">
<b class=""><span style="" class="">2. <span class="m_-5051817785915982835gmail-m_2506395340310723665m_2047545855745330147apple-tab-span">
</span>Information about the Initial
Report and the Public Comment</span></b></p><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">The objective of
this Initial Report is to document the
Working Group’s deliberations on charter
issues and preliminary recommendations,
potential options for recommendations,
as well as specific questions for which
the Working Group is seeking input.
Given the large number of issues, and
the thousands of hours spent on
addressing the 2012 New gTLD Program and
improvements that can be made to the
program moving forward, unlike other
Initial Reports, this one does not
contain a “Statement of level of
consensus for the recommendations
presented in the Initial Report.” The
Co-Chairs not only believed that it was
premature to measure the level of
consensus of the Working Group members
of dozens of recommendations contained
within the Initial Report, but that
doing so could have the unintended
consequence of locking Working Group
members into positions of support or
opposition prior to soliciting public
comment from the community on those
recommendations. To form such definitive
positions at this early of a stage could
have the adverse effect of being less
open to modifications to those positions
as a result of community input.</span></div><div class=""> <br class="webkit-block-placeholder"></div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">In addition, though
many of the preliminary recommendations
were generally agreed to by members that
participated in the different Work
Tracks, support has not been assessed
amongst the members of the overall
Working Group. The Overall Working Group
has not sought to form definitive
positions on each of these issues at
this stage. Therefore, any language in
this report that suggests that the
Working Group or any of its Work Tracks
is making a recommendation should be
read as merely a rough assessment by the
Working Group Co-Chairs or Work Track
leads. </span></div><div class=""> <br class="webkit-block-placeholder"></div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">After a
comprehensive review of public comments
received on this report, the Working
Group will deliberate further on the
preliminary recommendations contained
within the Initial Report. It is
possible that as a result of the
deliberations, there may be supplemental
reports released by the Working Group
seeking additional public comments. Once
all of that is completed, the Co-Chairs
will conduct any formal consensus
call(s) at the plenary level, on all
recommendations before the Working Group
issues its Final Report. </span>
</div><p style="margin:0cm 0cm 0.0001pt" class=""><span style="" class=""> </span></p><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Thank you for your
consideration of this request. We look
forward to any comments and any input
that you and the organization you Chair
are able to provide to our WG. While we
of course welcome input on any area of
the report, we would like to stress that
given the extensive number of topics and
preliminary outcomes, you should not
feel compelled to respond to every
single preliminary recommendation,
option, and question. If possible,
please submit your comments and input to
us by 5 September 2018 so that we may
fully consider it in our further
deliberations.</span></div><p style="margin:0cm 0cm 0.0001pt" class=""><span style="" class=""> </span></p><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Best regards,</span></div><div style="margin: 0cm 0cm 0.0001pt;" class=""><span style="" class="">Cheryl Langdon-Orr
and Jeff Neuman (WG Co-Chairs)</span></div><div style="margin-bottom: 12pt;" class=""> <br class="webkit-block-placeholder"></div><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11pt" class="">Nathalie
Peregrine</span></p><p class="MsoNormal"><span style="font-size:11pt" class="">Manager,
Operations Support (GNSO)</span></p><p class="MsoNormal"><span style="font-size:11pt" class="">Internet
Corporation for Assigned Names and
Numbers (ICANN) </span></p><p class="MsoNormal"><span style="font-size:11pt" lang="PT-BR" class="">Email: </span><span style="font-size:11pt" class=""><a href="http://nathalie.peregrine@icann.org%20" target="_blank" moz-do-not-send="true" class=""><span lang="PT-BR" class="">nathalie.peregrine@icann.org </span></a></span></p><p class="MsoNormal"><span style="font-size:11pt" lang="PT-BR" class="">Skype:
nathalie.peregrine.icann</span></p><div class=""><span style="font-size:11pt" lang="PT-BR" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11pt" class="">Find out more
about the GNSO by taking our i<a moz-do-not-send="true" class="">nteractive
courses</a> and visiting the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=-d9m4sr16OXloyLjz4TF6npbe51hgE0EHtoX1U6WUOA&s=Bw2Uzbh2Pu1X0lObLtbwtN5ZNEP3ECdPAfcqzVvIOYE&e=" target="_blank" moz-do-not-send="true" class="">GNSO
Newcomer pages</a></span></p><div class=""><span style="font-size:11pt" class=""> </span><br class="webkit-block-placeholder"></div><div class=""> <br class="webkit-block-placeholder"></div><div class=""> <br class="webkit-block-placeholder"></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<div class="">
<div class="">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
_______________________________________________<br class="">
NCSG-PC mailing list<br class="">
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank" moz-do-not-send="true" class="">NCSG-PC@lists.ncsg.is</a><br class="">
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank" moz-do-not-send="true" class="">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br class="">
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
-- <br class="">
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">--<br class="">
<br class="">
Elsa Saade<br class="">
Consultant</div>
</div>
<div class="">Gulf Centre for Human Rights</div>
<div class="">Twitter: @Elsa_Saade</div>
</div>
</div>
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">NCSG-PC mailing list<br class=""><a href="mailto:NCSG-PC@lists.ncsg.is" class="">NCSG-PC@lists.ncsg.is</a><br class="">https://lists.ncsg.is/mailman/listinfo/ncsg-pc<br class=""></div></blockquote></div><br class=""></body></html>