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/[email protected]/
[anti-abuse-wg] 2019-03 and over-reach
- Previous message (by thread): [anti-abuse-wg] 2019-03 and over-reach
- Next message (by thread): [anti-abuse-wg] 2019-03 and over-reach
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Sat Mar 23 19:52:44 CET 2019
Hank Nussbacher wrote on 23/03/2019 17:23: > Purity of concept will result in massive gov't intervention since we > will have shown that we don't know how to self-regulate. > The voices are already there: > https://hackernoon.com/why-the-internet-must-be-regulated-9d65031e7491 > If you have an alternative solution, not even a better one, please > suggest it. There is no quick or single solution because this is a complex problem which involves people and peoples' interactions with the internet. MANRS is beginning to make a difference and will continue to gain support. Several of the major global IXPs have implemented strict route-server filtering over the last 12-18 months. There is a good deal of pressure being put on transit service providers to implement prefix filtering on their customer network handoff points. RPKI adoption is now taking off in a big way - see AT&T's recent announcement and NTT's plans. Commoditisation of RPKI support for IXP route servers will be available within weeks. RPKI will help a good deal, and it shows more promise than IRR DB based filtering due to long term quality issues with IRRDBs in some areas (e.g. US, LATAM). Nick
- Previous message (by thread): [anti-abuse-wg] 2019-03 and over-reach
- Next message (by thread): [anti-abuse-wg] 2019-03 and over-reach
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]