/[gzz]/gzz/Documentation/misc/antont-wireless_security/data_ubiquity
ViewVC logotype

Diff of /gzz/Documentation/misc/antont-wireless_security/data_ubiquity

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by antont, Wed Mar 5 20:38:53 2003 UTC revision 1.3 by antont, Thu Mar 6 11:37:19 2003 UTC
# Line 1  Line 1 
1    =============================
2    Enabling Secure Data Ubiquity:
3    (meeting the requirements of the wireless and mobile communications)
4    =============================
5    
6    Abstract
7    ========
8    
9    ..
10    
11  Introduction  Introduction
12  ============  ============
13    
# Line 15  in the wired world as well (especially i Line 25  in the wired world as well (especially i
25  in order to have data ubiquity  in order to have data ubiquity
26  new solutions for improving data mobility are needed.  new solutions for improving data mobility are needed.
27    
28  there are also general problems in data mobility  (there are also general problems in data mobility
29  related to relationships management, (in other words,) i.e. hypermedia.  related to relationships management, (in other words,) i.e. hypermedia.
30  for example, when data is moved there may be difficulties in locating it  for example, when data is moved there may be difficulties in locating it
31  (e.g. links to URLs break). [refs?]  (e.g. links to URLs break). [refs?])
32    
33  an approach to improving data mobility is presented in [fallenstein03storm_].  The question this paper addresses is:
34  here the applicability of that system, called Storm (for storage module),  how to improve the usability and security
35  in wireless communications (hence also e.g. in small low-powered devices)  of systems that deliver/manage data for ubiquitous and mobile computing?
36  is evaluated. the treatment is organized as follows:  Specifically the issues of secure movement of data
37    over wireless connections and
38    to/from/between small devices in ad-hoc networks are in focus.
39    
40    the treatment is organized as follows:
41  in section 2., the requirements for secure (&usable) data mobility  in section 2., the requirements for secure (&usable) data mobility
42  over wireless communications are outlined.  over wireless communications with small devices are reviewed.
43  Then, the design and implemention of Storm is presented in section 3.  Then, design and implementation candidates are introduced in section 3.
44  Analysis of how the design meets the specific requirements set here  In section 4., analysis of how these systems meet
45  is conducted in section 4. Finally related issues and reseach is discussed  the specific requirements set here is conducted.
46    Finally related issues and reseach is discussed
47  and open questions identified in conclusion.  and open questions identified in conclusion.
48    
49  Requirements for data mobility over wireless communications  Requirements for secure and useful data ubiquity
50  ===========================================================  ================================================
51    
52    ((for data mobility) over wireless communications and in small devices)
53    
54  Technical  
55  ---------  Wireless communications
56    -----------------------
57    
58  - WLAN  - WLAN
59    
60  - Bluetooth  - Bluetooth
61     * SDP
62    
63  - 'Phone' (GSM/GPRS, UMTS)  - 'Phone' (GSM/GPRS, UMTS)
64    
65  (draw from lecture material?)  (draw from lecture material?)
66    
67    Small devices
68    -------------
69    
70  Usability  Usability
71  ---------  ---------
72    
# Line 57  the communication, e.g. confidentiality Line 81  the communication, e.g. confidentiality
81  That is but one of the many reasons why security must be considered on  That is but one of the many reasons why security must be considered on
82  higher levels as well. Even application layer solutions are commonplace,  higher levels as well. Even application layer solutions are commonplace,
83  e.g. using cryptographical means to protect data have been integrated in  e.g. using cryptographical means to protect data have been integrated in
84  mail and chat clients (in tools such as pgp [], gpg [], silc [], ..).  mail and chat clients (in tools such as pgp [], gpg [], silc [], ..)
85    and for terminal and web access (ssh [], ssl []).
86    
87  When considering mobile use, there may be different requirements for the  When considering mobile use, there may be different requirements for the
88  application layer software than in conventional stationary use. For example,  application layer software than in conventional stationary use. For example,
# Line 66  power and expense. Thus the solutions th Line 91  power and expense. Thus the solutions th
91  stationary use (more powerful machines) must be additionally evaluated with  stationary use (more powerful machines) must be additionally evaluated with
92  the small devices etc. in mind. Obviously, wireless connections can be used  the small devices etc. in mind. Obviously, wireless connections can be used
93  for stationary devices as well (e.g. satellite stations are very  for stationary devices as well (e.g. satellite stations are very
94  stationary), so there power distinction does not apply.  stationary), so there the computing power distinction does not apply.
95    
96    ..
97    
98    Candidate designs and implementations for enabling data ubiquity
99    ================================================================
100    
101    ..
102    
103    JXTA? whatelse? (ask MediaTeam, Gaedke, ..?)
104    
105    An approach to improving data mobility is presented in [fallenstein03storm_].
106    That system, called Storm (for storage module), is not targeted
107    towards low-powered devices but mainly desk- and laptop computers.
108    It does have interesting features conserning wireless communications,
109    such as .. (diffs, multisource, location-independence) [foot: bias alert!
110    (one of the) authors are involved in the design of this system]
111    
112    
113    Comparative analysis of the candidates vs. requirements
114    =======================================================
115    
116    ..
117    
118    Discussion and conclusions
119    ==========================
120    
121    Data ubiquity was identified as a way to characterize the goals of
122    ubiquitous and mobile computing. The requirements set by
123    the wireless communications and limitations of small devices were reviewed,
124    and candidate designs addressing these issues introduced.
125    
126    As results, ..
127    
128  ..  ..
129    
130    Future: experimenting?

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26