RFC 2322:Management of IP numbers by peg-dhcp
RFC-Ref

IP


Click on the red underlined text to get to the source

... 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 ...
... 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 ...
... 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 ...
... 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 ...
... a peg is a 'token' and represents one IP-number, therefore making the status of the IP-number (allocated or not allocated) ...
... 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. ...


... On the peg the IP-number is mentioned. The text on the peg can be described according to the following BNF: ...
... IP ...
... The short versions of the IP-number with only 1 or 2 chunks are meant for large servers where writing the whole number on the peg is just boring and time-consuming. It requires the prefix ...


... The IP-repository ...
... At large networks where it is not really known how many IP-numbers are needed, a first set of pegs can be made in advance, and the administration of produced pegs kept on paper so it is known for ...


... Issuing IP-numbers. ...
... The pegs and the IP-numbers are issued at the server to the client. Normally the client ...


... Reclaiming and reusing IP-numbers. ...
... TTL in this protocol. One obvious TTL is the duration of the event after which the IP-numbers are not valid anymore. ...
... However, if a client decides that it doesn't need an IP-number anymore it can bring the peg back to the server. ...


... network cable near the NIC of the device needing an IP-number allocated. This ensures a clear visual connection between the device and the IP ...
... IP-number allocated. This ensures a clear visual connection between the device and the IP-number allocated and makes it an easy task to see which IP-number is ...
... connection between the device and the IP-number allocated and makes it an easy task to see which IP-number is allocated. ...
... Transfer of the IP information from the peg and the additional vendorfield paper note to the settings in the IP stack is done by ...
... Transfer of the IP information from the peg and the additional vendorfield paper note to the settings in the IP stack is done by human transfer. A person reads the information from the peg and from the additional information and enters this in the configuration of ...
... human transfer. A person reads the information from the peg and from the additional information and enters this in the configuration of the used IP stack. This transfer is not completely free of corruption of the information or loss of the information contained on the peg. ...
... A certain amount of knowledge of the logic of IP settings is also assumed on the part of the person transferring the information. ...


... This protocol could be combined with avian carriers as described in RFC 1149exp to hand out IP-numbers remote. ...


... Pegs are small devices and can be lost. At that time, the IP-number which was lost can't be used anymore because someone else can find the peg and use the information stored on it. But, once the peg is ...
... Due to the human factor of the clients transferring information from peg to IP stack, the information can be misinterpreted, which could cause network troubles. In the field test at HIP ...
... address from the default router as his IP-number, rendering the network useless for a period of time. ...



Google
Web
RFC-Ref