Overview
| Comment: | Incorpore les últimes correccions i les adapte a les diapositives. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | sax-2012 |
| Files: | files | file ages | folders |
| SHA1: |
ab1b2eef517498ed4f7b8bc3fbc7b009 |
| User & Date: | ivan on 2012-09-27 12:04:44 |
| Other Links: | branch diff | manifest | tags |
Context
|
2012-09-27
| ||
| 14:38 | Traduïsc el diagrama del banc de proves. check-in: 7ab77e180e user: ivan tags: sax-2012 | |
| 12:04 | Incorpore les últimes correccions i les adapte a les diapositives. check-in: ab1b2eef51 user: ivan tags: sax-2012 | |
| 11:55 |
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. check-in: 0c8fbe81e2 user: ivan tags: trunk, cnbub-2012-1.0.1 | |
| 11:39 | Primera versió en català de les diapositives. check-in: 155a701800 user: ivan tags: sax-2012 | |
Changes
Modified script.txt from [6b0bf66290] to [0245513d23].
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 |
Modified slides,ca.svg from [55e6e20843] to [f1f7c7e9cf].
cannot compute difference between binary files
Modified slides.svg from [86c2c0bc10] to [57eb324029].
cannot compute difference between binary files