<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks Heather and team!</p>
<p>No more issues from my side. A big support re the Saturday night
bar approach!</p>
<p>Safe travels to all</p>
<p>Wolf-Ulrich</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 25.10.2019 um 09:31 schrieb Heather
Forrest:<br>
</div>
<blockquote type="cite"
cite="mid:CADWyk6z=gXgPaon41K3cO_oOpd9jwa-KjepJPijppZzv9VGZrQ@mail.gmail.com">
<div dir="ltr">Dear DT colleagues,
<div><br>
</div>
<div>A quick report/update/reminder, as I'm conscious of email
(not to mention document) fatigue:</div>
<div><br>
</div>
<div>1. I provided an update to the GNSO Council in its October
meeting yesterday on the package of Guidelines and Motion
Templates we have prepared. Councillors have access to all
documents except the 18.12 Guideline (which incorporates the
Joint Consultation process, as discussed in the email chain
below). There were no major queries. GNSO Chair Keith Drazek
profusely thanked the DT for all of its hard work. </div>
<div><br>
</div>
<div>2. Don't forget to review the final proposed 18.12
Guideline mentioned in the email chain below by the end of
today (Friday). Thanks very much to Maxim, whose minor
grammatical edits appear in the document. If you run out of
time, there is still an opportunity to flag issues with your
respective GNSO Councillors, who can post issues on the
Council list and discuss in Montreal.</div>
<div><br>
</div>
<div>3. Unless there are clearly articulated objections, staff
and I will submit the 18.12 document and a draft motion to
Council this Sunday for the Montreal meeting document
deadline. Recall that ICANN legal is still reviewing; any
issues that they or any DT member spots between now and
Council's vote in Montreal will be addressed.</div>
<div><br>
</div>
<div>4. Please consider adding to your respective SG/C agendas a
briefing on the DT's work for the upcoming GNSO Council vote
in Montreal. Julie, Ariel and I are developing a slide deck
based on the slides I used to update Council yesterday. If you
would like me to join you to help brief your SG/C, I'll be
very happy to do that - just let me know. Ariel and Julie will
flag the slides to your attention when they land in our
inboxes next week.</div>
<div><br>
</div>
<div>5. Last but not least, a celebration of the Annex D
survivors' club - if you are in Montreal on Saturday night and
would like to get together to collectively drown our sorrows
over the complexity of Annex D, Ariel, Julie and I will be
propping up seats at the Intercontinental Hotel bar at approx
7pm. </div>
<div><br>
</div>
<div>With best wishes and thanks for being such amazing
colleagues throughout this arduous but tremendously worthwhile
effort,</div>
<div><br>
</div>
<div>Heather</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 23, 2019 at 2:26
PM Heather Forrest <<a href="mailto:haforrestesq@gmail.com"
moz-do-not-send="true">haforrestesq@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">Huge thanks to Ariel for taking the lead on
finalising the Joint Consultation Guidelines.
<div><br>
</div>
<div>For those who were unable to attend the call on Monday
with the ccNSO Guidelines Review Committee, I took away
from that meeting that we were all comfortable with the
substance of the Joint Consultation Guidelines. The call
mainly focused on the next steps and logistics, and in
particular whether and how there would be some sort of
symbolic joint signing in Montreal by the two Councils.
What did come to me as a surprise was that the ccNSO
potentially may not vote on this in Montreal - only a
surprise to me because it was Katrina and Bart who had,
months ago, proposed the timeline, and that's what we in
the DT have been working to since.</div>
<div><br>
</div>
<div>After follow-up conversations with Ariel, Julie and the
GNSO Council leadership team, I feel quite comfortable in
proposing that the DT remains on track to submit both the
Joint Consultation Guideline and the GNSO-specific
guideline of which the Joint Consultation Guideline is a
part in time for the Montreal Council meeting document
deadline. That deadline is this Sunday 2359 UTC. </div>
<div><br>
</div>
<div>You may recall that David was initially tasked during
our final review efforts to look over 18.12 - he did so,
raised a few queries to the DT list, but then suggested
that it be parked for yet one more final review once the
Joint Consultation Guidelines were completed. David's
queries have since been addressed by Ariel's revisions,
and in the meantime she is proposing some further
revisions to actually de-complicate the process. When we
first started our work, we agreed to try out using the
GNSO Input Process (the "GIP") as a vehicle for the GNSO
to weigh in on the triggering events of a Special IFR. As
we have learned along the way, and come to better
understand 18.12 and the Joint Consultation Guidelines, it
seems to me on careful discussion with Ariel and Julie
(and David, whose questions in final review quite rightly
provoked further consideration) that the GIP, which relies
on a Council member filing a request for action, isn't
actually what we need for 18.12, because the triggering
event for 18.12 isn't a request from a Councillor, but
rather the Bylaws themselves and the escalation and
failure to resolve a performance issue under the IANA
contract. No "request" from a Councillor is needed to kick
off the GNSO's provision of input. That said, there are
some very useful things in the GIP, once one leaves aside
the need for making a request, such as forming a small
team, the team preparing a report for Council's
consideration, etc, that serve this process well and do
not conflict with the Bylaws 18.12 provisions. </div>
<div><br>
</div>
<div>I note for the record David's earlier remarks on the
substance and interpretation of 18.12(a)(i)-(iv) and their
relationship to 18.3 and a regular IFRT. I am not
convinced that we can resolve the possible differences in
interpretation of these provisions until the event
actually occurs (hopefully never), but I also take comfort
in the fact that ICANN Legal is reviewing each Guideline,
and to the extent that we have made a material error in
judgment, we hope that can be pointed out to us. Further,
I take comfort in the fact that each of these Guidelines
is just that -a Guideline, not a compulsory rule imposed
on the GNSO Council. If circumstances require or warrant a
different course of action or timeline, Council has full
freedom to be nimble.</div>
<div><br>
</div>
<div>I am mindful that the timing is now tight, and that we
are all rather exhausted (mentally, physically) by the
enormous work effort we have sustained in the DT since
early this year. I personally believe that the edits that
Ariel will circulate to the GNSO Guideline are
uncontroversial, but I very much welcome everyone on the
DT to review. Remember that ICANN Legal is also reviewing
in the background, and will raise any concerns if these
arise. If we believe that more time is needed beyond this
Friday to finalise this last document, I can advise
Council and the ccNSO and we'll hold 18.12 back until
Council's December meeting. Once Ariel circulates the
final proposed 18.12 Guideline, I will ask that each DT
member state by Friday their position - can be one-on-one
to me or to the group, as each prefers. The options will
be to sign-off on the Guideline and submit to Council or
hold back for more time for a further review and
discussion.</div>
<div><br>
</div>
<div>Very best wishes,</div>
<div><br>
</div>
<div>Heather</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 23, 2019 at
1:40 PM Ariel Liang <<a
href="mailto:ariel.liang@icann.org" target="_blank"
moz-do-not-send="true">ariel.liang@icann.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span>Dear All, </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Following the meeting with
the ccNSO GRC on Monday, staff have resolved the
edits and comments on the Guidelines for Joint
Consultation on Initiation of a Special IFR:
<a
href="https://docs.google.com/document/d/1NnaaoWKJWUu0Cw3pphuvT0wycmMIXhQmYyy0daPmnbI/edit?usp=sharing"
target="_blank" moz-do-not-send="true">
https://docs.google.com/document/d/1NnaaoWKJWUu0Cw3pphuvT0wycmMIXhQmYyy0daPmnbI/edit?usp=sharing</a>.
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>There have been no
substantive changes on this document, so please
provide your final review by
<b><u>COB Friday, 25 October</u></b>. The aim is
to incorporate this document in the whole package
of guidelines for the GNSO Council to adopt at
ICANN66.
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>In addition, staff are in
process revising the GNSO internal guidelines for
Section 18.12, as we have realized that the GIP
may be an ‘overkill’ in the process and has been
overtaken by events. More details will be provided
when we circulate the revised guidelines tomorrow.
</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Thank you!</span></p>
<p class="MsoNormal"><span>Ariel</span></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>
</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>