Project

General

Profile

Actions

Task #3513

closed

[NdnCon] Change user prefix to be compatible with auto prefix propagation

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
Due date:
03/16/2016
% Done:

100%

Estimated time:

Description

Currently, NdnCon creates the user prefix like ndn:/ndn/guest/ndnrtc/someone%40example.com, and publishes streams under this prefix.
Reachability of this user prefix depends on nfd-autoreg which adds a back-route like ndn:/ndn/guest that is same for every user, and forwarding relies on flooding by AccessStrategy which is inefficient (#3219).

This causes increased Interest traffic toward all hosts connected to a gateway router, if any host is publishing a stream.

To solve this problem, NdnCon should change the user prefix to like ndn:/ndn/guest/someone%40example.com/ndnrtc.
When the end host is configured with a testbed certificate ndn:/ndn/guest/someone%40example.com, automatic prefix propagation will create a back-route for ndn:/ndn/guest/someone%40example.com that is unique for each participant.

A more specific prefix of each participant allows AccessStrategy to forward Interests toward the correct host, and flood only if the same participant has multiple hosts connected which is unlikely.
This shall decrease Interest traffic on other hosts, and thus decrease CPU usage and network congestion.


Files

auto-prefix-propagation-tr.pdf (586 KB) auto-prefix-propagation-tr.pdf Jeff Burke, 03/06/2016 08:11 AM

Related issues 3 (1 open2 closed)

Related to NFD - Bug #3219: AccessStrategy measurements ineffective for NDN-RTC trafficNew09/21/2015

Actions
Related to ndnrtc - Task #3512: Prep for March 9 seminar with NDN-RTCClosedPeter Gusev03/04/2016

Actions
Blocked by NFD - Task #3515: Request all expired node and user certificates be manually updatedClosedJeff Burke03/05/2016

Actions
Actions

Also available in: Atom PDF