<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I would suggest inclusion of all the relevant text from the RIR proposal in the note, as well as a tweak to the first few words of the first sentence:</div><div><br></div><div>The IETF consensus as reflected in draft-ietf-ianaplan-icg-response did not include a formal request to change the arrangements regarding the IANA trademark and the <a href="http://iana.org">iana.org</a> domain as a requirement of its transition proposal. But Section III.A.2 of the RIR proposal says: </div><div><br></div><div>"With regards to the IANA trademark and the <a href="http://IANA.ORG">IANA.ORG</a> domain, it is the expectation of the Internet Number Community that both are associated with the IANA Numbering Services and not with a particular IANA Numbering Services Operator. Identifying an organization that is not the IANA Numbering Services Operator and which will permanently hold these assets will facilitate a smooth transition should another operator (or operators) be selected in the future. It is the preference of the Internet Number Community that the IANA trademark and the <a href="http://IANA.ORG">IANA.ORG</a> domain name be transferred to an entity independent of the IANA Numbering Services Operator, in order to ensure that these assets are used in a non-discriminatory manner for the benefit of the entire community. From the Internet Number Community’s perspective, the IETF Trust would be an acceptable candidate for this role.” </div><div><br></div><div>The numbers proposal sees these changes as a requirement of the transition and the protocols parameters proposal does not. If these aspects of the proposals are perceived as incompatible would the numbers and protocol parameters communities be willing to modify their proposals to reconcile them?</div><br><div><div>On Feb 6, 2015, at 7:24 PM, Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">No problem.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="color: rgb(31, 73, 125);">“The IETF IANAPLAN WG did not think a formal request to change the arrangements regarding the IANA trademark and the<span class="Apple-converted-space"> </span><a href="http://iana.org/" style="color: purple; text-decoration: underline;">iana.org</a><span class="Apple-converted-space"> </span>domain was a requirement of its transition proposal. But Section III.A.2 of the RIR proposal says "With regards to the IANA trademark and the<span class="Apple-converted-space"> </span><a href="http://iana.org/" style="color: purple; text-decoration: underline;">IANA.ORG</a><span class="Apple-converted-space"> </span>domain, it is the expectation of the Internet Number Community that both are associated with the IANA Numbering Services and not with a particular IANA Numbering Services Operator." The numbers proposal sees these changes as a requirement of the transition and the protocols parameters proposal does not. If these aspects of the proposals are perceived as incompatible would the numbers and protocol parameters communities be willing to modify their proposals to reconcile them?"<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><a name="_MailEndCompose"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></a></div><div style="border-style: none none none solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;"><div><div style="border-style: solid none none; border-top-color: rgb(225, 225, 225); border-top-width: 1pt; padding: 3pt 0in 0in;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><span class="Apple-converted-space"> </span>Russ Housley [<a href="mailto:housley@vigilsec.com" style="color: purple; text-decoration: underline;">mailto:housley@vigilsec.com</a>]<span class="Apple-converted-space"> </span><br><b>Sent:</b><span class="Apple-converted-space"> </span>Friday, February 6, 2015 9:51 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Milton L Mueller<br><b>Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:internal-cg@icann.org" style="color: purple; text-decoration: underline;">internal-cg@icann.org</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [Internal-cg] Proposed question for the protocols OC<o:p></o:p></span></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Please change "protocols proposal" to "protocol parameters proposal".<o:p></o:p></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Please change "protocols community" to "protocol parameters community".<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">Russ<o:p></o:p></div><div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">On Feb 6, 2015, at 8:34 PM, Milton L Mueller wrote:<o:p></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><br><br><o:p></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;"><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Based on feedback from numbers, another slight revision:</span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div><div style="border-style: none none none solid; padding: 0in 0in 0in 4pt; z-index: auto;"><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">“The IETF IANAPLAN WG did not think a formal request to change the arrangements regarding the IANA trademark and the<span class="apple-converted-space"> </span><a href="http://iana.org/" style="color: purple; text-decoration: underline;"><span style="color: rgb(5, 99, 193);">iana.org</span></a><span class="apple-converted-space"> </span>domain was a requirement of its transition proposal. But Section III.A.2 of the RIR proposal says "With regards to the IANA trademark and the<span class="apple-converted-space"> </span><a href="http://iana.org/" style="color: purple; text-decoration: underline;"><span style="color: rgb(5, 99, 193);">IANA.ORG</span></a><span class="apple-converted-space"> </span>domain, it is the expectation of the Internet Number Community that both are associated with the IANA Numbering Services and not with a particular IANA Numbering Services Operator." The numbers proposal sees these changes as a requirement of the transition and the protocols proposal does not. If these aspects of the proposals are perceived as incompatible would the numbers and protocols communities be willing to modify their proposals to reconcile them?"</span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div></div></blockquote></div></div></div></div>_______________________________________________<br>Internal-cg mailing list<br><a href="mailto:Internal-cg@icann.org" style="color: purple; text-decoration: underline;">Internal-cg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/internal-cg" style="color: purple; text-decoration: underline;">https://mm.icann.org/mailman/listinfo/internal-cg</a></div></blockquote></div><br></body></html>