[DBWG] route-object auto-created from a ROA

[Nishal Goburdhan]

On 15 Apr 2019, at 14:03, Yogesh Chadee wrote:

> Hi,
>
> We are very sorry we could not do it in Q1. We are fine tuning the 
> functional requirements and we will validate them during the DBWG 
> meeting, AIS 19. If all goes well, the implementation shall be in Q3.
>
> We hope to see you there.


hi,

first, let me say how completely underwhelmed i am, by this response.  
after zero (0) feedback for six (6) months, the first response that we 
hear from afrinic is :  “oh, sorry.  nope, we miscalculated”.  and, 
to top it off, *only* after you were prompted, and not of your own 
volition.

a *reasonable* response would have been, at some point during the six 
month process, when you realised that you could not commit to the 
deadline (that *you* set!), to admit to this, and to explain what the 
hold-up is.  instead, we’re pointed to a random date in some 
indeterminate future;  with a vague reference that a specification will 
be done at an undefined “DBWG meeting” - which does not even exist 
in the event calendar!

this is not what we expect from afrinic…

for a start, if you have issues with functional requirements, *raise 
them here*, in *this* working group.  because not everyone, is going to 
be at AIS-19.  feel free to raise the issues piecemeal;  it’s better, 
and easier, to focus on a small series of problems, than to try to solve 
everything at once.

how about coming clean with something like:
# this is what we thought initially
# this is what caused our delays
# this is where we are now;  what we’re stuck on
# this is why we actually think we’re be in a position to deliver in 
Q3.

.. because, frankly, right now, there’s nothing that stops you from 
replaying that “we need another 6 months” message, ad infinitum ..



>> On 31 Mar 2019, at 7:37 PM, Nishal Goburdhan 
>> <nishal at controlfreak.co.za> wrote:
>>> On 19 Oct 2018, at 07:58, Avinash GOKHOOL <avinash at afrinic.net> 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> Thanks a lot for the invaluable feedback.
>>>>
>>>> To answer your question, based on our resource availability and 
>>>> workload, we are planning to have this available during Q1 of 2019.
>>
>> hi,
>>
>> i saw a tweet about the different RPKI options available via the 
>> various RIRs, and remembered this outstanding FQ.
>>
>> any news?  :-)
>>
>> —n.