From info at arin.net Fri Feb 6 11:21:18 2015 From: info at arin.net (ARIN) Date: Fri, 06 Feb 2015 11:21:18 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2015.3: TIE ROUTE OBJECTS IN IRR TO NETBLOCKS OF RIR DATABASE Message-ID: <54D4E9FE.8080600@arin.net> A new suggestion was received through the ACSP, and was assigned number2015.3 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2015-3.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Description: The ability to tie route objects in the ARIN's IRR to netblocks of the RIR database. This would allow for IRR objects to be marked as authorized against a known trusted source. Value to Community: There has been an issue with the validity off IRR information in the ARIN region. In other regions the RIR's have provided coupled IRR and RIR data to provide strong provenance. Within the operator community there is increasing demand for trustworthy IRR data to improve the integrity of the routing system. The ARIN community would benefit from Operators being able to protect themselves in a more meaningful way. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Feb 12 09:55:56 2015 From: info at arin.net (ARIN) Date: Thu, 12 Feb 2015 09:55:56 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2015.1: CLARIFICATION OF ARIN'S IPV4 COUNTDOWN PHASES Message-ID: <54DCBEFC.4070305@arin.net> ARIN has issued its initial response to ACSP Suggestion 2015.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/2015-1.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Description: Submitter seeks clarification of ARIN's countdown phases (https://www.arin.net/resources/request/ipv4_countdown.html) and intended operational practices after the ARIN general free pool becomes empty, implying that we are substantially in a transfer-only ecosystem. Does ARIN remain in Phase 4 of the IPv4 Countdown Plan, and if not, what is Phase 5? Value to Community: There may be policy tweaks or further ACSP suggestions warranted based on ARIN's operational plans. *Response:* Going forward, including after the depletion of ARIN's IPv4 free pool, we intend to remain in Phase 4 for requests submitted against ARIN's IPv4 free pool. We anticipate requests for IPv4 address space from the ARIN free pool to continue following depletion with customers electing to be placed on the waiting list for unment requests, as specified in paragraph 4.1.8 of the ARIN Number Resource Policy Manual. We do not currently plan to create a 5th phase for IPv4 depletion procedures. We have recently published information on the ARIN public website to increase clarity on this matter. AS number requests, IPv6 requests, and transfer requests of all types will be processed as normal, and not reviewed in accordance with the phased countdown procedures. Thank you again for using the ARIN Consultation and Suggestion Process. This request for clarification will now be closed. If you wish to submit a related suggestion based on this response, please submit a new suggestion. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Feb 12 17:30:34 2015 From: info at arin.net (ARIN) Date: Thu, 12 Feb 2015 17:30:34 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2015.2: SUPPORT HSTS WHERE TECHNICALLY FEASIBLE Message-ID: <54DD298A.9010500@arin.net> ARIN has issued its initial response to ACSP Suggestion 2015.2. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2015-2.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: *Description: Support HSTS where technically feasible. Submitter has noticed that www.arin.net has for some time been https-only, with attempts to connect via http issued a 301 redirect to the https site. An improvement upon this practice would be to support HTTP Strict Transport Security (RFC 6797). At a high level, HSTS informs capable browsers [*] via an additional header in each HTTPS session that for a certain period of time (typically months to one year) they should never try to connect to the site via unencrypted HTTP. This is an additional layer of protection against man in the middle attacks. [*] At this writing, HSTS is widely supported (Chrome, Firefox, Opera, Safari, and upcoming in IE for Windows 10). Value to Community: Increased protection against spoofing/MITM attacks *Response:* Thank you for submitting your suggestion, numbered 2015.2, on the topic of HSTS support for the ARIN website. We will explore HSTS support to our website. Provided there are no adverse effects in testing, we will be rolling this improvement out within the next 60 days. Thank you again for suggesting this improvement. This ACSP item will remain open until the work is completed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Feb 20 17:00:59 2015 From: info at arin.net (ARIN) Date: Fri, 20 Feb 2015 17:00:59 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2015.3: TIE ROUTE OBJECTS IN IRR TO NETBLOCKS OF RIR DATABASE Message-ID: <54E7AE9B.7040005@arin.net> ARIN has issued its initial response to ACSP Suggestion 2015.3. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2015-3.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * The ability to tie route objects in the ARIN's IRR to netblocks of the RIR database. This would allow for IRR objects to be marked as authorized against a known trusted source. Value to Community: There has been an issue with the validity off IRR information in the ARIN region. In other regions the RIR's have provided coupled IRR and RIR data to provide strong provenance. Within the operator community there is increasing demand for trustworthy IRR data to improve the integrity of the routing system. The ARIN community would benefit from Operators being able to protect themselves in a more meaningful way. *Response:* Thank you for submitting your suggestion, numbered 2015.3, on the topic of tying route objects in ARIN's IRR to netblocks of the RIR database. We have a community consultation planned for Q1 2015 to discuss this and other IRR related suggestions recently submitted. We will ensure the language of your suggestion is included in the consultation that will open in March. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Feb 24 17:38:25 2015 From: info at arin.net (ARIN) Date: Tue, 24 Feb 2015 17:38:25 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2014.20: TRANSPARENCY OF ARIN BOARD OF TRUSTEES ACTIONS Message-ID: <54ECFD61.9020003@arin.net> ARIN has issued a response to ACSP Suggestion 2014.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/2014-20.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Increase awareness and transparency of ARIN Board of Trustees actions. 1) Take detailed minutes of ARIN Board meetings along the lines of what is done for the ARIN AC. 2)Publish Board of Trustees agenda 7 days in advance of a Board meeting. 3) Send notice of Board meeting and agenda to ARIN ppml 7 days in advance of Board meeting. 4) Send Board meeting minutes to ppml after existing review period, as is does for AC minutes. (Documenting the minute review periods on the ARIN website would also be nice) Value to Community: These steps will increase accountability of Board actions, as well as provide the community increased awareness and transparency of Board actions. *Response:* ARIN Comment 22 July 2014 Thank you for your suggestion, numbered 2014.20, regarding increased awareness and transparency of ARIN Board of Trustees actions. We will deliver this suggestion as a formal agenda item at an upcoming ARIN Board of Trustees meeting for consideration. ARIN staff will follow Board guidance on the suggestion. Thank you for participating in the ARIN Suggestion and Consultation Process. We will keep this suggestion open until it has been reviewed and considered by the ARIN Board of Trustees. ARIN Comment 24 February 2015 Thank you for your suggestion numbered 2014.20, regarding increased awareness and transparency of ARIN Board of Trustees actions. The ARIN Board of Trustees has considered this suggestion and taken specific steps to increase transparency, including formalizing the publication of Board agendas in advance of meetings and publication of supporting materials in the Board meeting minutes. Note that ARIN AC minutes are not published to the Public Policy Mailing List (PPML), but a summary of any policy actions, whether they originate from the ARIN AC or the ARIN Board of Trustees. We believe that this addresses your suggestion and it is now closed. Thank you for participating in the ARIN Suggestion and Consultation Process. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Feb 24 17:42:24 2015 From: info at arin.net (ARIN) Date: Tue, 24 Feb 2015 17:42:24 -0500 Subject: [ARIN-Suggestions] Response to Suggestion 2014.7: TERM LIMITS FOR ARIN ADVISORY COUNCIL Message-ID: <54ECFE50.1030006@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.7. 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-7.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * 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 3year or 6years After 3 year ineligibility is over a person my run for a position on the AC again. *Response:* ARIN Comment 10 April 2014 Thank you for your suggestion, numbered 2014.7 upon receipt and confirmation. Your suggestion that ARIN institute a 6-year contiguous term limit followed by a 3-year ineligibility period for Advisory Council representatives has been forwarded to the ARIN Board of Trustees' Governance Committee as input to their deliberations regarding ARIN's governance. This suggestion will remain open until such time that we have conclusion from the committee. ARIN Comment 24 February 2015 Thank you for your suggestion, numbered 2014.7, regarding term limits for the ARIN Advisory Council. Your suggestion that ARIN institute a 6-year contiguous term limit followed by a 3-year ineligibility period for Advisory Council representatives was forwarded to the ARIN Board of Trustees' Governance Committee (GovCom) as input to their deliberations regarding ARIN's governance. This suggestion was discussed by the ARIN GovCom and Board at the April 2014 meeting, as well as discussed at the ARIN 33 Member Meeting. While there was no official community consultation, there was substantial discussion on various ARIN mailing lists on this topic with no consensus. Given this input in its June 2014 report, the ARIN GovCom indicated that refinements to improve transparency and accountability were the thrust of its work in 2014, and that based on the input received it was not recommending any further changes at this time. As such, we are closing this suggestion, and thank you for your participation in the ARIN Suggestion and Consultation Process. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Feb 25 15:46:02 2015 From: info at arin.net (ARIN) Date: Wed, 25 Feb 2015 15:46:02 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2015.4: ASN NAMING IN WHOIS Message-ID: <54EE348A.3060602@arin.net> A new suggestion was received through the ACSP, and was assigned number2015.4 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2015-4.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * WHOIS info does not allow to put unique names on ASN's that are part of a range assignment. As we prepare to roll out a BGP-LU product it would be super helpful on several of our range allocations if we could place the name of the actual metro area being served. Value to Community: reflect more accurate and useful information in the database. -------------- next part -------------- An HTML attachment was scrubbed... URL: