<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Julie, tx for the notes!</p>
<p>To Jeff, Cheryl, Julie and Steve,</p>
In the interest of helping those who cannot participate in the
double meetings per week, it would help to have a few more
information bites in the notes to a) better understand what was
covered, b) know where discussion stopped and c) ideas where the is
likely to continue on the next call. <br>
<p>In particular for last night's call, could you share some basic
(and hopefully non-controversial) information: <br>
</p>
<p>-<i> Is the 2.3.2 discussion of Verified gTLDs completed -- or is
it likely to continue on Monday's meeting?</i></p>
<p><i> - Was any part of the 2.3.3 Applicant Freedom of Expression
section started? (it looks like no)<br>
</i></p>
<p><i>- Were any issues of 2.3.2 other than Verified gTLDs discussed
-- and will we be returning to other sections of 2.3.2 in the
next session? <br>
</i></p>
<p><i>- How many people attended and where can we find a list of
participants (we agreed to monitor participation in light of
concerns that many could not participate twice a week and had
already scheduled their Thursdays for the summer). we would all
monitor closely in light of real concerns about participation in
these Thursday calls.</i></p>
<p>Quick note: some participants missed the call last night because
they marked it in their calendars for Thursday night (Eastern
time). It was actually scheduled for Wednesday night (Eastern
time) -- and that in itself is a problem because Wednesdays are
RPM WG days. We should at least move the SubPro WG second call to
Thursdays nights/Friday AM to ensure the calls to do not come on
the same day. Asking for 3.0+ hours <i>on the same calendar day
for </i>participants in both WGs seems extraordinarily
difficult for those who are truly volunteers in this ICANN
process. Recommend changing it -- likely to increase participation
and decrease burdens during these hot days of summer (for some
hemispheres).<br>
</p>
<p>Best, Kathy</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/11/2019 11:44 AM, Julie Hedlund
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1D4C1B3D-3529-4DD7-B120-10CBBFB12400@icann.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:379209689;
mso-list-template-ids:50516402;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
<div class="WordSection1">
<p class="MsoPlainText">Dear Working Group members,<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText">Please see below the notes from the
meeting today, 11 July 2019. These high-level notes are
designed to help WG members navigate through the content of
the call and are not a substitute for the recording,
transcript, or the chat, which will be posted at: <a
href="https://community.icann.org/display/NGSPP/2019-07-11+New+gTLD+Subsequent+Procedures+PDP"
moz-do-not-send="true">
https://community.icann.org/display/NGSPP/2019-07-11+New+gTLD+Subsequent+Procedures+PDP</a>.
<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText">Kind regards,<o:p></o:p></p>
<p class="MsoPlainText">Julie<o:p></o:p></p>
<p class="MsoPlainText">Julie Hedlund, Policy Director<o:p></o:p></p>
<p class="MsoPlainText"> <o:p></o:p></p>
<p class="MsoPlainText"><b>Notes and Action Items:</b><o:p></o:p></p>
<p class="MsoNormal"><b> </b><o:p></o:p></p>
<p class="MsoNormal"><b>Action Items:</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ACTION ITEM re: CCT-RT Recommendations and
ALAC Statement -- Questions for Justine Chew:<o:p></o:p></p>
<p class="MsoNormal">1. Is ALAC's position documented anywhere?<o:p></o:p></p>
<p class="MsoNormal">2. On the CCT Review - Does John's comment
refer to ALL CCT Recommendations or to just those
prerequisites (as labeled by the CCT Review Team)<o:p></o:p></p>
<p class="MsoNormal">3. With respect to the RPM PDP, does
John's comment relate to just Phase 1 of the PDP or to both
Phase 1 and 2.<o:p></o:p></p>
<p class="MsoNormal">4. The value of precedent within the
ALAC...I will flush this one out further by comparing answers
from Community Comment 1 and 2.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Notes:</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. Updates to Statements of Interest
(SOIs): None provided.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">2. Review of summary document: (continued)
-- Global Public Interest (<a
href="https://docs.google.com/document/d/15rwviHM6AYtqDqyB6_5Yij2dTL6iuou8z7A32yzc7sE/edit?usp=sharing"
moz-do-not-send="true">https://docs.google.com/document/d/15rwviHM6AYtqDqyB6_5Yij2dTL6iuou8z7A32yzc7sE/edit?usp=sharing</a>)
– start at Verified TLDs, Page 6<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Verified TLDs:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- Updated the sections on mandatory and
voluntary PICs to include divergence from the Public Interest
Community and the NCSG.<o:p></o:p></p>
<p class="MsoNormal">-- The word “likelihood” should be fixed.
Edit and check with IPC re: IPC comment and the word
“likelihood”. Typo in the original comment.<o:p></o:p></p>
<p class="MsoNormal">-- As as it's been applied a verified TLD
is one that verifies the potential registrants meets registry
standards prior to registering a domain. So for instance, the
registry operator might require registrants to be
appropriately credentialed to practice where they do
business. And that's where that implied trust comes in, I
think, so that end users can trust that domains in that TLD
are going to be authentic. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CCT-RT Recommendations:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- For absolute clarity, is the ALAC
position that the RPM PDP must be completed in its entirety
(ie, Phase 1 and Phase 2) prior to next round commencing?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- As a reminder, this WG has a tracking
sheet for all of the CCT-RT recommendations aimed at SubPro:
<a
href="https://docs.google.com/spreadsheets/d/1PGV5_nMafLWtSHyCGdr-b8eqoJj9B8YKBSheVJQcvHg/edit?usp=sharing"
moz-do-not-send="true">
https://docs.google.com/spreadsheets/d/1PGV5_nMafLWtSHyCGdr-b8eqoJj9B8YKBSheVJQcvHg/edit?usp=sharing</a>.
And it has been updated to take into account what the Board
has passed through to SubPro.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">-- John Laprise - to answer Jeff's
question, could you add to your email earlier today to the
SubPro list re ALAC position the document in which this
position is recorded?<o:p></o:p></p>
<p class="MsoNormal">------------------------<o:p></o:p></p>
<p class="MsoNormal">ALAC statement:<o:p></o:p></p>
<p class="MsoNormal"><b>From: </b>Gnso-newgtld-wg <<u><a class="moz-txt-link-abbreviated" href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a></u>>
on behalf of John Laprise <<u><a class="moz-txt-link-abbreviated" href="mailto:jlaprise@gmail.com">jlaprise@gmail.com</a></u>><o:p></o:p></p>
<p class="MsoNormal"><b>Date: </b>Wednesday, July 10, 2019 at
22:20<o:p></o:p></p>
<p class="MsoNormal"><b>To: </b>"<u><a class="moz-txt-link-abbreviated" href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a></u>"
<<u><a class="moz-txt-link-abbreviated" href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a></u>><o:p></o:p></p>
<p class="MsoNormal"><b>Cc: </b>'ALAC Members' <<u><a class="moz-txt-link-abbreviated" href="mailto:ALAC-members@icann.org">ALAC-members@icann.org</a></u>>,
ICANN At-Large Staff <<u><a class="moz-txt-link-abbreviated" href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a></u>><o:p></o:p></p>
<p class="MsoNormal"><b>Subject: </b>[Gnso-newgtld-wg] ALAC
position on newgTLD subpro<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Just a useful reminder of ALAC’s position
as asserted to ICANN GDD at ICANN65:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">ALAC will not support a new gTLD round
until full implementation of CCT and RPM recommendations are
fully implemented.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">John Laprise, Ph.D.<o:p></o:p></p>
<p class="MsoNormal">NARALO ALAC Representative<o:p></o:p></p>
<p class="MsoNormal">ALAC Vice Chair-Policy<o:p></o:p></p>
<p class="MsoNormal">----------------------<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- Can staff please send me [Justine] an AI
on the questions being posed with respect to John Laprise's
comment? Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Questions:<o:p></o:p></p>
<p class="MsoNormal">1. Is ALAC's position documented anywhere?<o:p></o:p></p>
<p class="MsoNormal">2. On the CCT Review - Does John's comment
refer to ALL CCT Recommendations or to just those
prerequisites (as labeled by the CCT Review Team)<o:p></o:p></p>
<p class="MsoNormal">3. With respect to the RPM PDP, does
John's comment relate to just Phase 1 of the PDP or to both
Phase 1 and 2.<o:p></o:p></p>
<p class="MsoNormal">4. The value of precedent within the
ALAC...I will flush this one out further by comparing answers
from Community Comment 1 and 2.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--- @jeff, in respect of your #4 my
immediate answer is what you term as a “precedent”; is not
precedent in the actual sense of the word, but ALAC positions
are not immune to change with developments over time.<o:p></o:p></p>
<p class="MsoNormal">-- Thanks Justine - This is why seeing the
rationale and not just the final position/resolution/outcome
is important.<o:p></o:p></p>
<p class="MsoNormal">-- Jeff, your question #4 seems to assume
that, if there is a difference in position between Comment 1
and 2, that somehow this indicates that ALAC has disregarded
or “devalued” “precedent.” I don’t think that’s a fair
assumption.<o:p></o:p></p>
<p class="MsoNormal">-- Given that we have only one very
high-level articulation of a high-level agreement and many
divergent points under outstanding items;, it's not clear to
me what our overall objective is in this section. Are we
hoping to distill from outstanding items more points as
high-level agreements?<o:p></o:p></p>
<p class="MsoNormal">-- Thanks, Jeff - looking for commonalites
makes sense. Thanks for the explanation.<o:p></o:p></p>
<p class="MsoNormal">-- One thing to consider is that the policy
goal may not be achievable, insofar as we are not able to work
out some explicit implementation matrix (ie, X weighs heavier
than Y)<o:p></o:p></p>
<p class="MsoNormal">-- @Greg- and therein lies the problem.
Reaching agreement on a definition has not yet been achieved
at the level of international law, so us achieving that here
is a big ask.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Freedom of Expression:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- High-level agreement -- Support: May not
be accurate. May need a more neutral phrase. Need to provide
specific implementation guidance. Need to better define what
is meant by “applicant freedom of expression”. Broader term
than freedom of speech.<o:p></o:p></p>
<p class="MsoNormal">-- Difficult for the WG to develop a
definition since it hasn’t yet been done.<o:p></o:p></p>
<p class="MsoNormal">-- High level agreement is that there are
freedom of expression rights.<o:p></o:p></p>
<p class="MsoNormal">-- Start with Implementation Guidelines
section on the next call.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-newgtld-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a>
_______________________________________________
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 (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). 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.</pre>
</blockquote>
</body>
</html>