Jim,
I did not say that was a problem nor did I say all proposals should be discussed in the WG before.
I was just responding to your comment in regards to Leo's point:
---
Leo, like pretty much everything else in RIPE, this should be a consensus decision by the relevant WG(s). The WG chair should be responsible for making that happen.
---
"This" should refer to timelines/duration of periods according to Leo's initial point. So what you wrote as a response to him made me think that you want the duration of the period/timeline decision to be a WG consensus decision. This won't happen simply because Discussion Period duration will be set already before WG is informed about the proposal in the first place.
You also said:
---
I would have hoped it was not necessary to document this. IMO, RIPE needs to keep process and "rules" to the absolute minimum.
----
I think it will be useful to document who decides how long the duration of any period will be, due to transparency reasons.
Apart from Discussion phases', I think it is implied that it is the job of the relevant WG Chair's task on the document alteady. I agree with Sander that they are the best ones to make this decision too.
By the way, it will be an overkill to seek consensus on duration and times from the WG as a whole which you seem to be suggesting.
But maybe you misunderstood Leo's point initially... I am confused now what exactly you are suggesting too.
Filiz
Sent from my iPhone
> On 08 May 2014, at 18:06, Jim Reid <jim at rfc1035.com> wrote:
>>>> On 8 May 2014, at 16:49, "Yilmaz, Filiz" <koalafil at gmail.com> wrote:
>>>> As far as I can read from the document, some proposals can enter the system directly through Discussion Phase, without any prior discussion in the WG.
>> Huh? Are all proposals required to be discussed in the WG before they get created and then enter the Discussion Phase of the PDP where they ... eh... get discussed? :-)
>> Can you please explain why this is a problem Filiz and show what text led you to that interpretation?
>

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacypolicy. You can accept our cookies either by clicking here or by continuing to use the site.