[db-wg] Implementation plan and time line for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.

Dear all,

On Thu, Aug 30, 2018 at 04:26:04PM +0200, Nathalie Trenaman via db-wg wrote:
> On Tuesday, 4 September, we will make changes to the way out-of-region
> objects are handled in the RIPE Database, as directed by the RIPE
> Database Working Group.
> 
> We will implement the following changes in this order between 09:00 and 15:00 UTC+2.
> 
> 1. The RIPE Routing Registry will no longer support the creation of out-of-region ROUTE(6) and AUT-NUM objects
> 2. The creation of ROUTE(6) objects will no longer need authorisation from the ASN holder
> 3. Existing out-of-region objects will have their "source:" attribute changed to "RIPE-NONAUTH”
> 
> For users of NRTM, these changes will be reflected on the FTP website after 00:00 UTC+2 on Wednesday, 5 September.

Based on the above schedule, I'd recommend the following schedule for
NRTM operators such as NTT or RADB:

2018-09-04T07:00:00Z - stop tracking NRTM updates by blocking access to
    whois.ripe.net (193.0.6.135 / 2001:67c:2e8:22::c100:687). This is
    done to prevent picking up the deletions in the RIPE database while
    the RIPE-NONAUTH database is not yet ready for use.

2018-09-05T02:00:00Z - RIPE NCC batch job to generate database dump &
    split files starts

2018-09-05T07:00:00Z - split files for "RIPE" and "RIPE-NONAUTH" should
    now be available on ftp.ripe.net.

2018-09-05T07:00:00Z - add "RIPE-NONAUTH" as IRR source (seed from
    https://ftp.ripe.net/ripe/dbase/RIPE-NONAUTH.CURRENTSERIAL and
    https://ftp.ripe.net/ripe/dbase/split/ripe-nonauth.db.{route,route6,aut-num}.gz)

2018-09-05T07:05:00Z - reseed "RIPE" database from 
    https://ftp.ripe.net/ripe/dbase/RIPE.CURRENTSERIAL and
    https://ftp.ripe.net/ripe/dbase/split/ripe.db.{route,route6,aut-num}.gz

The upside of this approach is that we skip over hundreds of thousands
of mutations via NRTM that will occur in the RIPE source, and avoid
having a gap in continuity for route-objects that belong in
RIPE-NONAUTH.

The downside is that we won't be able to accept new route-objects or
mutations for RIPE/RIPE-NONAUTH route-objects for a period of ~ 24
hours. Given what is to be gained with the implementation of NWI-5, this
to me is an acceptable tradeoff. 

Kind regards,

Job