% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc951.txt

@misc{rfc951,
    series =    {Request for Comments},
    number =    951,
    howpublished =  {RFC 951},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC0951},
    url =       {https://www.rfc-editor.org/info/rfc951},
    author =    {},
    title =     {{Bootstrap Protocol}},
    pagetotal = 12,
    year =      1985,
    month =     sep,
    abstract =  {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.},
}