<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>In some ways we have already started on part of the next step, which includes assessing the compatibility of the proposals with each other. I think we should proceed with the rest of that step while we wait for responses, and then incorporate the responses as we receive them.</div><div><br></div><div>To Milton’s suggestion, I’m not clear on why we need to know how the communities intend to arrive at an answer to what is a fairly straightforward question (are you willing to modify your proposal?). I agree with Patrik’s suggestion of 2 weeks. We can always follow up with the communities to find out how long actually doing the modification might take, if they are willing to modify.</div><div><br></div><div>Alissa</div><br><div><div>On Feb 7, 2015, at 6:07 PM, joseph alhadeff <<a href="mailto:joseph.alhadeff@oracle.com">joseph.alhadeff@oracle.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000" 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;">Does waiting for the reply, impact the timing of any of the further review obligations we have?<br><div class="moz-cite-prefix">On 2/7/2015 8:58 PM, Milton L Mueller wrote:<br></div><blockquote cite="mid:b58ec5db011e4193b841c0f913e8b591@EX13-MBX-13.ad.syr.edu" type="cite"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">Alissa is awaiting suggestions for a date for a response to this question.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">My suggestion is that we request that they tell us within 30 days _<i>how</i>_ they plan to go about resolving this issue (e.g., meetings, etc.) and once they respond in that way we ask them to suggest a timeline for how quickly they think they can resolve it.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a moz-do-not-send="true" name="_MailEndCompose"><span style="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: 11pt; font-family: Calibri, sans-serif;"><b>From:</b><span class="Apple-converted-space"> </span><a class="moz-txt-link-abbreviated" href="mailto:internal-cg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">internal-cg-bounces@icann.org</a><span class="Apple-converted-space"> </span>[<a class="moz-txt-link-freetext" href="mailto:internal-cg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">mailto:internal-cg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Milton L Mueller<br><b>Sent:</b><span class="Apple-converted-space"> </span>Saturday, February 7, 2015 8:50 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Jennifer Chung; 'ICG'<br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [Internal-cg] Action items from ICG Face-to-Face Meeting #4, 6-7 February 2015<o:p></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">Jennifer,<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">You forgot the question we agreed to send jointly to the numbers and protocol parameters group.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">I was responsible for this, but yesterday when I said it was “done” I meant that the question had been approved by the group. I do not think it was “finished” in the sense that we have formally transmitted it to the two OCs. I would like to know how that will be done, and when.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);">For everyone’s reference, here is the agreed question:<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">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<span class="Apple-converted-space"> </span><a moz-do-not-send="true" href="http://iana.org/" style="color: rgb(149, 79, 114); text-decoration: underline;">iana.org</a><span class="Apple-converted-space"> </span>domain as a requirement of its transition proposal. But Section III.A.2 of the RIR proposal says: <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">"With regards to the IANA trademark and the<span class="Apple-converted-space"> </span><a moz-do-not-send="true" href="http://iana.org/" style="color: rgb(149, 79, 114); 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. 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 moz-do-not-send="true" href="http://iana.org/" style="color: rgb(149, 79, 114); text-decoration: underline;">IANA.ORG</a><span class="Apple-converted-space"> </span>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.” <o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">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></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span style="color: rgb(31, 73, 125);"> </span></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: 11pt; font-family: Calibri, sans-serif;"><b>From:</b><span class="Apple-converted-space"> </span><a moz-do-not-send="true" href="mailto:internal-cg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">internal-cg-bounces@icann.org</a><span class="Apple-converted-space"> </span>[<a moz-do-not-send="true" href="mailto:internal-cg-bounces@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">mailto:internal-cg-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Jennifer Chung<br><b>Sent:</b><span class="Apple-converted-space"> </span>Saturday, February 7, 2015 6:40 PM<br><b>To:</b><span class="Apple-converted-space"> </span>'ICG'<br><b>Subject:</b><span class="Apple-converted-space"> </span>[Internal-cg] Action items from ICG Face-to-Face Meeting #4, 6-7 February 2015<o:p></o:p></div></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Hello All,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">As reviewed by the ICG chairs, please find the list of action items from the ICG Face-to-Face Meeting #4 below:<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">1. Secretariat to summarize questions/answers resolved internally about the protocol parameters proposal and numbers proposal discussed.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">2. Arkko to compile a list of for a request for information from the protocol parameters community re jurisdiction, NTIA oversight and send it to internal-cg list.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">3. Wilson to request clarification from CRISP team, questions put forth by Arasteh (regarding Section II.B.2 and III.A of the numbers proposal).<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">4. ICG chairs to review details of the proposal finalization process and refine ICG timeline with assistance from Secretariat.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">5. Ismail, Arasteh, St. Amour, Alhadeff, Subrenat to continue working on community comments handling document with suggestions put forward by other ICG members.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">6. ICG to continue to discuss and agree on talking points and ICG chairs to send bullet points for Monday session on the internal-cg list.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">7. Fältström to communicate with CWG-IANA and CCWG-Accountability before coordinating ICG teleconference schedule.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Best Regards,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Jennifer<o:p></o:p></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" style="color: rgb(149, 79, 114); text-decoration: underline;">Internal-cg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/internal-cg" style="color: rgb(149, 79, 114); text-decoration: underline;">https://mm.icann.org/mailman/listinfo/internal-cg</a>
</pre></blockquote><br>_______________________________________________<br>Internal-cg mailing list<br><a href="mailto:Internal-cg@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;">Internal-cg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/internal-cg" style="color: rgb(149, 79, 114); text-decoration: underline;">https://mm.icann.org/mailman/listinfo/internal-cg</a><br></div></blockquote></div><br></body></html>