[rpd] Decisions on policy proposals discussed during themeeting

[Sylvain Baya]

Hi all,

Hope you are well !

Le lun. 23 déc. 2019 8:25 PM, Sander Steffann <sander at steffann.nl> a écrit :

>

> Hi,


Dear Sander,

How are you, brother ?


> > For better or worse, however, the current PDP does not give co-chairs power over accepting or rejecting updates.

>

> I think they do. They are tasked with making sure the PDP is followed,


...yes, but to which purpose ?


> and the PDP says a new version must address the raised issues.


...problem : “MUST” seems to be the missing word on CPM 3.4.1 :-/


> If the author violates the PDP by not doing that the chairs have to deny the update.


...by doing what ?

Don't forget that the PDP [1] is roughly clear about what the Chairs can do :-)

If i'm reading [1] well, the Chairs have the power to declare (CPM
3.4.2) consensus (rough), and that's a sufficient power because of the
word rough !
...and yes ! to Varying the Process (CPM 3.6); which appears to be not
too easy to implement, finally :-/

Or am i missing something ? :-/

...please elaborate.
__
[1]: <https://afrinic.net/policy/manual#PDP>

Before backing to my mute mode, let me point you to two or three
implementation issues within this PDP.

Some implementation issues to address  (rather than trying to
force/varying the withdrawal of an inoffensive DPP) :

•—
• CPM 3.4.0 : Relevant Facts provided on demand {though, that isn't a
report like the needed IAR} ???
• CPM 3.4.1 : IAR provided on demand ???
• CPM 3.4.2 : Insertion into the PPM Agenda
• CPM 3.4.2 : Announcement of the PPM Agenda
• CPM 3.4.2 : Blocking the DPP revision system to prevent new changes
closer to the PPM
• CPM 3.4.3 : Last Call Announcement
• CPM 3.4.3 : Evaluation of the feedback received
• CPM 3.4.5 : Implementation Timing
• CPM 3.4.5 : Implementation Announcement
• CPM 3.4.5 : Policy Implementation Waiver
• CPM 3.5 :-)
• CPM 3.6 : Vary in the case of an Emergency
• ...
•—

Shalom,
--sb.


> Cheers,

> Sander

> [...]