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]/
[ripe-list] PDP Appeals Process
- Previous message (by thread): [ripe-list] PDP Appeals Process
- Next message (by thread): [ripe-list] PDP Appeals Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Sat Apr 10 19:31:54 CEST 2021
> Therefore I suggest to make more fundamental changes that do address > these shortcomings. Here are three generic suggestions: > > 1) There should be a higher threshold to make an appeal because > appeals are costly to the community. > > 2) Appeals should be handled by a small number of people who commit to > handling it properly within a defined time line because someone has > to take responsibility. > > 3) Appeals should be fully and transparently documented from the first > submission until the conclusion, because this is the RIPE standard. how may appeals has ripe had? how many appeals were upheld? how much sturm, drang, and omplaloskepsis are we willing suffer to tune it? imiho, your point one is the toughie. you want to require N signatures? > I have some implementation ideas already, similar but not identical to > the RIPE NCC arbitration procedure. However before I get to those I > would like to have some feedback on the general idea. i fear we have to go through this. if so, i respect and value your start. randy --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header butchery
- Previous message (by thread): [ripe-list] PDP Appeals Process
- Next message (by thread): [ripe-list] PDP Appeals Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]