From info at arin.net Fri May 2 15:59:41 2014 From: info at arin.net (ARIN) Date: Fri, 02 May 2014 15:59:41 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2014.9: ANONYMIZING INFORMATION Message-ID: <5363F92D.1020606@arin.net> A new suggestion was received through the ACSP, and was assigned number 2014.9 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-9.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Inclusion of Registered participants, asked to anonymize their information. This would refer to the Original Prime Contractor. *ARIN Comment: * ARIN is talking to the author to get a clear understanding of the issue. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu May 29 10:01:07 2014 From: info at arin.net (ARIN) Date: Thu, 29 May 2014 10:01:07 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2013.5: PROVIDE WHOIS-RWS RESULTS IN JSONP FOR EASE OF 3RD-PARTY APPLICATION DEVELOPMENT Message-ID: <53873DA3.4060303@arin.net> 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: https://www.arin.net/participate/acsp/suggestions/2013-5.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Author: Colin Robinson Submitted On: 18 March 2013 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. 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. *Response:* /ARIN Comment/ 27 March 2013 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. We do not have a scheduled implementation at this time, but will keep this suggestion open until implemented. /ARIN Comment/ 26 September 2013 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: Estimated staff effort to implement: 1 person month, plus communications efforts. For information about the consultation and how to participate in the survey, please see the 26 September 2013 announcement. / //ARIN Comment/ 28 May 2014 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 arin-tech-discuss at arin.net. This suggestion will be closed. Thank you for your suggestion. -------------- next part -------------- An HTML attachment was scrubbed... URL: