<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
OECD meeting is running long so I won't be able to join the call.
On the accountability issue, I'm fine with the concept of leaving it
to the individual communities to be the one who raise the issue to
us.<br>
<div class="moz-cite-prefix">On 12/10/2014 5:21 AM, WUKnoben wrote:<br>
</div>
<blockquote cite="mid:F99CE76F2D164F12B53386039A382A19@WUKPC"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR:
#000000">
<div>I’ve inserted some comments to be discussed.</div>
<div> </div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR:
#000000"><br>
<br>
Best regards<br>
<br>
Wolf-Ulrich<br>
<br>
</div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline">
<div style="FONT: 10pt tahoma">
<div> </div>
<div style="BACKGROUND: #f5f5f5">
<div style="font-color: black"><b>From:</b> <a
moz-do-not-send="true" title="alissa@cooperw.in"
href="mailto:alissa@cooperw.in">Alissa Cooper</a> </div>
<div><b>Sent:</b> Wednesday, December 10, 2014 12:19 AM</div>
<div><b>To:</b> <a moz-do-not-send="true"
title="joseph.alhadeff@oracle.com"
href="mailto:joseph.alhadeff@oracle.com">joseph
alhadeff</a> </div>
<div><b>Cc:</b> <a moz-do-not-send="true"
title="internal-cg@icann.org"
href="mailto:internal-cg@icann.org">ICG</a> </div>
<div><b>Subject:</b> Re: [Internal-cg] Please review:
proposal finalization process</div>
</div>
</div>
<div> </div>
</div>
<div style="FONT-SIZE: small; TEXT-DECORATION: none;
FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal;
COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline">On Dec
9, 2014, at 2:53 PM, joseph alhadeff <<a
moz-do-not-send="true"
href="mailto:joseph.alhadeff@oracle.com">joseph.alhadeff@oracle.com</a>>
wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF">Alissa, Milton:<br>
<br>
Accountability. The phrasing may not be correct to
avoid confusion, it was whether we needed to have a
cross reference on whether any developments of the
ICANN accountability process could/had impact/ed the
accountability processes of the member communities.
This is a foward looking factor that may never arise,
but there could be sshadow cast by developments in the
ICANN accountability work. More of a place holder
than anything.<br>
</div>
</blockquote>
<div> </div>
<div>Ok. I still think the first question in 2b covers
this, but perhaps it will become more clear if we can
discuss it on the call. I think it’s important that we
not build in a way for us to second-guess the substance
of the proposals we receive from any of the operational
communities. For example, if between the time we receive
the names community proposal and the time we’re wrapping
up step 2, something happens in the ICANN accountability
work that undermines the names proposal, I want the
names community to be the judge of that, not us.</div>
<br>
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF"><br>
The General comment. Do we accept any comments from
stakeholders on individual community proposals after
they are released by the community and while we are in
the process of reviewing them in step 1. <br>
</div>
</blockquote>
<div> </div>
<div>Of course people can submit comments to us at any
time, but I don’t think we should specifically seek
comments in the step 1 phase, because commenters would
be commenting on the same substance that they had an
opportunity to comment on in the operational communities
themselves. We have two public comment periods planned
for after changes may have been made depending on our
assessments.</div>
<div> </div>
<div>Alissa</div>
<br>
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF"><br>
Thanks-<br>
<br>
Joe<br>
<br>
<div class="moz-cite-prefix">On 12/9/2014 5:32 PM,
Alissa Cooper wrote:<br>
</div>
<blockquote
cite="mid:252F50A9-15E4-4893-8B93-24B9865B532D@cooperw.in"
type="cite">
<div>Hi Joe,</div>
<div> </div>
<div>Couple of questions below.</div>
<div> </div>
<div>
<div>On Dec 9, 2014, at 8:41 AM, joseph alhadeff
<<a href="mailto:joseph.alhadeff@oracle.com"
moz-do-not-send="true">joseph.alhadeff@oracle.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="WHITE-SPACE: normal; WORD-SPACING:
0px; TEXT-TRANSFORM: none; FONT: 12px
helvetica; LETTER-SPACING: normal;
TEXT-INDENT: 0px; -webkit-text-stroke-width:
0px" text="#000000" bgcolor="#FFFFFF">Colleagues
as I may not be able to make the call, I
wanted to provide some high level observations
and minor proposed edits (attached in redline
in the document):<br>
<br>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: symbol"><span>·<span
style="FONT: 7pt 'Times New Roman'">
<span class="Apple-converted-space"> </span></span></span></span><span
style="FONT-FAMILY: arial, sans-serif">(1a
2<sup>nd</sup><span
class="Apple-converted-space"> </span>bullet)Whether
input/comments the ICG received directly<span
class="Apple-converted-space"> </span><span
style="COLOR: red">that</span><span
class="Apple-converted-space"> </span>were
shared with the operational community<span
class="Apple-converted-space"> </span><span
style="COLOR: red">were</span><span
class="Apple-converted-space"> </span><font
color="#ff0000">considered</font>/addressed.</span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><br>
<span style="FONT-FAMILY: arial, sans-serif"><o:p></o:p></span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: symbol"><span>·<span
style="FONT: 7pt 'Times New Roman'">
<span class="Apple-converted-space"> </span></span></span></span><span
style="FONT-FAMILY: arial, sans-serif">(Para
2) According to the ICG Charter, its role
is not to draft a single transition
proposal, but rather to assemble a
proposal from component proposals.<span> <span
class="Apple-converted-space"> </span></span>These
components are<span
class="Apple-converted-space"> </span><span
style="COLOR: red">not</span>expected to
be<span class="Apple-converted-space"> </span><span
style="COLOR: red">uniform</span><span
class="Apple-converted-space"> </span></span><span
class="MsoCommentReference"><span
style="FONT-SIZE: 8pt"><a id="_anchor_1"
class="msocomanchor"
language="JavaScript"
href="x-msg://108/#_msocom_1"
name="_msoanchor_1"
moz-do-not-send="true">[j1]</a><span> </span></span></span><span
style="FONT-FAMILY: arial, sans-serif">as
they relate to the specific IANA functions
which are of interest to each operational
community.</span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><br>
<span style="FONT-FAMILY: arial, sans-serif"><o:p></o:p></span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: symbol"><span>·<span
style="FONT: 7pt 'Times New Roman'">
<span class="Apple-converted-space"> </span></span></span></span><span
style="FONT-FAMILY: arial, sans-serif">(2a)
Compatibility and interoperability: Do the
proposals work together in a single
unified proposal? Do they suggest any
arrangements that are not compatible with
each other? Is the handling of all<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true">possibly
conflicting overlaps</a></span><span
class="MsoCommentReference"><span
style="FONT-SIZE: 8pt"><a id="_anchor_2"
class="msocomanchor"
language="JavaScript"
href="x-msg://108/#_msocom_2"
name="_msoanchor_2"
moz-do-not-send="true">[j2]</a><span> </span></span></span><span
style="FONT-FAMILY: arial, sans-serif"><span
class="Apple-converted-space"> </span>between
the functions resolved in a workable
manner?</span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><br>
<span style="FONT-FAMILY: arial, sans-serif"><o:p></o:p></span></div>
<div style="FONT-SIZE: 10pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-SIZE: 12pt; FONT-FAMILY:
symbol"><span>·<span> <span
class="Apple-converted-space"> </span></span></span></span><span
style="FONT-SIZE: 12pt; FONT-FAMILY:
arial, sans-serif">(2b) comment from
previous round:<span
class="Apple-converted-space"> </span></span><span
style="FONT-SIZE: 12pt; FONT-FAMILY:
arial, sans-serif">Do we add a cross
reference to overall accountability work
here: Proposal Do any of the changes
proposed in the relevant stream of ICANN
accountability work negatively impact any
of the operations com unity accountability
functions outlined in the unified
proposal?</span></div>
</div>
</blockquote>
<div> </div>
<div>Milton had asked you to clarify what you mean
by “operations community accountability
functions.” I am also having trouble
understanding what you mean with your suggestion
here, or what is not already covered by the fact
that we are already asking "Do the proposals
together include appropriate and properly
supported independent accountability mechanisms
for running the IANA function?"</div>
<br>
<blockquote type="cite">
<div style="WHITE-SPACE: normal; WORD-SPACING:
0px; TEXT-TRANSFORM: none; FONT: 12px
helvetica; LETTER-SPACING: normal;
TEXT-INDENT: 0px; -webkit-text-stroke-width:
0px" text="#000000" bgcolor="#FFFFFF">
<div style="FONT-SIZE: 10pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><br>
<span style="FONT-SIZE: 12pt; FONT-FAMILY:
arial,
sans-serif"><o:p></o:p></span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: symbol"><span>·<span
style="FONT: 7pt 'Times New Roman'">
<span class="Apple-converted-space"> </span></span></span></span><span
style="FONT-FAMILY: arial, sans-serif">(2c)
I think the RFP called for a description
of appropriate testing, therefore it
should be part of the submission.<span> <span
class="Apple-converted-space"> </span></span>How
its described is not the issue, that its
described and sufficient is.</span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><br>
<span style="FONT-FAMILY: arial, sans-serif"><o:p></o:p></span></div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: symbol"><span>·<span
style="FONT: 7pt 'Times New Roman'">
<span class="Apple-converted-space"> </span></span></span></span><span
style="FONT-FAMILY: arial, sans-serif">General
Question.<span> <span
class="Apple-converted-space"> </span></span>Do
we have a general comment process for a
proposal that is going through step 1, or
just a process who don’t think their
comments were taken on board.</span></div>
</div>
</blockquote>
<div> </div>
<div>What do you mean by a “general comment
process”?</div>
<div> </div>
<div>Thanks,</div>
<div>Alissa</div>
<br>
<blockquote type="cite">
<div style="WHITE-SPACE: normal; WORD-SPACING:
0px; TEXT-TRANSFORM: none; FONT: 12px
helvetica; LETTER-SPACING: normal;
TEXT-INDENT: 0px; -webkit-text-stroke-width:
0px" text="#000000" bgcolor="#FFFFFF">
<div style="FONT-SIZE: 12pt; FONT-FAMILY:
calibri, sans-serif; MARGIN: 0in 0in 0pt
0.75in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: arial, sans-serif"><o:p></o:p></span></div>
<div>
<hr class="msocomoff" align="left" size="1"
width="33%">
<div>
<div id="_com_1" class="msocomtxt"
language="JavaScript"><span><a
name="_msocom_1"
moz-do-not-send="true"></a></span>
<div style="FONT-SIZE: 10pt;
FONT-FAMILY: calibri, sans-serif;
MARGIN: 0in 0in 0pt"><span
class="MsoCommentReference"><span
style="FONT-SIZE: 8pt"><span> <a
class="msocomoff"
href="x-msg://108/#_msoanchor_1"
moz-do-not-send="true">[j1]</a></span></span></span>Remove
“essentially disjoint” as may be read
by some as incoherent within their own
logic as opposed to in comparison to
others.<o:p></o:p></div>
</div>
</div>
<div>
<div id="_com_2" class="msocomtxt"
language="JavaScript"><span><a
name="_msocom_2"
moz-do-not-send="true"></a></span>
<div style="FONT-SIZE: 10pt;
FONT-FAMILY: calibri, sans-serif;
MARGIN: 0in 0in 0pt"><span
class="MsoCommentReference"><span
style="FONT-SIZE: 8pt"><span> <a
class="msocomoff"
href="x-msg://108/#_msoanchor_2"
moz-do-not-send="true">[j2]</a></span></span></span>An
overlap may not be necessarily
conflicting and may not need to be
resolved.<o:p></o:p></div>
</div>
</div>
</div>
<div> </div>
<div class="moz-cite-prefix">On 12/8/2014
10:44 AM, Alissa Cooper wrote:<br>
</div>
<blockquote
cite="mid:091F653C-FCE5-488B-B5CD-B5E4E6E543DD@cooperw.in"
type="cite">All,
<div> </div>
<div>Please take a look at the proposal
finalization process document and the
thread below. We really need to wrap this
up, hopefully on this week’s call or
shortly thereafter.</div>
<div> </div>
<div>Thanks,</div>
<div>Alissa<br>
<div>
<div> </div>
<div>Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="MARGIN: 0px"><span
style="FONT-FAMILY: helvetica"><b>From:<span
class="Apple-converted-space"> </span></b></span><span
style="FONT-FAMILY: helvetica">Alissa
Cooper <<a
href="mailto:alissa@cooperw.in"
moz-do-not-send="true">alissa@cooperw.in</a>><br>
</span></div>
<div style="MARGIN: 0px"><span
style="FONT-FAMILY: helvetica"><b>Subject:<span
class="Apple-converted-space"> </span></b></span><span
style="FONT-FAMILY: helvetica"><b>Re:
[Internal-cg] Proposal
finalization process v3</b><br>
</span></div>
<div style="MARGIN: 0px"><span
style="FONT-FAMILY: helvetica"><b>Date:<span
class="Apple-converted-space"> </span></b></span><span
style="FONT-FAMILY: helvetica">December
1, 2014 at 3:37:31 PM PST<br>
</span></div>
<div style="MARGIN: 0px"><span
style="FONT-FAMILY: helvetica"><b>To:<span
class="Apple-converted-space"> </span></b></span><span
style="FONT-FAMILY: helvetica">Paul
Wilson <<a
href="mailto:pwilson@apnic.net"
moz-do-not-send="true">pwilson@apnic.net</a>><br>
</span></div>
<div style="MARGIN: 0px"><span
style="FONT-FAMILY: helvetica"><b>Cc:<span
class="Apple-converted-space"> </span></b></span><span
style="FONT-FAMILY: helvetica">ICG
<<a
href="mailto:internal-cg@icann.org"
moz-do-not-send="true">internal-cg@icann.org</a>><br>
</span></div>
<div> </div>
<div>
<div style="WORD-WRAP: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break:
after-white-space">
<div>Hi Paul,</div>
<div> </div>
<div>I reviewed your proposed
edits to v3 and my comments are
below. I’ve also uploaded and
attached an edited version that
reflects my comments and
includes the finalization
process steps provided by Kuo.
<<a
href="https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process"
moz-do-not-send="true">https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process</a>></div>
<div> </div>
<div>
<div>On Nov 9, 2014, at 4:58 PM,
Paul Wilson <<a
href="mailto:pwilson@apnic.net"
moz-do-not-send="true">pwilson@apnic.net</a>>
wrote:</div>
<br
class="Apple-interchange-newline">
<blockquote type="cite">Hi all,<br>
<br>
I’ve proposed a bunch of edits
to this document, attached,
and also in dropbox here:<br>
<br>
<a
href="https://www.dropbox.com/s/wvemyk00s5l86w9/proposal-finalization-process-v3-pw.docx?dl=0"
moz-do-not-send="true">https://www.dropbox.com/s/wvemyk00s5l86w9/proposal-finalization-process-v3-pw.docx?dl=0</a><br>
<br>
<br>
Some of these changes reflect
my understanding of the
timeline, as shown in the
Excel file here:<br>
<br>
<a
href="https://www.dropbox.com/s/07zp3xlgx2uvwcs/TimelineDiscussion-v7.docx?dl=0"
moz-do-not-send="true">https://www.dropbox.com/s/07zp3xlgx2uvwcs/TimelineDiscussion-v7.docx?dl=0</a><br>
<br>
In particular this timeline
show the release of a draft
proposal in March, and a final
proposal in June; so I’ve
added these extra steps to the
process.<br>
</blockquote>
<div> </div>
<div>Agreed, good to have these
other milestones in there.</div>
<br>
<blockquote type="cite"><br>
<br>
Also, please note I’ve
proposed a few substantial
additional steps in this
process:<br>
<br>
- A public call for comments
on the community proposal
development processes
(deadline 31 Jan 2015); this
will allow us to formally
gather remaining concerns, or
statements of support for the
processes which produced
community proposals.<br>
</blockquote>
<div> </div>
<div>I have concerns about
asking the communities to
duplicate efforts here. RFP
Section VI already asks the
communities to document their
processes, level of consensus
achieved, and areas of
contention or disagreement. We
also made it explicit in the
RFP that if people felt that
they could not provide
comments within those
processes, they could send
them to the ICG forum <<a
href="http://forum.icann.org/lists/icg-forum/"
moz-do-not-send="true">http://forum.icann.org/lists/icg-forum/</a>>
and we’ve been passing those
on to the communities.</div>
<div> </div>
<div>The target deadline for RFP
responses is 15 January, so I
don’t think we want to ask
people to separately document
similar information in a
parallel process that we run
ourselves at the same time
when we’re expecting the
communities to be focusing on
finishing their RFP responses.
I also do not think it’s
appropriate for us to try to
circumvent the community
processes — if the process
comments we receive after
receiving the proposals
themselves and the statements
made in the proposals are
inconsistent, it’s not clear
what we would do with that
information.</div>
<div> </div>
<div>My edits in the attached
reflect this view — I’ve
re-combined into a single step
1 the ICG’s initial reviews of
both process and substance.</div>
<br>
<blockquote type="cite"><br>
- A specific provision for ICG
consultation with communities
and other stakeholders during
assessment of the first draft
proposal.<br>
<br>
- Incorporating the ICANN
meetings in February and June
2015 into the process as
opportunities for (in Feb)
communities to present their
proposals to the ICANN
audience, and then (in June)
ICG to present the final
transition proposal.<br>
<br>
- Presentation of the final
proposal to the ICANN board,
during a meeting with them;
rather than mere
“transmission” to them.<br>
</blockquote>
<div> </div>
<div>I would prefer if we not be
overly prescriptive about any
of the above items, nor about
the exact structure or format
of any text we might draft to
accompany the transition
proposal. We have already
declared in the timeline our
intention to consult with
everyone, so I don’t think we
need to say it again.
Obviously we will be talking
to people at various ICANN
meetings, but there will
surely be other venues where
the proposal gets discussed
(as it should be), so I’d
rather not single out any
particular meetings in this
document. And I’m not sure why
we would need to specifically
meet the ICANN Board in order
to send them the final
proposal, particularly in
light the statement of
finalization steps that we now
have from Kuo.</div>
<div> </div>
<div>Looking forward to feedback
from you and others.</div>
<div> </div>
<div>Thanks,</div>
<div>Alissa</div>
<div> </div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
=<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<div>
<div>
<blockquote type="cite">
<div style="WORD-WRAP: break-word;
-webkit-nbsp-mode: space;
-webkit-line-break:
after-white-space">
<div><br>
<blockquote type="cite"><br>
I’ve highlighted these additions
in yellow, to distinguish them
from other edits.<br>
<br>
(and these are open to
discussion of course).<br>
<br>
Thanks,<br>
<br>
Paul.<br>
<br>
<span><proposal-finalization-process-v3-pw.docx></span><br>
<br>
________________________________________________________________________<br>
Paul Wilson, Director-General,
APNIC <<a
href="mailto:dg@apnic.net"
moz-do-not-send="true">dg@apnic.net</a>><br>
<a href="http://www.apnic.net/"
moz-do-not-send="true">http://www.apnic.net</a><span
class="Apple-converted-space"> </span>
+61 7 3858 3100<br>
<br>
<br>
<br>
On 5 Nov 2014, at 4:11 am,
Alissa Cooper <<a
href="mailto:alissa@cooperw.in"
moz-do-not-send="true">alissa@cooperw.in</a>>
wrote:<br>
<br>
<blockquote type="cite">Attached
and in Dropbox is an updated
version of the proposal
finalization process document.
Joe did the heavy lifting to
incorporate edits based on our
discussion in LA. I have also
incorporate the appropriate
section of Lynn’s text
concerning the role of ICANN
in the submission process.
However, I think the full list
of Lynn’s bullets belong in a
separate statement that is
specifically about
expectations concerning
ICANN/ICANN Board/NTIA
participation during the
entire transition plan
development process. I think
the attached document should
remain focused on proposal
finalization, and ultimately
the content of section 4
should directly reflect the
appropriate portion of
whatever final content emerges
from the thread that Lynn
started.<br>
<br>
Feedback is of course welcome,
and there are a few comments
in the document from Joe and
myself that are worth
discussion. I have attached a
clean copy; a redlined version
is also available in Dropbox.<br>
<br>
Thanks,<br>
Alissa<br>
<br>
<proposal-finalization-process-v3.docx>_______________________________________________<br>
Internal-cg mailing list<br>
<a
href="mailto:Internal-cg@icann.org"
moz-do-not-send="true">Internal-cg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/internal-cg"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
</blockquote>
<br>
</blockquote>
</div>
<div> </div>
</div>
_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org"
moz-do-not-send="true">Internal-cg@icann.org</a><br>
<a class="moz-txt-link-freetext"
href="https://mm.icann.org/mailman/listinfo/internal-cg"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
</blockquote>
</div>
<div> </div>
</div>
=<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Internal-cg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Internal-cg@icann.org" moz-do-not-send="true">Internal-cg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/internal-cg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/internal-cg</a></pre>
</blockquote>
<br>
<span><proposal-finalization-process-v3-pw-alc-jha.docx></span>_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org"
moz-do-not-send="true">Internal-cg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/internal-cg"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
<p>
</p>
<hr>
_______________________________________________<br>
Internal-cg mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>