[arin-tech-discuss] IRR PGP key records

[Mark Kosters]

On 8/25/15, 5:47 PM, "arin-tech-discuss-bounces at arin.net on behalf of
Oliver Ddin" <arin-tech-discuss-bounces at arin.net on behalf of
oliver.d at prodege.com> wrote:

>Hi folks,
>
>Has anyone successfully managed to submit a PGP key to ARIN¹s IRR? The
>instructions seem to be incorrect as I initially submitted just the record
>and the IRR would just fail to recognize the base64 key data (RSA4096)
>then
>I tried taking the RIPE approach and sending the e-mail with a PGP
>signature
>by the same key over it but now I get no response at all.
>
>I did open a ticket with ARIN but it¹s been over a week and nothing has
>been
>done so I figured I might as well reach out to the community to see if
>someone else has succeeded where I have failed.

Hi Oliver

We've taken some time to look at this problem. If you follow the
instructions in https://www.arin.net/resources/routing/#pgp to the letter,
it will work. But it needs to be exact and the failure modes are poor
(i.e. It fails silently if there is any formatting error). We realize that
this not good and have a work-around that will be coming out shortly to
help for the near-term. Basically we are going to do a couple of things:

1) We will create a script that takes a PGP key and other pertinent
information as input, formulates an email, and sends it into ARIN's IRR
system. This script will be placed on GitHub so people can run it
themselves. We will announce the availability on the list when the script
is done. 

2) We will be updating our instructions on the website for those who don't
want to or cannot run the script to send their PGP key and other necessary
information to hostmaster at arin.net. ARIN staff will then take care of this
registration on their behalf.

ARIN is in the planning process of replacing the current IRR software
suite so we really don't want to devote much time on fixing the internals
of very old RIPE code. More details on this upgrade will be coming shortly.

Thanks for bringing this to our attention and I apologize for the delay in
responding.

Regards,
Mark
ARIN CTO