<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p class="MsoNormal" style="margin: 6pt 0in; line-height: 18pt;
background: none repeat scroll 0% 0% white;"><span
style="font-family:Helvetica;mso-fareast-font-family:
"Times New Roman";mso-bidi-font-family:"Times New
Roman"">ARIN has issued its initial response to ACSP
Suggestion 2012.18. The suggestion and response text are
provided below. This suggestion remains open and is available
at: </span><span style="font-family: Times;"></span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""></span><span
style="font-family: Helvetica;"><br>
</span></p>
<p class="MsoNormal"
style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
margin-left:0in;line-height:18.0pt;background:white"><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman""><a class="moz-txt-link-freetext" href="https://www.arin.net/participate/acsp/suggestions/2012-18.html">https://www.arin.net/participate/acsp/suggestions/2012-18.html</a></span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">Regards,</span><span style="font-family:
Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:"Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">Communications and Member Services</span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family: "Times New Roman""><br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">American Registry for Internet Numbers (ARIN)</span><span
style="font-family:Times;mso-fareast-font-family:"Times New
Roman"; mso-bidi-font-family:"Times New Roman""><br>
<br>
</span><span
style="font-family:Helvetica;mso-fareast-font-family:"Times
New Roman"; mso-bidi-font-family:"Times New
Roman"">***</span><span style="font-family:
Times;mso-fareast-font-family:"Times New
Roman";mso-bidi-font-family:"Times New Roman""><o:p></o:p></span><b><span
style="font-family: Helvetica;mso-bidi-font-family:"Times
New Roman";color:black"><br>
Suggestion: </span></b><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span></p>
1. ARIN should not phase out the <a class="moz-txt-link-abbreviated" href="mailto:hostmaster@arin.net">hostmaster@arin.net</a> channel for
additional communication about requests. Ideally, restoring that as
a channel for request submission should be restored.<br>
<br>
2. ARIN needs to provide much better tools for consultants to use to
work with their customers on ARIN resource requests. The need for
these better tools is a direct result of the conversion to ARIN
on-line.<br>
<br>
Prior to ARIN on-line, it was relatively easy to collaborate with my
clients because we could pass the request information around in
email and submit the template once it was finalized in the
collaborative process. Ticket responses via email could be easily
forwarded to the client and additional response information could be
submitted to hostmaster directly from email. This made for very
convenient integration between the client<--->consultant and
consultant<--->ARIN communication.<br>
<br>
ARIN online has made the entire process unacceptably more
time-consuming and difficult.<br>
<br>
One good step in the right direction would be to provide better
integration between <a class="moz-txt-link-abbreviated" href="mailto:hostmaster@arin.net">hostmaster@arin.net</a> and ARIN on-line. For
example, an email to <a class="moz-txt-link-abbreviated" href="mailto:hostmaster@arin.net">hostmaster@arin.net</a> containing attachments with
a properly formed Re: [ARIN-20121018-X2854] style header should have
the email body included in the ticket as the comments and the
attached files treated as if they had been uploaded through ARIN
on-line without requiring intervention from the RSHD staff, let
alone requiring them to print the attachments, then scan them and
submit that back into the web form to get it into ARIN on-line.<br>
<br>
(If the above description of the process is inaccurate, then, RSHD
personnel I have spoken to are misinformed about the process because
that is how they described it to me).<span style="font-family:
Helvetica;mso-bidi-font-family:"Times New
Roman";color:black"></span><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span>
<p class="MsoNormal"
style="margin-top:6.0pt;margin-right:0in;margin-bottom:6.0pt;
margin-left:0in;line-height:18.0pt;background:white"><b><span
style="font-family: Helvetica;mso-bidi-font-family:"Times
New Roman";color:black">Response:</span></b><span
style="font-family:Arial;mso-bidi-font-family:"Times New
Roman";color:black"><o:p></o:p></span></p>
I wanted to formally acknowledge your suggestion 2012.18: Improve
Request Submission Options. We will take your suggestions under
consideration as we complete ARIN's 2013 operating plan. Once the
plan is approved, we will follow back up with you on those items we
plan to implement in 2013. This suggestion will remain open.<br>
<br>
Regards,<br>
<br>
Nate Davis<br>
Chief Operations Officer<br>
American Registry for Internet Numbers (ARIN)<span
style="font-family:Helvetica; mso-bidi-font-family:"Times New
Roman";color:black"></span>
</body>
</html>