Option 8.17 in the DHCP proposal
"Philip A. Prindeville" <philipp@erols.com> Wed, 17 April 1996 19:53 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19403;
17 Apr 96 15:53 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19399;
17 Apr 96 15:53 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa13926;
17 Apr 96 15:53 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA27030; Wed, 17 Apr 1996 15:39:00 -0400
Date: Wed, 17 Apr 1996 15:39:00 -0400
Message-Id: <199604171936.PAA03149@erols.erols.com>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Philip A. Prindeville" <philipp@erols.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Option 8.17 in the DHCP proposal
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
I was wondering about section 8.17 -- "Default World Wide Web (WWW) Server Option"... Is this supposed to be a Proxy server? I couldn't think of any reason to have it unless this was the case... Also, what about other proxy services? FTP, telnet, socks, gopher, wais, etc? And on the subject of WWW, could we include the URL of a sort of "message of the day" that a remote user should look at when his machine is booted up (sort of like /etc/motd under unix when you log in) that might contain information about maintenance, new features, etc... Especially useful for ISPs trying to reach their subscribers. I wonder how long it might conceivably take before popular PC-based Internet software (like Plus! or Netscape) starts making use of some of the new DHCP features: NNTP, SMTP, POP3 servers, etc... >From my limited understanding of the NT/95 Registry, plugging new values into the Registry (or even setting dynamic hooks) shouldn't be too complicated. Can anyone confirm this? -Philip
- Option 8.17 in the DHCP proposal Philip A. Prindeville