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/anti-abuse-wg@ripe.net/
[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 ]
ac
ac at main.me
Mon Mar 25 13:44:28 CET 2019
On Mon, 25 Mar 2019 12:24:13 +0000 "Sascha Luck [ml]" <aawg at c4inet.net> wrote: > On Mon, Mar 25, 2019 at 12:44:47PM +0200, ac wrote: > >I frequently read someone saying "RIPE is not the Internet > >Police" (even I have said that a few times myself) but the hard > >truth is that any RIR has a duty to exercise administrative > >authority. > > Only as far as it pertains to the registration of > allocated/assigned resources. All membership of the RIPE NCC > since its foundation was entered into with the understanding that > the NCC is a *registry* not an *enforcer* and does not regulate > the operation or behaviour of member networks. <snip> exactly my point. for the purposes of discussing administrative authority and/or force, as it relates to abuse, we need to set aside 2019-03 specifically and focus on the core principles of administrative authority. do you agree that any registry has an administrative authority? any registry is an *enforcer* by default as the very act of registration implies force. (as, for example, a resource is assigned to you and not to me) how registration happens (the process), the criteria for registration, the criteria for de-registration, these are all examples of administrative authority. IF RIPE (or any RIR) should de-register/remove a resource registration it is acting administratively It is not forcing anyone to do anything, it is doing exactly that which it is supposed to be doing: Being a Registry.
- 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 ]