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] Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
- Previous message (by thread): Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
- Next message (by thread): [db-wg] Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Jun 20 00:25:42 CEST 2017
In message <mailman.1675.1497881039.4885.db-wg at ripe.net>, Jeroen Massar <jeroen at massar.ch> wrote: >Thus the big question: why does the RIPE NCC allow that junk to exist >there? (Noting that it was shown last year that that "organisation" >inserted bogus stuff too... and it has not been resolved) That is indeed the Big Question. What is the answer? I am seriously asking. I also am aware of at least one very large clump of IPv4-related "pollution" within the RIPE data base... about which I will say more soon (although as far as I can tell, nobody on -any- of the RIPE mailing lists gives a damn about such things)... and I also wonder why no one seems to care about all of the blatantly bogus pollution in the RIPE data base. I can only guess that the answer to that probably has a lot to do with money, one way or another. covfefe
- Previous message (by thread): Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
- Next message (by thread): [db-wg] Cleaning up SixXS inet6nums & 400.000++ junk inet6nums from 2a07:7ec0::/29 in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]