<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">A few brief replies inline.</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 class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 28, 2016 at 9:39 AM, Andrew Sullivan <span dir="ltr"><<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Greg,<br>
<br>
I am speaking for myself and _not_ for the Trust here. The Trust has<br>
not yet expressed a view of the position that the names community is<br>
taking, and I don't want anyone to mistake my remarks below as a<br>
position of the Trust. But I too was involved in the discussions that<br>
led to the Principal Terms and I think we may have different memories.<br>
<span class=""><br>
On Thu, Jul 28, 2016 at 04:33:09AM -0400, Greg Shatan wrote:<br>
<br>
> comments and also find them somewhat troubling. The "Proposed Principal<br>
> Terms of IANA Intellectual Property Agreements" document was worked out<br>
> among representatives of all the communities and the IETF Trust over many<br>
> months, and these comments seem to ignore or contradict many aspects of<br>
> that document, which formed the design and basis for preparing the actual<br>
> Community Agreement and License Agreement.<br>
<br>
</span>I agree that we want to be true to the Principal Terms, but I think we<br>
need to be very careful with attempting to rely too hard on that<br>
document, because it also makes perfectly clear that the Trust is the<br>
ultimate controller here and that it is not subject to the CCG.<br>
<br>
I believe that the original drafts that were offered cleave to that<br>
principal, and that the position you are taking leans further toward<br>
empowering the CCG to direct the Trust in various ways. I also recall<br>
several occasions during the development of the Principal Terms in<br>
which you argued for a more formal or more supervisory role for the<br>
OCs -- a position that I and others then resisted as implying<br>
unacceptable modifications to the Trust Agreement or else to the way<br>
the Trust actually operates. It appears to me, if I may be quite<br>
frank, that you are attempting to reintroduce your position as part of<br>
the negotiations over this agreement. You're free to do that, but I<br>
am no more reconciled to that mode of working now than I was many<br>
months ago when we were hammering out the Principal Terms.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">My view is somewhat different. I think the first draft backed away from a number of aspects of the Principal Terms. I think the Principal Terms represented the balance and outcome of the discussions we all had about the relative roles of the Trust and the communities/CCG. The intent of the second draft was to move closer to the letter and concept of the Principal Terms. If there are places where we missed the mark as well, I'm sure we can correct for that together. I'll also say again that there are very few instances where the CCG actually directs the Trust; in almost all instances, the Trust takes the initiative subject to advice and approval (but not in all cases) from the CCG.</div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I believe I was crystal clear all along that the Trust needed to<br>
retain its abolute and independent control over the marks and domain<br>
names, because the advice I have is that that is the only way that the<br>
Trustees can ensure their ability to perform their fiduciary duty.</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Speaking as someone on the pointy end of that duty, I feel the</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
responsibility quite strongly. I believe that the Principal Terms say<br>
that the Trust holds the ultimate authority, and I do not believe that<br>
the draft you have circulated is quite as faithful to those Terms as<br>
you suggest. The Terms were always ambiguous on this matter, however,<br>
because we knew this was where the trouble was going to be. </blockquote><div><br></div><div><div class="gmail_default" style="font-family:verdana,sans-serif">I think what we need to do here is strike the right balance between the CCG and the Trust.</div><div class="gmail_default" style="font-family:verdana,sans-serif">I would say that we're not there yet, and that the answer lies somewhere between the two drafts, so that we carry out the intentions of the Principal Terms and the plans that preceded it, while respecting the concerns of all parties.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is<br>
why many months ago I was pressing for us to move on to actual<br>
drafting, rather than polishing the Terms document until it was shiny.<br>
We chose not to do that, and now we have this problem.<br>
<br>
I'm confident that with good will all around we can come to an<br>
agreement in time. But to me, that agreement should not vest too much<br>
responsibility or authority in the CCG. The normal mode of operation<br>
of the IETF is to create bodies that do such work as is absolutely<br>
necessary, and no more. I think it's a good approach, and I think we<br>
should design an agreement here that encourages and maximises<br>
collaboration and minimises formal approval and authority.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">I also think we can get this done, and that there should not be "too much" authority vested in the CCG/communities. But neither should there be too little. I like the idea of encouraging and maximizing collaboration and minimizing formal approval and authority. The more we can avoid hierarchy -- in either direction -- the better. But collaboration requires some shared responsibility and authority and the right balance between the parties. That is the key.</div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best regards,<br>
<br>
A<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
</font></span></blockquote></div><br></div></div>