This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Previous message (by thread): Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Tue Oct 17 10:01:12 CEST 2017
Hi, Op 17 okt. 2017, om 09:53 heeft Job Snijders via db-wg <db-wg at ripe.net> het volgende geschreven: > These two options represent what currently is the lowest hanging fruit > to improve in this problem space. Funny enough, neither of these items > makes things more difficult for anyone involved, on the contrary - by > making route: authorisation easier, _and_ showing what is authoritative > data and what is not, we improve the security posture of the RIPE > community. +1 This is low-hanging fruit indeed, and I see no problems with either of them. Cheers, Sander
- Previous message (by thread): Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]