-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathdraft-community-nets-00.txt
280 lines (179 loc) · 9.53 KB
/
draft-community-nets-00.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
GAIA IRTF Group L. Kaplan
Internet-Draft Funkfeuer Wien
Intended status: Informational E. Baccelli
Expires: October 4, 2014 INRIA
April 2, 2014
A case study on community wireless networks - experiences from the
trenches
draft-community-wireless-nets-00
Abstract
Roughly ten years ago, a huge number of so called community wireless
networks appeared worldwide, often employing mesh routing based on
cheap off the shelf Wi-Fi equipment and often enough covering whole
cities. These community wireless networks had notable successes in
deploying results from the IETF MANET working group (for example OLSR
RFC3626 XXX fix reference properly XXX). In addition, there have
been some interesting lessons learned from deploying these large
MANETs. This document discusses the structures and findings of the
community networks.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 4, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Kaplan & Baccelli Expires October 4, 2014 [Page 1]
Internet-Draft CWNs April 2014
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. meta . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Intro . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Disclaimer? . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Motivation for this draft . . . . . . . . . . . . . . . . . . 3
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Why CWNs? . . . . . . . . . . . . . . . . . . . . . . . . . . 3
7. History / Genesis . . . . . . . . . . . . . . . . . . . . . . 3
8. Current situation / overview and description of existing CWNs 3
9. A case study: details on FF . . . . . . . . . . . . . . . . . 3
10. case study 2: details on XYZ / Freifunk / ... . . . . . . . . 4
11. Lessons learned . . . . . . . . . . . . . . . . . . . . . . . 4
12. Reality check on current research topics: what is still
needed? Where to concentrate on? . . . . . . . . . . . . . . 4
13. Bib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
14. Meta . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
14.1. Stuff needed . . . . . . . . . . . . . . . . . . . . . . 4
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
15.1. Normative References . . . . . . . . . . . . . . . . . . 4
15.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. meta
author: - ins: Funkfeuer name: L. Aaron Kaplan org: Funkfeuer.at
email: [email protected] country: Austria role: editor - ins: INRIA
name: Emmanuel Baccelli org: Freie Universitaet, Institut fuer
Informatik role: editor street: Room 148, Takustrasse 9 city: Berlin
code: 14195 country: Germany phone: "+358407796297" email: Emmanuel
"dot" Baccelli "at" inria "dot" fr
o url: https://etherpad.funkfeuer.at/p/I-D_CWNs
2. Intro
3. Disclaimer?
We are not claiming to be exhaustive for all CWNs You are welcome to
contribute... here is the gihub page and send us pull requests
Kaplan & Baccelli Expires October 4, 2014 [Page 2]
Internet-Draft CWNs April 2014
4. Motivation for this draft
"here is the stuff where your results are actually used" -> MANET WG
and academic community for gaia: how to build these networks
5. Definitions
o what is a CWN? Comparison to MANETs. Not every CWN is a MANET.
But where MANETs make sense in CWNs.
6. Why CWNs?
on a high level... * because we can * because it's fun: technical
experiment * because it helps with disaster recovery * because it can
help in suppressed internet situations * because they complement
existing cable based networks: cheap to build, filling up the white
spots on the broadband landscape
7. History / Genesis
o consume.net, 2003 Freifunk, Funkfeuer, Paris Sans Fils, Seattle
Wireless, etc.
8. Current situation / overview and description of existing CWNs
o how do they work?
o which exist?
o sizes and how to measure
o differences between CWNs
o categorisations
o interactions (wireless summit, battlemesh)
9. A case study: details on FF
o social aspects
o legal aspects
o special discussion on things relating to MANET WG
o metrics
o management of nodes
Kaplan & Baccelli Expires October 4, 2014 [Page 3]
Internet-Draft CWNs April 2014
10. case study 2: details on XYZ / Freifunk / ...
11. Lessons learned
users of CWNs are describing their lessons learned * special
discussion on things relating to GAIA/MANET WG * metrics * security -
how to deal with routing security issues in CWNs? * legal framework
lacks/challenges
12. Reality check on current research topics: what is still needed?
Where to concentrate on?
(This is already an interpretation of the results of the previous
chapters) * what did we not yet manage to solve? What are the most
stringent needs right now? * for example: * automatic channel
assignment - distributed agreement protocol * multi-topology *
multipath routing which is channel aware * metrics * CSN * routing
security - detection is important!
13. Bib
... (generated)...
14. Meta
14.1. Stuff needed
github repo: * README.markdown * TIMELINE.md * HOWTO-contribute.md
"evangelism": * contact co-contributors * why should they contribute?
* what can the MANET WG learn? GAIA?
howto work on github?: * send us pull requests! * initial master
editors: Emmanuel Baccelli , Aaron Kaplan
15. References
15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005.
[RFC4086] Eastlake, D., Schiller, J., and S. Crocker, "Randomness
Requirements for Security", BCP 106, RFC 4086, June 2005.
Kaplan & Baccelli Expires October 4, 2014 [Page 4]
Internet-Draft CWNs April 2014
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, October 2006.
15.2. Informative References
[I-D.ietf-behave-turn]
Rosenberg, J., Mahy, R., and P. Matthews, "Traversal Using
Relays around NAT (TURN): Relay Extensions to Session
Traversal Utilities for NAT (STUN)", draft-ietf-behave-
turn-16 (work in progress), July 2009.
[I-D.ietf-xmpp-3920bis]
Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Core", draft-ietf-xmpp-3920bis-22 (work
in progress), December 2010.
[I-D.meyer-xmpp-e2e-encryption]
Meyer, D. and P. Saint-Andre, "XTLS: End-to-End Encryption
for the Extensible Messaging and Presence Protocol (XMPP)
Using Transport Layer Security (TLS)", draft-meyer-xmpp-
e2e-encryption-02 (work in progress), June 2009.
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
"Session Traversal Utilities for NAT (STUN)", RFC 5389,
October 2008.
[STUNT] Hanson, R., "STUNT & out-of-band channels", September
2007, <http://deusty.blogspot.com/2007/09/
stunt-out-of-band-channels.html>.
Appendix A. Examples
This appendix provides some examples of the STuPiD protocol
operation.
Authors' Addresses
L. aaron Kaplan
Funkfeuer Wien
Email: [email protected]
Emmanuel Baccelli
INRIA
Germany
Email: XXX
Kaplan & Baccelli Expires October 4, 2014 [Page 5]