Project

General

Profile

Actions
Copy link

Bug #4178

closed

Unnecessary readvertise of names under site prefix

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

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/09/2017
Due date:
% Done:

0%

Estimated time:

Description

Steps to reproduce on NDN testbed:

  1. Send a prefix registration command to ARIZONA node for /ndn/edu/arizona/cs/shijunxiao prefix with origin=client.
  2. Observe the RIB on another node.

Actual: /ndn/edu/arizona/cs/shijunxiao prefix has been readvertised alongside /ndn/edu/arizona.
Expected: /ndn/edu/arizona/cs/shijunxiao prefix is not readvertised because it falls under a statically configured site prefix /ndn/edu/arizona. However, in case /ndn/edu/arizona is withdrawn by editing config or nlsrc command, /ndn/edu/arizona/cs/shijunxiao should then be readvertised.

Actions
Copy link
 #1

Updated by Nicholas Gordon over 8 years ago

  • Status changed from New to Rejected

This was discussed on the NDN platform call on 07-10-17, and the conclusion was that there is a use-case for this, such as multi-homed users that want to receive data on multiple prefixes. So this issue is rejected.

Actions
Copy link
 #2

Updated by Junxiao Shi over 8 years ago

multi-homed users that want to receive data on multiple prefixes

This use case doesn't seem correct. Readvertise has nothing to do with "multiple prefixes". It's same prefix via multiple routers.

I can think of: I have the same device connecting to both ARIZONA and UCLA, and the device registers /ndn/edu/arizona/cs/shijunxiao on both routers. If only UCLA readvertises this prefix, it would cause all incoming traffic to go through UCLA, while I expect incoming traffic to go through either ARIZONA or UCLA.

I somehow thought readvertise is needed only if the user is roaming on another router, but I was wrong.

Actions
Copy link

Also available in: Atom PDF