Differences From 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...]
To Artifact [777bb9d984]:
- File script.txt — part of check-in [ea16ad6d02] at 2012-09-27 22:44:15 on branch trunk — Fix location of first slide switch; other minor changes in script. (user: ivan, size: 11067) [annotate] [blame] [check-ins using] [more...]
1
2
3
4
5
6
7
8
9
10
11
12
13
..
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
#+title: Community-Lab: A Community Networking Testbed for the Future Internet * Introduction Hello, I'm (Speaker) from (organization), I work at the CONFINE project and I'm going to talk you about *##* Community-Lab, a community networking testbed for the future Internet. ** Community networks - Infrastructure deployed by organized groups of people for self-provision of broadband networking that works and grows according to their own interests. - Characteristics: Open participation, open and transparent management, distributed ownership. - The EU regards CNs as fundamental for *##* the universalization of broadband networking. ................................................................................ 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 - CNs have IPv4 scarcity and incompatible addressing with little IPv6 support. - support testbed spanning different CNs? *##* * Community-Lab testbed architecture ** Overall architecture This is the architecture developed by the CONFINE project to handle the previous challenges. It applies to all testbeds using CONFINE software. *##* |
|
|
>
|
|
>
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
..
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
#+title: Community-Lab: A Community Networking Testbed for the Future Internet * Introduction Hello, I'm (Speaker) from (organization), I work at the CONFINE project and I'm going to talk you about Community-Lab, a community networking testbed for the future Internet. *##* ** Community networks - Infrastructure deployed by organized groups of people for self-provision of broadband networking that works and grows according to their own interests. - Characteristics: Open participation, open and transparent management, distributed ownership. - The EU regards CNs as fundamental for *##* the universalization of broadband networking. ................................................................................ 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 outages in the CN when managing nodes? *##* ** Reachability vs. IP address provisioning - CNs suffer from IPv4 scarcity and incompatible addressing besides little IPv6 support. - support testbed spanning different CNs? *##* * Community-Lab testbed architecture ** Overall architecture This is the architecture developed by the CONFINE project to handle the previous challenges. It applies to all testbeds using CONFINE software. *##* |