| 1 |
<pre>Network Working Group K. van den Hout |
| 2 |
Request for Comments: 2322 HvU/HIP-networkteam |
| 3 |
Category: Informational A. Koopal |
| 4 |
UUnet NL/HIP-networkteam |
| 5 |
R. van Mook |
| 6 |
University of Twente/HIP-networkteam |
| 7 |
1 April 1998 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Management of IP numbers by peg-dhcp</span> |
| 11 |
|
| 12 |
Status of this Memo |
| 13 |
|
| 14 |
This memo provides information for the Internet community. It does |
| 15 |
not specify an Internet standard of any kind. Distribution of this |
| 16 |
memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 21 |
|
| 22 |
Introduction |
| 23 |
|
| 24 |
This RFC describes a protocol to dynamically hand out ip-numbers on |
| 25 |
field networks and small events that don't necessarily have a clear |
| 26 |
organisational body. |
| 27 |
|
| 28 |
It can also provide some fixed additional fields global for all |
| 29 |
clients like netmask and even autoproxyconfigs. It does not depend on |
| 30 |
a particular ip-stack. |
| 31 |
|
| 32 |
History of the protocol. |
| 33 |
|
| 34 |
The practice of using pegs for assigning IP-numbers was first used at |
| 35 |
the HIP event (<a href="http://www.hip97.nl/">http://www.hip97.nl/</a>). HIP stands for Hacking In |
| 36 |
Progress, a large three-day event where more then a thousand hackers |
| 37 |
from all over the world gathered. This event needed to have a TCP/IP |
| 38 |
lan with an Internet connection. Visitors and participants of the |
| 39 |
HIP could bring along computers and hook them up to the HIP network. |
| 40 |
|
| 41 |
During preparations for the HIP event we ran into the problem of how |
| 42 |
to assign IP-numbers on such a large scale as was predicted for the |
| 43 |
event without running into troubles like assigning duplicate numbers |
| 44 |
or skipping numbers. Due to the variety of expected computers with |
| 45 |
associated IP stacks a software solution like a Unix DHCP server |
| 46 |
would probably not function for all cases and create unexpected |
| 47 |
technical problems. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">van den Hout, et. al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 55 |
|
| 56 |
|
| 57 |
So a way of centrally administrating IP-numbers and giving them out |
| 58 |
to people to use on their computers had to be devised. After some |
| 59 |
discussion, the idea came up of using wooden clothes-pegs. Using pegs |
| 60 |
has the following advantages in respect to other methods: |
| 61 |
|
| 62 |
- cheap |
| 63 |
- a peg is a 'token' and represents one IP-number, therefore |
| 64 |
making the status of the IP-number (allocated or not allocated) |
| 65 |
visible. |
| 66 |
- a peg can be clipped to a network cable giving a very clear |
| 67 |
view of where a given IP-number is in use. |
| 68 |
|
| 69 |
Credits for the original idea of using wooden pegs go to Daniel |
| 70 |
Ockeloen. |
| 71 |
|
| 72 |
The server. |
| 73 |
|
| 74 |
The server can have many appearances. At HIP it was a large tent |
| 75 |
situated at the central field where all the activities were. It can |
| 76 |
also be a small table in the corner of a terminalroom. |
| 77 |
|
| 78 |
The server can hand out two parts to the client, the peg and a paper |
| 79 |
with additional fields fixed for the site the server is running for. |
| 80 |
We will describe both here. |
| 81 |
|
| 82 |
The peg. |
| 83 |
|
| 84 |
On the peg the IP-number is mentioned. The text on the peg can be |
| 85 |
described according to the following BNF: |
| 86 |
|
| 87 |
Total ::== IP | Net |
| 88 |
|
| 89 |
IP ::== num.num.num.num | num.num | num |
| 90 |
|
| 91 |
Net ::== num.num.num/mask | num.num/mask | num/mask |
| 92 |
|
| 93 |
num ::== {1..255} |
| 94 |
|
| 95 |
mask ::== {8..31} |
| 96 |
|
| 97 |
The Net-method of writing larger nets is an optional part of the |
| 98 |
protocol, it doesn't have to be implemented. If it is implemented, it |
| 99 |
requires more administration at the server (see below). |
| 100 |
|
| 101 |
The short versions of the IP-number with only 1 or 2 chunks are meant |
| 102 |
for large servers where writing the whole number on the peg is just |
| 103 |
boring and time-consuming. It requires the prefix to be mentioned on |
| 104 |
the additional field paper, but that can be produced in more |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">van den Hout, et. al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 111 |
|
| 112 |
|
| 113 |
convenient ways. It is not recommended to work with more prefixes. It |
| 114 |
is better to write more numbers on the peg and use a smaller prefix. |
| 115 |
|
| 116 |
If the network to be numbered is rather large and some kind of |
| 117 |
subnetting has to be implemented it is possible to give the pegs from |
| 118 |
the different subnets different colors. This has proven to be a very |
| 119 |
convenient way at HIP. |
| 120 |
|
| 121 |
The additional vendorfield paper. |
| 122 |
|
| 123 |
This part is meant for information that is fixed for the whole site. |
| 124 |
It can either be implemented as small printed notes handed out with |
| 125 |
the peg or as a large paper billboard hung at a convenient place |
| 126 |
where everybody can read it. |
| 127 |
|
| 128 |
The information can be described with the following BNF: |
| 129 |
|
| 130 |
Network ::== num.num.num.num |
| 131 |
|
| 132 |
Netmask ::== num.num.num.num | num |
| 133 |
|
| 134 |
Gateway ::== num.num.num.num | num.num | num |
| 135 |
|
| 136 |
Proxy ::== num.num.num.num:port | num.num:port | num:port |
| 137 |
|
| 138 |
Paper ::== Network Netmask Gateway Proxy | Network Netmask Gateway |
| 139 |
|
| 140 |
num ::== {0..255} |
| 141 |
|
| 142 |
port ::== {1..65535} |
| 143 |
|
| 144 |
The paper and the peg are of course one part, if two numbers are used |
| 145 |
on the peg, two numbers are used on the paper. |
| 146 |
|
| 147 |
Because it is fixed information, it can be produced with means of |
| 148 |
mass-production (printing, copying). |
| 149 |
|
| 150 |
The IP-repository |
| 151 |
|
| 152 |
Due to the nature of the peg, the repository can be quite simple. |
| 153 |
Just a clothes-line with all the pegs that are ready to be handed out |
| 154 |
attached to it. If you work with different subnets, it is convenient |
| 155 |
to group the pegs for the different subnets (colors). |
| 156 |
|
| 157 |
At large networks where it is not really known how many IP-numbers |
| 158 |
are needed, a first set of pegs can be made in advance, and the |
| 159 |
administration of produced pegs kept on paper so it is known for |
| 160 |
which numbers pegs have already been made. If use is made of the |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">van den Hout, et. al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 167 |
|
| 168 |
|
| 169 |
net-extension on the pegs, numbers given out that way can be |
| 170 |
administrated this way too. |
| 171 |
|
| 172 |
Issuing IP-numbers. |
| 173 |
|
| 174 |
The pegs and the IP-numbers are issued at the server to the client. |
| 175 |
Normally the client has to visit the server personally. Depending on |
| 176 |
how secure and controlled you want the process, the client has to ask |
| 177 |
for a peg to a responsible person, or he or she can just get a peg |
| 178 |
from store himself. |
| 179 |
|
| 180 |
If someone could apply for a networkrange, and he net-extension isn't |
| 181 |
used, coat-hangers can be prepared with sets of pegs attached to |
| 182 |
them. |
| 183 |
|
| 184 |
The vendorfields paper doesn't have to be issued with every peg, it |
| 185 |
is only needed when wanted. |
| 186 |
|
| 187 |
Reclaiming and reusing IP-numbers. |
| 188 |
|
| 189 |
It is not easy to implement a TTL in this protocol. One obvious TTL |
| 190 |
is the duration of the event after which the IP-numbers are not valid |
| 191 |
anymore. |
| 192 |
|
| 193 |
However, if a client decides that it doesn't need an IP-number |
| 194 |
anymore it can bring the peg back to the server. |
| 195 |
|
| 196 |
The server should at that point decide what to do, if desired, it can |
| 197 |
bring the peg back into the pool (attach it to the clothes-line |
| 198 |
again). |
| 199 |
|
| 200 |
If the server is not manned (the client has to help themselves), the |
| 201 |
only thing possible is that the client just places the peg back into |
| 202 |
the pool. |
| 203 |
|
| 204 |
The client side. |
| 205 |
|
| 206 |
The optimum location for the peg is clipped to the network cable near |
| 207 |
the NIC of the device needing an IP-number allocated. This ensures a |
| 208 |
clear visual connection between the device and the IP-number |
| 209 |
allocated and makes it an easy task to see which IP-number is |
| 210 |
allocated. |
| 211 |
|
| 212 |
Transfer of the IP information from the peg and the additional |
| 213 |
vendorfield paper note to the settings in the IP stack is done by |
| 214 |
human transfer. A person reads the information from the peg and from |
| 215 |
the additional information and enters this in the configuration of |
| 216 |
the used IP stack. This transfer is not completely free of |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">van den Hout, et. al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 223 |
|
| 224 |
|
| 225 |
corruption of the information or loss of the information contained on |
| 226 |
the peg. |
| 227 |
|
| 228 |
A certain amount of knowledge of the logic of IP settings is also |
| 229 |
assumed on the part of the person transferring the information. |
| 230 |
|
| 231 |
Other information on the vendorfield paper note has to be transferred |
| 232 |
to the settings within specific application programs. |
| 233 |
|
| 234 |
Use with other protocols |
| 235 |
|
| 236 |
This protocol could be combined with avian carriers as described in |
| 237 |
<a href="./rfc1149">RFC 1149</a> to hand out IP-numbers remote. |
| 238 |
|
| 239 |
At the first avian carrier, the peg is clipped to the leg of the |
| 240 |
carrier after rolling the additional vendorfield paper around it. |
| 241 |
|
| 242 |
The remote site can take the peg on arrival of the avian carrier and |
| 243 |
use the information on it. |
| 244 |
|
| 245 |
This part of the protocol is still experimental and requires some |
| 246 |
additional research on topics like the weight of the peg and loss of |
| 247 |
the peg/whole carrier. |
| 248 |
|
| 249 |
Security Considerations |
| 250 |
|
| 251 |
Some remarks about security can be made. |
| 252 |
|
| 253 |
Pegs are small devices and can be lost. At that time, the IP-number |
| 254 |
which was lost can't be used anymore because someone else can find |
| 255 |
the peg and use the information stored on it. But, once the peg is |
| 256 |
attached to a network cable, the chance to loose the peg is |
| 257 |
minimized. |
| 258 |
|
| 259 |
All the information on both the peg and on the additional 'fixed' |
| 260 |
fields on the paper record are plain text and readable for everyone. |
| 261 |
Private information should not be exchanged through this protocol. |
| 262 |
|
| 263 |
On the client side all sorts of clients exist and cooperate freely. |
| 264 |
Due to the human factor of the clients transferring information from |
| 265 |
peg to IP stack, the information can be misinterpreted, which could |
| 266 |
cause network troubles. In the field test at HIP this became |
| 267 |
perfectly clear when someone mixed up the numbers and used the |
| 268 |
address from the default router as his IP-number, rendering the |
| 269 |
network useless for a period of time. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">van den Hout, et. al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 279 |
|
| 280 |
|
| 281 |
Authors' Addresses |
| 282 |
|
| 283 |
Koos van den Hout |
| 284 |
Hogeschool van Utrecht / Expertisecentrum Cetis |
| 285 |
P.O. box 85029 |
| 286 |
3508 AA Utrecht |
| 287 |
The Netherlands |
| 288 |
|
| 289 |
Phone: +31-30-2586287 |
| 290 |
Fax: +31-30-2586292 |
| 291 |
EMail: [email protected] |
| 292 |
|
| 293 |
|
| 294 |
Andre Koopal |
| 295 |
UUnet Netherlands |
| 296 |
P.O. box 12954 |
| 297 |
1100 AZ AMSTERDAM |
| 298 |
The Netherlands |
| 299 |
|
| 300 |
Phone: +31-20-4952727 |
| 301 |
Fax: +31-20-4952737 |
| 302 |
EMail: [email protected] |
| 303 |
|
| 304 |
|
| 305 |
Remco van Mook |
| 306 |
Van Mook Consulting |
| 307 |
Calslaan 10-31 |
| 308 |
7522 MA Enschede |
| 309 |
The Netherlands |
| 310 |
|
| 311 |
Phone: +31-53-4895267 |
| 312 |
EMail: [email protected] |
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">van den Hout, et. al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2322">RFC 2322</a> Management of IP numbers by peg-dhcp 1 April 1998</span> |
| 335 |
|
| 336 |
|
| 337 |
Full Copyright Statement |
| 338 |
|
| 339 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 340 |
|
| 341 |
This document and translations of it may be copied and furnished to |
| 342 |
others, and derivative works that comment on or otherwise explain it |
| 343 |
or assist in its implementation may be prepared, copied, published |
| 344 |
and distributed, in whole or in part, without restriction of any |
| 345 |
kind, provided that the above copyright notice and this paragraph are |
| 346 |
included on all such copies and derivative works. However, this |
| 347 |
document itself may not be modified in any way, such as by removing |
| 348 |
the copyright notice or references to the Internet Society or other |
| 349 |
Internet organizations, except as needed for the purpose of |
| 350 |
developing Internet standards in which case the procedures for |
| 351 |
copyrights defined in the Internet Standards process must be |
| 352 |
followed, or as required to translate it into languages other than |
| 353 |
English. |
| 354 |
|
| 355 |
The limited permissions granted above are perpetual and will not be |
| 356 |
revoked by the Internet Society or its successors or assigns. |
| 357 |
|
| 358 |
This document and the information contained herein is provided on an |
| 359 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 360 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 361 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 362 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 363 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 364 |
|
| 365 |
|
| 366 |
|
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
van den Hout, et. al. Informational [Page 7] |
| 389 |
</pre> |