<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 2013.5. The suggestion and response text are provided
below. This suggestion is now closed 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/2013-5.html">https://www.arin.net/participate/acsp/suggestions/2013-5.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>
Author: Colin Robinson Submitted On: 18 March 2013<br>
WHOIS-RWS provides results in XML or JSON. Due to the same-origin
policy, it is not possible for a client's web browser to access
WHOIS-RWS. Of course the server of the website that the client is
visiting could act as a proxy between the client's browser and
WHOIS-RWS, but that is a waste of bandwidth.<br>
<br>
If WHOIS-RWS could provide results in JSONP or set
"Access-Control-Allow-Origin: *" to allow CORS, it would allow
developers that depend on WHOIS-RWS to create easier and more
efficient web applications.<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>ARIN Comment</i><br>
27 March 2013<br>
<br>
ARIN believes your suggestion warrants further development and
implementation. To that end, ARIN will go with the
Access-Control-Allow-Origin header setting to enable this
functionality as it is the best standardized approach to providing
these types of services.<br>
<br>
We do not have a scheduled implementation at this time, but will
keep this suggestion open until implemented.<br>
<br>
<i>ARIN Comment</i><br>
26 September 2013<br>
<br>
As part of the ARIN 32 ACSP Consultation: Open Suggestion Review and
Project Prioritization Survey, we're providing feedback and
estimates on the predicted work involved. For this suggestion, the
following is noted:<br>
<br>
Estimated staff effort to implement: 1 person month, plus
communications efforts.<br>
<br>
For information about the consultation and how to participate in the
survey, please see the 26 September 2013 announcement.<br>
<i><br>
</i><i>ARIN Comment</i><br>
28 May 2014<br>
<br>
The ARIN Engineering team has completed the work to enable Whois-RWS
Cross-origin resource sharing (CORS) using
Access-Control-Allow-Origin header functionality. This enhancement
is now in production. If you have any questions, please feel free to
contact <a class="moz-txt-link-abbreviated" href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a>.<br>
<br>
This suggestion will be closed.<br>
<br>
Thank you for your suggestion.<span style="font-family:Helvetica;
mso-bidi-font-family:"Times New Roman";color:black"></span>
</body>
</html>