ndn np applications update
play

NDN-NP Applications Update Jeff Burke NDNcomm 2015 Collaborative - PowerPoint PPT Presentation

NDN-NP Applications Update Jeff Burke NDNcomm 2015 Collaborative work by many. Reformulation Storytelling => What if streaming media could be composed just-in-time? => What if expeditionary networks were the norm? Health and Wellness


  1. NDN-NP Applications Update Jeff Burke NDNcomm 2015 Collaborative work by many.

  2. Reformulation Storytelling => What if streaming media could be composed just-in-time? => What if expeditionary networks were the norm? Health and Wellness => What if the user was the root of trust for their own data? Building management / IoT => What if there was no assumption of perimeter security? Real-time conferencing => What if it’s about what the network can deliver, not reaching a producer?

  3. Outline Four applications covered in this talk: - NDNFit (user-centric health & wellness) - NDN UX (user experience of identity / data sharing in NDNFit) - EBAMS (and IoT) - NDN-RTC (low-latency media / conferencing) Also, the team has been working on scientific data apps (covered in the next presentation) and higher-level communication protocols (sync, infomax). More about all of these in other presentations, demos, breakouts. 9/28/15 NDNcomm 2015 3

  4. NDN-NP Progress So Far Where we started – • Incorporate security : Name-based trust definition, verification, confidentiality. • Practical deployment needs that yield research challenges: publisher mobility, autoconfig, trust bootstrapping, etc. • Higher-level communication concepts – e.g., sync, manifests. What also emerged – • App / strategy relationships . • Traffic measurement requirements . • Performance requirements . (Finally!) 9/28/15 NDNcomm 2015 4

  5. NDNFit Haitao Zhang, Alexander Afanasyev, Jianxun Cao, Euihyun Jung, Jiewen Tan, Jeff Thompson, Yingdi Yu, Jeff Burke, Dan Pei, Christian Tschudin, Lixia Zhang, and others. 9/28/15 NDNcomm 2015 5

  6. NDNFit: Open mHealth example application An ecosystem conceived with data exchange as the thin waist (Sim & Estrin, 2010), which is natural for NDN. Gartner, ¡2014 ¡ 9/28/15 NDNcomm 2015 6

  7. NDNFit: Open mHealth example application How do we conceive and build a familiar-looking application that demonstrates interaction in this ecosystem? NDN enables a user-centric reformulation of health and wellness data management. One simple step: the user can be the root of trust. 9/28/15 NDNcomm 2015 7

  8. Concept FITNESS ¡ MOBILE ¡TRACE ¡ PERSONAL ¡DATA ¡ LOCATION ¡ ACTIVITY ¡ VISUALIZER ¡ ¡ CAPTURE ¡ REPOSITORY ¡ ANONYMIZATION ¡ CLASSIFICATION ¡ (NO ¡LOC. ¡DATA) ¡ Ohmage ¡on ¡Android ¡ DSU ¡ DPU ¡ DPU ¡ DVU ¡ GEOFENCING ¡ PATH ¡VISUALIZER ¡ ¡ FILTER ¡ (LOC. ¡DATA) ¡ DPU ¡ DVU ¡ LOCATION-­‑BASED ¡ CONTENT ¡EMITTER ¡ DVU ¡ 9/28/15 NDNcomm 2015 8

  9. Authorization to publish in the /org/openmhealth/<user_id> namespace User's personal mobile device NDNFit Android App Registers globally routable CONFIGURE (DATA MGR) ID Manager Auto-configure support Any machine User-facing web sites link name for on current infrastructure, Mobile App /org/openmealth/ operated as part of CAPTURE Open mHealth <user_id> jNDN testbed Select/marshal keys for apps Web Browser Namespace Assignment accessed by NAME, SIGN, ENCRYPT NDN Provide temporary Interface to: user namespace and key for NFD Auto- 1. Sign up for Open mHealth UPLOAD publishing while roaming namespace. conf NDNFit User Site (DVU) NDNS Data and key exchange protocol, HTTPS for now Interface to: Operated as prioritizing t-i name, 1. Sign up for NDNFit service, part of testbed then trying routable Sync? NDN in next iteration 2. Download mobile application 3. Set up omh, DSU namespace to use. 4. Select features implemented in DPUs. Retrieval / Confirmation Process HealthPDV Requests globally Configuration Site routable LINK name HealthPDV (DSU) Interface to: 1. Sign up for DSU service. Topology-independent data ns: /org/openmhealth/<user_id> 2. Authorize applications, like NDNFit, Routable ns for access on global Internet: /com/healthpdv to access data. Classification (DPU) Sync? Sync? Storage Distribute data encryption keys Virtual hosts on Basel PDV Server hosted at UCLA or UCLA box Virtual hosts on UCLA box 9/28/15 RPC via NDN? NDNcomm 2015 9

  10. ����������������� ���������������� ��������������� �� ���������� ���������� ���������������������� ��������������� ��������������� ��������� �������� ��������������� ��������������� ��� ������ �������� ��������� ��������� ��������� ��������� ���� ������� ����� ����������������� ��������� ���� ����������������� ����������������� ������������� ��������� ��������� ������������ ���� ����������������� ����������������� ����������������� ��� ��������� ����������� ���������� ���������� ��� ���������� ��� ����������������� �������������� 9/28/15 NDNcomm 2015 10 �������� �������� ���� ������ ���������� �������������� ���� ����� ��� ���������������� ����������������� �������������������� ������ ���������������� ���������������� ���������������� ���������� ���������� ���� �������������� �������������� ����������� ��������������� ��������������� ���������������� ������

  11. Data-Centric Security • Good fit for this application. • Schematized trust • Initial design developed. • jNDN support for Android. • Name-based access control • Names capture dimensions we want to manage. • New pieces / future areas • Access control for NFN processing blocks. • Name confidentiality. 9/28/15 NDNcomm 2015 11

  12. Challenges • Life-long data. Enabling the user to “move” data storage from provider to provider and maintain the same namepsace. • Usable security. Schematized trust and name-based security are conceptually simple, but work to be done on how to provide this power to developers in a simple way. • Best type of sync protocol(s) for mobile upload, storage – processing. • Access control between processing blocks. • Publisher mobility. • See Haitao Zhang’s poster for more information. 9/28/15 NDNcomm 2015 12

  13. User Experience for NDNFit Dustin O’Hara, Jeff Burke 9/28/15 NDNcomm 2015 13

  14. 9/28/15 NDNcomm 2015 14

  15. But this application is a new kind • User owns the data • Ecosystem of interoperable applications Named data! • 9/28/15 NDNcomm 2015 15

  16. Bridging the NDN architecture with users NDN Namespaces • How are users introduced to the application namespaces? • How much exposure to the namespaces is necessary? Identity management & Data signing • How do we get users involved in signing their data? Managing access control of personal data • How do we make data-centric security usable for personal data? Data-centric Interoperability • What design choices can be made that move us towards a data-centric ecosystem rather than silo’ed applications? 9/28/15 NDNcomm 2015 16

  17. 9/28/15 NDNcomm 2015 17

  18. 9/28/15 NDNcomm 2015 18

  19. 9/28/15 NDNcomm 2015 19

  20. 9/28/15 NDNcomm 2015 20

  21. 9/28/15 NDNcomm 2015 21

  22. 9/28/15 NDNcomm 2015 22

  23. But this application is a new kind • User owns the data • Ecosystem of interoperable applications Named data! • 9/28/15 NDNcomm 2015 23

  24. 9/28/15 NDNcomm 2015 24

  25. 9/28/15 NDNcomm 2015 25

  26. 9/28/15 NDNcomm 2015 26

  27. 9/28/15 NDNcomm 2015 27

  28. 9/28/15 NDNcomm 2015 28

  29. Challenges NDN Namespaces • How are users introduced to the application namespaces? • How much exposure to the namespaces is necessary? Identity management & Data signing • How do we get users involved in signing their data? Managing access control of personal data • How do we make data-centric security usable for personal data? Data-centric Interoperability • What design choices can be made that move us towards a data-centric ecosystem rather than silo’ed applications? • See Dustin O’Hara’s poster for more discussion. 9/28/15 NDNcomm 2015 29

Recommend


More recommend