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/ripe-list@ripe.net/
[ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
- Previous message (by thread): [ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
- Next message (by thread): [ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sun Feb 7 23:56:20 CET 2021
> On 7 Feb 2021, at 22:04, JORDI PALET MARTINEZ via ripe-list <ripe-list at ripe.net> wrote: > > I agree that the chairs may decide that it may be "out of the scope of the WG", but nothing else. Deciding something's “out of scope for the WG” can be a diplomatic way to avoid embarrassing the proposer(s). WG cochairs have the discretion to exercise that sort of common sense. Which doesn’t need to be written down the Big Book of RIPE Rules.
- Previous message (by thread): [ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
- Next message (by thread): [ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]