Fwd: [arin-announce] Upcoming Web-Based Internet Routing Registry Deployment
FYI, This should simplify things for many of you to get your prefixes into the IRR. ---------- Forwarded message --------- From: ARIN <info@arin.net> Date: Fri, Apr 17, 2020 at 1:31 PM Subject: [arin-announce] Upcoming Web-Based Internet Routing Registry Deployment To: <arin-announce@arin.net> On 17 March 2020, we notified our community via a blog post on TeamARIN that we were in the process of developing a new web-based Internet Routing Registry (IRR). That blog post can be read at the following link: https://teamarin.net/2020/03/17/making-progress-on-arins-new-web-based-irr/ Now, we are pleased to announce that the initial deployment of this new web-based IRR will occur on or around 10 June 2020. This deployment will provide core functionality to create, edit, and delete IRR objects via ARIN Online. The existing IRR-email interface will continue to function; however, when your organization begins using the web-based IRR, you will lose access to the email interface. For that reason, if your organization would like to retain access to the email interface, please do not make any changes to IRR objects using ARIN Online. As part of this deployment, ARIN will analyze data in the current IRR before migration and objects will be placed into two categories: * Objects that were created by the authorized organization and meet all ARIN requirements will be migrated to the new system and placed in an authorized dataset (“ARIN-AUTH”). They can be managed in either ARIN Online or via email templates. (Note that using ARIN Online the first time to manage these objects will permanently disallow future changes using email templates.) * Objects that cannot be verified will still be migrated, but placed into a non-authorized (“ARIN-NONAUTH”) dataset. These objects can be managed only by using email templates or by creating a Help Desk Ticket using the Ask ARIN feature in ARIN Online. Users who get routing data from ARIN’s IRR will need to make some changes when connecting to our two Near Real Time Monitoring (NRTM) streams: ARIN-AUTH and ARIN-NONAUTH. Port 43 whois queries to rr.arin.net will still be accepted and return both authorized and unauthorized objects. More information will be provided in later updates. Best regards, John Sweeting Chief Customer Officer American Registry for Internet Numbers (ARIN) _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info@arin.net if you experience any issues. -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
participants (1)
-
David Farmer