<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 23 September, we closed two ACSPs.<br>
<br>
1. ACSP 2013.29: Improve ARIN Online Form Time-out Behavior<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.arin.net/vault/participate/acsp/suggestions/2013-29.html">https://www.arin.net/vault/participate/acsp/suggestions/2013-29.html</a><br>
<br>
Response:<br>
<br>
Thank you for your suggestion, numbered 2013.29 on confirmed
receipt, <br>
asking that we extend the time-out behavior for forms in ARIN
Online. We <br>
have completed this work when we deployed stateless architecture
on 2 <br>
March 2019. <br>
<br>
Because this work has been completed, we are closing your
suggestion. <br>
Thank you for your participation in the ARIN Consultation and
Suggestion <br>
Process. We apologize for the delay in notification that this work
was <br>
completed. <br>
<br>
Suggestion:<br>
<br>
Bug Report: Timed-out ticket forms are not graceful.<br>
<br>
To reproduce:<br>
<br>
</p>
<ol>
<li>Log into ARIN Online</li>
<li>Track Tickets</li>
<li>Select an open ticket and bring up its details.</li>
<li>Walk away from the browser long enough for the session to time
out.</li>
<li>Come back, the ticket is still on the screen and no
asynchronous notification of the session timeout is presented.</li>
<li>Not realizing that the session has timed out, enter comments
for the ticket into the text box and press submit.</li>
</ol>
<p>Expected result: A) The comments are accepted and then I am
logged out of the ticket system for inactivity, or, B) the
comments are buffered and I must log into ARIN online again to
validate their submission<br>
<br>
Actual result: I am dumped back to the logged-out state, all of my
text is lost, and I have to log in, find the ticket, and retype my
comments from scratch.<br>
<br>
2. ACSP 2019.17: RSA Changes<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.arin.net/vault/participate/acsp/suggestions/2019-17.html">https://www.arin.net/vault/participate/acsp/suggestions/2019-17.html</a><br>
<br>
Response:<br>
<br>
Thank you for your suggestion, numbered 2019.17 upon confirmed
receipt. <br>
<br>
As we understand it, this suggestion recommends changes to the
Registrations Services Agreement (RSA) to an obligation regarding
acceptable routing of IP address blocks. <br>
<br>
Given that changes to the RSA are initiated by the ARIN Board of
Trustees, this suggestion will be provided to the ARIN Board Chair
for future consideration. <br>
<br>
Thank you for your participation in the ARIN Consultation and
Suggestion Process. This suggestion is now closed. <br>
<br>
Suggestion:<br>
<br>
Description: ARIN should modify its Registration Services
Agreement so that address holders agree to only announce routing
for its own address blocks, or those address blocks for which it
has obtained permission of the registrant as listed in the
Internet Number Registry System.<br>
<br>
Value to Community: The additional value to the community would be
that ARIN address holders would be far less likely to hijack
routes as it would represent a breach of their agreement with
ARIN. <br>
<br>
Regards, <br>
<br>
Communications and Member Services <br>
American Registry for Internet Numbers (ARIN)</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>