<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<style>@font-face {
font-family: "ＭＳ 明朝";
}@font-face {
font-family: "ＭＳ 明朝";
}@font-face {
font-family: "Cambria";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: Cambria; }.MsoChpDefault { font-family: Cambria; }div.WordSection1 { page: WordSection1; }</style>
<p class="MsoNormal">A new suggestion was received through the ACSP,
and was assigned number<span style=""> </span>2013.5 upon
receipt of confirmation.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The text of the Suggestion is available at: <br>
<br>
</p>
<p class="MsoNormal"><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><br>
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">ARIN will issue an initial response within 10
business days.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Communications and Member Services</p>
<p class="MsoNormal">American Registry for Internet Numbers (ARIN)</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style=""></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"">***</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><br>
<br>
</p>
<p class="MsoNormal">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.<br>
</p>
<p class="MsoNormal">
<meta charset="utf-8">
</p>
</body>
</html>