From info at arin.net Fri Feb 1 17:54:20 2013 From: info at arin.net (ARIN) Date: Fri, 01 Feb 2013 17:54:20 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2010.16 - LEGACY REGISTRATION SERVICE AGREEMENT MODIFICATION Message-ID: <510C479C.8010101@arin.net> ARIN has issued a response to ACSP Suggestion 2010.16. The suggestion and response text are provided below. This suggestion is now closed and is available at: https://www.arin.net/participate/acsp/suggestions/2010-16.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Under the ARIN Policy Development Process, the board will not ratify any policy which exclusively affects LRSA signatories in a manner inconsistent with its effect on other resource holders. *Response:* This suggestion is now closed as a result of the converging modifications to both the RSA and LRSA. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Feb 1 17:56:27 2013 From: info at arin.net (ARIN) Date: Fri, 01 Feb 2013 17:56:27 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2011.35 - INVOICE PAYMENT THROUGH ARIN ONLINE Message-ID: <510C481B.20000@arin.net> ARIN has issued its initial response to ACSP Suggestion 2011.35. 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-35.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * I should be able to go to ARIN On-line, pull up any unpaid invoice and click on a link to pay it. I shouldn't have to go to a completely separate part of the website and re-enter all the information from the invoice just to pay it. The first rule of business... Make it easy for your customer to pay you. *Response:* This suggestion is now closed as a result of functionality that was implemented and has been confirmed to meet Owen's suggestion. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Feb 1 17:58:43 2013 From: info at arin.net (ARIN) Date: Fri, 01 Feb 2013 17:58:43 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2011.21: ARIN ONLINE USER INTERFACE Message-ID: <510C48A3.7070101@arin.net> ARIN has issued its initial response to ACSP Suggestion 2011.21. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2011-21.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * So: Officially, three suggestions: 1. Immediately bring back resource request templates for the convenience of those of us who understand and liked them. 2. Fix the deficiencies mentioned above in the ARIN on-line process. 3. Spend some time having a good UI designer go through ARIN on-line with a fine-tooth comb and generally improve the over all user experience. BACKGROUND: Per Mark Kosters: Hi Owen I have two suggestions for you. One is to create a ACSP to improve the interaction. Another is to start a discussion on arin-tech-discuss as ARIN engineers hang out there. I think opening it up for discussion would be a good thing. It is up to you. Mark From: Owen DeLong Date: Wed, 27 Apr 2011 12:08:07 -0700 To: Mark Kosters User Subject: Fwd: ARIN-20110425-X18134 Updated This blows [ARIN On-Line resource requests compared to templates] OK, so, we can't do stuff with templates any more, that's bad enough. However, not getting real responses to tickets and having to click on a URL to go review the ticket history where the latest stuff shows up in the middle of the web page presented is even worse. DO NOT WANT Owen *Response:* While suggestion 2012.21 remains open pending the implementation of changes from a user interface / usability assessment of the ARIN website, the specific issue of resource request templates is a duplicate of suggestion 2012.1. This was determined after discussion with Owen. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Feb 1 18:01:32 2013 From: info at arin.net (ARIN) Date: Fri, 01 Feb 2013 18:01:32 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.18: IMPROVE REQUEST SUBMISSION OPTIONS Message-ID: <510C494C.80305@arin.net> ARIN has issued a response to ACSP Suggestion 2012.18. The suggestion and response text are provided below. This suggestion is now closed and is available at: https://www.arin.net/participate/acsp/suggestions/2012-18.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * 1. ARIN should not phase out the hostmaster at arin.net channel for additional communication about requests. Ideally, restoring that as a channel for request submission should be restored. 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. 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. ARIN online has made the entire process unacceptably more time-consuming and difficult. One good step in the right direction would be to provide better integration between hostmaster at arin.net and ARIN on-line. For example, an email to hostmaster at arin.net 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. (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). *Response:* ARIN is closing suggestion 2012.18 as a result of discussions with Owen and arriving at the conclusion that this is duplicate with another open suggestion, specifically 2012.1. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Feb 1 18:04:03 2013 From: info at arin.net (ARIN) Date: Fri, 01 Feb 2013 18:04:03 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.1: RESTORE SOME EMAIL FUNCTIONALITY Message-ID: <510C49E3.30504@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.1. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2012-1.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * First you took away email templates. Now, instead of being at least able to continue working the ticket in email exchanges, I get something useless like this: ARIN-20120216-X4804 - End-user IPv4 Request has been updated. To view the full details, log in to your ARIN Web account and visit the Message Center, or click the URL below. https://www.arin.net/public/communication/ticket/view.xhtml?ticketNo=20120216-X4804 If the URL will not load from this message, copy and paste it into your browser. Please do not reply to this message. Regards, American Registry for Internet Numbers in response to my ticket submission. At least please restore the following email based functionality: Email confirmation of submitted IP requests Full text updates sent to my email when the ticket is updated. The ability to reply to the email in order to interact with ARIN rather than forcing me through the web interface. *Response:* This suggestion is noted as having similar recommended improvements to 2012.18 and 2011.21. Therefore 2012.18 will be closed and the scope of 2011.21 will be constrained to user interface/usability improvements. This suggestion will remain open until implemented or some other future action. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Feb 21 11:23:17 2013 From: info at arin.net (ARIN) Date: Thu, 21 Feb 2013 11:23:17 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2013.2 - Enable Use of Extended Characters in Records Message-ID: <512649F5.4020609@arin.net> ARIN has received a new ACSP Suggestion 2013.2. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2013-2.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * I think we should be able to use characters beyond the basic characters. Currently for example in the Customer name field, only a-z A-Z 0-9 @ ( ) ' # / & , . - + * ! and space are allowed. I think we should be able to put other characters such as accents etc that are found in languages other then English. I think it is sad that in 2013 such restrictions exist. Even the most basic web app coded in 30 minutes can usually handle them. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Feb 27 09:15:19 2013 From: info at arin.net (ARIN) Date: Wed, 27 Feb 2013 09:15:19 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2013.4: CHANGE WHOIS OUTPUT FOR CERTAIN /8 RECORDS Message-ID: <512E14F7.7050408@arin.net> A new suggestion was received through the ACSP, and was assigned number 2013.4 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2013-4.html ARIN will issue an initial response within 10 business days. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Feb 27 09:20:19 2013 From: info at arin.net (ARIN) Date: Wed, 27 Feb 2013 09:20:19 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2013.2 - ENABLE USE OF EXTENDED CHARACTERS IN RECORDS Message-ID: <512E1623.5080707@arin.net> ARIN has issued its initial response to ACSP Suggestion 2013.2. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2013-2.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * I think we should be able to use characters beyond the basic characters. Currently for example in the Customer name field, only a-z A-Z 0-9 @ ( ) ' # / & , . - + * ! and space are allowed. I think we should be able to put other characters such as accents etc that are found in languages other then English. I think it is sad that in 2013 such restrictions exist. Even the most basic web app coded in 30 minutes can usually handle them. Thanks! *Response:* Internationalization is straightforward on the registration side. Unfortunately, internationalization requires special handling on search/retrieval side (directory services). Further, UTF-8 gets complicated when we have legacy directory services that rely on ascii (like the WHOIS protocol). There is an effort underway within the WEIRDS working group of the IETF that is focused on replacing WHOIS with a new protocol with features like internationalization. ARIN, as one of the technology leaders within the WEIRDS WG, will readdress internationalization once IETF has a reasonable standard underway. This suggestion will remain open, but please note that it might be quite some time before there is something definitive coming out of the WEIRDS working group. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Feb 27 09:25:17 2013 From: info at arin.net (ARIN) Date: Wed, 27 Feb 2013 09:25:17 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2013.1 - EMAIL TEMPLATES FOR INTERACTING WITH RSD Message-ID: <512E174D.3000808@arin.net> ARIN has issued its initial response to ACSP Suggestion 2013.1. 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-1.html This has been combined with the similar existing suggestion 2012.1: https://www.arin.net/participate/acsp/suggestions/2012-1.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Return email submitted templates as an option for interacting with RSD. ARIN's Online submission process is overly cumbersome and actively inhibits me from aiding my customers in interacting with ARIN. With a template, I can discuss information with my customer offline prior to involving ARIN. I can complete ARIN templates for my customer prior to my customers submitting them to ARIN. Templates add value to an ISP in educating our customers and an option to our three-party communication that streamlines the ARIN request process. *Response:* Thank you for your suggestion, numbered 2013.1 upon receipt, to restore template and email functionality to better serve your customers as well as interact with ARIN. We will be evaluating a collaboration tool and/or platform to provide the functionality that you have requested as part of our project efforts in 2014. I would like to point out that your request is similar to the existing open suggestion 2012.1. Therefore, we will close your request and note that your suggestion will be combined with 2012.1. We will also note in suggestion 2012.1 that similar functionality has been requested 2013.1 and should be considered in weighing the priority of suggestion 2012.1. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Feb 28 12:21:04 2013 From: info at arin.net (ARIN) Date: Thu, 28 Feb 2013 12:21:04 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.9- IPV6 FEE REDUCTION Message-ID: <512F9200.3010604@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.9. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2012-9.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * I suggest that ARIN make a temporary fee reduction for initial IPv6 assignments (to end-users). Some possibilities are a $1,250 reduction for one or two years or make the initial IPv6 assignments free for a year and then half price for a year. That would do two things: First, it lowers a potential barrier to IPv6 deployment in the enterprise, pure cost of assignment. Second, it puts a touch of urgency on initial IPv6 requests: "Hey boss, we have to at least get our assignment this year if we don't want to be forced to pay later?EUR?" Especially if coordinated with officer attestation of IPv4 exhaustion *Response:* This is in response to your suggestion noted below and assigned number 2011.34 upon receipt of your confirmation. The ARIN Board of Trustees recently adopted a new fee schedule, effective 1 July 2013. The adopted fee schedule is the result of many considerations, including input from multiple fee schedule consultations and suggestions such as this one. As a result of the new fee schedule being announced, this suggestion is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Feb 28 12:23:03 2013 From: info at arin.net (ARIN) Date: Thu, 28 Feb 2013 12:23:03 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.34 - AMEND IPv6 FEE STRUCTURE Message-ID: <512F9277.2050006@arin.net> ARIN has issued its initial response to ACSP Suggestion 2011.34 The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2011-34.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * As a small ISP, we have been working to get our customers involved in IPv6 for years now. Our IPv4 allocation is XSmall, and until this year, our IPv6 allocation has cost us nothing above our IPv4 allocation. As I'm sure you are aware, the new system that is now in place is phasing in IPv6 pricing over the next few years, with the price being the larger of the allocations that the organization has. Unfortunately, this has exposed a problem for very small ISPs which have been moving customers to IPv6, in that we are now faced with the choice of either dropping our IPv6 allocation, or paying for a Small allocation, without the need or availability of the extra V4 addresses. This is basically a tax on smaller ISPs (not borne by any other class of ISP, since they all can get V6 allocations commensurate with their V4 allocations, thus removing the extra fee), during an economic climate that is already making things difficult for smaller organizations. We believe that this practice creates an undo hardship for the smallest of the ISPs in our community, and will increase pressure to drop IPv6 support due to the nearly doubling of ARIN fees. Considering the much larger pool of IPv6 small blocks vs the size of the pool of IPv4 XSmall blocks, this seems capricious. Clearly, making it more expensive for small ISPs to provide IPv6 support runs counter to ARINs goals of increasing IPv6 adoption. We propose that ARIN explicitly allow ISPs who are only using XSmall allocations in IPv4 to continue to bring the benefits of IPv6 to their customers by allowing those organizations to be eligible for Small IPv6 allocations at no extra cost. This should discourage small ISPs from removing IPv6 support as a cost cutting measure or being the only class of ISPs that have to pay EXTRA for IPv6 support. *Response:* This is in response to your suggestion noted below and assigned number 2011.34 upon receipt of your confirmation. The ARIN Board of Trustees recently adopted a new fee schedule, effective 1 July 2013. The adopted fee schedule is the result of many considerations, including input from multiple fee schedule consultations and suggestions such as this one. As a result of the new fee schedule being announced, this suggestion is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: