From info at arin.net Tue Nov 6 10:40:59 2012 From: info at arin.net (ARIN) Date: Tue, 06 Nov 2012 10:40:59 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2011.20: Remove result limit for Whois-RWS child network queries Message-ID: <50992F8B.6010104@arin.net> A new suggestion was received through the ACSP, and was assigned number 2012.20 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2012-20.html ARIN will soon issue an initial response. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) *___ * Suggestion: Remove result limit for Whois-RWS child network queries Allow for more than 256 results for a RESTful query of network children (e.g. whois SWIPs for a parent netblock). An example of this issue can be seen at http://whois.arin.net/rest/net/NET-69-0-0-0-0/children - I would recommend to keep the existing behavior of limiting /children requests to only 256 entries (with a warning that the output has been truncated) so as not to overload any systems which aren't expecting a large volume of output. Provide a flag to allow a query which is not truncated (e.g. /children/full) for when the full output is desired. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Nov 6 10:47:18 2012 From: info at arin.net (ARIN) Date: Tue, 06 Nov 2012 10:47:18 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.19: Make Company Name optional for billing form Message-ID: <50993106.4030504@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.19. 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-19.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * In the billing form on ARIN On-Line, Company name should be an optional field for the person paying the bill. Currently it is mandatory and requires 3-150 characters. It is nonsensical in the case where an individual may be paying an ARIN invoice. *Response:* It is a timely suggestion, as you may know, ARIN has just implemented a new online credit card payment process whereas the organization name is no longer required, as per your suggestion. The payee needs to enter the following data if they are not logged into ARIN Online: OrgID; invoice number, and dollar amount. The remaining information is then automatically populated. If the payee is logged into ARIN Online, all they need to do is click "pay" on the invoice display page and all the information is then auto-populated. We hope this satisfies your suggestion. Suggestion 2012.19 is now closed. Sincerely, Financial Services American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Nov 6 10:50:54 2012 From: info at arin.net (ARIN) Date: Tue, 06 Nov 2012 10:50:54 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.18 - Improve Request Submission Options Message-ID: <509931DE.4030701@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.18. The suggestion and response text are provided below. This suggestion remains open 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:* I wanted to formally acknowledge your suggestion 2012.18: Improve Request Submission Options. We will take your suggestions under consideration as we complete ARIN's 2013 operating plan. Once the plan is approved, we will follow back up with you on those items we plan to implement in 2013. This suggestion will remain open. Regards, Nate Davis Chief Operations Officer American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Nov 6 10:53:32 2012 From: info at arin.net (ARIN) Date: Tue, 06 Nov 2012 10:53:32 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2012.21: NOTE WHEN POLICY PROPOSALS RESULT FROM STAFF EXPERIENCE REPORTS Message-ID: <5099327C.4010707@arin.net> A new suggestion was received through the ACSP, and was assigned number201.21 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2012-21.html ARIN will soon issue an initial response. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) ___ Suggestion: Policy proposals that result from staff experience reports should be noted as such in the proposal announcements and presentations. It will help show value of such experience reports. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Nov 13 16:52:17 2012 From: info at arin.net (ARIN) Date: Tue, 13 Nov 2012 16:52:17 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.17 - CHANGES TO DOCUMENTATION REQUIREMENTS FOR ASN REQUESTS Message-ID: <50A2C111.3000002@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.17. The suggestion and response text are provided below. This suggestion remains is now closed and is available at: https://www.arin.net/participate/acsp/suggestions/2012-17.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * ARIN should accept any valid evidence of a unique routing policy and/or multihomed connectivity as proof of the need for an autonomous system number, per policy. It is ridiculous for ARIN to insist on copies of signed agreements as the only form of acceptable evidence. As an example, ARIN can independently corroborate that route-views shows a prefix or collection of prefixes terminating at or being routed via the stated transit providers in the case where an organization is moving from static-routed connectivity to BGP-based multi-homing. *Response:* ARIN has received your suggestion entitled "Changes to Documentation Requirements for ASN Requests" and assigned it the number 2012.17. We would like to first take the time to clarify our existing procedures so that you have a better understanding of what is required since there seems to be some misconceptions. For example, your suggestion to "independently corroborate that route-views shows a prefix or collection of prefixes terminating at or being routed via the stated transit providers " is already standard practice at ARIN. ARIN accepts a pretty broad range of things to verify connectivity. We will accept a reassignment from an ISP to the requester, or an ISP routing a block that's assigned/reassigned to the requester, or a copy of their signed connectivity agreement, or a recent/bill invoice showing the connectivity. It should be noted that when an organization is requesting an additional AS number, we need to verify not just connectivity, but that a second AS number is justified. We typically can't verify that with a reassignment from an ISP or based on routing of IP addresses since those don't tell us the location(s) at which the customer has connectivity, and non-connected multi-homed networks at geographically different sites are very often the requester's justification for an additional AS number. Obtaining a copy of a signed connectivity agreement for the new location or a recent bill/invoice showing connectivity at the new location may be the only way to verify a second AS number is justified. So in closing, we would like to state that ARIN already accepts multiple verification methods for connectivity during an ASN request, including the one you used as an example. If you have any additional feedback or ideas for new verification methods, we would be happy to review them. Thank you for taking the time to participate in the ARIN Consultation and Suggestion Process. Suggestion 2012.17 is closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Nov 13 16:56:44 2012 From: info at arin.net (ARIN) Date: Tue, 13 Nov 2012 16:56:44 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.21 - NOTE WHEN POLICY PROPOSALS RESULT FROM STAFF EXPERIENCE REPORTS Message-ID: <50A2C21C.6020100@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.21. 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-21.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Policy proposals that result from staff experience reports should be noted as such in the proposal announcements and presentations. It will help show value of such experience reports. *Response:* ARIN has received your suggestion and assigned it the number 2012.21. You suggested that it would be helpful to note in public policy presentations at ARIN meetings if a proposal has been developed in response to a staff experience report. For future meetings, ARIN staff will compare incoming proposals with issues raised by staff in Policy Implementation and Experience reports. If a proposal deals with an area that has been reported on by staff in a recent Policy Implementation and Experience Report, then staff will make a note of that in the staff assessment and in it's history so that it is noted when the proposal is presented at a Public Policy Meeting. Thank you for this valuable feedback; this suggestion is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Nov 15 12:45:10 2012 From: info at arin.net (ARIN) Date: Thu, 15 Nov 2012 12:45:10 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2012.22 - ADDITIONAL DETAIL IN NRPM CHANGE LOG Message-ID: <50A52A26.1060402@arin.net> A new suggestion was received through the ACSP, and was assigned number2012.22 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2012-22.html ARIN will issue an initial response within 10 business days.Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * The NRPM Change log ( https://www.arin.net/policy/nrpm_changelog.html ) is an excellent record of the changes in the NRPM over time. Most changes are caused by the implementation of Draft Policies, and the related Draft Policies for each change, in addition to the sections changed, are recorded for each change and the Draft Policies may be reviewed to provide more detailed context regarding the change in question. However, in the case of editorial changes there is no additional context provided, only a listing of the sections changed. Future, editorial changes should provide a reference explaining the details of the change and possibly the rationale or motivation for the editorial change for historical reference. If possible, previous editorial changes should be updated with such information as well. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Nov 19 17:30:19 2012 From: info at arin.net (ARIN) Date: Mon, 19 Nov 2012 17:30:19 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.22 - ADDITIONAL DETAIL IN NRPM CHANGE LOG Message-ID: <50AAB2FB.1010503@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.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/2012-22.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * The NRPM Change log ( https://www.arin.net/policy/nrpm_changelog.html ) is an excellent record of the changes in the NRPM over time. Most changes are caused by the implementation of Draft Policies, and the related Draft Policies for each change, in addition to the sections changed, are recorded for each change and the Draft Policies may be reviewed to provide more detailed context regarding the change in question. However, in the case of editorial changes there is no additional context provided, only a listing of the sections changed. Future, editorial changes should provide a reference explaining the details of the change and possibly the rationale or motivation for the editorial change for historical reference. If possible, previous editorial changes should be updated with such information as well. Thanks. *Response:* Thank you for your suggestion, numbered 2012.22 upon receipt, requesting some short description in the NRPM change log when editorial changes are made. We think this is a valid request and going forward we will add a small description about what prompted the editorial update. As time permits we will back fill the change log with this information where appropriate. Thank you for participating in the ARIN Consultation and Suggestion Process. Suggestion 2012.22 is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Nov 28 14:29:06 2012 From: info at arin.net (ARIN) Date: Wed, 28 Nov 2012 14:29:06 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2012.20 - REMOVE RESULT LIMIT FOR WHOIS-RWS CHILD NETWORK QUERIES Message-ID: <50B66602.8080007@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.20. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2012-20.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Allow for more than 256 results for a RESTful query of network children (e.g. whois SWIPs for a parent netblock). An example of this issue can be seen at http://whois.arin.net/rest/net/NET-69-0-0-0-0/children - I would recommend to keep the existing behavior of limiting /children requests to only 256 entries (with a warning that the output has been truncated) so as not to overload any systems which aren't expecting a large volume of output. Provide a flag to allow a query which is not truncated (e.g. /children/full) for when the full output is desired. *Response:* Thank you for your suggestion, which was numbered 2012.20 upon receipt. This suggestion is reasonable and we plan on adding it to the list of outstanding projects awaiting prioritization found at: https://www.arin.net/features/#tbd Please note that we will be consulting the ARIN community to help access prioritization of improvements of existing systems, as well as additional services that the community desires. This will be fed back into ARIN's planning process for scheduling development resources to complete the suggestion. ARIN will keep this suggestion open until it is completed. -------------- next part -------------- An HTML attachment was scrubbed... URL: