Hi Robert,
>> Or you think that DROID as proposed could take on day one flowspec v2 with
>> its various extensions as example ?
I realized I did not answer this explicitly.
DROID aspires to be completely generic. If it can be encoded in bytes, then
there’s no reason that it can’t go in
Hi Robert,
> Just two follow up points,
>
> #1 - I can't stop the feeling that DROID is very IGP centric and not generic
> enough. Do you think we need DROID-2 to start offloading BGP or at least stop
> trashing it ? Or you think that DROID as proposed could take on day one
> flowspec v2
Hi Tony,
Just two follow up points,
#1 - I can't stop the feeling that DROID is very IGP centric and not
generic enough. Do you think we need DROID-2 to start offloading BGP or at
least stop trashing it ? Or you think that DROID as proposed could take on
day one flowspec v2 with its various
Les,
> Nice acronym.
Thank you. I blame the wordle craze. :)
> As regards the original use case (Node Liveness), my opinion hasn’t changed.
> Repackaging this in a more generic wrapper (which makes sense to me) doesn’t
> alter my opinion – which is this isn’t a good way to go.
This
Hi Robert,
> Very happy to see this draft.
Thanks.
> First question - the draft seems to be focusing on hierarchical IGPs and is
> clearly driven by liveness propagation discussion.
The main problem in networking is scale. If you haven’t dealt with scale, you
haven’t solved the
