<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I could make it - but please fix it asap.</p>
<p>Best regards</p>
<p>Wolf-Ulrich</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 03.07.2019 um 04:00 schrieb Heather
Forrest:<br>
</div>
<blockquote type="cite"
cite="mid:CADWyk6wA6iifypiVx4x=NFzobN=ij4zoB+J8-Nw2dgzkEpjyvA@mail.gmail.com">
<div dir="ltr">Thanks very much to all. Monday 15 July will be
Tuesday 16th my time - it's a busy morning for me, but I'll do
whatever I can to make it work.
<div><br>
</div>
<div>Best wishes,</div>
<div><br>
</div>
<div>Heather<br>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jul 2, 2019 at 5:24 AM
Julie Hedlund <<a href="mailto:julie.hedlund@icann.org"
moz-do-not-send="true">julie.hedlund@icann.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div lang="EN-US">
<div class="gmail-m_-469013421670548793WordSection1">
<p class="MsoNormal">Dear David and all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">After a staff discussion with Katrina
and Heather at ICANN65 it is suggested that the joint
GRC/DT meeting could be held on Monday, 15 July. Staff
will confirm the time and will send an invitation.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Kind regards,</p>
<p class="MsoNormal">Julie</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><b><span>From: </span></b><span>Gnso-bylaws-dt
<<a
href="mailto:gnso-bylaws-dt-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt-bounces@icann.org</a>>
on behalf of Julie Hedlund <<a
href="mailto:julie.hedlund@icann.org"
target="_blank" moz-do-not-send="true">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Thursday, June 20, 2019 at 10:46 AM<br>
<b>To: </b>"McAuley, David"
<a class="moz-txt-link-rfc2396E" href="mailto:dmcauley@Verisign.com"><dmcauley@Verisign.com></a>, "<a
href="mailto:gnso-bylaws-dt@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt@icann.org</a>"
<<a href="mailto:gnso-bylaws-dt@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:ccnso-grc@icann.org"
target="_blank" moz-do-not-send="true">ccnso-grc@icann.org</a>"
<<a href="mailto:ccnso-grc@icann.org"
target="_blank" moz-do-not-send="true">ccnso-grc@icann.org</a>><br>
<b>Subject: </b>Re: [Gnso-bylaws-dt] ccNSO GRC
questions re: consulting on Special IFRs</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">Dear David,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thank you very much for passing on
these very helpful comments and questions from the GRC.
Staff will take the action to schedule a joint GRC/DT
meeting as soon as possible following ICANN65, noting
that we do not schedule meetings the week immediately
following an ICANN meeting, so the soonest would be the
week of 07 July.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Kind regards,</p>
<p class="MsoNormal">Julie</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><b><span>From: </span></b><span>Gnso-bylaws-dt
<<a
href="mailto:gnso-bylaws-dt-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt-bounces@icann.org</a>>
on behalf of "McAuley, David via Gnso-bylaws-dt"
<<a href="mailto:gnso-bylaws-dt@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt@icann.org</a>><br>
<b>Reply-To: </b>"McAuley, David"
<a class="moz-txt-link-rfc2396E" href="mailto:dmcauley@Verisign.com"><dmcauley@Verisign.com></a><br>
<b>Date: </b>Thursday, June 20, 2019 at 8:07 AM<br>
<b>To: </b>"<a
href="mailto:gnso-bylaws-dt@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt@icann.org</a>"
<<a href="mailto:gnso-bylaws-dt@icann.org"
target="_blank" moz-do-not-send="true">gnso-bylaws-dt@icann.org</a>><br>
<b>Cc: </b>"<a href="mailto:ccnso-grc@icann.org"
target="_blank" moz-do-not-send="true">ccnso-grc@icann.org</a>"
<<a href="mailto:ccnso-grc@icann.org"
target="_blank" moz-do-not-send="true">ccnso-grc@icann.org</a>><br>
<b>Subject: </b>[Gnso-bylaws-dt] ccNSO GRC
questions re: consulting on Special IFRs</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">Dear Heather and fellow members of
the GNSO Drafting Team:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">At the ccNSO Guideline Review
Committee (GRC) meeting on Monday, June 17, some
questions/comments came up with respect to the draft
<b>Guidelines for GNSO-ccNSO Joint Consultation on
Initiation of a Special IFR</b>
<a
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__bit.ly_2KXUOMr&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=J4fIptoHzDWaABRUbLvMqZNBoYO-2Qa4daPs0YbDgh8&s=QbpKPs3BRIsEG3hGO4DqaCnWVHJ4md-uoFmdrofi9yE&e="
target="_blank" moz-do-not-send="true">
document [bit.ly]</a> we have been discussing. (FYI, I
am a participant in the GRC as well as in this GNSO
team.)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I will summarize those
questions/comments here to help us discuss. In addition,
I told the GRC that we believe another joint meeting of
GRC and this team will help us close work on this
document. We should think about scheduling that – and it
is my hope that this summary will help us focus on the
GRC concerns so that we may be able to address these
with the GRC in fairly short order when we meet.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Here are the questions/comments the
GRC noted during the June 17th meeting:</p>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpFirst"> </p>
<ol start="1" type="1">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
We envision the creation of a GNSO-ccNSO Special IFR
Initiation Coordination Team (<b>SICT</b>) – see
paragraph 5.2. We say that as
<span>soon as the CSC informs the ccNSO and GNSO
Councils about a performance issue as defined in the
CSC Remedial Action Procedure, the two Councils
shall as soon as possible each appoint three (3)
members including the Chairs to the SICT. Well,
these CSC procedures involve going first to the PTI
Board, then the ICANN CEO, and then to the ICANN
Board. The GRC wonders when specifically should the
SICT be established and they suggest that it not be
until the ICANN Board is engaged in the matter.
(Note – The CSC will inform the Councils of every
escalation step in the RAP.)</span></li>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="1" type="1">
<ol start="1" type="a">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
Question: Do we agree? What do we think?</li>
</ol>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="2" type="1">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
In reading through paragraph 5.3, the GRC was not
quite sure whether the respective Councils would have
to make one joint statement or two – and how the
interplay takes place between posting input on the
various websites and jointly releasing a statement
through the SICT.</li>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="2" type="1">
<ol start="1" type="a">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
Question: Can we clarify how this process works?</li>
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
Related question: Can we two groups jointly map out
the timeline of the SICT to test its viability? (For
instance, we allow up to 30 days for input from SOs
and ACs (see last sentence of paragraph 4.4) and
then perhaps allow for the time needed for public
comment – will these time periods work?)</li>
</ol>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="3" type="1">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
For the work and deliberations involved in paragraphs
5.4 through 5.6 (this is a considerable amount of
work) the document places most of the onus on the
SICT. THE GRC wonders if this is too much to load onto
the SICT and whether some of this should be shifted to
the respective Councils – and what that balance would
look like in a bit more detail. Moreover, given the
ramifications of the decisions involved which decision
should be on the plate of the full Councils and which
on the plate of the coordination team?</li>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="3" type="1">
<ol start="1" type="a">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
Question: What do we think?</li>
</ol>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="4" type="1">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
With respect to considerations of a Special IFR
itself, the GRC noted that other avenues exist through
which to address PTI issues – for instance (1)
possible removal of director(s) and (2) the ability to
bring an IRP relating to PTI service complaints and/or
ICANN’s failure to enforce its rights under the IANA
Naming Functions Contract – and mediation is also
available.
</li>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle"> </p>
<ol start="4" type="1">
<ol start="1" type="a">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
Question: Should this document note the fact that
Councils will possibly be looking at alternative
courses of action and thus we should be careful to
check on that possibility to factor it into our
calculations?</li>
</ol>
</ol>
<p
class="gmail-m_-469013421670548793MsoListParagraphCxSpMiddle">
<span> </span></p>
<ol start="5" type="1">
<li
class="gmail-m_-469013421670548793MsoListParagraphCxSpLast">
Finally, the document should perhaps make reference to
ongoing steps by CSC to resolve the issue. What
happens if the PTI/IANA issue is resolved along the
way – should we address closing down the SIFR and
SICT. (Note – once the CSC informs the Councils at the
end of the RAP the role of the CSC is very limited –
see the <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_csc-2Dremedial-2Daction-2Dprocedures-2D19feb19-2Den.pdf&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=adDIs0WEx_lLwFfrsdovxTYY8GkRHo5ibc8SR3Npdh8&m=tUtS7m-JUxApMefTA-tx6ZrWo-aozx7FEFckQ-LUJFg&s=DIpp1vLnjJrHjA1eO6dqbtpeJZ9KjakYSwjFDfI9yYw&e="
target="_blank" moz-do-not-send="true">
RAP process [icann.org]</a>.)</li>
</ol>
<p class="MsoNormal">Best regards,</p>
<p class="MsoNormal">David</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">David McAuley</p>
<p class="MsoNormal">Sr International Policy &
Business Development Manager</p>
<p class="MsoNormal">Verisign Inc.</p>
<p class="MsoNormal">703-948-4154</p>
<p class="MsoNormal"> </p>
</div>
</div>
_______________________________________________<br>
Gnso-bylaws-dt mailing list<br>
<a href="mailto:Gnso-bylaws-dt@icann.org" target="_blank"
moz-do-not-send="true">Gnso-bylaws-dt@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt</a><br>
_______________________________________________<br>
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 href="https://www.icann.org/privacy/policy"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos" rel="noreferrer"
target="_blank" moz-do-not-send="true">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.</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-bylaws-dt mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-bylaws-dt@icann.org">Gnso-bylaws-dt@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt">https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt</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>