Adding the NACR filter program has helped make the NACR process work better. However, there needs to be cleaner data and the maintainer objects need to be cleaner.
The next step will be an addition to the filter program to do the NACR
processing
and do the gated.conf automatically and compare it to what
is generated manually. This is about a month away.
Next, route objects will be accepted. The route object must include the advisory line for AS list. This is about six weeks away. NACRs can still be used.
RIPE-123 discusses the authorization mechanism in use fro the RRDB.
Next, AS690 policy will be expressed in general
RIPE-181 format.
Netlists will be used in gated.conf express the policy.
There may be some mildly inconsistent policy for some nets while this
happens.
Eventually, aslist will no longer be used to generate AS690 policies.
Entities may choose to register in multiple registries. Those registries may choose to reject those registrations.
Do this NOW: