Skip to Content.
Sympa Menu

wg-irr - Re: [WG-IRR] Retirement of ARIN Non-Authenticated IRR on 31 March 2022

Subject: Registry Working Group

List archive

Re: [WG-IRR] Retirement of ARIN Non-Authenticated IRR on 31 March 2022


Chronological Thread 
  • From: Steve Wallace <>
  • To: "" <>
  • Subject: Re: [WG-IRR] Retirement of ARIN Non-Authenticated IRR on 31 March 2022
  • Date: Wed, 1 Dec 2021 19:15:26 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=JxRMfEeDT8vXfOnLngAywjzTISOUoBhrHJvZX+QObvM=; b=d/Zm8mVjliM2rNHtU/oIB5jgTQgjVV9uftPPS0FYwBOe/7Pb/skrcUJvlGoErPsEIF4p0xQr+7OotMM7F2zCIeKaQAv8dYdVo1CTOaqm66EYKGY3YvV7wHK/b3+SV18rcVxtW9z1dNvTYRXetQWeVuii7RFNBMsWMasamj1gYUIQIrkt3/j/1nrqOMUct6Syn5YKvIWdmOyoA/HGPzIxN1v/UNWqiKCximyqEXWXghncuMyHzOX1kp1nsEg5dTDkaZ7QaScITO9EY6N2LyJanqgXSZfh6ZJG+o8SIiTKYWCiEkr+k+zpLPzm+LE9uUYntQ6vShzBbx5zejJL6sqbqQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZAbx8hPQvmAqjXE9y+tUXkiHOqnRITdERnWqo/5+OrDcdHJ2WYUHPcfWEMogiTCvUYcePpyOLRxmzi9xIFYIWnDW4GNpkUqpTZ9C/RUZdsu5dgDt2wIJM9PlGZ8ZPXO1uc7kkdYO6OINF3laLa7693oG3l/rAVDPvhQeTpvmCPVWzZcEONTe8rK67Jdi8zXlSQyDxQZ1EB8QnwNfhgn0pmj+WG2ZU9eVUlVonoQ+0Ix6DB2AoLYUQ4wIDaJ+vFpQoWmgqLthlX9Rkg2t61W6wIOj3lPI5w9dKlsbp+Qkg9Pyrcv8mM4fOaCUjBTlQA0yHBerihhRNF1kSKO1SF5yYQ==

These are flagged in the router reports. I’m hesitent to publishing a single
list that includes these.

Is being in the router reports effective enough you think?

Steven



> On Dec 1, 2021, at 2:12 PM, Michael H Lambert <> wrote:
>
> Steve,
>
> What are your thoughts on making this list available to the community? It
> is publicly available, after all, assuming one is willing to do the work.
>
> Michael
>
>> On 1 Dec 2021, at 08:54:32, wrote:
>>
>> FYI, there are about 150 prefixes in the Internet2 R&E table that have
>> records only in this deprecated IRR. That’s 150 prefixes that might lose
>> some access at the end of March.
>>
>> Steve
>>
>>
>>> On Dec 1, 2021, at 8:39 AM, David Farmer (via wg-irr Mailing List)
>>> <> wrote:
>>>
>>> This is just a reminder.
>>>
>>> ---------- Forwarded message ---------
>>> From: ARIN <>
>>> Date: Wed, Dec 1, 2021 at 07:32
>>> Subject: [arin-announce] Retirement of ARIN Non-Authenticated IRR on 31
>>> March 2022
>>> To: arin-announce <>
>>>
>>>
>>> ARIN has been engaged in a multi-year project to create and deploy a new
>>> and improved Internet Routing Registry (IRR). As a result of these
>>> efforts, ARIN now provides users with the ability to create, update, and
>>> delete objects in ARIN’s authenticated IRR database using ARIN Online or
>>> ARIN’s RESTful API. Unfortunately, use of ARIN’s previous
>>> non-authenticated email-based IRR service actually increased after ARIN
>>> released its authenticated IRR, in opposition to the outcome ARIN
>>> anticipated when improving its IRR.
>>>
>>> On 8 February 2021, ARIN held a consultation to solicit input on the
>>> retirement of ARIN’s non-authenticated email-based IRR service. This
>>> retirement was originally scheduled for 30 September 2021. Based on
>>> community input, the proposed date for the ARIN-NONAUTH retirement was
>>> delayed to 31 March 2022 to allow more transition time for users. We also
>>> notified by email Points of Contact (POCs) of organizations who have
>>> objects in the ARIN-NONAUTH database of the retirement date and offered
>>> them our assistance with the transition.
>>>
>>> This announcement serves as a reminder that ARIN will retire its
>>> ARIN-NONAUTH IRR database on 31 March 2022. After this date, users will
>>> no longer be able to create, update, or delete records in the
>>> ARIN-NONAUTH database, and the ARIN-NONAUTH data stream will no longer be
>>> available in Near Real Time Mirroring (NRTM) or via FTP or Whois Port 43.
>>>
>>> If you have questions about this transition or need assistance, you can
>>> contact us by:
>>>
>>> - submitting an Ask ARIN ticket or chat with us using your ARIN Online
>>> account
>>> - emailing the Routing Security Team at
>>> - contacting the Registration Services Help Desk by phone Monday through
>>> Friday, 7:00 AM to 7:00 PM ET at +1.703.227.0660
>>>
>>> Regards,
>>>
>>> Brad Gorman
>>> Senior Product Owner, Routing Security
>>> American Registry for Internet Numbers (ARIN)
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> --
>>> ===============================================
>>> David Farmer Email:
>>> 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
>>> ===============================================
>>
>




Archive powered by MHonArc 2.6.24.

Top of Page