[routing-wg] RIPE IRR DB schema changes (follow-up from Q at mic)

Dear Ruediger, routing-wg,

Today at the microphone Ruediger asked "Where can I read the solution?".

The procedure to move work through db-wg is described here:
https://www.ripe.net/manage-ips-and-asns/db/numbered-work-items

We are now in "phase 2", which states: "For the NWI to move to Phase 3,
the RIPE NCC has to provide the working group with a summary of their
understanding of the solution, and the chairs declare consensus on the
group's acceptance of this summary."

The summary of RIPE NCC's understanding (who are the people supposed to
implement the request) will probably be the closest thing to a formal
description of what the proposed change entails.

RIPE NCC was tasked to do their part through this email
https://www.ripe.net/ripe/mail/archives/db-wg/2017-October/005711.html

So, we are now waiting for RIPE NCC's feedback. This step serves to
ensure that the NCC's understanding and the working group's
understanding actually are aligned.

Kind regards,

Job

ps. I'll try to summarize the 2 changes for the benefit of the working
group. There has been extensive discussion on _why_ these two changes
are deemed helpful, that discussion can be read here:
https://www.ripe.net/ripe/mail/archives/db-wg/2017-October/thread.html

1) To put the "removal of origin authorization" in context of RPSS.
Section 6 (https://tools.ietf.org/html/rfc2725#section-6) states:

    "The key attributes in a route object (key with regard to making it
    unique) contain both an address prefix and an AS number, known as
    the origin AS. The addition of a route object must be validated
    against the authorization criteria for both the AS and the address
    prefix."

Essentially that aspect is changed to:

    "The key attributes in a route object (key with regard to making it
    unique) contain both an address prefix and an AS number, known as
    the origin AS. The addition of a route object must be validated
    against the authorization criteria for the address prefix."

2) Furthermore, if the route/route6 object falls outside the address
space pool that RIPE NCC manages, instead of "source: RIPE", "source:
RIPE-NONAUTH" is used to signify that the RIPE IRR is not an
authoritative source for information about that address prefix.