<HTML xmlns:o><HEAD>
<META content="text/html charset=windows-1252" http-equiv=Content-Type></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
dir=ltr>
<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 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 title=joseph.alhadeff@oracle.com
href="mailto:joseph.alhadeff@oracle.com">joseph alhadeff</A> </DIV>
<DIV><B>Cc:</B> <A 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
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>
<HR>
_______________________________________________<BR>Internal-cg mailing
list<BR>Internal-cg@icann.org<BR>https://mm.icann.org/mailman/listinfo/internal-cg<BR></DIV></DIV></DIV></BODY></HTML>