From info at arin.net Wed Mar 20 14:04:38 2013 From: info at arin.net (ARIN) Date: Wed, 20 Mar 2013 14:04:38 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2013.5: PROVIDE WHOIS-RWS RESULTS IN JSONP FOR EASE OF 3RD-PARTY APPLICATION DEVELOPMENT Message-ID: <5149FA36.4010601@arin.net> A new suggestion was received through the ACSP, and was assigned number2013.5 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2013-5.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion:* 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Mar 25 17:14:46 2013 From: info at arin.net (ARIN) Date: Mon, 25 Mar 2013 17:14:46 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2011.22: PPML FORMAT CHANGE Message-ID: <5150BE46.3030702@arin.net> ARIN has issued its response to ACSP Suggestion 2011.22. The suggestion and response text are provided below. This suggestion is now closed and is available at: https://www.arin.net/participate/acsp/suggestions/2011-22.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Reading PPML is now impossible because the traffic is to high and the signal to noise ratio is too low. I would lke to sugges using a blog/wiki instead to discuss new proposal. The 'owner' of a proposal would have a top post explaining the idea, there would be discussions following up in blog comment format. If shepherds are assigned, the 'pro' shepherd would be in charge of updating the top post with summary of new arguments and the 'con' shepherd will update a side box with a summary of the 'cons'. That way, I could come and have a summary of the proposal and the pros/cons arguments in just one view. I'm not interested in the 100th repeat of the same point, but in the collection of the pros and cons point. I have to say that I've now stopped reading PPML, and I hope such a system could be put in place very quickly. *Response:* The ARIN Advisory Council has formed an Improve Communications Group (ICG) to improve policy related discussions in general. Your suggestion has been provided to the ICG as input into their effort. The ICG will be reporting progress periodically at ARIN Public Policy Consultations and Public Policy and Member Meetings and therefore you will be able to provide additional input as well as monitor progress at those events. Note that you can participate remotely if you are unable to attend in person. Since this suggestion has been provided to the ICG and is now part of their deliberations, this suggestion is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Mar 26 15:04:25 2013 From: info at arin.net (ARIN) Date: Tue, 26 Mar 2013 15:04:25 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2013.4 -CHANGE WHOIS OUTPUT FOR CERTAIN /8 RECORDS Message-ID: <5151F139.5040105@arin.net> ARIN has issued its initial response to ACSP Suggestion 2013.4. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2013-4.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * I would like ARIN to consider and act on this request so suppress the RIR /8 output when a more specific DA or DS exists, and instead, display the DA or DS. This is specify for 154/8 however I feel it should cover any space ARIN has in it's registry. This request is intended to allow the referrals for the specific space to be returned. Please see ARIN-20130219.211 for additional information behind this request. *Response:* Thank you for your suggestion. This behavior started when Whois-RWS rolled out in March 2011. The issue exists only with ERX space (where another RIR is authoritative for the /8). We don't show /8's in ARIN space if the query hits a DA or DS record. It does break RWhois referrals, but as far as we know, that is all that it breaks. So ARIN essentially has 2 choices here: - Continue to show the majority RIR when someone looks up an IP address outside of the ARIN region or -Stop showing the ERX /8 record, which fixes the rwhois referral problem. But keep in mind, if we remove the /8 for the minority /8s, we won't be telling folks which RIR has the block they're looking for. We believe that it would be prudent to put this suggestion, with potential solutions, out to the community as a consultation in order to get additional feedback on this issue. Please be sure to add your opinion to the consultation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Mar 27 17:11:04 2013 From: info at arin.net (ARIN) Date: Wed, 27 Mar 2013 17:11:04 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2013.5 - PROVIDE WHOIS-RWS RESULTS IN JSONP FOR EASE OF 3RD-PARTY APPLICATION DEVELOPMENT Message-ID: <51536068.3050002@arin.net> ARIN has issued its initial response to ACSP Suggestion 2013.5. The suggestion and response text are provided below. This suggestion remains open 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: * 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 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: