[db-wg] Foreign ROUTE objects in RIPE Database - final decision?

Hi,

On Mon, Oct 09, 2017 at 03:48:43PM +0200, denis walker via db-wg wrote:
> Question - Should the RIPE Database allow creation of ROUTE objects for non RIPE resources?

I wonder if this is the right question to ask, or we should step back
and ask the question

   what can we do to provide a secure routing registry where people
   can document "this prefix will be announced by that AS" in a way
   that is a) strongly authenticated (= only the current holder of the
   address space can create such a route: object), and b) easy to use
   for people building filters (= not having to walk 5 different IRRDBs
   to find the set of prefixes announced by a possible customer)?

instead?  A, B or C may be a consequence of this.


In any case, given that we have no proper global registry, and we have
lots of cross-region routes ("addresses from RIR A, AS number from RIR B"),
we need to find a way to document these properly.

From a user perspective, I like to have all route: objects for my customers
in a single place (RIPE BD, that is), so for me, "A" would be most convenient
- but we need to add some sort of cross-RIR authentication layer.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/db-wg/attachments/20171009/b84c8adf/attachment.sig>