BOOTP and DHCP on Mixed Media Link-Layer Networks
draft-martel-bootp-mixedlinklayers-00

Document Type Expired Internet-Draft (individual)
Authors Walter Wimer  , Sam Martel 
Last updated 1997-02-20
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-martel-bootp-mixedlinklayers-00.txt

Abstract

RFCs 951 [1], 1541 [2], and 1542 [3] describe the interactions of BOOTP [1] and DHCP [2] client, server, and relay agents. However, further experience with these protocols has revealed the existence of an interoperability issue. The issue occurs when a given IP subnet is constructed over one link-layer network inter-connected by translational bridges to other dissimilar link-layer networks. The following information attempts to address this problem. It is impossible for a BOOTP or DHCP client, server, or relay agent to know in advance whether or not it will be operating in a mixed media link-layer network environment. Given this fact, all BOOTP and DHCP client, server, and relay agents SHOULD adopt the recommendations defined in this memo.

Authors

Walter Wimer (wwimer@fore.com)
Sam Martel (martel@ctron.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)