Re: DHCPINFORM _vs_ INIT-REBOOT
Shawn Mamros <mamros@ftp.com> Fri, 18 October 1996 12:52 UTC
Received: from cnri by ietf.org id aa15704; 18 Oct 96 8:52 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa09390;
18 Oct 96 8:52 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA31839; Fri, 18 Oct 1996 08:44:07 -0400
Date: Fri, 18 Oct 1996 08:44:07 -0400
Message-Id: <199610181233.IAA05004@MAILSERV-2HIGH.FTP.COM>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Shawn Mamros <mamros@ftp.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCPINFORM _vs_ INIT-REBOOT
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Don, If you are maintaining lease information across stack teardowns, the *only* acceptable means of using that information is via INIT-REBOOT. DHCPINFORM is NOT acceptable for this purpose. The only reason DHCPINFORM exists is to allow systems which already have a permanent, pre-assigned IPv4 address that was NOT obtained via DHCP to obtain configuration information *other than* their IPv4 address. If your address is leased, use INIT-REBOOT. -Shawn Mamros E-mail to: mamros@ftp.com
- DHCPINFORM _vs_ INIT-REBOOT Don Coolidge
- Re: DHCPINFORM _vs_ INIT-REBOOT Charles Ragan
- Re: DHCPINFORM _vs_ INIT-REBOOT Shawn Mamros
- Re: DHCPINFORM _vs_ INIT-REBOOT Shawn Mamros