Yes but I want a standard for comparison: how long does RIPE take? I have never been involved in that side of RIPE, so I have no idea whether they manage it in weeks, months or years. What is a realistic target?
If we want to fast-track Rapid Operational Advice Documents*, I don't believe it will be done via the RFC process.
*Oh look, I made you an acronym, although we have used it before.
Brian
On 19-Jul-19 17:27, Jared Mauch wrote:
>
>
>> On Jul 19, 2019, at 1:20 AM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
>>
>>
>> How long does RIPE take to produce a BCOP?
>> See https://www.ripe.net/publications/docs/ripe-690#2--what-is-a-bcop-
>
> Some IETF WGs may take several years to produce a BCP.
>
> Sometimes advice needs to change quickly as new things are learned, the IETF process may not reflect that. Iterative drafts reflect the best collective knowledge at that point in time. Capturing that historical view may not feel interesting today, but over time understanding the iterations and why things that changed quickly (eg: ip directed-broadcast) is useful. Those recommendations often shift faster than the IETF could move even in the best of scenarios.
>
> - Jared
>
