RFC 951: Bootstrap Protocol

In plain English — editorial summary, not part of the RFC

This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The bootstrap operation can be thought of as consisting of TWO PHASES. This RFC describes the first phase, which could be labeled `address determination and bootfile selection'. After this address and filename information is obtained, control passes to the second phase of the bootstrap where a file transfer occurs. The file transfer will typically use the TFTP protocol, since it is intended that both phases reside in PROM on the client. However BOOTP could also work with other protocols such as SFTP or FTP. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.

Document record

Document ID

RFC951

Published

September 1985

Authors

W.J. Croft; J. Gilmore

Status

DRAFT STANDARD

Stream

Legacy

Area

—

Pages

12

Also known as

—

Updated by:

RFC 1395, RFC 1497, RFC 1532, RFC 1542, RFC 5494

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC951
• Reported errata exist →

Topics

• BOOTP

Referenced by

5 later RFCs formally update or obsolete part of this document.

• RFC 1395BOOTP Vendor Information ExtensionsObsoleted

  January 1993

• RFC 1497BOOTP Vendor Information ExtensionsObsoleted

  August 1993

• RFC 1532Clarifications and Extensions for the Bootstrap ProtocolObsoleted

  October 1993

• RFC 1542Clarifications and Extensions for the Bootstrap ProtocolCurrent

  October 1993

• RFC 5494IANA Allocation Guidelines for the Address Resolution Protocol (ARP)Current

  April 2009

Also filed under

• DRAFT STANDARD
• 1985
• Legacy stream