<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Colleagues:<br>
    <br>
    I agree focus should be on the time needed to implement the changes,
    but don't want to overstate our position either.  While I don't
    believe that ICANN can change our proposal, I also don't think we
    can compel them to accept it. We should never arrive at this point
    as they should have provided input to us and the communities along
    the way to avoid a last minute impasse.  Perhaps we can phrase it as
    time needed for implementation of the proposal after the Bard has
    finalized its review?<br>
    <br>
    Joe  <br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 6/13/2015 12:06 PM, Drazek, Keith
      wrote:<br>
    </div>
    <blockquote
      cite="mid:4410ABE9-68E8-4C29-8351-99091A199D60@verisign.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>I share Milton's concerns.</div>
      <div><br>
      </div>
      <div>Regards,</div>
      <div>Keith Drazek<br>
      </div>
      <div><br>
        On Jun 13, 2015, at 10:13 AM, Milton L Mueller <<a
          moz-do-not-send="true" href="mailto:mueller@syr.edu">mueller@syr.edu</a>>
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <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;}
@font-face
        {font-family:Cambria;
        panose-1:2 4 5 3 5 4 6 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.apple-converted-space
        {mso-style-name:apple-converted-space;}
span.EmailStyle18
        {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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
          <div class="WordSection1">
            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
            <div style="border:none;border-left:solid blue
              1.5pt;padding:0in 0in 0in 4.0pt">
              <div>
                <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                  <div>
                    <div>
                      <div>
                        <div>
                          <p class="MsoNormal"><span
                              style="font-family:"Cambria",serif">With
                              regards to the path leading to
                              implementation, the Board believes that it
                              will be necessary for ICANN to follow its
                              normal processes for dealing with
                              reviews.  This will include the normal
                              process for bylaws changes, where the
                              proposed new text will be published for
                              public comment before Board approval, and
                              the normal process of taking public
                              comment for important implementation
                              options and details.<o:p></o:p></span></p>
                        </div>
                        <div>
                          <p class="MsoNormal"><span
                              style="font-family:"Cambria",serif"> <o:p></o:p></span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM:
                              This seems a bit strange to me. As I
                              understand it, we are talking about bylaw
                              changes required to implement the
                              finalized ICG proposal that has been
                              approved by the NTIA. For ICANN to follow
                              its “normal process for dealing with
                              reviews” implies that ICANN itself is in
                              control of _<i>making</i>_ the changes
                              rather than _<i>implementing</i>_ the
                              changes required by the proposal.
                              Publishing the proposed text for public
                              comment seems duplicative given that ICG
                              will have already gone through a public
                              comment process. It also would seem to
                              provide an avenue for changing the
                              proposal in response to comments made in
                              its own process.
                              <o:p></o:p></span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">So
                              if I understand what is being proposed by
                              ICANN here, I would view it as both
                              duplicative and potentially destabilizing.
                              <o:p></o:p></span></p>
                        </div>
                      </div>
                    </div>
                  </div>
                </blockquote>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>_______________________________________________</span><br>
          <span>Internal-cg mailing list</span><br>
          <span><a moz-do-not-send="true"
              href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a></span><br>
          <span><a moz-do-not-send="true"
              href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a></span><br>
          <span></span><br>
          <span></span><br>
        </div>
      </blockquote>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Internal-cg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a>
<a class="moz-txt-link-freetext" href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>