Project

General

Profile

Actions
Copy link

Task #5348

open

Revisit prefix announcement / injection / propagation

Added by Davide Pesavento about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
needs-discussion

Description

After a local application creates a prefix registration in the local forwarder via PrefixAnnouncement, how to decide whether the prefix should (1) stay in the local forwarder, or (2) propagate to the connected testbed router and advertised into the global routing system?

What should be the security model (or trust schema) for the testbed (or other global routing system) to verify the prefix announcement objects?

Related issues 2 (1 open — 1 closed)

Related to NFD - Feature #4649: Include PrefixAnnouncement in prefix registration commandsClosedJunxiao Shi

Actions
Related to NFD - Feature #4651: Prefix propagation: use stored PrefixAnnouncementNew

Actions
Actions
Copy link
 #1

Updated by Davide Pesavento about 1 month ago

Some comments/thoughts from others (taken from the agenda/issue list on NDN workspace):

  1. trust schema works on a given system model
  2. we still need to answer the question of how the local host and local hub find each other
  3. with that, local hub fetches prefix announcement from the app
  4. local forwarder is not in the business of verifying all the data forwarded, why prefix announcement (a data packet) should be different?
Actions
Copy link
 #2

Updated by Davide Pesavento about 1 month ago

  • Related to Feature #4649: Include PrefixAnnouncement in prefix registration commands added
  • Related to Feature #4651: Prefix propagation: use stored PrefixAnnouncement added
Actions
Copy link

Also available in: Atom PDF