24 May
2020
24 May
'20
10:26 p.m.
Hello,
On Sun, May 24, 2020 at 9:17 PM Matt Peterson via 44Net
<44net(a)mailman.ampr.org> wrote:
Can ARDC publicly admit that remaining allocations are
not under ARIN
stewardship *(either under an LRSA or RSA)*? The ARIN whois database shows
updates as recently as a few weeks
<https://whois.arin.net/rest/org/ARDC> ("Last
updated 2020-05-01") ago for the ARDC organization record. Generally ARIN
facilitates these changes via a web portal or API, these services are only
available to ARIN members, which execute an Registration Services Agreement
<https://www.arin.net/about/corporate/agreements/rsa_faq/>. It's highly
likely that the Amazon transaction required that the "left over" prefixes
be formalized with ARIN, likely with an executed RSA contract. Again, as
the steward of this space - ARDC could choose to be more transparent with
the operational nature of the transaction.
False. You do not need to sign an LRSA or RSA to change whois records.
See <https://www.arin.net/resources/guide/legacy/services/>. I suspect
the latest change finally put Chris Smith as tech contact. I don't
recall seeing it before.
When the news came in July of the sale I was excited because I thought
one was signed and we would get to register to ARIN RPKI. Brian
replied to me off-list (sorry for top-posts):
On Fri, Jul 19, 2019 at 8:18 PM Brian Kantor <Brian(a)bkantor.net> wrote:
No worries.
I believe the part we sold changed status, but the
part we kept status was unchanged.
- Brian
On Fri, Jul 19, 2019 at 08:13:37PM -0400, Scott Nicholas wrote:
> Sorry. I figured it would be requirement to sell. That any change basically
> lost legacy status.
>
> On Fri, Jul 19, 2019, 7:27 PM Brian Kantor <Brian(a)bkantor.net> wrote:
>
> > Where did you hear that?
> >
> > It's still legacy space as far as I know!
> >
> > ARDC has NOT signed an RSA or LRSA with ARIN.
> > - Brian
Several large tier 1 providers have begun filtering
based on RPKI data,
such as NTT, ATT, and many others. Does ARDC have a plan to support ROA's?
I think we could run our own RPKI but the ARIN won't sign us.
Therefore we would just have to publish our trust anchor for others to
include in their validators if they must use it..
Regards,
Scott.