<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>We should proceed as far as we can with the responses we have received. We should do this at a reasonably agressive pace. </div><div><br></div><div>Some reasons:</div><div><br></div><div>- We owe it to the communities that worked hard to meet the deadlines. We need to keep a positive relationship with them goong forward. They need to stay motivated. We should not frustrate them by appearing to be tardy.</div><div><br></div><div>- We gain time for discussing clarifications and improvements of the responses we already have with the respective communities. </div><div><br></div><div>- It makes sense get as much work out of the way as we can as early as possible to free up capacity for the later stages. </div><div><br></div><div>- We need to exercise our own machinery as much as we can.</div><div><br></div><div>So I wholeheartedly support proceeding as Alissa sugests. </div><div><br></div><div>Daniel<br><br><div><br></div>---<div><span class="Apple-style-span" style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.231373); -webkit-composition-frame-color: rgba(77, 128, 180, 0.231373); ">Sent from a handheld device.</span><br></div></div><div><br>On 15.01.2015, at 19:08, Alissa Cooper <<a href="mailto:alissa@cooperw.in">alissa@cooperw.in</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div>Hi Milton,</div><div><br></div><div>I suggested Jan 26 because our next call is on Jan 28. That way we can devote a good part of that call to starting the discussion about the protocol parameters proposal. We can continue that discussion in Singapore. </div><div><br></div><div>Since Step I of our finalization process involves evaluating the proposals individually <<a href="https://www.icann.org/en/system/files/files/iana-transition-assembly-finalization-24dec14-en.pdf">https://www.icann.org/en/system/files/files/iana-transition-assembly-finalization-24dec14-en.pdf</a>>, I think we can and should proceed with that step for the proposals we do receive. We’re aiming to get that done by Feb 15 according to our process.</div><div><br></div><div>Of course, the names work taking place right now is very important and folks who are heavily involved in that might not have as much time to review the protocol parameters proposal. I think that’s perfectly fine, since we have a couple people on the hook to do a thorough review of that proposal and bring their evaluations back to the rest of us.</div><div><br></div><div>Best,</div><div>Alissa</div><br><div><div>On Jan 15, 2015, at 7:43 AM, 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="#0563C1" vlink="#954F72" 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: 11pt; font-family: Calibri, sans-serif;">I’ve been looking at the total landscape related to IANA transition and I have a question about the Jan 26 deadline for reviewing the IETF proposal.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">There is a ton of work going on in the names CWG and CCWG in that time frame, and given the relatively unfinished state of the names work I think it’s more important to advance that work.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">At the same time, I am having trouble understanding what we can do with a review of the protocols proposal by Jan 26. Is the purpose to be able to discuss it at the Singapore meeting, or what?<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;">Milton L Mueller<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Laura J. and L. Douglas Meredith Professor<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Syracuse University School of Information Studies<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://faculty.ischool.syr.edu/mueller/" style="color: rgb(149, 79, 114); text-decoration: underline;">http://faculty.ischool.syr.edu/mueller/</a><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Internet Governance Project<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://internetgovernance.org/" style="color: rgb(149, 79, 114); text-decoration: underline;">http://internetgovernance.org</a><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>_______________________________________________<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></div></blockquote></div><br></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Internal-cg mailing list</span><br><span><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a></span><br></div></blockquote></body></html>