> The only question in my mind has been, what is the right timetable for
> deprecating the ORIGIN-AS field? Currently, some legacy resource holders
> don’t have access to ARIN’s authenticated IRR or to RPKI and only can use the
> ORIGIN-AS field. However, with the recent changes to the RSA/LRSA and the
> deadline to take advantage of the legacy fee cap, legacy resource holders
> should be properly incentivized to sign an LRSA and resolve this contracting
> issue well within the current timetable for implementation of this policy.
> See the following ARIN Announcements;
>
> https://www.arin.net/announcements/20220912/
> https://www.arin.net/announcements/20220913/
>
> I support this Recommended Draft Policy as written.
While it’s true that ARIN does not make the authenticated IRR or RPKI available
to legacy holders without a contract, those that care
to publish the information are free to do any of the following:
+ Transfer their legacy resources to RIPE and publish RPKI there
+ Use ALT-DB or another IRR to publish their RPSL statements
I will admit that during the original debate, I opposed the creation of this
field expecting that it would end up exactly where it is now. Of limited
use and even less accuracy.
IMHO, it’s well past time to recognize this as a failed experiment and clean up
after it.
Owen
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.
