<div>I fully support these comments as well. Publicly recording my personal thanks to you, Kathy, for taking the time and making the effort to write this response to that infantile document that ICANN staff for some reason had the resources to produce. Thanks again.<br></div><div><br></div><div class="protonmail_signature_block "><div class="protonmail_signature_block-user "><div>Ayden Férdeline<br></div><div><a href="http://www.linkedin.com/in/ferdeline" title="http://www.linkedin.com/in/ferdeline">linkedin.com/in/ferdeline</a><br></div></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: Re: [PC-NCSG] Health Identifiers Concerns/Comments - deadline tomorrow!<br></div><div>Local Time: 22 January 2017 5:43 PM<br></div><div>UTC Time: 22 January 2017 17:43<br></div><div>From: egmorris1@toast.net<br></div><div>To: Kathy Kleiman <kathy@kathykleiman.com><br></div><div>NCSG-Policy <pc-ncsg@ipjustice.org><br></div><div><br></div><div>Hi Kathy,<br></div><div><br></div><div>I'm happy to endorse these as NCSG comments. <br></div><div><br></div><div>Best,<br></div><div><br></div><div>Ed Morris<br></div><div><div><br></div><div>Sent from my iPhone<br></div></div><div><div><br></div><div>On 22 Jan 2017, at 17:39, Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>> wrote:<br></div></div><blockquote type="cite"><div><p>Hi All, <br></p><p>On Thursday's PC call, I promised Tapani and you that I would
draft a short set of comments on the Open Public Comment: <i>Identifier
Technology Health Indicators: Definition. </i>Staff's idea here
is to assign made up "disease names" to policy issues and
concerns. On the PC call, Matthew Shears and I shared the view
that this is an utterly ridiculous proposal. Frankly, this
proposal is straight out of Monty Python and the Ministry of Silly
Walks! <br></p><p>I've drafted a one page set of comments that set forth the view
that the proposals is unfair and even dangerous for the types of
issues we work on. In this comment, we are supporting the prior
comments of James Gannon (individual comment), John Berryhill and
IAB Chair Andrew Sullivan in sharing that this is a really bad
idea.<br></p><div>The draft comments are below and posted on Google Doc at<a href="https://docs.google.com/document/d/1S2s5pTiD1aXrB3V2QZSRyqfJ720rg7epvPQnkUi7XdE/edit?usp=sharing" class="moz-txt-link-freetext">https://docs.google.com/document/d/1S2s5pTiD1aXrB3V2QZSRyqfJ720rg7epvPQnkUi7XdE/edit?usp=sharing</a><br></div><div><br></div><div><i>Might we have your fast review and signoff so that we can submit
these comments by the deadline tomorrow? <br> <br> Tapani, could you kindly add the appropriate sign off to these
comments once we have approval? </i></div><div>Best, Kathy<br></div><div>--------------------------------------------------------------------------------------------------------------------------------------<br></div><div><br></div><h4><br></h4><h4><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">Comments
to Identifier Technology Health Indicators: Definition</span><br></p><div><span style="font-family:Calibri, sans-serif" class="font"><a href="https://www.icann.org/public-comments/ithi-definition-2016-11-29-en">https://www.icann.org/public-comments/ithi-definition-2016-11-29-en</a></span><br></div><div><br></div><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">Comment
periods like this one rank as a complete abuse of the time of
volunteers in the ICANN Community who have to stop their lives
to
respond to them. I think we should create a name for it:
AbuseOfVolunteersitis.</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">The
comments below strongly support the cries of John Berryhill,
IAB
Chair Andrew Sullivan and James Gannon in setting forth that
sometimes a comment topic does not deserve consideration and
should
be eliminated at the start. How this slide presentation made
it to
the level of a poorly-presented public comment is beyond the
understanding of those reviewing it – we have serious issues
and
PDPs before us.</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">In
all
seriousness, let us share that:</span><br></p><p style="margin-bottom: 0in"><br></p><ul><li><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">SSAC
wants metric of the DNS and that is certainly supportable;</span><br></p></li><li><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">BUT
assigning silly, strange and distorted names to issues
that need <i>careful and balanced </i>review,
consideration and evaluation is, as you have been told in
other comments, DANGEROUS:</span><br></p><ul><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">1. It's prejudicial – assigning a disease
name to a certain situation implies it is a problem. For
example, DATAMALGIA (Pain from Bad Data) delves into
difficulties we have been exploring for over 15 years:
of privacy and data protection protections and laws not
currently allowed to be implemented by Registrars, of
legitimate exercises of Free Expression by individuals
and organizations operating in opposition to oppressive
regimes and governments who would jail them for their
views (or worse); of students who have no phones, but do
have computers, Internet connections and ideas that to
share via domain names. This data is not a disease, but
a complex policy discussion and concern.</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">2. It's unfair – superimposing a disease
name atop an area of serious research, study and
evaluation minimizes the problems, discourages the
robustness of the debate, and makes it more difficult to
fully evaluate and resolve the issues.</span><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">3. It's unwise – labeling a serious research
area with a silly name. It diminishes the work of many
years and the good faith efforts of numerous task
forces, working groups and committees.</span><br></p></ul></li></ul><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">The
answer here is simple. Whoever introduced this idea either was
either
a) new to ICANN or b) does not appreciate the attention and
intensity
of the debate. We are technologists, lawyers, registration
industry
members and other Community members who have become policy
makers. We
look at facts, situations, data and evidence. It destroy and
diminishes our efforts, time and discussions to label them
with silly
names.</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">Overall,
this is a a poorly presented comment – you have asked us
(Commenters) to delve into a slide presentation for the
materials
that are the basis of your question. The 5 disease names that
have
been created impose prejudicial interpretations on debates
within the
scope of ICANN, and ask us to go far beyond the boundaries of
ICANN. The answer is “no.”</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">Best,</span><br></p><p style="margin-bottom: 0in"><br></p><p style="margin-bottom: 0in"><span style="font-family:Calibri, sans-serif" class="font">NonCommercial
Stakeholders & The Undersigned</span><br></p><p style="margin-bottom: 0in"><br></p></h4></div></blockquote><blockquote type="cite"><div><div><span>_______________________________________________</span><br></div><div><span>PC-NCSG mailing list</span><br></div><div><span><a href="mailto:PC-NCSG@ipjustice.org">PC-NCSG@ipjustice.org</a></span><br></div><div><span><a href="http://mailman.ipjustice.org/listinfo/pc-ncsg">http://mailman.ipjustice.org/listinfo/pc-ncsg</a></span><br></div></div></blockquote></blockquote><div><br></div>