You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently the v4 address for invalid testing us from APNIC and the v6 address is from ARIN. A second invalid test should be added to test v4/v6 from ARIN space and test v4/v6 from non-ARIN space. This will mark networks as safe/unsafe plus mark their ARIN region coverage.
A second invalid url is needed. Additional space and announcements are needed.
This issue exists because some networks outside of ARINs region refuse to accept the ARIN RPA, even with its new language.
[1] ARIN is the Regional Internet Registry for North America and some of the Caribbean region.
We (AS37271) are one such network. We are unable to agree to the ARIN RPA because of the indemnification that it contains.
We were one of the first major networks to begin dropping ROV invalids, and the first in Africa.
To publically suggest that we do not take routing security seriously, just because we cannot accept the unreasonable legal risks that ARIN seeks to impose on RPs, would be irresponsible and counter productive.
Presently the v4 address for invalid testing us from APNIC and the v6 address is from ARIN. A second invalid test should be added to test v4/v6 from ARIN space and test v4/v6 from non-ARIN space. This will mark networks as safe/unsafe plus mark their ARIN region coverage.
A second invalid url is needed. Additional space and announcements are needed.
This issue exists because some networks outside of ARINs region refuse to accept the ARIN RPA, even with its new language.
[1] ARIN is the Regional Internet Registry for North America and some of the Caribbean region.
[2] ARIN updates it’s RPA October 2019.
The text was updated successfully, but these errors were encountered: