<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#330033">
    Hi,<br>
    <br>
    Sounds right to me as well.<br>
    <br>
    I think any incidental compatibility issues that may spring up
    become an issue for the ICG, as long as we remain careful to not
    include any extra work or participation by the other operational
    communities in any of the PTI mechanisms.<br>
    <br>
    avri<br>
    <br>
    <div class="moz-cite-prefix">On 21-Apr-15 13:36, Greg Shatan wrote:<br>
    </div>
    <blockquote
cite="mid:CA+aOHUSBRtEMcQN5c_xKHLt5NiA0MvgTdDgixmOBwoncSHqpkg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">Andrew,</div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">By George, I think
          you've got it.</div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">Greg</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Apr 21, 2015 at 1:23 PM, Andrew
          Sullivan <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
              class="">On Tue, Apr 21, 2015 at 04:32:40PM +0000, Martin
              Boyle wrote:<br>
              &gt; I think that Greg is right, that we were not mandated
              in the CWG to look at numbers or protocol parameters. 
              While that might sit uneasily, I’m not sure I really know
              about the flow of funding or the
              accountability/stewardship role in the light of Milton’s
              assertion.<br>
              &gt;<br>
              <br>
            </span>I believe here are two completely different things
            here.<br>
            <br>
            1.  The IANA functions -- all of them -- move from inside
            ICANN to the<br>
            affiliate.  This is how ICANN performs the IANA functions. 
            The agreements with other parties can remain between ICANN
            and those other parties, but that does not affect the "how
            ICANN gets IANA done."<br>
            <br>
            2.  The names IANA function gets all the accountability
            rules and so<br>
            on we've been talking about.  That's the "names community
            proposal".<br>
            This part really is names-only.<br>
            <br>
            If follows from these two premises, however, that ICANN
            needs also to<br>
            undertake some sort of agreement with PTI about how the
            other<br>
            communities' needs get satisfied.  Presumably, if the other<br>
            communities maintain an agreement with ICANN, then ICANN
            concludes an<br>
            agreement with PTI that says, "You implement that."  The
            details of<br>
            how that is worked out, however, are not our problem and we
            don't need<br>
            to have an opinion about it reflected in this document, I
            think.<br>
            <br>
            Best regards,<br>
            <br>
            A<br>
            <span class="HOEnZb"><font color="#888888"><br>
                --<br>
                Andrew Sullivan<br>
                <a moz-do-not-send="true"
                  href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
              </font></span>
            <div class="HOEnZb">
              <div class="h5">_______________________________________________<br>
                CWG-Stewardship mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
                <a moz-do-not-send="true"
                  href="https://mm.icann.org/mailman/listinfo/cwg-stewardship"
                  target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
CWG-Stewardship mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
</pre>
    </blockquote>
    <br>
  
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
        <tr>
                <td style='border:none;padding:0px 15px 0px 8px'>
                        <a href="http://www.avast.com/">
                                <img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
                        </a>
                </td>
                <td>
                        <p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
                                This email has been checked for viruses by Avast antivirus software.
                                <br><a href="http://www.avast.com/">www.avast.com</a>
                        </p>
                </td>
        </tr>
</table>
<br />
</body>
</html>