1. NFD forwarding pipelines Junxiao Shi, 2016-03-10 1

2. Overview Forwarding consists of pipelines and strategies Pipeline: a series of steps that operate on a packet or a PIT entry Strategy: a decision maker on whether, when, and where to forward an Interest 2

3. Pipelines incoming Interest Interest loop ContentStore miss ContentStore hit outgoing Interest Interest reject Interest unsatisfied Interest finalize incoming Data Data unsolicited outgoing Data incoming Nack outgoing Nack 3

4. Legend in diagrams 4 building block pipeline tables feature strategy face feature

5. Pipelines Overall Workflow 5 incoming Interest incoming Data outgoing Interest outgoing Data after receive Interest Interest reject Interest unsatisfied Interest loop Data unsolicited before satisfy Interest before expire Interest unsatisfy timer straggler timer Interest finalize ContentStore miss ContentStore hit incoming Nack after receive Nack outgoing Nack

6. incoming Interest pipeline 6 CS lookup PIT insert cancel unsatisfy & straggler timer Y receive Interest detect duplicate Nonce in PIT entry Interest loop Y is pending? Y violates /localhost? N (drop) ContentStore miss ContentStore hit Y N N N detect duplicate Nonce with Dead Nonce List N Y

7. detect duplicate Nonce If the Name+Nonce of the incoming Interest appear in Dead Nonce List, or any InRecord or OutRecord in PIT entry contains the same Nonce as the incoming Interest, a duplicate Nonce is detected. If the duplicate Nonce is found in InRecord only, this is a multi-path arrival, and not a loop. If the duplicate Nonce is found in OutRecord or Dead Nonce Table, this is either a multi-path arrival or a loop, and these two reasons are indistinguishable. Nonce is later recorded on an InRecord. 7

8. Interest loop pipeline Process an Interest that has been considered looped. Keep this simple for now: unconditionally send Nack- Duplicate when duplicate Nonce is detected. Don't enter outgoing Nack pipeline: in-record isn't inserted yet. In the future, strategy could be invoked, because duplicate Nonce may be multi-path arrival instead of loop. 8 reason=Duplicate send Nack is multi-access face? (drop) N Y

9. ContentStore miss pipeline This pipeline is entered when an incoming Interest is pending (so ContentStore lookup is unnecessary), or is miss from ContentStore This pipeline will start forwarding the Interest 9

10. ContentStore miss pipeline 10 FIB lookup with Interest Name dispatch to strategy insert InRecord set PIT unsatisfy timer Interest unsatisfied timer event in producer region? has Selected Delegation ? FIB lookup with SelectedDelegation choose and set SelectedDelegation Y N N Y FIB lookup with first Delegation Name in default- free zone? Y N has Link object? N Y

11. set PIT unsatisfy timer Given PIT entry, set an unsatisfy timer which fires when InterestLifetime expires for all unexpired InRecords When the unsatisfy timer fires, Interest unsatisfied pipeline is entered 11

12. determine whether in producer region Input: regionNames: the router's region names, from configuration interest Algorithm: 1.foreach delegation in Link: 1.foreach regionName in regionNames: 1.if delegation Name is a prefix of regionName, return true and abort these steps 2.return false Note: We consider all delegations, not just SelectedDelegation, to maximize flexibility. This is cheap because there's no table lookup. 12

13. determine whether in default- free zone Input: interest, with Link but without SelectedDelegation FIB lookup result for the first delegation Algorithm: 1.if FIB lookup result is the root entry (ndn:/), and the entry has at least one nexthop record, return false 2.return true Note: FIB lookup will never return "no match", because the FIB always has a root entry, but this entry can have no nexthop record. We consider only the first delegation, to minimize table lookup cost. Checking all delegations probably gives better results, but it requires too many lookups. 13

14. choose and set SelectedDelegation Input: interest, with Link but without SelectedDelegation FIB Algorithm: 1.foreach delegation in Link, sorted by increasing Preference 1.lookup FIB with delegation Name 2.if a match (with non-zero nexthop records) is found, insert SelectedDelegation field with the index of this delegation, return the match, and abort these steps 2.lookup FIB with Interest Name Note: This is the only operation that requires multiple table lookups, but it happens only once on an Interest's path at the first default-free router. 14

15. 15 outgoing Data set PIT straggler timer timer event Interest finalize ContentStore hit pipeline

16. dispatch incoming Interest to strategy Given FIB entry and incoming Interest, determine which strategy should process this Interest, and trigger that strategy 16

17. outgoing Interest pipeline 17 insert OutRecord pick Interest send Interest violates /localhost? Y (drop) violates /localhop? (drop) Y NN

18. pick outgoing Interest packet Given PIT entry and nexthop, decide the guiders on the outgoing Interest Nonce and InterestLifetime come from an InRecord with longest remaining lifetime, however InRecord with same Face as the nexthop cannot be used InterestLifetime is carried from the original packet without deducting the time elapsed Scope is the most relaxed among all unexpired InRecords The last incoming Interest is picked This is a simple choice until we understand the effect of guiders better 18

19. Interest reject pipeline Process an Interest that has been decided that it has nowhere to go 19 set PIT straggler timer timer event cancel unsatisfy & straggler timer Interest finalize

20. Interest unsatisfied pipeline 20 invoke PIT unsatisfied callback Interest finalize

21. Interest finalize pipeline 21 PIT delete Dead Nonce List insert need Dead Nonce List insert? Y N

22. Dead Nonce List insert Dead Nonce List insertion is needed if: Interest is unsatisified, OR Interest has MustBeFresh=yes and Data FreshnessPeriod is shorter than 6 seconds Nonces in OutRecords are inserted to Dead Nonce List. 22

23. incoming Data pipeline 23 PIT match receive Data Y CS insert outgoing Data cancel unsatisfy & straggler timer mark PIT satisfied set PIT straggler timer foreach PIT entry foreach pending downstream Data unsolicited timer event violates /localhost? Y (drop) invoke PIT satisfy callback Interest finalize Dead Nonce List insert need Dead Nonce List insert? Y N N N

24. set PIT straggler timer Given PIT entry, set a straggler timer which fires after a short time T straggler = 100ms When the straggler timer fires, PIT entry is deleted The purpose of retaining PIT entry for a short time is to facilitate loop detection and to collect measurement for non-fastest upstreams 24

25. Data unsolicited pipeline 25 accept to cache? Y CS insert N

26. outgoing Data pipeline 26 traffic managersend Data violates /localhost? Y (drop) N

27. Pass-through traffic manager Provide a traffic manager that does nothing and merely passes Data packet to the next step 27

28. Incoming Nack pipeline PIT match receive Nack trigger strategy: after receive Nack (drop) mark out-record as Nacked N has out-record with correct Nonce? Y (drop) N Y 28 is multi-access face? N Y (drop)

29. Outgoing Nack pipeline send Nack strategy action: send Nack erase in-record has in- record? (drop) N Y 29 is multi-access face? N Y (drop)