From info at arin.net Mon Jul 16 11:36:56 2018 From: info at arin.net (ARIN) Date: Mon, 16 Jul 2018 11:36:56 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018-13: RPKI-based BGP Origin Validation Message-ID: <4205ebe1-faff-842e-d7e2-f9ca04b3026a@arin.net> On 13 July we received a new suggestion, numbered 2018-13 upon confirmed receipt, requesting that ARIN enable RPKI-based BGP origin validation on our Autonomous System numbers and reject "invalid" route announcements. The full text of the suggestion is available for review at: https://www.arin.net/participate/acsp/suggestions/2018-13.html We will be issuing our response to this suggestion soon. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jul 20 11:32:22 2018 From: info at arin.net (ARIN) Date: Fri, 20 Jul 2018 11:32:22 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018-14: SUPPORT RRDP FOR RPKI PUBLICATION Message-ID: <4de16605-02a3-f253-0b6a-e832544ed4a7@arin.net> On 20 July we received a new suggestion, numbered 2018-14 upon confirmed receipt, requesting that ARIN support RDAP for RPKI publication. The full text of the suggestion is available for review at: https://www.arin.net/participate/acsp/suggestions/2018-14.html We will be issuing our response to this suggestion soon. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Jul 30 11:15:28 2018 From: info at arin.net (ARIN) Date: Mon, 30 Jul 2018 11:15:28 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018.15: Add "routing" and "DNS" Points of Contact Message-ID: <76ab75d1-097f-86bf-5f5a-f9b036825f47@arin.net> On 30 July we received a new suggestion, numbered 2018.15 upon confirmed receipt, requesting that ARIN add two new optional Point of Contact (POC) types for routing and DNS. https://www.arin.net/participate/acsp/suggestions/2018-15.html Description: Add "Routing" and "DNS" points of contact. There are currently a number of different types of Point of Contact, including Administrative, Technical, Abuse, and others. I suggest that we add two more types of optional POC: one for routing contacts (such as would be responsible for IRR and RPKI implementation) and one for DNS contacts (such as would be responsible for updating in-addr DNSSEC DS records and in-addr DNS nameserver delegations). Value to Community: This will allow ARIN resource recipients to optionally delegate authority for specific technical tasks (updating IRR, RPKI, DS, and NS records in ARIN's databases, for example) to the appropriate people within their organization, without exposing all functions to all POCs. It will also allow network operators to use the more specific whois POC records to directly contact the appropriate people responsible for these functions within counterpart networks. We will be issuing our response to this suggestion soon. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)