<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Owen – <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Appreciate your input here. Related to the policy you reference about the definition of Allocation. As the lead shepherd for that policy, I will share that your (and other) feedback about the definition was
heard (I referenced it in the slide presentation specifically.) <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Not changing the language immediately was not a result of picking one side or another, but more about keeping the draft language stable to allow for additional in-person community feedback at the public policy
meeting. The policy had undergone many changes in August and September with final revisions from staff and legal review at the end of September. Given that, it seemed prudent to allow the as-written language to elicit a complete cycle of feedback both on PPML
and in person. My apologies if that understanding wasn’t conveyed. The feedback received at the microphone and in the room was helpful in shaping the understanding for the next steps.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hope that helps – <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Doug<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Douglas J. Camin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">ARIN Advisory Council<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">doug@dougcamin.com</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">ARIN-PPML <arin-ppml-bounces@arin.net> on behalf of Owen DeLong via ARIN-PPML <arin-ppml@arin.net><br>
<b>Date: </b>Thursday, October 26, 2023 at 1:30 PM<br>
<b>To: </b>William Herrin <bill@herrin.us><br>
<b>Cc: </b>arin-ppml@arin.net <arin-ppml@arin.net><br>
<b>Subject: </b>Re: [arin-ppml] AC candidates<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
> On Oct 26, 2023, at 09:47, William Herrin <bill@herrin.us> wrote:<br>
> <br>
> On Thu, Oct 26, 2023 at 9:28 AM Andrew Dul <andrew.dul@quark.net> wrote:<br>
>> On 10/26/2023 9:20 AM, William Herrin wrote:<br>
>>> It plummeted after the Board changed the AC's role from shepherding<br>
>>> policy proposals to developing policy proposals.<br>
>> <br>
>> I realize that might be a distinction with out a difference, but I<br>
>> wanted to point it out.<br>
> <br>
> Shepherds guide folks through process. They don't edit proposals.<br>
> Today's AC does much more of the latter than the former.<br>
> <br>
> <br>
>> From a policy development perspective the AC's role has not changed<br>
>> significantly in more than a decade.<br>
> <br>
> I can still be sore about changes made a decade ago.<br>
> <br>
> <br>
>> Should we disallow an AC member from submitting a policy proposal?<br>
> <br>
> I don't think that's the problem. The AC members are some of the best<br>
> informed folks around. It would be a waste to be unable to leverage<br>
> their ideas. The problem is the next step where they get together and<br>
> edit them privately. This is inherently exclusionary of everybody else<br>
> and IMO is uncorrectable as long as the AC has the unilateral power to<br>
> edit an author's proposal.<br>
<br>
In my experience, the AC works very hard to remain true to the author’s<br>
original intent and involve author(s) in the editorial process of a policy.<br>
The AC is also extremely receptive to whatever community input is<br>
available on a policy in most cases.<br>
<br>
The only recent counterexample I can point to is efforts to wordsmith<br>
a proposal that sought to redefine assignment and (slightly) expand the<br>
definition of allocation. You and I both wanted to choose a new term,<br>
Mr. Curran was very clearly opposed to doing so. The AC obviously<br>
chose to weigh Mr. Curran’s guidance more heavily than ours.<br>
<br>
At the end of the day, that’s not one of the hills I’m willing to die on.<br>
<br>
I don’t take that as an indication that the AC is conspiring with Mr. Curran<br>
behind my back. That debate was quite open and public.<br>
<br>
I have seen the AC depart from the author(s)’ intent in the following<br>
circumstances:<br>
<br>
+ Significant community pressure to go in a different direction<br>
+ The author becomes unresponsive or unwilling to accommodate<br>
community feedback<br>
<br>
Otherwise, I’ve seen the AC work very hard to remain true to the author(s)’<br>
original intent, even to the point of recognizing that editing a proposal would<br>
be disingenuous and authoring a new proposal as an alternative rather than<br>
override an existing proposal.<br>
<br>
> What should be disallowed to AC members is:<br>
> <br>
> 1. Editing proposals, except by the individual who authored it (which<br>
> if an AC member should be only that individual).<br>
<br>
I think this would be significantly more dysfunctional than the current<br>
process, TBH. The most likely result would be the AC abandoning more<br>
proposals and spinning up competing proposals as a workaround.<br>
<br>
> 2. Private debate about proposals between AC members. Restrict the AC<br>
> meetings to voting on proposals without debate or advocacy. Require<br>
> the discussion and debate to happen on PPML.<br>
<br>
ROFLMAO… This would not be an improvement of the process. This would<br>
be chaos. You could sooner ban hallway discussions of proposals at the meetings.<br>
<br>
<br>
Owen<br>
<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.arin.net%2Fmailman%2Flistinfo%2Farin-ppml&data=05%7C01%7C%7C8a89f9e636ae4891c29308dbd649396c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638339382209052982%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ehWMFNhly6c%2BCPzBT0HXiBOGjU0uHWjl57sN8P8%2BFUc%3D&reserved=0</a><br>
Please contact info@arin.net if you experience any issues.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>