RFC 2322 (rfc2322) - Page 1 of 7
Management of IP numbers by peg-dhcp
Alternative Format: Original Text Document
Network Working Group K. van den Hout
Request for Comments: 2322 HvU/HIP-networkteam
Category: Informational A. Koopal
UUnet NL/HIP-networkteam
R. van Mook
University of Twente/HIP-networkteam
1 April 1998
Management of IP numbers by peg-dhcp
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
Introduction
This RFC describes a protocol to dynamically hand out ip-numbers on
field networks and small events that don't necessarily have a clear
organisational body.
It can also provide some fixed additional fields global for all
clients like netmask and even autoproxyconfigs. It does not depend on
a particular ip-stack.
History of the protocol.
The practice of using pegs for assigning IP-numbers was first used at
the HIP event (http://www.hip97.nl/). HIP stands for Hacking In
Progress, a large three-day event where more then a thousand hackers
from all over the world gathered. This event needed to have a TCP/IP
lan with an Internet connection. Visitors and participants of the
HIP could bring along computers and hook them up to the HIP network.
During preparations for the HIP event we ran into the problem of how
to assign IP-numbers on such a large scale as was predicted for the
event without running into troubles like assigning duplicate numbers
or skipping numbers. Due to the variety of expected computers with
associated IP stacks a software solution like a Unix DHCP server
would probably not function for all cases and create unexpected
technical problems.
van den Hout, et. al. Informational