<html xmlns:v="urn:schemas-microsoft-com:vml" 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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;line-break:after-white-space">Precisely because of the delay. The old tickets are a way to see the info you want (albeit possibly stale) without the pause which completely messes up your workflow.<br><br>Although you raise a valid point: the problem isn't the tickets being deleted, the problem is that they are/were necessary in the first place. With the exception of association reports which I might want for forensic purposes, I think the remainder have little historical value per se, I just want instant access to the data (and the ability to see if it had changed over time).<br><br>-Adam<br><br><div class="gmail_quote">On July 1, 2019 11:06:18 a.m. CDT, "Delacruz, Anthony B" <Anthony.DeLaCruz@CenturyLink.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Why not just run the whowas report again and get updated info if any more has occurred. The same history should be in there. That probably is the one a do a
few times a week and would be good with those all getting tossed out as tickets since I could just query again. I’m fine with the removal of the 4 listed types as the data is still accessible. I don’t think we need to have a record of every time the tool is
use. Ideally just give me the info asked and don’t even make a ticket. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> ARIN-consult [mailto:arin-consult-bounces@arin.net]
<b>On Behalf Of </b>Adam Thompson<br>
<b>Sent:</b> Monday, July 01, 2019 9:52 AM<br>
<b>To:</b> John Curran<br>
<b>Cc:</b> <arin-consult@arin.net><br>
<b>Subject:</b> Re: [ARIN-consult] ACSP Consultation: Deleting Aged Report Request Tickets<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Acknowledged. I'm saying there is some value in those reports, months or years later. Not a *lot* of value, necessarily, but certainly non-zero. The casual, instant access to them is what makes them still useful
IMHO.<br>
-Adam<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On July 1, 2019 9:25:00 a.m. CDT, John Curran <jcurran@arin.net> wrote:<o:p></o:p></p>
<p class="MsoNormal">On 1 Jul 2019, at 10:11 AM, Adam Thompson <<a href="mailto:athompso@athompso.net">athompso@athompso.net</a>> wrote:<o:p></o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">As an alternate suggestion, I don't see any problem with moving those records out of the mainline UI onto another page and into another database.</span><o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Acknowledged.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Like many others here, though, I'm puzzled at how a modern database system could be this badly hobbled (in an apparently-intractable way) by mere millions of tickets.</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">The ARIN Online system handles these tickets now quite capably, but staff prepared the suggestion because it is clear that the system performance could be even better if we did not have infinite retention on tickets which are created solely
for report generation. Users can run these reports at any time to obtain such information if they desire it. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Again, the only reason these tickets exist is that the time to go through the entire registry history and generate historical reports is significant and thus not real-time – if information had been available instantly, then we would have
instead had it displayed directly on the screen and there never would have been any “report ticket" generated in the first place. Given that ARIN Online creates such “report tickets” on the users behalf (and the questionable value of the report output months
later), it was felt best to assign an expiration on the these ticket types. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">/John<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">John Curran<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">President and CEO<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">American Registry for Internet Numbers<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"></p></div></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>