<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 4/4/2022 7:08 PM, Tom Beecher wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL9Qcx61PDr3F6dgz2chtz5kHR8oznPDzjJvYZp6C68+DnU6QA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
am an ARIN admin and tech POC for one of the affected
ASNs/sets of<br>
prefixes across 2 OrgIDs. I looked back at the messages I've
received<br>
that mention NONAUTH or Non-Authenticated. The only thing I've
gotten is<br>
the message originally sent via ARIN-Announce that John
forwarded, plus<br>
similar reminders.<br>
</blockquote>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm
extremely grateful to Job and Kenneth for stepping in to
address<br>
ARIN's failure here before it ruined a lot of people's weeks.<br>
</blockquote>
<div><br>
</div>
<div>ARIN clearly stated they were attempting to reach people
with records for the last year. If the contact info you had
was correct and they still didn't get to you, perhaps it
better to speak with them to figure out why before just
branding it a 'failure'.</div>
</div>
</blockquote>
<p><br>
</p>
<p>In the interest of fairness and accuracy, there's an important
clarifying detail. ARIN *did* notify the POCs associated with the
actual NONAUTH IRR records. But those are wholly separate from the
POCs for the actual address or ASN resources, which is what I was
referencing above, and thus it resulted in a bad assumption on my
part. That said, if the email addresses associated with what are
likely stale/crufty/unmaintained records in the NONAUTH IRR were
dead, no one got notified. Reasonable people can disagree on
whether that was enough of an attempt. In this case, I didn't know
these existed, and thus didn't know that the contact info for them
was similarly out of date. I suspect I'm not the only one in this
situation.<br>
</p>
<p>My calling this a failure was too strong, and for that I
apologize, but I disagree with their choice to not notify the
current resource holder POCs when they were unable to successfully
notify the POCs for the corresponding objects. That said, it's not
an easy problem, and there are things that multiple parties
(including me) could or should have done to address this, so the
blame is not solely ARIN's. <br>
</p>
<p>Wes George<br>
</p>
</body>
</html>