Thanks for the reply. Looks like I need to do some real world testing,
instead of online research.
On 2014-03-20 13:04, Dean Pemberton wrote:
At the moment because of the way that ARIN have chosen to allow people
to use their RPKI trust anchor, your ROAs may just get ignored unless
they are in a more accessible place.
framework installs the following trust anchors by default
without the need for terms and conditions (ie in an open manner).
Their webpage gives the following guidance:
"Also note that, at least for now, ARIN's trust anchor locator is
absent from the default set of trust anchors. This is not an accident:
it's the direct result of a deliberate policy decision by ARIN to
require anyone using their trust anchor to jump through legal hoops
). If you have a
problem with this, complain to ARIN. If and when ARIN changes this
policy, we will be happy to include their trust anchor locator along
with those of the other RIRs."
On Wed, Mar 19, 2014 at 10:42 AM, Bill Walker <bill(a)wjw.co.nz> wrote:
Hoping someone can help. I am in the middle of a project to build 4
Chicago, London, Sydney and Mumbai. As part of this I have been given
role of creating all the necessary Route objects etc. Our address space
from ARIN, but our ASN's are from RIPE, APNIC & ARIN. I have created
aut-num and route objects in RADb to enable us to manage them from a
point. However I would like to setup ROA records for these route
have setup RPKI with ARIN and created our first ROA object.
Onto my question, am I likely to have operational issues if the route
objects are in RADb and the ROA with ARIN?
NZNOG mailing list