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]/
[db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Previous message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Mon Mar 7 15:47:37 CET 2016
[ contains question to NCC ] > I have not seen one opinion clearly stating that abuse is not an issue > and that they do not care about abuse. the american idiom is "primrose path." it looks good at the start but you end up regretting walking it. there are many issues of concern to operators. i would love to see a *usable* way to report a vulnerability in your network, a routing issue, ... but i know this ain't gonna work. what data do the ncc need to do its job. tech and admin. but, let's not make assertions of others' needs. NCC, to run the registry, do you need/want more than admin and tech? randy
- Previous message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [db-wg] [anti-abuse-wg] objection to RIPE policy proposal 2016-01
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]