MulticastStrategy: remove NACK processing / keep PIT entry even when no nexthops are available
Per our discussions, we have agreed for the multicast strategy to keep PIT entries even in cases when they don't have outgoing faces. Such entries can support async fetching in cases when the corresponding FIB updates during the lifetime of the PIT entry with a new (useful) face.
Updated by Davide Pesavento 7 months ago
- Subject changed from Make multicast strategy keep PIT even when no outgoing faces exist / remove NACK processing in the strategy to MulticastStrategy: remove NACK processing / keep PIT entry even when no nexthops are available
- Status changed from Code review to Closed