From info at arin.net Wed Jun 4 12:04:31 2014 From: info at arin.net (ARIN) Date: Wed, 04 Jun 2014 12:04:31 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2014.10: CHANGES TO CANDIDATE SPEECHES Message-ID: <538F438F.2090400@arin.net> A new suggestion was received through the ACSP, and was assigned number2014.10 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-10.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * With election time starting to be on the horizon again, it's time for ARIN to address the events of October in Phoenix, where an outgoing Board member hijacked the agenda to stump for his preferred board candidates, and an AC candidate used his speech time to endorse others. I think that for the integrity of the ARIN election process to remain intact, ARIN either needs to remove candidate speeches and stick to written materials, or have the speeches given in premade form like a video or something on the ARIN website. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Jun 5 13:41:15 2014 From: info at arin.net (ARIN) Date: Thu, 05 Jun 2014 13:41:15 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2014.10: CHANGES TO CANDIDATE SPEECHES Message-ID: <5390ABBB.8090401@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.10. The suggestion and response text are provided below. This suggestion remains open and is available at: https://www.arin.net/participate/acsp/suggestions/2014-10.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * With election time starting to be on the horizon again, it's time for ARIN to address the events of October in Phoenix, where an outgoing Board member hijacked the agenda to stump for his preferred board candidates, and an AC candidate used his speech time to endorse others. I think that for the integrity of the ARIN election process to remain intact, ARIN either needs to remove candidate speeches and stick to written materials, or have the speeches given in premade form like a video or something on the ARIN website. * * *Response:* Thanks for your suggestion, numbered 2014.10 upon confirmed receipt, regarding candidate speeches during the election process at the ARIN fall meetings. ARIN will address this suggestion in two separate actions. First, the 2014 Election Process will clarify that the purpose of candidate speeches is to allow candidates to briefly state their own qualifications and positions for consideration by the electorate. Second, this suggestion will be provided to the 2014 Nomination Committee (NomCom) for their post-election review to determine if any further changes in this area are recommended. Thank you for participating in the ARIN Suggestion and Consultation Process. We will keep this suggestion open until implementation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Jun 16 15:34:16 2014 From: info at arin.net (ARIN) Date: Mon, 16 Jun 2014 15:34:16 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2014.12: WHOIS RESPONSE FOR IPV6 UNIQUE LOCAL ADDRESSES FC00::/7 Message-ID: <539F46B8.4010909@arin.net> A new suggestion was received through the ACSP, and was assigned number 2014.12 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-12.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Please install a 'whois' entry for IPv6 Unique Local Addresses fc00::/7 When performing this query: $ whois -h whois.arin.net fc00::/7 . . . the results are: No match found for fc00::/7. However, per http://tools.ietf.org/html/rfc4193, that prefix has been identified as "Unique Local" addressing. RIPE has registered it accordingly: $ whois -h whois.ripe.net fc00::/7 inet6num: fc00::/7 netname: IANA-BLK descr: Unique Local Addresses (ULAs) country: EU # Country is really world wide org: ORG-IANA1-RIPE admin-c: IANA1-RIPE tech-c: RFC1918-RIPE mnt-by: RIPE-NCC-HM-MNT mnt-lower: RIPE-NCC-HM-MNT remarks: MNTNER added for RIPE NCC DB Group testing 20121024 More specific objects will be created and deleted during this testing over the next few days mnt-lower: aardvark-mnt remarks: This network should never be routed outside an enterprise remarks: See RFC4193 for further information status: ALLOCATED-BY-RIR remarks: This network in not allocated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Jun 18 12:02:44 2014 From: info at arin.net (ARIN) Date: Wed, 18 Jun 2014 12:02:44 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2014.13: STAFF A FAST-LANE FOR IPV6 AND ASN REQUEST Message-ID: <53A1B824.5080703@arin.net> A new suggestion was received through the ACSP, and was assigned number2014.13 upon receipt of confirmation. The text of the Suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2014-13.html ARIN will issue an initial response within 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Since Registration Services is backlogged with IPv4 requests and extra processing measures for those requests, ARIN should devote some amount of staff resources to providing a fast-lane for IPv6 and ASN requests so that they are not stuck behind the backlog of requests for antiquated protocols nearing end-of-life. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Jun 18 13:12:23 2014 From: info at arin.net (ARIN) Date: Wed, 18 Jun 2014 13:12:23 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2014.9: ANONYMIZING INFORMATION Message-ID: <53A1C877.4040007@arin.net> ARIN has issued its initial response to ACSP Suggestion 2012.XX. 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-9.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Inclusion of Registered participants, asked to anonymize their information. This would refer to the Original Prime Contractor. *Response:* Thank you for suggestion, numbered 2014.9, in which you asked that your information not be anonymized in our Whois directory service. Our Whois service provides contact information, for network operation purposes, associated with a large set of IP addresses (known as a "block"), usually referring either to contacts associated with an Internet Service Provider (ISP) or organization that received its space directly from ARIN. It does not provide listings or contact information for individual IP addresses. As such, your suggestion is unfortunately out-of-scope, and we are unable to assist you. This suggestion will now be closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Wed Jun 18 18:25:58 2014 From: info at arin.net (ARIN) Date: Wed, 18 Jun 2014 18:25:58 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2014.13: STAFF A FAST-LANE FOR IPV6 AND ASN REQUESTS Message-ID: <53A211F6.3050506@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.13. 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-13.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * Since Registration Services is backlogged with IPv4 requests and extra processing measures for those requests, ARIN should devote some amount of staff resources to providing a fast-lane for IPv6 and ASN requests so that they are not stuck behind the backlog of requests for antiquated protocols nearing end-of-life. *Response:* The Service Level Agreement (SLA) that the Registration Services Department has committed to over the past 10 years, and in the 7 years preceding its formalization, has been to respond to all ticket requests within a 2 business day period. Currently, Registration Services is working within a 2-4 business day response window for IPv4 requests, due not only to the new operational procedures put into place when we moved into Phase 4 of the IPv4 Countdown plan, but also in part to the complexities we are seeing with many of the incoming IPv4 requests. All other requests including Orgs, POCs, postmaster and Ask ARIN questions, transfers, IPv6, and ASNs, are currently being responded to within the designated 2 day response window. We will work diligently to ensure these responses continue to meet our 2 business day SLA and will evaluate ways to close the response time gap on IPv4 requests going forward. It is our intention to keep the processing of ASN and IPv6 requests within our SLA without the creation of a fast-lane process. We have noted your desire that these types of requests not be slowed by the additional processing time requirements of the fourth phase of the IPv4 countdown plan. We are committed to meeting the SLA, and thank you for your patience. This suggestion is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Jun 24 15:07:37 2014 From: info at arin.net (ARIN) Date: Tue, 24 Jun 2014 15:07:37 -0400 Subject: [ARIN-Suggestions] Response to Suggestion 2014.11: CHANGES TO TEMPLATE & PROCESS FOR NETMODS Message-ID: <53A9CC79.1070806@arin.net> ARIN has issued its initial response to ACSP Suggestion 2014.11. The suggestion and response text are provided below. This suggestion remains open until implemented and is available at: https://www.arin.net/participate/acsp/suggestions/2014-11.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) **** Suggestion: * The netmod template reverts to manual processing by hostmaster when the prefix length matches the allocation. For example, ARIN allocates a /18 and you have swip'd out the entire /18. It seems the automation doesn't understand which record to remove (the parent or the subdelegation) Suggestion: Change the netmod template and process to accept submissions to Modify or Remove by Net Handle. When you swip the prefix it has a unique nethandle, separate from the parent allocation. This should be sufficient to tell which record should be modified. If you don't want to allow modification or removal of the direct allocation with a Netmod, and if all direct allocation NetHandles end in -01, it should be easy enough to exclude those. This would cut down the number of templates that have to be manually processed. *Response:* We agree the process related to your suggestion can be improved. We plan to make the improvements you suggest in parallel with other SWIP related enhancements. We currently have this work prioritized under the title "SWIP Easy" on our planned functionality page. https://www.arin.net/features/ Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. -------------- next part -------------- An HTML attachment was scrubbed... URL: