Task #5348
openRevisit prefix announcement / injection / propagation
0%
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?
Updated by Davide Pesavento 2 months ago
Some comments/thoughts from others (taken from the agenda/issue list on NDN workspace):
- trust schema works on a given system model
- we still need to answer the question of how the local host and local hub find each other
- with that, local hub fetches prefix announcement from the app
- local forwarder is not in the business of verifying all the data forwarded, why prefix announcement (a data packet) should be different?
Updated by Davide Pesavento 2 months ago
- Related to Feature #4649: Include PrefixAnnouncement in prefix registration commands added
- Related to Feature #4651: Prefix propagation: use stored PrefixAnnouncement added
Updated by Jacob Zhi 11 days ago
I wanted to share some work I’ve been doing on the Prefix Injection idea (allowing data producers to communicate their routes directly to a routing entity rather than the forwarder). I’ve written out a spec and am ready to start by implementing it in ndnd.
Here are the slides by Lixia giving a bit of background context:
https://docs.google.com/presentation/d/1Ni4Gdx49RJyNjnVjKPMXoKu7ez7l3hPO/edit
And here is a verbose spec (with motivation) — wire format is at the end
https://gist.github.com/jaczhi/5408716346761de953bec18444b9daf4
(note: I updated the spec with some of the feedback on Slack from 4/14. some remaining points of discussion: name of the overall protocol (inject), how to wrap/staple certificates, using existing Prefix Announcement block, how to know there is a routing entity running locally)
Please feel free to share any thoughts and feedback you have!