<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 15 (filtered medium)">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
</HEAD>
<BODY lang=EN-US dir=ltr link=blue vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Re para 98 I could agree with Milton.</DIV>
<DIV>Reading para X028, I don\u2019t get tempted of this kind of interpretation. The
text just says that the communities satisfaction with the IANA performance will
not be impacted \u2013 which to my knowledge is intended.</DIV>
<DIV><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=milton@gatech.edu
href="mailto:milton@gatech.edu">Mueller, Milton L</A> </DIV>
<DIV><B>Sent:</B> Tuesday, October 27, 2015 4:43 PM</DIV>
<DIV><B>To:</B> <A title=alissa@cooperw.in
href="mailto:alissa@cooperw.in">Alissa Cooper</A> ; <A
title=internal-cg@ianacg.org href="mailto:internal-cg@ianacg.org">IANA etc etc
Coordination Group</A> </DIV>
<DIV><B>Subject:</B> Re: [Internal-cg] Proposal for final
review</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'>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>All:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>I
went through this document as quickly as I could. It\u2019s in great shape overall. I
made some minor edits to the clean version in the attached draft, with tracking
turned on. There are a couple of substantive changes I propose which I will
discuss here: <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>Para
X028 currently says:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>\u201cAll
three communities determined that the global customers and partners of the IANA
services and their communities of stakeholders are presently satisfied with the
performance of the IANA functions by the IANA department of ICANN. The combined
proposal is not expected to impact that.\u201d<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>This
gives I think the (false) impression that the proposal just keeps everything the
same and the customers didn\u2019t want any change. However, all 3 communities also
made it clear that they want to be able to choose (or continue to choose) a
different IFO should the need arise, a capability which does _<I>not</I>_
currently exist for numbers and names, but which is created by this proposal.
Also if the customers wanted no change then why did the proposal create
PTI?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>So on
p. 28-9, paragraph 98 I edited the end of paragraph 98 to
read:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>98
All three communities determined that the global customers and partners of the
IANA services, including the gTLD and ccTLD registries and their communities of
stakeholders; the RIRs; and the IETF are presently satisfied with the
performance of the IANA functions by the IANA department of ICANN. The combined
proposal is structured such that the PTI will continue to provide the IANA
functions to its global customers and partners post-transition in essentially
the same manner as ICANN\u2019s IANA department does today. In the names community,
IANA customers expressed support for a clearer separation between ICANN as
policy developer and IANA as implementer, and the PTI separation accomplishes
this. Also, the proposal makes it possible for each operational community to
choose a different IFO should the need arise, a capability which does not
currently exist for numbers and names. Thus the needs and expectations of the
global customers and partners should continue to be satisfied after the
transition.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>Also,
on p. 30, para 108 implementation list I believe we need to
add:<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'>\u2022
Transfer of the IANA-related intellectual property and domain names to the
entity.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d'><o:p></o:p></SPAN> </P>
<DIV
style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in">
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'>From:</SPAN></B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif'> Internal-cg
[mailto:internal-cg-bounces@ianacg.org] <B>On Behalf Of </B>Alissa
Cooper<BR><B>Sent:</B> Monday, October 26, 2015 1:19 PM<BR><B>To:</B> IANA etc
etc Coordination Group<BR><B>Subject:</B> [Internal-cg] Proposal for final
review<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p></o:p> </P>
<P class=MsoNormal>Please find attached a redlined and clean copy of the
proposal reflected all changes agreed at the F2F. There are still a few spacing
and footnote numbering issues to be worked out once the secretariat produces the
PDF but otherwise this is the version intended for publication with our agreed
status update announcement on October 29.<o:p></o:p></P>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>If you see any errors in this version, please make them known
on the mailing list by 23:59 UTC on October 28. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Thanks,<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>Alissa<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal>Dropbox:<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><A
href="https://www.dropbox.com/s/yhvx3pl8hx2oju0/IANA-transition-proposal-v8.docx?dl=0">https://www.dropbox.com/s/yhvx3pl8hx2oju0/IANA-transition-proposal-v8.docx?dl=0</A><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><A
href="https://www.dropbox.com/s/pj6s0igu8s8k4tq/IANA-transition-proposal-v8-clean.docx?dl=0">https://www.dropbox.com/s/pj6s0igu8s8k4tq/IANA-transition-proposal-v8-clean.docx?dl=0</A><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV>
<DIV>
<P class=MsoNormal><o:p></o:p> </P></DIV></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>Internal-cg mailing
list<BR>Internal-cg@mm.ianacg.org<BR>http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org<BR></DIV></DIV></DIV></BODY></HTML>