Differences From Artifact [6b0bf66290]:
- File script.txt — part of check-in [9f04d0def1] at 2012-09-27 10:33:46 on branch trunk — Mark template text. (user: ivan, size: 11046) [annotate] [blame] [check-ins using]
To Artifact [0245513d23]:
- File
script.txt
— part of check-in
[0c8fbe81e2]
at
2012-09-27 11:55:17
on branch trunk
— Minor fixes after review.
- Don't use abbreviations in challenges (CN) and experiments (RD) slides. - Use ampersand instead of comma in challenges. - Properly name CC license. - Remove visible frame from deleted slide in interaction diagram. (user: ivan, size: 11062) [annotate] [blame] [check-ins using] [more...]
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
..
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
* Requirements and challenges A testbed has requirements that are challenged by the unique characteristics of CNs. For instance, how to *##* ** Simple management vs. Distributed node ownership - manage devices belonging to diverse owners? *##* ** Features vs. Lightweight, low cost - support devices ranging from PCs to embedded boards? *##* ** Compatibility vs. Heterogeneity - work with devices which allow little customization? - support diverse connectivity models and link technologies including wireless, wired and fiber? *##* ................................................................................ - keep nodes stable to avoid in-place maintenance? *##* ** Flexibility vs. Network stability - Remember that network experiments run on a production network. - allow interaction at the lowest possible layer of the CN while not disrupting or saturating it? *##* ** Traffic collection vs. Privacy of CN users - allow experiments performing traffic collection and characterization? - While avoiding researchers spying on users' data? *##* ** Management robustness vs. Link instability - deal with frequent network outages in the CN when managing nodes? *##* ** Reachability vs. IP address provisioning |
|
|
|
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
..
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
* Requirements and challenges A testbed has requirements that are challenged by the unique characteristics of CNs. For instance, how to *##* ** Simple management vs. Distributed node ownership - manage devices belonging to diverse owners? *##* ** Features vs. Lightweight & low cost - support devices ranging from PCs to embedded boards? *##* ** Compatibility vs. Heterogeneity - work with devices which allow little customization? - support diverse connectivity models and link technologies including wireless, wired and fiber? *##* ................................................................................ - keep nodes stable to avoid in-place maintenance? *##* ** Flexibility vs. Network stability - Remember that network experiments run on a production network. - allow interaction at the lowest possible layer of the CN while not disrupting or saturating it? *##* ** Traffic collection vs. Privacy of community network users - allow experiments performing traffic collection and characterization? - While avoiding researchers spying on users' data? *##* ** Management robustness vs. Link instability - deal with frequent network outages in the CN when managing nodes? *##* ** Reachability vs. IP address provisioning |