Project

General

Profile

Actions

Feature #3157

closed

Nack scenario

Added by Junxiao Shi over 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Category:
Integration Tests
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
6.00 h

Description

Develop an IntegrationTests scenario to test Nack with best-route strategy.

Topology:

B
|
A---D
|
C

Procedure:

  1. start NFD on A,B,C,D
  2. configure NFD on A,C,D to use best-route strategy
  3. configure NFD on B to use best-route v1 strategy, which will not transmit or process Nack
  4. on A, create a route for prefix ndn:/P toward B and C, where the cost toward B is lower than the cost toward C
  5. on D, create a route for prefix ndn:/P toward A
  6. on D, express an Interest for ndn:/P/1 with InterestLifetime=4000ms and no consumer retransmission;
    wait 8000ms since expressing Interest, fail the scenario if Nack comes back;
    reason: A shouldn't generate a Nack when upstream times out
  7. on D, express an Interest for ndn:/P/2 with InterestLifetime=4000ms, and retransmit with a new Nonce after 200ms;
    wait 8000ms since expressing first Interest, fail the scenario if Nack comes back;
    reason: A shouldn't return a Nack when some upstream times out, even if some other upstream returns Nack
  8. configure NFD on B to use best-route strategy
  9. on B and C, configure unidirectional link delay toward A as 500ms
  10. on D, express an Interest for ndn:/P/3 with InterestLifetime=4000ms, and retransmit with nonce2 after 200ms;
    wait 3000ms since expressing first Interest, expect exactly one Nack comes back where Reason is NoRoute and Nonce equals nonce2, otherwise fail the scenario;
    reason: A should return a Nack after both upstreams have returned Nack
  11. on B, configure unidirectional link delay toward A as 1000ms
  12. on D, express an Interest for ndn:/P/4 with InterestLifetime=4000ms, and retransmit with nonce2 after 200ms;
    wait 3000ms since expressing first Interest, expect exactly one Nack comes back where Reason is NoRoute and Nonce equals nonce2, otherwise fail the scenario;
    reason: the Nack should carry the latest incoming Nonce from downstream, not the Nonce from last incoming Nack

Files

20161026145052.tgz (575 KB) 20161026145052.tgz integ 3283,4 Junxiao Shi, 10/26/2016 09:27 AM
20161109193307.tgz (594 KB) 20161109193307.tgz Hila Ben Abraham, 11/09/2016 12:56 PM
20161115205445.tgz (575 KB) 20161115205445.tgz Verified patch set 11 Hila Ben Abraham, 11/16/2016 12:00 PM
20161118002228.tgz (575 KB) 20161118002228.tgz integ 3283,12 Junxiao Shi, 11/17/2016 05:38 PM

Related issues 2 (0 open2 closed)

Blocked by NFD - Feature #3156: NACK in forwarding and best-routeClosedJunxiao Shi

Actions
Blocked by NFD - Feature #3104: NDNLPv2: GenericLinkService encoding/decodingClosedEric Newberry

Actions
Actions

Also available in: Atom PDF