The Bootstrap Protocol (BOOTP) is a computer networking protocol used in Internet Protocol networks to automatically assign an IP address to network devices from a configuration server. The BOOTP was originally defined in RFC 951.
While some parts of BOOTP have been effectively superseded by the Dynamic Host Configuration Protocol (DHCP), which adds the feature of leases, parts of BOOTP are used to provide service to the DHCP protocol. DHCP servers also provide the legacy BOOTP functionality.
When a network-connected computer boots-up, its IP-stack broadcasts BOOTP network-messages requesting an IP-address assignment. A BOOTP configuration-server replies to the request by assigning an IP address from a pool of addresses, which is preconfigured by an administrator.
BOOTP is implemented using the User Datagram Protocol (UDP) for transport protocol, port number 67 is used by the (DHCP) server for receiving client-requests and port number 68 is used by the client for receiving (DHCP) server responses. BOOTP operates only on IPv4 networks.
Historically, BOOTP has also been used for Unix-like diskless workstations to obtain the network location of their boot image, in addition to the IP address assignment. Enterprises used it to roll out a pre-configured client (e.g., Windows) installation to newly installed PCs.
Initially requiring the use of a boot floppy disk to establish the initial network connection, manufacturers of network cards later embedded the protocol in the BIOS of the interface cards as well as system boards with on-board network adapters, thus allowing direct network booting.
The BOOTP was first defined in September 1985 in RFC 951 as a replacement for the Reverse Address Resolution Protocol RARP, published in RFC 903 in June 1984. 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 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.
- Case 1
- Client and server on same network
When a BOOTP client is started, it has no IP address, so it broadcasts a message containing its MAC address onto the network. This message is called a “BOOTP request”, and it is picked up by the BOOTP server, which replies to the client with the following information that the client needs:
- The client’s IP address, subnet mask, and default gateway address.
- The IP address and host name of the BOOTP server.
- The IP address of the server that has the boot image, which the client needs to load its operating system.
When the client receives this information from the BOOTP server, it configures and initializes its TCP/IP protocol stack, and then connects to the server on which the boot image is shared. The client loads the boot image and uses this information to load and start its operating system.
The Dynamic Host Configuration Protocol (DHCP) was developed as an extension of BOOTP. BOOTP is defined in Request for Comments (RFC) 951 and 1084.
- Case 2
- Client and server on different networks
- Problem with the bootp request is that the request is broadcast. A broadcast IP datagram cannot pass through any router. The router discards this packet.
- To solve this problem, there is a need for an intermediary (relay).
- One of the host or router can be configured at application layer to operate as relay agent.
- The relay agent knows the uni-cast address of bootp server and listens for broadcast message on port 67.
- When it receives this broadcast packet, it encapsulates the message in unicast datagram and sends request to bootp server.
- The packet carrying a unicast destination address is routed by any router and reaches the bootp server.
- The relay agent, after receiving the reply, sends it to bootp client.
IETF standards documentationEdit
|RFC #||Title||Date||Obsolete and Update Information|
|RFC 3942||Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options||Nov-04||Updates RFC 2132|
|RFC 2132||DHCP Options and BOOTP Vendor Extensions||Mar-97||Obsoletes RFC 1533, Updated by RFC 3442, RFC 3942, RFC 4361, RFC 4833, RFC 5494|
|RFC 1542||Clarifications and Extensions for the Bootstrap Protocol||Oct-93||Obsoletes RFC 1532, Updates RFC 951|
|RFC 1534||Interoperation Between DHCP and BOOTP||Oct-93|
|RFC 1533||DHCP Options and BOOTP Vendor Extensions||Oct-93||Obsoletes RFC 1497, RFC 1395, RFC 1084, RFC 1048, Obsoleted by RFC 2132|
|RFC 1532||Clarifications and Extensions for the Bootstrap Protocol||Oct-93||Obsoleted by RFC 1542, Updates RFC 951|
|RFC 1497||BOOTP Vendor Information Extensions||Aug-93||Obsoletes RFC 1395, RFC 1084, RFC 1048, Obsoleted by RFC 1533, Updates RFC 951|
|RFC 1395||BOOTP Vendor Information Extensions||Jan-93||Obsoletes RFC 1084, RFC 1048, Obsoleted by RFC 1497, RFC 1533, Updates RFC 951|
|RFC 1084||BOOTP vendor information extensions||Dec-88||Obsoletes RFC 1048, Obsoleted by RFC 1395, RFC 1497, RFC 1533|
|RFC 1048||BOOTP vendor information extensions||Feb-88||Obsoleted by RFC 1084, RFC 1395, RFC 1497, RFC 1533|
|RFC 951||Bootstrap Protocol||Sep-85||Updated by RFC 1395, RFC 1497, RFC 1532, RFC 1542, RFC 5494|