[Nfd-dev] some notes from the sync call with Van

Lan Wang (lanwang) lanwang at memphis.edu
Fri Mar 13 15:09:05 PDT 2015


- mobile phone doesn't contain the entire set of data (at some point, may need to purge data), it syncs only that subset of data
- different subsets of the data is synced among different groups of people
- different subsets of the data is synced with different data processing units (DPU)

- name should make the mobile's operation efficient, e.g., if most operations are based on time, then time should be higher up on the name tree (things that you are likely to use for filtering should be higher up on the tree).
- mobile operations: pruning, discovering new data.  

- is there one specific filtering attribute/name component (e.g., time) or multiple attributes?
  * Van: time is likely near the root.  essentially a database problem, but a modern one.  

- need to get interest to mobile? no, with sync
  * if one side is anchored, can use data/interest to bootstrap two-way communication
  * mobile can get nonce name space under whichever place they are attached to, send interest to repo with this information about this name space, sign it.
  * same model as the IEEE communication paper (custodian)

- need to add something to autoreg (assign a name prefix to mobile)

Lan





More information about the Nfd-dev mailing list