<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">If we do consider these questions, I would suggest omitting the second question and rephrasing the third. I believe the references to "principal" and "agent" are incorrect. In a principal/agent relationship, the parties enter into an agreement whereby the agent can act for the principal to create binding legal agreements between the principal and third parties. An agency relationship must be set forth in an agreement (though that agreement can have other purposes besides creating the agency relationship). I'm virtually certain the CA is not an agency agreement, and I see no reason why any other agreement with the RZM would be an agency agreement. The Law of Agency (surprise!) governs such relationships.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If the words "principal" and "agent" are being used loosely and not for the legal meaning above, I would suggest other terms be used to avoid confusion and to avoid any implication that the Law of Agency applies here. Perhaps "hiring party" and "contractor" if that is the sense in which these words are being used?</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 Mon, Oct 5, 2015 at 2:19 PM, Gomes, Chuck <span dir="ltr"><<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Milton,<br>
<br>
Are you advocating that the CWG should develop proposed answers to the questions you raised and I have copied here?<br>
<span class=""><br>
"- Does PTI contract with the RZM, or does ICANN? Or does someone else?<br>
- Who is the principal and who is the agent of this contract?<br>
- If ICANN is the principal, can it decide to give the contract to someone besides Verisign? On what time frame? On what criteria?<br>
- What are the basic terms/elements of this contract? Does the RZM get paid?"<br>
<br>
</span>Note that the third question may be out of scope for the CWG. Our charter says the following: "In respect of Function 2. ("Perform Administrative Functions Associated With Root Zone Management"), this process currently involves distinct roles performed by three different entities through two separate legal agreements: the Contractor as the IANA Functions Operator, NTIA as the Administrator, and VeriSign ('or any successor entity as designated by the U.S. Department of Commerce") as the Root Zone Maintainer. The accountability function currently performed by NTIA regarding the RZM role, as well as the discussion of the RZM management administrative interface currently used by NTIA are within the scope of the CWG. The issue of who performs the Root Zone Maintainer (RZM) role is not in scope for the CWG and should be dealt with in a subsequent effort as needed. . ."<br>
<br>
If I am correct on the scope, the charter can be changed but that would require approval of all the chartering organizations.<br>
<br>
For anything that is out of scope, the CWG could recommend that 'a subsequent effort' be initiated and could possibly provide guidelines/requirements for that effort.<br>
<span class="HOEnZb"><font color="#888888"><br>
Chuck<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>] On Behalf Of Mueller, Milton L<br>
Sent: Monday, October 05, 2015 10:39 AM<br>
To: Alan Greenberg; Grace Abuhamad; <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
Subject: Re: [CWG-Stewardship] Responses to ICG Questions<br>
<br>
Alan,<br>
<br>
I still find your answers unsatisfying.<br>
<br>
> -----Original Message-----<br>
AG<br>
> What I (or anyone on the CWG or ICG) is not the issue. WE cannot<br>
> unilaterally cancel the agreement between tow other parties, and if<br>
> Verisign plans to do that, I have not been informed.<br>
<br>
Please stop knocking down straw men. No one is claiming that CWG can alter the Verisign Cooperative Agreement, and in fact there are several statements I have made and ICG has made recognizing that that part of the transition is in NTIA's hands. I see a tendency here to say that because NTIA must modify the CA, that CWG is absolved of the responsibility for designing the relationship between PTI, ICANN and whoever the RZM is.<br>
<br>
> The CWG *HAS* laid out how this should unfold and it is documented in<br>
> 1150, 2b. We have not drafted the contract, and I believe that without<br>
> an indication from the NTIA as to how it will proceed, I believe that<br>
> is premature.<br>
<br>
Does 1150 2b answer any of the following questions?<br>
- Does PTI contract with the RZM, or does ICANN? Or does someone else?<br>
- Who is the principal and who is the agent of this contract?<br>
- If ICANN is the principal, can it decide to give the contract to someone besides Verisign? On what time frame? On what criteria?<br>
- What are the basic terms/elements of this contract? Does the RZM get paid?<br>
<br>
<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
</div></div></blockquote></div><br></div>