Browse Prior Art Database

Management of IP numbers by peg-dhcp (RFC2322)

IP.com Disclosure Number: IPCOM000002889D
Original Publication Date: 1998-Apr-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 7 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. van den Hout: AUTHOR [+2]

Related Documents

10.17487/RFC2322: DOI

Abstract

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. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 28% of the total text.

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 [Page 1]

RFC 2322 Management of IP numbers by peg-dhcp 1 April 1998

So a way of centrally administrating IP-numbers and giving them out to people to use on their computers had to be devised. After some discussion, the idea came up of using wooden clothes-pegs. Using pegs has the following advantages in respect to other methods:

- cheap - a peg is a ’token’ and represents one IP-number, therefore making the status of the IP-number (allocated or not allocated) visible. - a peg can be clipped to a network cable giving a very clear view of where a given IP-number is in use.

Credits for the original idea of using wooden pegs go to Daniel Ockeloen.

The server.

The server can have many appearances. At HIP it was a large tent situated at the central field where all the activities were. It can also be a small table in the corner of a terminalroom.

The server can hand out two parts to the client, the peg and a paper with additional fields fixed for the site the server is running for. We will describe both here.

The peg.

On the peg the IP-number is mentioned. The text on the peg can be described according to the following BNF:

Total ::== IP | Net

IP ::== num.num.num.num | num.num | num

Net ::== num.num.num/mask | num.num/mask | num/mask

num ::== {1..255}

mask ::== {8..31} ...

Processing...
Loading...