DHCP was first defined as a standards track protocol in RFC 1531 in October 1993, as an extension to the Bootstrap Protocol ( BOOTP ).

The primary motivation for replacing RARP with BOOTP was that RARP was a data link layer protocol.

In computer networking, the Bootstrap Protocol, or BOOTP, is a network protocol used by a network client to obtain an IP address from a configuration server.

The BOOTP protocol was originally defined in RFC 951.

The Dynamic Host Configuration Protocol ( DHCP ) is a more advanced protocol for the same purpose and has superseded the use of BOOTP.

The BOOTP protocol 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 data link layer protocol.

The motivation for extending BOOTP was that BOOTP required manual intervention to add configuration information for each client, and did not provide a mechanism for reclaiming disused IP addresses.

RFC 2132 describes the available DHCP options defined by Internet Assigned Numbers Authority ( IANA )-DHCP and BOOTP PARAMETERS.

DHCP uses the same two ports assigned by IANA for BOOTP: destination UDP port 67 for sending data to the server, and UDP port 68 for data to the client.

Historically, BOOTP has also been used for Unix-like diskless workstations to obtain the network location of their boot image in addition to an IP address, and also by enterprises to roll out a pre-configured client ( e. g., Windows ) installation to newly installed PCs.

* X terminals, produced in the 1990s, used as graphical front-ends ( X servers ) for Unix systems ( early thin-clients, downloaded their operating systems mostly by TFTP / BOOTP )

* UDP Helper Address — a tool for routing DHCP and BOOTP broadcast requests across subnet boundaries

The SRM firmware contains drivers for booting from boot media including SCSI hard disks and CD-ROM drives attached to a supported SCSI adapter, various IDE ATA and ATAPI devices, and network booting via BOOTP or DHCP is possible with supported network adapters.

It has been rendered obsolete by the Bootstrap Protocol ( BOOTP ) and the modern Dynamic Host Configuration Protocol ( DHCP ), which both support a much greater feature set than RARP.

BOOTP uses the User Datagram Protocol ( UDP ) as a transport on IPv4 networks only.

BOOTP introduced the innovation of a relay agent, which allowed the forwarding of BOOTP packets off the local network using standard IP routing, thus one central BOOTP server could serve hosts on many IP subnets.

Boot screen of a Compaq Personal computer | PC displaying a BOOTP option.

BOOTP is usually used during the bootstrap process when a computer is starting up.

A BOOTP configuration server assigns an IP address to each client from a pool of addresses.

Most DHCP servers also function as BOOTP servers.

BOOTP introduced the innovation of a relay agent, which allowed BOOTP packets to be forwarded from the local network using standard IP routing, so that one central BOOTP server could serve hosts on many subnets.

For socket numbers, a few well-known numbers were reserved for special purposes specific to the AppleTalk protocol itself.

The experimental protocol used in Carlson's study was agreed to by a group of physicists and astrologers prior to the actual experiment itself.

Although Diffie – Hellman key agreement itself is an anonymous ( non-authenticated ) key-agreement protocol, it provides the basis for a variety of authenticated protocols, and is used to provide perfect forward secrecy in Transport Layer Security's ephemeral modes ( referred to as EDH or DHE depending on the cipher suite ).

In the classic gnutella protocol, response messages were sent back along the route the query came through, as the query itself did not contain identifying information of the node.

Technically, it is not a protocol in itself ; rather, it is the result of simply layering the Hypertext Transfer Protocol ( HTTP ) on top of the SSL / TLS protocol, thus adding the security capabilities of SSL / TLS to standard HTTP communications.

An entry can look like this when represented in LDAP Data Interchange Format ( LDIF ) ( LDAP itself is a binary protocol ):

In fact, the existence of these types of networks discourages dominance of the market by one company, as it creates pressures which work against one company attempting to establish a proprietary protocol or to even distinguish itself by means of product differentiation.

* « The distinction between plain text and other forms of data in the same data stream is the function of a higher-level protocol and is not specified by the Unicode Standard itself .».

The transmission of streaming data itself is not a task of the RTSP protocol.

Most of the overhead comes from network round-trip delay time between client and server ( latency ) rather than from the protocol itself: the best solutions to performance issues depend on efficient application design.

Frame Relay began as a stripped-down version of the X. 25 protocol, releasing itself from the error-correcting burden most commonly associated with X. 25.

SONET / SDH is not itself a communications protocol per se, but a transport protocol.

SONET therefore isn't in itself a native communications protocol per se and should not be confused as being necessarily ' connection-oriented ' in the way that term is usually used.

While OSPF is natively built to route IP and is itself a Layer 3 protocol that runs on top of IP, IS-IS is natively an OSI network layer protocol ( it is at the same layer as CLNS ).

CYCLADES was the first network to make the hosts responsible for the reliable delivery of data, rather than the network itself, using unreliable datagrams and associated end-to-end protocol mechanisms.

The ROSE protocol itself is defined using the notation of ASN. 1.

This detection occurs when a router identifies itself in a hello OSPF protocol packet.

While the CNS network was not itself based on the X. 25 protocol, the network presented a standard X. 25 interface to the outside world, providing dialup connectivity to corporate hosts, and allowing CompuServe to form alliances with private networks Tymnet and Telenet, among others.

Although the B + protocol was not widely supported by other software, it was used by default for some time on CIS itself.

Although the HyperTalk language languished just like HyperCard itself, it received a second lease on life through its plugin protocol, so-called External Commands ( XCMDs ) and External Functions ( XFCNs ), which were native code containers attached to stacks ( as Macintosh-specific resources ) with a single entry point and return value.

SNA describes the protocol and is, in itself, not a single piece of software.