RIB is not thread safe

[pulsejet]

Got a race while removing a face

[zjkmxy]

I remember a previous decision is to move RIB outside the forwarder app. Is this still the case?

[pulsejet]

I want to, but this seems like the shortest path to not break NFD compatibility for now :(

[Pesa]

this seems like the shortest path to not break NFD compatibility for now :(

What do you mean by NFD compatibility here? And why does it matter for NFD compatibility whether the NDNd RIB is internal or separate? From the point of view of an NDN app, this is little more than an implementation detail.

[pulsejet]

What do you mean by NFD compatibility here? And why does it matter for NFD compatibility whether the NDNd RIB is internal or separate? From the point of view of an NDN app, this is little more than an implementation detail.

If we remove the RIB, the management protocol would need to change (rib/register, for instance wouldn't make sense when there's no RIB). This will break tooling (nfdc) as well as NDN apps that call management directly (e.g. Workspace).

[Pesa]

I'm still not following. rib/register is handled by the RIB component, whether that's built-in or external makes no difference. Again, the app doesn't need to care.

[Pesa]

And for the record, I'm still not convinced that an external/separate RIB is a good idea.

[pulsejet]

I'm still not following. rib/register is handled by the RIB component, whether that's built-in or external makes no difference. Again, the app doesn't need to care.

Say the RIB is in the router instead of NFD, then it won't be /localhost/nfd/rib/register, no? (not an NFD route anymore)

And for the record, I'm still not convinced that an external/separate RIB is a good idea.

Earlier I didn't fully understand what the RIB was doing in NFD, but now it makes more sense to me. For now I've no plan to remove the RIB / change the existing design.

[Pesa]

I'm still not following. rib/register is handled by the RIB component, whether that's built-in or external makes no difference. Again, the app doesn't need to care.

Say the RIB is in the router instead of NFD, then it won't be /localhost/nfd/rib/register, no? (not an NFD route anymore)

Are you concerned about the nfd component in the name? I don't think it matters, it's just a convention. It simply means "this is the NFD management protocol". Isn't that the whole point of names btw? what, not where.