<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Aug 24, 2015, at 9:57 PM, Brian Jones <<a href="mailto:bjones@vt.edu" class="">bjones@vt.edu</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">My organization last signed RSA agreement was version 10.0 in 2009. I am curious to know what happens as versions of the RSA changes over time while organizations signed agreements become out of date. Are we
held responsible for the latest RSA version that is approved or the latest version the organization has signed?
<br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Brian - </div>
<div><br class="">
</div>
<div>The organization is bound by latest version that the organization has signed. In the general </div>
<div>provisions of the RSAs (usually section 14), you’ll find language similar to the following - </div>
<div><br class="">
</div>
<div>"<span style="font-family: ArialMT; font-size: 10pt;" class="">(l) Subsequent Version(s). If any subsequent version(s) of the Registration Services Agreement is authorized by ARIN, the parties may choose to substitute a signed copy of the then- existing
subsequent version, with all its terms, instead of this Agreement, and the Included Number Resources and other Services will then be governed by the subsequent version. The consideration for such change is the original agreement and the agreement to abide
by the revised terms. There is no requirement for a Holder who has signed this Agreement to engage in any subsequent version.</span><font face="ArialMT" size="2" class="">”</font></div>
<div><span style="font-family: ArialMT; font-size: 10pt;" class=""><br class="">
</span></div>
<div><font face="ArialMT" size="2" class="">i.e. parties that wish to move to the latest version may do so (but are not required to do so)</font></div>
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small"><br class="">
</div>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">Section d.) of the introduction makes it sound as though everyone who has signed an agreement with ARIN at any point in time will be subject to any policy changes or obsoletes. I do not recall our organization
receiving notice of changes to our RSA (version 10) to get to version 11 or I would have more involved in this discussion then. Assuming an organization complies with changes in policy that they may not even be aware of seems to create a backdoor for policy
changes made in a vacuum. It also could apply undue liability to the unknowing party.
<br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
That is correct. I would recommend that your organization pay attention to policy changes that</div>
<div>are proposed by the community, as they can affect your existing Internet number resources.</div>
<div>The ARIN Public Policy Mailing List (<font color="#4787ff" class=""><u class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a>)</u></font> is where </div>
<div>such changes are discussed.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">In my initial review of our version 10, and the provided links to version 11 an 12, I find much of the version 12 wording more appealing than some of our version 10 agreement. I will have more comments after
I have time for a more thorough review. There are several changes from version 10 to version 11 and I want to understand the removal of some of the "may's" leaving only the implicit "must" in their place. </div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>Understood - we’ve tried to accommodate suggestions received to date from the community, </div>
<div>but are open to any additional suggestions for changes on this proposed new version.</div>
<div><br class="">
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
<br class="">
</body>
</html>