<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Predictably enough, Susan is demanding exactly what I told Keith
would happen...immediate development of the implementation of the
access model<br>
</p>
<div class="moz-forward-container">SP<br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Re: [Epdp-dt] EPDP Scope</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Sun, 15 Jul 2018 19:44:27 -0700</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Susan Kawaguchi <a class="moz-txt-link-rfc2396E" href="mailto:susankpolicy@gmail.com"><susankpolicy@gmail.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td>Drazek, Keith <a class="moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com"><kdrazek@verisign.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
<td>McGrady, Paul D. <a class="moz-txt-link-rfc2396E" href="mailto:PMcGrady@winston.com"><PMcGrady@winston.com></a>,
<a class="moz-txt-link-abbreviated" href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>
<a class="moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca"><stephanie.perrin@mail.utoronto.ca></a>,
<a class="moz-txt-link-abbreviated" href="mailto:Donna.Austin@team.neustar">Donna.Austin@team.neustar</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Donna.Austin@team.neustar"><Donna.Austin@team.neustar></a>,
<a class="moz-txt-link-abbreviated" href="mailto:marika.konings@icann.org">marika.konings@icann.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:marika.konings@icann.org"><marika.konings@icann.org></a>,
<a class="moz-txt-link-abbreviated" href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:caitlin.tubergen@icann.org"><caitlin.tubergen@icann.org></a>, <a class="moz-txt-link-abbreviated" href="mailto:haforrestesq@gmail.com">haforrestesq@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:haforrestesq@gmail.com"><haforrestesq@gmail.com></a>, <a class="moz-txt-link-abbreviated" href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:rafik.dammak@gmail.com"><rafik.dammak@gmail.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Hello All,
<div><br>
</div>
<div>I had intermittent access to the internet this weekend. A
few comments. </div>
<div><br>
</div>
<div>It appears that we use the term "Registration" data and
"Registrant" data interchangeably in the document. I think it
would be more concise to replace Registrant for Registration
through out the document. Registration data is not at issue
in the Temp Spec as it includes generated data, registry and
registrar data etc. along with the Registrant data. </div>
<div><br>
</div>
<div><br>
</div>
<div>I am also concerned with the 3rd deliverable, as we agreed
to move from phase 2 on access to a staggered approach I think
we should also give the working group the option of dealing
with the access piece in the report when they feel it is
appropriate. It imposes an unnecessary restriction. </div>
<div><br>
</div>
<div>It also sets up the access issue to have absolutely no hope
in being resolved before the Temp Spec expires. </div>
<div><br>
</div>
<div>I somehow missed the fact that the ePDP would issue a Final
report without actually doing all their work. From a purely
structural issue is this possible. Usually when a Final
report is issued the working group is done and it moves on to
an implementation phase. </div>
<div><br>
</div>
<div>Thank you for resolving the issue on the council voting I
agree with Paul on this issue. </div>
<div><br>
</div>
<div><br>
</div>
<div>Susan </div>
<div><br>
</div>
<div><br>
</div>
<div class="gmail_extra">
<div class="gmail_quote">On Sun, Jul 15, 2018 at 7:14 PM,
Drazek, Keith <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kdrazek@verisign.com" target="_blank">kdrazek@verisign.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div><span></span></div>
<div>
<div>Thanks very much Paul, I appreciate your response
and agree with your view on this. The Council would
need to vote to approve a motion objecting to the
consensus of the WG. Otherwise the WG consensus
would stand. </div>
<div><br>
</div>
<div>Regards,</div>
<div>Keith</div>
<div><br>
On Jul 15, 2018, at 9:45 PM, McGrady, Paul D. <<a
moz-do-not-send="true"
href="mailto:PMcGrady@winston.com" target="_blank">PMcGrady@winston.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div
class="m_2648086008221523898m_4786140953234300216WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">Thanks
Keith. Your changes are fine with me so
long as it is clear that the Council doesn’t
have to take a vote on whether or not it
objects. In other words, if the idea is
that some portion of the GNSO community does
object to the notion that the gating
questions have been answered, they would
need to bring a motion objecting and get it
past the Council. If that is the case, that
is fine with me. Thanks Keith!</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Best,</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Paul</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Drazek,
Keith [<a moz-do-not-send="true"
href="mailto:kdrazek@verisign.com"
target="_blank">mailto:kdrazek@verisign.com</a>]
<br>
<b>Sent:</b> Sunday, July 15, 2018 6:20 PM<br>
<b>To:</b> McGrady, Paul D. <<a
moz-do-not-send="true"
href="mailto:PMcGrady@winston.com"
target="_blank">PMcGrady@winston.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank">stephanie.perrin@mail.utoronto<wbr>.ca</a>;
<a moz-do-not-send="true"
href="mailto:susankpolicy@gmail.com"
target="_blank">susankpolicy@gmail.com</a>;
<a moz-do-not-send="true"
href="mailto:Donna.Austin@team.neustar"
target="_blank">
Donna.Austin@team.neustar</a>; <a
moz-do-not-send="true"
href="mailto:marika.konings@icann.org"
target="_blank">marika.konings@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:caitlin.tubergen@icann.org"
target="_blank">caitlin.tubergen@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:haforrestesq@gmail.com"
target="_blank">
haforrestesq@gmail.com</a>; <a
moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com"
target="_blank">rafik.dammak@gmail.com</a><br>
<b>Subject:</b> RE: [Epdp-dt] EPDP Scope</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Paul and Stephanie,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Please see my responses and
proposed path forward inline in red font
below.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal">Keith</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> McGrady,
Paul D. <<a moz-do-not-send="true"
href="mailto:PMcGrady@winston.com"
target="_blank">PMcGrady@winston.com</a>>
<br>
<b>Sent:</b> Sunday, July 15, 2018 4:29 PM<br>
<b>To:</b> Drazek, Keith <<a
moz-do-not-send="true"
href="mailto:kdrazek@verisign.com"
target="_blank">kdrazek@verisign.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank">stephanie.perrin@mail.utoronto<wbr>.ca</a>;
<a moz-do-not-send="true"
href="mailto:susankpolicy@gmail.com"
target="_blank">susankpolicy@gmail.com</a>;
<a moz-do-not-send="true"
href="mailto:Donna.Austin@team.neustar"
target="_blank">
Donna.Austin@team.neustar</a>; <a
moz-do-not-send="true"
href="mailto:marika.konings@icann.org"
target="_blank">marika.konings@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:caitlin.tubergen@icann.org"
target="_blank">caitlin.tubergen@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:haforrestesq@gmail.com"
target="_blank">
haforrestesq@gmail.com</a>; <a
moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com"
target="_blank">rafik.dammak@gmail.com</a><br>
<b>Subject:</b> [EXTERNAL] RE: [Epdp-dt]
EPDP Scope<br>
<b>Importance:</b> High</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1f497d">Thanks
Keith.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Regarding
Stephanie’s proposal to change “</span><span
style="font-family:"Calibri
Light",sans-serif">Does ICANN have
additional responsibilities to the data
subject beyond what is required by
applicable law?”
</span><span style="color:#1f497d">to “</span><span
style="font-family:"Calibri
Light",sans-serif">ICANN as a data
controller has specific duties to the
registrant or data subject under applicable
law. What other other legal or other
obligations should be noted by this EPDP WG
in its analysis, including any duties that
ICANN might have in its role as
administrator of a finite resource in the
Internet governance sphere?”</span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri
Light",sans-serif"> </span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri
Light",sans-serif">Respectfully, I
think the first sentence gets into answering
questions rather than posing them –
something we have tried to avoid from the
beginning. I think Stephanie’s statement in
that first new sentence is presupposed in
the question which she proposes to delete.
I think we should leave “Does ICANN have
additional responsibilities to the data
subject beyond what is required by
applicable law?” and not include her first
proposed new sentence.</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span
style="font-family:"Calibri
Light",sans-serif">Regarding the second
sentence “What other other legal or other
obligations should be noted by this EPDP WG
in its analysis, including any duties that
ICANN might have in its role as
administrator of a finite resource in the
Internet governance sphere?” – I simply have
no idea what this question is getting at.
What finite resource? What is a governance
sphere? Is there any way to tighten this up
so that it’s meaning is clear? Assuming we
can do that and that it is harmless when
completed, I see no reason not to tack it
on.</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:red">KEITH:
How about rephrasing this sentence as:
</span></p>
<p class="MsoNormal"><span style="color:red"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="color:red">“In addition to any
specific duties ICANN may have as data
controller, what other obligations should be
noted by this EPDP WG, including any duties
to registrants that are unique and specific
to ICANN’s role as the administrator of
policies and contracts governing gTLD domain
names.”</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1f497d">Lastly,
and most importantly, I am opposed to this
change: “and confirmation by the GNSO
Council” seen here in its context: “The
threshold for establishing “answered” for
the gating questions shall be consensus of
the WG and confirmation by the GNSO
Council.” Since the only way for the
Council to confirm something is through a
vote, what this is proposing is that there
must be a formal Council vote before we take
up unified access model (or whatever
Stephanie’s preferred term is). This is a
de facto 2 phase approach we have already
argued over and agreed we wouldn’t do. This
is important to the IPC, so it is a change
we really can’t live with. I’m troubled to
see this well settled argument rearing its
head again. We made a lot of good faith
compromises as a result of eliminating
formal phasing – including cooperating with
the “gating questions” idea you introduced.
This feels like a 14<sup>th</sup> hour bait
and switch. I hope you will take it out.</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:red">KEITH:
How about changing the proposed affirmative
approval threshold to non-objection, as
follows:</span></p>
<p class="MsoNormal"><span style="color:red"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="color:red">“Work on this topic shall
begin once the gating questions above have
been answered and finalized in preparation
for the Temporary Specification initial
report. The threshold for establishing
“answered” for the gating questions shall be
consensus of the WG and non-objection by the
GNSO Council.”</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Can
you please confirm receipt? Thanks!</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Best,</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Paul</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:red">KEITH:
I hope this helps bridge the remaining gap
and gets us to a final draft. If anyone has
further thoughts or concerns, raise them
now.
</span></p>
<p class="MsoNormal"><span style="color:red"> </span></p>
<p class="MsoNormal"><span style="color:red">Paul
and Stephanie, please respond so I can nail
this down and send to the DT list.
</span></p>
<p class="MsoNormal"><span style="color:red"> </span></p>
<p class="MsoNormal"><span style="color:red">Best,</span></p>
<p class="MsoNormal"><span style="color:red">Keith</span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times
New Roman",serif;color:red"> </span></p>
<p class="MsoNormal"><span
style="font-family:"Calibri
Light",sans-serif"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Drazek,
Keith [<a moz-do-not-send="true"
href="mailto:kdrazek@verisign.com"
target="_blank">mailto:kdrazek@verisign.com</a>]
<br>
<b>Sent:</b> Sunday, July 15, 2018 2:49 PM<br>
<b>To:</b> McGrady, Paul D. <<a
moz-do-not-send="true"
href="mailto:PMcGrady@winston.com"
target="_blank">PMcGrady@winston.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank">stephanie.perrin@mail.utoronto<wbr>.ca</a>;
<a moz-do-not-send="true"
href="mailto:susankpolicy@gmail.com"
target="_blank">susankpolicy@gmail.com</a>;
<a moz-do-not-send="true"
href="mailto:Donna.Austin@team.neustar"
target="_blank">
Donna.Austin@team.neustar</a>; <a
moz-do-not-send="true"
href="mailto:marika.konings@icann.org"
target="_blank">marika.konings@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:caitlin.tubergen@icann.org"
target="_blank">caitlin.tubergen@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:haforrestesq@gmail.com"
target="_blank">
haforrestesq@gmail.com</a>; <a
moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com"
target="_blank">rafik.dammak@gmail.com</a><br>
<b>Subject:</b> RE: [Epdp-dt] EPDP Scope</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hi all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Attached is the latest
version of the red-line with Stephanie’s edits
incorporated. She and I just spoke on the
phone and walked through them, and we both
realized there was some confusion this morning
around which version of Section J was most
recent, but that’s now straightened out. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">According to Stephanie,
NCSG still has significant concerns about any
discussion of unified access/accreditation
<u>models</u> before finalizing the Initial
Report. I explained the gating questions are
designed to ensure we focus in the near term
on the Temp Spec and answer the necessary
questions before designing something with
incomplete data.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Paul and Susan, please
review and let us know if these new edits are
acceptable or if you have concerns. My goal is
still to get this finalized tonight. The
previous edits from the last version are still
showing, and I noted the new edits from
Stephanie by adding a comment box for each.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks in advance.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Keith</p>
<p class="MsoNormal"> </p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> McGrady,
Paul D. <<a moz-do-not-send="true"
href="mailto:PMcGrady@winston.com"
target="_blank">PMcGrady@winston.com</a>>
<br>
<b>Sent:</b> Sunday, July 15, 2018 1:36 PM<br>
<b>To:</b> Drazek, Keith <<a
moz-do-not-send="true"
href="mailto:kdrazek@verisign.com"
target="_blank">kdrazek@verisign.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank">stephanie.perrin@mail.utoronto<wbr>.ca</a>;
<a moz-do-not-send="true"
href="mailto:susankpolicy@gmail.com"
target="_blank">susankpolicy@gmail.com</a>;
<a moz-do-not-send="true"
href="mailto:Donna.Austin@team.neustar"
target="_blank">
Donna.Austin@team.neustar</a>; <a
moz-do-not-send="true"
href="mailto:marika.konings@icann.org"
target="_blank">marika.konings@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:caitlin.tubergen@icann.org"
target="_blank">caitlin.tubergen@icann.org</a>;
<a moz-do-not-send="true"
href="mailto:haforrestesq@gmail.com"
target="_blank">
haforrestesq@gmail.com</a>; <a
moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com"
target="_blank">rafik.dammak@gmail.com</a><br>
<b>Subject:</b> [EXTERNAL] RE: [Epdp-dt]
EPDP Scope</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1f497d">Thanks
Keith.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Since
you are doing some after-deadline edits,
some on the IPC wonder whether the questions
at c) are necessary gating questions for
discussion of a unified access model. I
admit that this is further in the weeds that
I am comfortable, but I wonder if you could
look at those again and see if they can be
removed from the gating questions? If they
can’t be removed, can I have a few sentences
on why they need to be gating questions that
I can send back to those who asked?</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Also,
with after deadline changes form the NCUC,
the IPC will need to be able to see what the
proposed changes will be before we can agree
that the draft charter is “final.” 13<sup>th</sup>
hour changes are sometimes benign or
sometimes they are designed to try to get
through changes at the last minute under
pressure that the small team would not have
agreed to earlier. So, I guess I will have
to reserve judgment on those until we see
them.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Thanks
so much and hang in there!</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Best,</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Paul</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<div>
<div style="border:none;border-top:solid
#e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Epdp-dt [<a
moz-do-not-send="true"
href="mailto:epdp-dt-bounces@icann.org"
target="_blank">mailto:epdp-dt-bounces@icann.<wbr>org</a>]
<b>On Behalf Of </b>Drazek, Keith via
Epdp-dt<br>
<b>Sent:</b> Sunday, July 15, 2018 9:28 AM<br>
<b>To:</b> Drazek, Keith <<a
moz-do-not-send="true"
href="mailto:kdrazek@verisign.com"
target="_blank">kdrazek@verisign.com</a>><br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:Epdp-dt@icann.org"
target="_blank">Epdp-dt@icann.org</a><br>
<b>Subject:</b> Re: [Epdp-dt] EPDP Scope</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hi all. Please wait
before reviewing. I may have jumped the gun
and we may have more suggested edits
incoming from NCSG.<span
style="font-size:12.0pt"></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thanks,</p>
</div>
<div>
<p class="MsoNormal">Keith</p>
</div>
<div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><br>
On Jul 15, 2018, at 8:44 AM, Drazek, Keith
via Epdp-dt <<a moz-do-not-send="true"
href="mailto:epdp-dt@icann.org"
target="_blank">epdp-dt@icann.org</a>>
wrote:</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi all,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As discussed on
Wednesday’s EPDP Drafting Team call,
attached is the final draft of the EPDP
charter scope section.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I received a few
suggested edits from Stephanie and Darcy
and did my best to incorporate/address
them. The small group has reviewed and
agreed this is ready for approval at the
19 July Council meeting.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks to everyone for
your contributions to this effort.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">Keith</p>
</div>
</blockquote>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times
New Roman",serif"><Updated Scope
Section 15 July 2018 -- Consolidated
Edits.docx></span></p>
</div>
</blockquote>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times
New Roman",serif"><Updated Scope
Section 15 July 2018 -- Consolidated
Edits CLEAN.docx></span></p>
</div>
</blockquote>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times
New Roman",serif">______________________________<wbr>_________________<br>
Epdp-dt mailing list<br>
<a moz-do-not-send="true"
href="mailto:Epdp-dt@icann.org"
target="_blank">Epdp-dt@icann.org</a><br>
<a moz-do-not-send="true"
href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fepdp-dt&data=02%7C01%7Cpmcgrady%40winston.com%7C0921852e6c3241b372f308d5ea5f2fef%7C12a8aae45e2f4ad8adab9375a84aa3e5%7C0%7C0%7C636672616898611630&sdata=vxYmX%2FaQPOzgFPCOr57t3rR48fCa4%2FXGpNfssGVDt1w%3D&reserved=0"
target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/epdp-dt</a></span></p>
</div>
</blockquote>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"> </span></p>
<div class="MsoNormal" style="text-align:center"
align="center"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray">
<hr align="center" size="3" width="100%">
</span></div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray">The
contents of this message may be privileged
and confidential. If this message has been
received in error, please delete it without
reading it. Your receipt of this message is
not intended to waive any applicable
privilege. Please do not disseminate this
message without the permission of the
author. Any tax advice contained in this
email was not intended to be used, and
cannot be used, by you (or any other
taxpayer) to avoid penalties under
applicable tax laws and regulations. </span></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>