<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>On Oct 24, 2024, at 6:36 PM, Lee Howard via ARIN-PPML <arin-ppml@arin.net> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div>
<div class="yahoo-style-wrap" style="font-family:times new roman, new york, times, serif;font-size:16px;">
<div dir="ltr" data-setdir="false">In the spirit of offering constructive feedback, I would like to describe what I would like to see at ARIN Public Policy meetings.</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">Broadly, the purpose of the Public Policy Meetings is to discuss policy and policy proposals. The purpose of the Members Meeting is to provide the Members with information about the operation of the organization, especially
as it will help guide governance, including elections.</div>
</div>
</div>
</div>
</blockquote>
<div>
<blockquote type="cite">...</blockquote>
</div>
<blockquote type="cite">
<div>
<div>
<div class="yahoo-style-wrap" style="font-family:times new roman, new york, times, serif;font-size:16px;">
<div dir="ltr" data-setdir="false">I think this organization will better align the work in each meeting with the purpose of the meeting. </div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>
<div>Lee -</div>
<div><br>
</div>
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;">
<div>
<div>Thanks for sending this! I also noted your comment at the microphone that we should never shortchange public policy discussions at these meetings—a view that I strongly agree with (and observed that, thanks to Hollis and Chair Sandiford’s excellent moderation,
this was not an issue yesterday).</div>
</div>
<div>
<div><br>
</div>
</div>
<div>
<div>As you are aware, we tended to have a stronger delineation between the Public Policy Meeting and the Members Meeting in the past, and it is true that we could organize that way in the future.
</div>
<div><br>
</div>
<div>However, I believe there are a few factors to consider before we commit to a strict delineation – </div>
</div>
<div>
<div><br>
</div>
</div>
<div>
<div>
<ol class="MailOutline">
<li>In recent years, we’ve been able to “expand the tent” of ARIN members; in other words, members are no longer limited to ISPs and large organizations. Due to changes in membership structure, nearly every customer is now an ARIN member. As such, those participating
in our public policy discussions are largely ARIN members—individuals from organizations that pay fees to support ARIN, receive services from ARIN, and can (if they wish) become general members and participate in ARIN’s governance.
</li><li>We are also in an era where ARIN is engaged in many activities beyond just number resource policy, which have the potential for significant implications for all of ARIN’s customers. For example, topics such as the evolution and deployment of RPKI services,
the current ICP-2 update activities, and our cybersecurity efforts are not public policy per se, but they have equally significant potential impacts on ARIN’s customers. As such, these topics deserve to be informed by feedback from our entire customer community.</li><li>Finally, I note that ARIN is committed to capacity development within the ARIN community—i.e., we aim to improve the knowledge and experience of our entire community. Over time, this has proven to help grow our pool of volunteers who advance to important
roles such as the ARIN AC, the ASO AC, and the ARIN Board of Trustees. Those participating in our meetings presently gain broad exposure to all aspects of ARIN – not just number resource policy development – and I do worry that a strict delineation of the
Public Policy Meeting and the Members Meeting could hinder an important element of cross-pollination that has historically bolstered leadership development from within ARIN’s community. </li></ol>
</div>
</div>
<div>
<div><br>
</div>
</div>
<div>
<div>To be clear, I am not saying that a clear distinction between the two aspects of the meeting is no possible, but rather that there are potential downsides that should be considered and balanced against any benefits we hope to achieve by such delineation.</div>
</div>
<div><br>
</div>
</blockquote>
<div>
<div>Thanks!</div>
<div>/John</div>
<div><br>
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>