From info at arin.net Tue Mar 4 11:40:59 2014 From: info at arin.net (ARIN) Date: Tue, 04 Mar 2014 11:40:59 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2014.3: PUBLISH INFORMATION AND SUPPORTING DOCUMENTS FOR EXPERIMENTAL ALLOCATIONS Message-ID: <5316021B.6060205@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.3. The suggestion and response text are provided below. This suggestion is now closed and is available at: https://www.arin.net/participate/acsp/suggestions/2014-3.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Section 11 of the NRPM permits allocations for recognized experimental activity. ARIN should prominently publish both the allocation and the supporting documentation for the experiment on the ARIN website. ARIN should also notify their relevant mailing lists and other technical mailing lists, such as nanog. *Response:* Thank you for submitting your suggestion, assigned identification number 2014.3 . NRPM 11 "Experimental Internet Resource Allocations" states that both the "experiment's objectives and practices" be described in a publicly accessible document and that the "experiment's outcomes be published in a publicly accessible document at the end of the experiment." Because the policy clearly requires any experiment in which ARIN issues resources to be publicly documented, it seems like adding information about these experimental allocations to the ARIN website would not only be consistent with policy, but would also benefit the community. ARIN will therefore proceed with this suggestion. Information published will include a description of the experiment/research project, the resources issued, and a link to the public documentation if one exists. Additionally, ARIN will make an announcement to both the ARIN-PPML and NANOG mailing lists when these experimental allocations are made, to include a brief description of the project and the resources issued for that purpose. Suggestion 2014.3 is now considered closed. Thank you for your participation in the ARIN ACSP. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Mar 4 11:45:05 2014 From: info at arin.net (ARIN) Date: Tue, 04 Mar 2014 11:45:05 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2014.4: SUPPORT HTTPS FOR WHOIS-RWS Message-ID: <53160311.40603@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.4. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2014-4.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * ARIN should support https for whois-rws. It's important not just to protect the privacy of people querying the whois db, but more importantly to ensure the integrity of answers from ARIN. *Response:* Thank you for your suggestion, numbered 2014.4 upon receipt and confirmation, requesting https support for Whois-RWS. ARIN agrees that this would be a very useful, in fact we previously attempted to provide a https solution approximately two years ago. We were unable to complete the effort due to the operational issues described below. In deploying new services for Whois-RWS, ARIN has three requirements. 1) Whois-RWS is fronted by load balancers. 2) The load balancers must support ssl-offloading for effective throughput. 3) We must have both IPv4 and IPv6 capability for any existing or new public service. Unfortunately, we have found that our existing load balancers do not support IPv6 adequately and become unreliable when the ssl-offloading feature is enabled. Despite promises made by our vendor following multiple requests that fix their systems to enable feature parity between IPv4 and IPv6, they have indicated that they will not support these features in a timely manner. Therefore, ARIN is in the process of replacing these load balancers with a vendor who can deliver IPv6 capability. We hope to Have the new load balancers deployed in Q4 of this year, which will permit us to enable https support for Whois-RWS by Q1 of 2015. Thank you for your suggestion; it will remain open until this work is completed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Mar 25 15:05:00 2014 From: info at arin.net (ARIN) Date: Tue, 25 Mar 2014 15:05:00 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2014.6 - RPKI ROAS WITH AN ORIGIN OF AS0 Message-ID: <5331D35C.5060904@arin.net> A new suggestion was received through the ACSP, and was assigned number2014.6 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-6.html ARIN will soon issue an initial response. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Allow creation of RPKI ROAs with an origin of AS0. Rationale: Some prefixes are never intended to be injected into the global routing table. Specifically IXP LAN prefixes. By creating an ROA for AS0, this would create an invalid signature for any announcement. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Mar 25 15:09:06 2014 From: info at arin.net (ARIN) Date: Tue, 25 Mar 2014 15:09:06 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2013.11: PUBLICATION OF LONG-TERM STRATEGIC PLAN Message-ID: <5331D452.8000907@arin.net> ARIN has issued its final response to ACSP Suggestion 2013.11. 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-11.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * ARIN should make public it's long term strategic plan, by publishing it online and sharing it at least once a year at the public meeting. *Response:* ARIN Comment 06 May 2013 Thank you for your suggestion, numbered 2013.11 upon confirmed receipt, to publish ARIN's long-term strategic plan online and share the plan at an ARIN meeting once a year. Staff will review this suggestion with the ARIN Board during their August 2013 workshop/meeting. ARIN will report back to you the decision with which the Board took regarding your suggestion. ARIN Comment 20 March 2014 The ARIN Board of Trustees has published ARIN's 2014-2015 Strategic Plan which can be found at: https://www.arin.net/about_us/corp_docs.html Additionally, John Curran will be briefly review the strategic plan at the upcoming ARIN 33 meeting in Chicago. Thanks for making the suggestion which we now consider closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Mar 25 15:14:17 2014 From: info at arin.net (ARIN) Date: Tue, 25 Mar 2014 15:14:17 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2013.20: AUTO-FILL BILLING CONTACT DATA Message-ID: <5331D589.2090405@arin.net> ARIN has issued its initial response to ACSP Suggestion 2013.20. 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-20.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * When paying an invoice through ARIN-online, I should not have to re-enter my billing information. There should be a check-box to populate that data from my billing contact record. *Response:* We are going to close Suggestion 2013.20: Auto-Fill Billing Contact Data per staff analysis and discussion with you. For clarity to the community, it turns out that there are minimal matches between the billing contact information and the payment (credit card) information. This suggestion was intended to further reduce entry of payment information and was predicated on the assumption that there was a high correlation between the billing contact information and payment information. Staff analysis revealed two items. First, there was a very low correlation between the billing contact and payment information. Second, pre-populating the payment information with billing contact information would increase credit card rejections as payor would largely accept, and not correct, the payment information so that it accurately matched their payment (credit card) information. Based on additional community feedback, ARIN staff has significantly reduced the required payment information to streamline the payment process. As a result much of the payment information has been removed and remaining text clarified. These changes will be released 5 April 2014. Thank you for the suggestion which is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Mar 28 15:20:08 2014 From: info at arin.net (ARIN) Date: Fri, 28 Mar 2014 15:20:08 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2014.6: RPKI ROAS WITH AN ORIGIN OF AS0 Message-ID: <5335CB68.5070803@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.6. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2014-6.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Allow creation of RPKI ROAs with an origin of AS0. Rationale: Some prefixes are never intended to be injected into the global routing table. Specifically IXP LAN prefixes. By creating an ROA for AS0, this would create an invalid signature for any announcement. *Response:* Thank you for your suggestion, numbered 2014.6 upon receipt and confirmation, requesting that we allow for the creation of RPKI ROAs with an origin of AS 0. You raise an excellent point. RFC 6483 section 4 specifically describes AS 0 origination, and it was an oversight in ARIN's RPKI implementation not to allow it. We will be correcting our RPKI system to include this core feature by the end of Q2. Thank you for bringing this to our attention. This suggestion will remain open until this work is completed. This will take 1.5 person months. Please note that these are good-faith, general estimates to include development, testing, and implementation; as such they are subject to change. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Mar 28 15:29:14 2014 From: info at arin.net (ARIN) Date: Fri, 28 Mar 2014 15:29:14 -0400 Subject: [ARIN-Suggestions] New ACSP SUGGESTION 2014.7: TERM LIMITS FOR ARIN ADVISORY COUNCIL Message-ID: <5335CD8A.9080908@arin.net> A new suggestion was received through the ACSP, and was assigned number2014.7 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-7.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Author: Marla Azinger I propose the following be used for AC: Keep the 3 year terms in place and add a 6 year contiguous term limit a 3 year ineligibility year period after a term ends be it 3 year or 6 years After 3 year ineligibility is over a person my run for a position on the AC again. -------------- next part -------------- An HTML attachment was scrubbed... URL: