Content deleted Content added
→History: Historic {{Ref RFC}}s. |
|||
Line 16:
==History==
The BOOTP was first defined in September 1985{{Ref RFC|951}} as a replacement for the Reverse Address Resolution Protocol [[RARP]], published in June 1984.{{Ref RFC|903}} The primary motivation for replacing RARP with BOOTP is that RARP was a [[link layer]] protocol. This made implementation difficult on many server platforms, and required that a server be present on each individual IP [[subnetwork|subnet]]. BOOTP introduced the innovation of relay agents, which forwarded BOOTP packets from the local network using standard IP routing, so that one central BOOTP server could serve hosts on many subnets.{{Ref RFC|951|rsection=6}}
An increasing set of BOOTP vendor information extensions was defined{{Ref RFC|1048}}{{Ref RFC|1084}}{{Ref RFC|1395}}{{Ref RFC|1497}} to supply BOOTP clients of relevant information about the network, like [[default gateway]], [[Domain name system|name server IP address]], the [[___domain name]], etcetera.
With the advent of the [[Dynamic Host Configuration Protocol]], the BOOTP vendor information extensions were incorporated as DHCP option fields,{{Ref RFC|1533}}{{Ref RFC|2132}} to allow DHCP servers to also serve BOOTP clients.
==Operation==
| |||