From listserv@bucknell.edu  Thu Oct  1 22:35:54 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id WAA20257
	for <dhc-archive@odin.ietf.org>; Thu, 1 Oct 1998 22:35:38 -0400 (EDT)
From: listserv@bucknell.edu
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id WAA02421;
	Thu, 1 Oct 1998 22:35:27 -0400 (EDT)
Date: Thu, 1 Oct 1998 22:35:27 -0400 (EDT)
Message-Id: <199810020235.WAA02421@mail.bucknell.edu>
Errors-To: droms@bucknell.edu
Reply-To: listserv@bucknell.edu
Sender: listserv@bucknell.edu
To: dhc-archive@ietf.org
Cc: droms@bucknell.edu
Subject: SUBSCRIBE DHCP-V4 IETF ARCHIVER 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Bucknell University ListProcessor

You have been added to list dhcp-v4@bucknell.edu.
The system has recorded your address as

			dhc-archive@lists.ietf.org

and in order for your messages to get posted (if the list accepts postings),
you will have to send them from this address, unless the list does not require
subscription for posting.
If a message is ever rejected, please contact the list's owner: droms@bucknell.edu

For information on this service and how to use it, send the following
request in the body of a mail message to listserv@bucknell.edu:

			HELP

All requests should be addressed to listserv@bucknell.edu.

The amount of acknowledgement you wish to receive from this list upon
completion of a mailing operation can be changed by means of a "SET DHCP-V4
MAIL option" command, where "option" may be either "ACK" (mail acknowledgement)
or "NOACK":

        SET DHCP-V4 MAIL ACK
        SET DHCP-V4 MAIL NOACK

If you prefer to receive messages from DHCP-V4 in one fell swoop, you may
use the the DIGEST option to have DHCP-V4 messages accumulated into digests
which will be periodically sent to you:

        SET DHCP-V4 MAIL DIGEST

If you wish to stop delivery of list messages temporarily without unsubscribing
from the list, you can use the POSTPONE option:

	SET DHCP-V4 MAIL POSTPONE

When you're ready to receive messages again, use the ACK or NOACK options as
described above.

To issue any of these commands, send them in the body of a message to the
LISTSERV@BUCKNELL.EDU e-mail address.

Contributions sent to this list are automatically archived.  You can obtain a
list of the available archive files by sending an "INDEX DHCP-V4"
command to LISTSERV@BUCKNELL.EDU.  These files can then be retrieved by means
of a "GET DHCP-V4 filetype" command.

To post an article to the list, send your message to the list address
DHCP-V4@BUCKNELL.EDU.

To leave the list at any time, you can send an e-mail message to
LISTSERV@BUCKNELL.EDU with the body of your message containing the
line:

        UNSUBSCRIBE DHCP-V4

Virtually,

The LISTSERVer at Bucknell


From dhcp-v4@bucknell.edu  Thu Oct  1 22:50:25 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id WAA20309
	for <dhc-archive@odin.ietf.org>; Thu, 1 Oct 1998 22:50:22 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id WAA25126;
	Thu, 1 Oct 1998 22:47:38 -0400 (EDT)
Date: Thu, 1 Oct 1998 22:47:38 -0400 (EDT)
Message-Id: <v03007801b239eb09c79d@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: I-D ACTION:draft-ietf-dhc-new-options-03.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: multipart/mixed; boundary="============_-1304827033==_============"
Mime-Version: 1.0

--============_-1304827033==_============
Content-Type: text/plain; charset="us-ascii"

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group
of the IETF.

	Title		: Procedure for Defining New DHCP Options
	Author(s)	: R. Droms
	Filename	: draft-ietf-dhc-new-options-03.txt
	Pages		: 6
	Date		: 30-Sep-98

   The Dynamic Host Configuration Protocol (DHCP) provides a framework
   for passing configuration information to hosts on a TCP/IP network.
   Configuration parameters and other control information are carried in
   tagged data items that are stored in the 'options' field of the DHCP
   message.  The data items themselves are also called 'options.'

   New DHCP options may be defined after the publication of the DHCP
   specification to accommodate requirements for conveyance of new
   configuration parameters.  This document describes the procedure for
   defining new DHCP options.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-new-options-03.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-new-options-03.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za

	Europe: ftp.nordu.net
		ftp.nis.garr.it

	Pacific Rim: munnari.oz.au

	US East Coast: ftp.ietf.org

	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-new-options-03.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

Content-Type: text/plain
Content-ID:	<19980930160046.I-D@ietf.org>

[This attachment must be fetched by mail.
Open the stationery below and send the resulting
message to get the attachment.]

Content-Type: Message/External-body;
	name="draft-ietf-dhc-new-options-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

[This attachment must be fetched by ftp.
 Open the document below to ask your ftp client to fetch it.]

Content-Type: text/plain
Content-ID:	<19980930160046.I-D@ietf.org>

--============_-1304827033==_============
Content-Type: message/external-body
 ; access-type=anon-ftp
 ; site="ftp.ietf.org"
 ; directory="/internet-drafts"
 ; name="draft-ietf-dhc-new-options-03.txt"
 ; mode="ascii"

Content-Type: application/octet-stream; name="draft-ietf-dhc-new-options-03.txt"
Content-Disposition: attachment; filename="draft-ietf-dhc-new-options-03.txt"
--============_-1304827033==_============--



From dhcp-v4@bucknell.edu  Tue Oct  6 02:33:54 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id CAA10557
	for <dhc-archive@odin.ietf.org>; Tue, 6 Oct 1998 02:33:53 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id CAA05947;
	Tue, 6 Oct 1998 02:28:48 -0400 (EDT)
Date: Tue, 6 Oct 1998 02:28:48 -0400 (EDT)
Message-Id: <000301bdf0f0$afc9d7e0$a964fea9@troll>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Ryan Troll" <ryan@andrew.cmu.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCP AutoConfig Option Size
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

All,

I posted here last week asking about a possible change to the size of the
DHCP AutoConfigure option, to allow for future use of more bits for
enabling/disabling different items in the future.  If there's a general
consensus on this, I'd like to get this change made sooner rather than
later, so that this draft can be moved forward faster.  However, so far I've
only heard one response, and I'd like to get more input.

Please let me know if you have an opinion about this idea.

Thanks,
-Ryan



From dhcp-v4@bucknell.edu  Tue Oct  6 03:18:12 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA11081
	for <dhc-archive@odin.ietf.org>; Tue, 6 Oct 1998 03:18:11 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id DAA06077;
	Tue, 6 Oct 1998 03:13:45 -0400 (EDT)
Date: Tue, 6 Oct 1998 03:13:45 -0400 (EDT)
Message-Id: <Pine.LNX.3.95.981006145503.13669A-100000@mars.netspire.com.sg>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Colin Gan <colin@ddns.org>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP-V4 digest 607
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0

hi ryan,you have offered a very good option and i support it.  cheers.

Colin Gan			Webworks Pte Ltd
Research Division		103A, Geylang Road
colin@ddns.org			Singapore 389212

http://www.ddns.org		Tel: (65) 741-9526
Sales: sales@ddns.org		Fax: (65) 749-3806
Tech:  tech@ddns.org		Pgr: 9284-4823
Info:  info@ddns.org
Spt:   support@ddns.org



From dhcp-v4@bucknell.edu  Tue Oct  6 14:11:29 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA23317
	for <dhc-archive@odin.ietf.org>; Tue, 6 Oct 1998 14:11:26 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id NAA30972;
	Tue, 6 Oct 1998 13:55:38 -0400 (EDT)
Date: Tue, 6 Oct 1998 13:55:38 -0400 (EDT)
Message-Id: <199810061745.NAA02271@andare.fugue.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: Ted Lemon <mellon@hoffman.vix.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP AutoConfig Option Size 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


> I posted here last week asking about a possible change to the size of the
> DHCP AutoConfigure option, to allow for future use of more bits for
> enabling/disabling different items in the future.

The one response you got was that you shouldn't do it, and I tend to
agree - we've made a policy decision not to overload options, and what
you're proposing is essentially that.

			       _MelloN_


From dhcp-v4@bucknell.edu  Tue Oct  6 17:08:49 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA25834
	for <dhc-archive@odin.ietf.org>; Tue, 6 Oct 1998 17:08:48 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA11213;
	Tue, 6 Oct 1998 16:50:10 -0400 (EDT)
Date: Tue, 6 Oct 1998 16:50:10 -0400 (EDT)
Message-Id: <000001bdf16a$7f6e3bc0$252afea9@troll>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Ryan Troll" <ryan@andrew.cmu.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: DHCP AutoConfig Option Size 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

Ah.  I was unaware of the previous policy decision to not overload options.
That makes this choice easy.

Thanks,
-Ryan

> -----Original Message-----
> From: dhcp-v4@bucknell.edu [mailto:dhcp-v4@bucknell.edu]On Behalf Of Ted
> Lemon
> Sent: Tuesday, October 06, 1998 2:05 PM
> To: Multiple recipients of list
> Subject: Re: DHCP AutoConfig Option Size
>
>
>
> > I posted here last week asking about a possible change to the
> size of the
> > DHCP AutoConfigure option, to allow for future use of more bits for
> > enabling/disabling different items in the future.
>
> The one response you got was that you shouldn't do it, and I tend to
> agree - we've made a policy decision not to overload options, and what
> you're proposing is essentially that.
>
> 			       _MelloN_
>



From dhcp-v4@bucknell.edu  Wed Oct  7 07:41:11 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA09428
	for <dhc-archive@odin.ietf.org>; Wed, 7 Oct 1998 07:41:10 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA32486;
	Wed, 7 Oct 1998 07:35:56 -0400 (EDT)
Date: Wed, 7 Oct 1998 07:35:56 -0400 (EDT)
Message-Id: <v0300780ab240ff2e7f67@[209.173.86.17]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ralph Droms <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP AutoConfig Option Size
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

At 2:04 PM -0400 10/6/98, Ted Lemon wrote:
>The one response you got was that you shouldn't do it, and I tend to
>agree - we've made a policy decision not to overload options, and what
>you're proposing is essentially that.

I'll second that response - we've discovered we're not as short of option
codes as we thought, so we have enough (I hesitate to say "plenty") to use
until the new options encoding is developed.

- Ralph





From dhcp-v4@bucknell.edu  Fri Oct  9 13:15:08 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA03400
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 13:15:07 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id NAA16962;
	Fri, 9 Oct 1998 13:10:53 -0400 (EDT)
Date: Fri, 9 Oct 1998 13:10:53 -0400 (EDT)
Message-Id: <199810091611.LAA20379@us.networkcs.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: Tim Salo <salo@networkcs.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCP and SCSP
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

As best I can tell, the DHCP working group started to explore the use
of SCSP to synchronize DHCP servers, but then stopped.

Can anyone provide me a summary of why the DHCP working group concluded
that SCSP wasn't the most appropriate method of synchronizing DHCP
servers?

Thanks,
	-tjs


From dhcp-v4@bucknell.edu  Fri Oct  9 14:12:08 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA04487
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 14:12:06 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id OAA10086;
	Fri, 9 Oct 1998 14:08:49 -0400 (EDT)
Date: Fri, 9 Oct 1998 14:08:49 -0400 (EDT)
Message-Id: <63D30D6E10CFD11190A90000F805FE86569942@lespaul.process.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: Steve Gonczi <Gonczi@process.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: DHCP and SCSP
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain
X-Mailer: Internet Mail Service (5.0.1460.8)
Mime-Version: 1.0

Kim Kinnear is the best person to answer this...

As I recall, there was nothing wrong with SCSP per se, but the entire Server
to Server Protocol ( which was a multi-server protocol, with server group
management)
was set aside in favor of a much simpler approach.

sG

> ----------
> From: 	Tim Salo[SMTP:salo@networkcs.com]
> Reply To: 	dhcp-v4@bucknell.edu
> Sent: 	Friday, October 09, 1998 1:15 PM
> To: 	Multiple recipients of list
> Subject: 	DHCP and SCSP
> 
> As best I can tell, the DHCP working group started to explore the use
> of SCSP to synchronize DHCP servers, but then stopped.
> 
> Can anyone provide me a summary of why the DHCP working group concluded
> that SCSP wasn't the most appropriate method of synchronizing DHCP
> servers?
> 
> Thanks,
> 	-tjs
> 


From dhcp-v4@bucknell.edu  Fri Oct  9 17:26:42 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA07062
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 17:26:41 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id RAA20482;
	Fri, 9 Oct 1998 17:24:07 -0400 (EDT)
Date: Fri, 9 Oct 1998 17:24:07 -0400 (EDT)
Message-Id: <199810092105.RAA02731@prospero.dma.isg.mot.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: "Michael W. Patrick" <mpatrick@dma.isg.mot.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Microsoft NT4 DHCP problems with Docsis
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

I had heard that Microsoft NT's 4.0 DHCP server"couldn't be used" in a
Docsis cable modem network and we recently discovered why.  (If this
is old news, my apologies.)

For other reasons, Service Pack 3 must be installed on the DHCP 4.0
server.  Unfortunately, the SP3 software does not correctly return the
(next) Server IP Address (siaddr) field of the BOOTP header. The
siaddr field of the BOOTP header is required by Docsis to be the IP
address of the configuration file TFTP server.  Microsoft NT SP3
documentation says that the IP value resolved for the DNS name in DHCP
option 67 "Bootfile Name" is placed into siaddr, but this doesn't work
in the shipped SP3. (Either a DNS name or dotted decimal notation may
be entered as the Option 67 value.)

This problem is documented in Microsoft Support article #Q175035
"Diskless Workstations Cannot Find BOOTP Server with DHCP".
The article calls for applying the patch "dhcpssvc.dll" on top of SP3.

Motorola has tested this patch and found it to work for Docsis
operation. We are using NT server successfully as the DHCP server
for our Docsis modem and CMTS system testing.  Our thanks to 
Ye Gu and Peter Ford of Microsoft for assistance with this problem.

Regards,
-mike









From dhcp-v4@bucknell.edu  Fri Oct  9 17:28:17 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA07089
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 17:28:17 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id RAA17340;
	Fri, 9 Oct 1998 17:25:38 -0400 (EDT)
Date: Fri, 9 Oct 1998 17:25:38 -0400 (EDT)
Message-Id: <199810092111.RAA06613@andare.fugue.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: Ted Lemon <mellon@hoffman.vix.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP and SCSP 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


> Can anyone provide me a summary of why the DHCP working group concluded
> that SCSP wasn't the most appropriate method of synchronizing DHCP
> servers?

Because it's too complicated and has a subtlely but significantly
different model of what server database synchronization means than
the model that's needed to support a DHCP interserver protocol.

			       _MelloN_


From dhcp-v4@bucknell.edu  Fri Oct  9 17:30:10 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA07138
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 17:30:09 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id RAA29044;
	Fri, 9 Oct 1998 17:25:59 -0400 (EDT)
Date: Fri, 9 Oct 1998 17:25:59 -0400 (EDT)
Message-Id: <4FD6422BE942D111908D00805F3158DF080C9030@RED-MSG-52>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ye Gu <yegu@microsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Microsoft NT4 DHCP problems with Docsis
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Internet Mail Service (5.5.2232.9)

The patch that Mike mentioned below has been rolled into Microsoft
NT 4.0 Service Pack 4, which will be available shortly.

Thanks!

Ye

-----Original Message-----
From: Michael W. Patrick [mailto:mpatrick@dma.isg.mot.com]
Sent: Friday, October 09, 1998 2:05 PM
To: docsis-oss@cablelabs.com; docsis-macup@cablelabs.com
Cc: dhcp-v4@bucknell.edu; Peter Ford; Ye Gu; mpatrick@dma.isg.mot.com;
astheime@dma.isg.mot.com
Subject: Microsoft NT4 DHCP problems with Docsis


I had heard that Microsoft NT's 4.0 DHCP server"couldn't be used" in a
Docsis cable modem network and we recently discovered why.  (If this
is old news, my apologies.)

For other reasons, Service Pack 3 must be installed on the DHCP 4.0
server.  Unfortunately, the SP3 software does not correctly return the
(next) Server IP Address (siaddr) field of the BOOTP header. The
siaddr field of the BOOTP header is required by Docsis to be the IP
address of the configuration file TFTP server.  Microsoft NT SP3
documentation says that the IP value resolved for the DNS name in DHCP
option 67 "Bootfile Name" is placed into siaddr, but this doesn't work
in the shipped SP3. (Either a DNS name or dotted decimal notation may
be entered as the Option 67 value.)

This problem is documented in Microsoft Support article #Q175035
"Diskless Workstations Cannot Find BOOTP Server with DHCP".
The article calls for applying the patch "dhcpssvc.dll" on top of SP3.

Motorola has tested this patch and found it to work for Docsis
operation. We are using NT server successfully as the DHCP server
for our Docsis modem and CMTS system testing.  Our thanks to 
Ye Gu and Peter Ford of Microsoft for assistance with this problem.

Regards,
-mike








From dhcp-v4@bucknell.edu  Fri Oct  9 19:41:34 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA08115
	for <dhc-archive@odin.ietf.org>; Fri, 9 Oct 1998 19:41:29 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id TAA15012;
	Fri, 9 Oct 1998 19:37:09 -0400 (EDT)
Date: Fri, 9 Oct 1998 19:37:09 -0400 (EDT)
Message-Id: <4FD6422BE942D111908D00805F3158DF080C9032@RED-MSG-52>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ye Gu <yegu@microsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Microsoft NT4 DHCP problems with Docsis
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Internet Mail Service (5.5.2232.9)

First, a small correction...  The option 67 in the context of the thread
below should really be option 66 'TFTP Server Name'.

Current MS DHCP server sets BOOTP header fields ('siaddr', 'file',
'sname') as the following:
1. A DHCP client doesn't request options 66 and 67 explicitly.  DHCP
   server returns option 66 in 'siaddr' and option 67 in 'file', if these
   options have specified values and option 66 contains an IP address.
   If option 66 contains a DNS name instead, server resolves that name
   first and returns the DNS name in 'sname' and IP address in 'siaddr'.
2. A DHCP client requests options 66 and 67 explicitly.  DHCP server sets
   'siaddr', 'file', 'sname' according to step #1.  In addition, it
   returns option 66 and 67.

Cheers,

Ye

-----Original Message-----
From: Jason Schnitzer [mailto:J.Schnitzer@cablelabs.com]
Sent: Friday, October 09, 1998 3:23 PM
To: DOCSIS OSS Majordomo List; DOCSIS Macup Majordomo List; 'Michael W.
Patrick'
Cc: dhcp-v4@bucknell.edu; Peter Ford; Ye Gu; astheime@dma.isg.mot.com
Subject: RE: Microsoft NT4 DHCP problems with Docsis


Mike,

Thanks for the info. I thought rfc2132 recommended that option 67 only be
used as a backup -- if the header's siaddr was overloaded or being used for
something else. Conceivably, a DHCP client could use both fields
(siaddr+Option67). Does the MS DHCP server support this?

Cheers,
Jason
CableLabs

> ----------
> From: 	Michael W. Patrick[SMTP:mpatrick@dma.isg.mot.com]
> Sent: 	Friday, October 09, 1998 3:05 PM
> To: 	docsis-oss@cablelabs.com; docsis-macup@cablelabs.com
> Cc: 	dhcp-v4@bucknell.edu; peterf@microsoft.com; yegu@microsoft.com;
> mpatrick@dma.isg.mot.com; astheime@dma.isg.mot.com
> Subject: 	Microsoft NT4 DHCP problems with Docsis
> 
> I had heard that Microsoft NT's 4.0 DHCP server"couldn't be used" in a
> Docsis cable modem network and we recently discovered why.  (If this
> is old news, my apologies.)
> 
> For other reasons, Service Pack 3 must be installed on the DHCP 4.0
> server.  Unfortunately, the SP3 software does not correctly return the
> (next) Server IP Address (siaddr) field of the BOOTP header. The
> siaddr field of the BOOTP header is required by Docsis to be the IP
> address of the configuration file TFTP server.  Microsoft NT SP3
> documentation says that the IP value resolved for the DNS name in DHCP
> option 67 "Bootfile Name" is placed into siaddr, but this doesn't work
> in the shipped SP3. (Either a DNS name or dotted decimal notation may
> be entered as the Option 67 value.)
> 
> This problem is documented in Microsoft Support article #Q175035
> "Diskless Workstations Cannot Find BOOTP Server with DHCP".
> The article calls for applying the patch "dhcpssvc.dll" on top of SP3.
> 
> Motorola has tested this patch and found it to work for Docsis
> operation. We are using NT server successfully as the DHCP server
> for our Docsis modem and CMTS system testing.  Our thanks to 
> Ye Gu and Peter Ford of Microsoft for assistance with this problem.
> 
> Regards,
> -mike
> 
> 
> 
> 
> 
> 


From dhcp-v4@bucknell.edu  Sun Oct 11 11:40:58 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA03303
	for <dhc-archive@odin.ietf.org>; Sun, 11 Oct 1998 11:40:52 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id LAA00502;
	Sun, 11 Oct 1998 11:37:03 -0400 (EDT)
Date: Sun, 11 Oct 1998 11:37:03 -0400 (EDT)
Message-Id: <v03007801b2467326b4d8@[209.173.86.57]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Microsoft NT4 DHCP problems with Docsis
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


message sent to dhcp-v4@bucknell.edu by J.SCHNITZER@CABLELABS.COM follows.
--------------------------------------------------------------------------
Mike,

Thanks for the info. I thought rfc2132 recommended that option 67 only be
used as a backup -- if the header's siaddr was overloaded or being used for
something else. Conceivably, a DHCP client could use both fields
(siaddr+Option67). Does the MS DHCP server support this?

Cheers,
Jason
CableLabs

> ----------
> From: 	Michael W. Patrick[SMTP:mpatrick@dma.isg.mot.com]
> Sent: 	Friday, October 09, 1998 3:05 PM
> To: 	docsis-oss@cablelabs.com; docsis-macup@cablelabs.com
> Cc: 	dhcp-v4@bucknell.edu; peterf@microsoft.com; yegu@microsoft.com;
> mpatrick@dma.isg.mot.com; astheime@dma.isg.mot.com
> Subject: 	Microsoft NT4 DHCP problems with Docsis
>
> I had heard that Microsoft NT's 4.0 DHCP server"couldn't be used" in a
> Docsis cable modem network and we recently discovered why.  (If this
> is old news, my apologies.)
>
> For other reasons, Service Pack 3 must be installed on the DHCP 4.0
> server.  Unfortunately, the SP3 software does not correctly return the
> (next) Server IP Address (siaddr) field of the BOOTP header. The
> siaddr field of the BOOTP header is required by Docsis to be the IP
> address of the configuration file TFTP server.  Microsoft NT SP3
> documentation says that the IP value resolved for the DNS name in DHCP
> option 67 "Bootfile Name" is placed into siaddr, but this doesn't work
> in the shipped SP3. (Either a DNS name or dotted decimal notation may
> be entered as the Option 67 value.)
>
> This problem is documented in Microsoft Support article #Q175035
> "Diskless Workstations Cannot Find BOOTP Server with DHCP".
> The article calls for applying the patch "dhcpssvc.dll" on top of SP3.
>
> Motorola has tested this patch and found it to work for Docsis
> operation. We are using NT server successfully as the DHCP server
> for our Docsis modem and CMTS system testing.  Our thanks to
> Ye Gu and Peter Ford of Microsoft for assistance with this problem.
>
> Regards,
> -mike
>
>
>
>
>
>




From dhcp-v4@bucknell.edu  Sun Oct 11 11:42:36 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA03323
	for <dhc-archive@odin.ietf.org>; Sun, 11 Oct 1998 11:42:30 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id LAA05039;
	Sun, 11 Oct 1998 11:40:57 -0400 (EDT)
Date: Sun, 11 Oct 1998 11:40:57 -0400 (EDT)
Message-Id: <v03007803b24673dee005@[209.173.86.57]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: FreeBSD / Linux DHCP implementation w/ Docsis?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


Message sent to dhcp-v4@bucknell.edu by GSUTTER@ORCRIST.MEDIACITY.COM follows.
-----------------------------------------------------------------------------
 I have a Docsis problem: I have to use NT DHCP servers rather than
(for example) ISC DHCP on FreeBSD, because ISC doesn't support Docsis.
Does anyone know of a free _or commercial_ DHCP solution that has
support for Docsis _and_ runs on either FreeBSD or Linux?

Thanks for your help.

Greg
--
Gregory S. Sutter                    "Very funny, Scotty.
mailto:gsutter@pobox.com              Now beam down my clothes."
http://www.pobox.com/~gsutter/
PGP DSS public key 0x40AE3052




From dhcp-v4@bucknell.edu  Mon Oct 12 16:35:09 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA04256
	for <dhc-archive@odin.ietf.org>; Mon, 12 Oct 1998 16:35:03 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA30849;
	Mon, 12 Oct 1998 16:23:48 -0400 (EDT)
Date: Mon, 12 Oct 1998 16:23:48 -0400 (EDT)
Message-Id: <36225DFC.4C3AD74@alpha.fh-furtwangen.de>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Daniel Thelen <thelen@alpha.fh-furtwangen.de>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: NT 3.51 Server and Linux DHCP Client
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
X-Mailer: Mozilla 4.05 [de]C-NECCK  (Win95; I)

Hello,

I am trying to connect a Linux computer with a Win NT 3.51 server.
According to the manual of the client it works with that kind of server.
I identify with MAC Address the Linux computer, but it hasn't any name.
After a short time the Linux computer is shutting down the network.
Before it shuts down 'ifconfig' reports 0.0.0.0 as IP address. Probably
the computer is waiting for the NT server to get his dynamic IP. Does
anybody know how to solve that problem ??? Thanx a lot.

D.Thelen



From dhcp-v4@bucknell.edu  Thu Oct 15 06:27:26 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id GAA06756
	for <dhc-archive@odin.ietf.org>; Thu, 15 Oct 1998 06:27:25 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id GAA15884;
	Thu, 15 Oct 1998 06:20:33 -0400 (EDT)
Date: Thu, 15 Oct 1998 06:20:33 -0400 (EDT)
Message-Id: <v03007804b24b783c8e80@[209.173.94.115]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ralph Droms <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: WG last call for "DHCP Option to Disable Stateless
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

This is a WG last call for "DHCP Option to Disable Stateless
Auto-Configuration in IPv4 Clients" <draft-ietf-dhc-autoconfig-01.txt>.
Please respond to the dhcp-v4@bucknell.edu mailing list with comments by
10/23/98.  If there are no comments, the draft will be submitted for
acceptance as a Proposed Standard.

- Ralph Droms




From dhcp-v4@bucknell.edu  Thu Oct 15 10:50:55 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA09681
	for <dhc-archive@odin.ietf.org>; Thu, 15 Oct 1998 10:50:54 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id KAA18178;
	Thu, 15 Oct 1998 10:45:46 -0400 (EDT)
Date: Thu, 15 Oct 1998 10:45:46 -0400 (EDT)
Message-Id: <199810151417.KAA17572@andare.fugue.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: Ted Lemon <mellon@hoffman.vix.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: WG last call for "DHCP Option to Disable Stateless 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


Blah.  It's late to bring this up, but I just read the draft for the
first time today.  I have one nit, and it's fairly minor: most DHCP
options that I know of currently use 0 for false and 1 for true.  The
Autoconfigure option uses 1 for false and 2 for true.  I'd really like
to see this normalized.  Right now, boolean options in the Internet
Software Consortium DHCP server can be configured like this:

	option boolean-foo true;

and

	option boolean-foo false;

This autoconfig option would have to be configured like this:

	option permit-auto-configuration 1;

or

	option permit-auto-configuration 2;

This seems like a fairly noticable inconsistency that we can safely do
without.

			       _MelloN_


From dhcp-v4@bucknell.edu  Thu Oct 15 12:32:49 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA13492
	for <dhc-archive@odin.ietf.org>; Thu, 15 Oct 1998 12:32:49 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id MAA17452;
	Thu, 15 Oct 1998 12:28:11 -0400 (EDT)
Date: Thu, 15 Oct 1998 12:28:11 -0400 (EDT)
Message-Id: <Roam.SIMC.2.0.6.908463988.16977.mwc@atlantic.east.sun.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: Mike Carney - SNT Internet Engineering <Michael.Carney@East.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: WG last call for "DHCP Option to Disable Stateless 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Mime-Version: 1.0

> 
> Blah.  It's late to bring this up, but I just read the draft for the
> first time today.  I have one nit, and it's fairly minor: most DHCP
> options that I know of currently use 0 for false and 1 for true.  The
> Autoconfigure option uses 1 for false and 2 for true.  I'd really like
> to see this normalized.  Right now, boolean options in the Internet
> Software Consortium DHCP server can be configured like this:
> 
> 	option boolean-foo true;
> 
> and
> 
> 	option boolean-foo false;

Ouch. I agree with Ted. False is 0, True is 1.



Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.




From dhcp-v4@bucknell.edu  Thu Oct 15 12:32:58 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA13503
	for <dhc-archive@odin.ietf.org>; Thu, 15 Oct 1998 12:32:53 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id MAA31059;
	Thu, 15 Oct 1998 12:29:28 -0400 (EDT)
Date: Thu, 15 Oct 1998 12:29:28 -0400 (EDT)
Message-Id: <63D30D6E10CFD11190A90000F805FE86569980@lespaul.process.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: Steve Gonczi <Gonczi@process.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: WG last call for "DHCP Option to Disable Stateless
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain
X-Mailer: Internet Mail Service (5.0.1460.8)
Mime-Version: 1.0

I have to agree with Ted Lemon. 
It would be much better to stick to using 0 for false and 1 for true.

Steve Gonczi @ PSC

> ----------
> From: 	Ralph Droms[SMTP:droms@bucknell.edu]
> Reply To: 	dhcp-v4@bucknell.edu
> Sent: 	Thursday, October 15, 1998 6:24 AM
> To: 	Multiple recipients of list
> Subject: 	WG last call for "DHCP Option to Disable Stateless
> 
> This is a WG last call for "DHCP Option to Disable Stateless
> Auto-Configuration in IPv4 Clients" <draft-ietf-dhc-autoconfig-01.txt>.
> Please respond to the dhcp-v4@bucknell.edu mailing list with comments by
> 10/23/98.  If there are no comments, the draft will be submitted for
> acceptance as a Proposed Standard.
> 
> - Ralph Droms
> 
> 


From dhcp-v4@bucknell.edu  Thu Oct 15 18:08:00 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA24923
	for <dhc-archive@odin.ietf.org>; Thu, 15 Oct 1998 18:07:54 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id SAA19531;
	Thu, 15 Oct 1998 18:03:40 -0400 (EDT)
Date: Thu, 15 Oct 1998 18:03:40 -0400 (EDT)
Message-Id: <Pine.GSO.4.03.9810151718030.11730-100000@castor>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Ralph E. Droms" <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0


The IESG has received a request from the Dynamic Host Configuration
Working Group to consider DHCP Option for User Authentication Protocol
<draft-ietf-dhc-options-uap-01.txt> as a Proposed Standard.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by October 29, 1998.

Files can be obtained via
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-options-uap-01.txt




From dhcp-v4@bucknell.edu  Fri Oct 16 17:16:18 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA20520
	for <dhc-archive@odin.ietf.org>; Fri, 16 Oct 1998 17:16:17 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id RAA01999;
	Fri, 16 Oct 1998 17:10:14 -0400 (EDT)
Date: Fri, 16 Oct 1998 17:10:14 -0400 (EDT)
Message-Id: <v03007807b24d56b425be@[209.173.94.113]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ralph Droms <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP and SCSP
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

At 1:16 PM -0400 10/9/98, Tim Salo wrote:
>Can anyone provide me a summary of why the DHCP working group concluded
>that SCSP wasn't the most appropriate method of synchronizing DHCP
>servers?

The WG concluded that the proposed synchronization protocol for DHCP
servers was  complex and depended on SCSP, which is, as yet, not completed.
The WG decided to pursue a simpler "failover" protocol, which provides less
function but is much less complex and can be implemented today.

- Ralph





From dhcp-v4@bucknell.edu  Sat Oct 17 23:36:07 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id XAA15006
	for <dhc-archive@odin.ietf.org>; Sat, 17 Oct 1998 23:36:06 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id XAA18435;
	Sat, 17 Oct 1998 23:32:59 -0400 (EDT)
Date: Sat, 17 Oct 1998 23:32:59 -0400 (EDT)
Message-Id: <emacs-smtp-6819-13865-22887-34914@lister.net.cmu.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ryan Troll <ryan@andrew.cmu.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: autoconfig option draft change
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0 (generated by tm-edit 7.108)
X-Mailer: BatIMail version 3.1


I just submitted a new version of this draft.  The only change in it
is the DHCP option values changing from 1/2 to 0/1.

-Ryan



From dhcp-v4@bucknell.edu  Mon Oct 19 10:21:30 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA19436
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 10:21:27 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id KAA18829;
	Mon, 19 Oct 1998 10:10:45 -0400 (EDT)
Date: Mon, 19 Oct 1998 10:10:45 -0400 (EDT)
Message-Id: <002001bdfb63$04a777a0$8a50fb8d@gwaters2.corpnorth.baynetworks.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: Glenn_Waters@BayNetworks.COM (Glenn Waters)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

this spec proposes that URLs be separated by a space character.  is that not
problematic if a URL contains a space?

/gww

> -----Original Message-----
> From: dhcp-v4@bucknell.edu [mailto:dhcp-v4@bucknell.edu]On Behalf Of
> Ralph E. Droms
> Sent: Thursday, October 15, 1998 18:07
> To: Multiple recipients of list
> Subject: Last Call: DHCP Option for User Authentication Protocol to
> (fwd)
>
>
>
> The IESG has received a request from the Dynamic Host Configuration
> Working Group to consider DHCP Option for User Authentication Protocol
> <draft-ietf-dhc-options-uap-01.txt> as a Proposed Standard.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by October 29, 1998.
>
> Files can be obtained via
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-options-uap-01.txt
>
>
>



From dhcp-v4@bucknell.edu  Mon Oct 19 13:12:35 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA23690
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 13:12:28 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id NAA02129;
	Mon, 19 Oct 1998 13:01:01 -0400 (EDT)
Date: Mon, 19 Oct 1998 13:01:01 -0400 (EDT)
Message-Id: <Roam.SIMC.2.0.6.908807273.3408.mwc@atlantic.east.sun.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: Mike Carney - SNT Internet Engineering <Michael.Carney@East.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Mime-Version: 1.0

> this spec proposes that URLs be separated by a space character.  is that not
> problematic if a URL contains a space?
> 
> /gww
> 

Hi glenn,
	The space is used to differentiate one URL from another. The client would
need to parse this into a list of URLs (simple, since it can use the space
character as the separator).



Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.




From dhcp-v4@bucknell.edu  Mon Oct 19 13:16:44 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA23809
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 13:16:37 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id NAA20954;
	Mon, 19 Oct 1998 13:10:57 -0400 (EDT)
Date: Mon, 19 Oct 1998 13:10:57 -0400 (EDT)
Message-Id: <Pine.LNX.4.05.9810190719260.6671-100000@parhelion>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Steve Drach <drach@Eng.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0


>From RFC1738: "The space character is unsafe ....  All unsafe characters
must always be encoded within a URL."  So, the space character must be
represented by %20.  Further on in the RFC, it does say that whitespace
in URL's embedded in context (i.e. e-mail) should be ignored.  But this
option isn't really the kind of context it's refering to.  We can specify
that, for this option, a space seperates URLs.

On Mon, 19 Oct 1998, Glenn Waters wrote:

> this spec proposes that URLs be separated by a space character.  is that not
> problematic if a URL contains a space?



From dhcp-v4@bucknell.edu  Mon Oct 19 15:16:44 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA27222
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 15:16:35 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id PAA00999;
	Mon, 19 Oct 1998 15:10:03 -0400 (EDT)
Date: Mon, 19 Oct 1998 15:10:03 -0400 (EDT)
Message-Id: <002901bdfb73$ffb6e8f0$8a50fb8d@gwaters2.corpnorth.baynetworks.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: Glenn_Waters@BayNetworks.COM (Glenn Waters)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

how do you tell if a space is separating two URLs or whether the space is
part of the URL?

/gww

> -----Original Message-----
> From: Mike Carney - SNT Internet Engineering
> [mailto:Michael.Carney@East.Sun.COM]
> Sent: Monday, October 19, 1998 10:28
> To: Glenn Waters
> Cc: Multiple recipients of list
> Subject: RE: Last Call: DHCP Option for User Authentication Protocol to
> (fwd)
>
>
> > this spec proposes that URLs be separated by a space character.
>  is that not
> > problematic if a URL contains a space?
> >
> > /gww
> >
>
> Hi glenn,
> 	The space is used to differentiate one URL from another.
> The client would
> need to parse this into a list of URLs (simple, since it can use the space
> character as the separator).
>
>
>
> Mike Carney
> SNT Internet Engineering
> Sun Microsystems, Inc.
>
>
>



From dhcp-v4@bucknell.edu  Mon Oct 19 16:21:43 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA28981
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 16:21:40 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA05408;
	Mon, 19 Oct 1998 16:14:57 -0400 (EDT)
Date: Mon, 19 Oct 1998 16:14:57 -0400 (EDT)
Message-Id: <Roam.SIMC.2.0.6.908824275.21836.mwc@atlantic.east.sun.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: Mike Carney - SNT Internet Engineering <Michael.Carney@East.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Mime-Version: 1.0

> how do you tell if a space is separating two URLs or whether the space is
> part of the URL?
> 
> /gww

As you said yourself, a space is an illegal character in an URL. Thus, steve's
draft is using a space to separate URLs within the field.

Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.




From dhcp-v4@bucknell.edu  Mon Oct 19 16:24:55 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29026
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 16:24:41 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA28973;
	Mon, 19 Oct 1998 16:19:22 -0400 (EDT)
Date: Mon, 19 Oct 1998 16:19:22 -0400 (EDT)
Message-Id: <002101bdfb96$7fc49de0$48146c3e@a2000.nl>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "metin" <metin@cable.A2000.nl>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook Express 5.00.0518.4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

unsubscribe






From dhcp-v4@bucknell.edu  Mon Oct 19 16:26:30 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29066
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 16:26:29 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA28060;
	Mon, 19 Oct 1998 16:20:01 -0400 (EDT)
Date: Mon, 19 Oct 1998 16:20:01 -0400 (EDT)
Message-Id: <000001bdfb9a$6e12c0a0$6a50fb8d@lborsato.corpnorth.baynetworks.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: Larry_Borsato@BayNetworks.COM (Larry Borsato)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

The RFC states that all unsafe characters (i.e. space) must be encoded
within an URL. So space = %20.

Best,
Larry

--------------------------------------------
Larry W. Borsato,   NetID Product Manager
Bay Networks, a Nortel Networks Business
Email:  mailto:lborsato@baynetworks.com
Phone:  +1 (613) 722-1921

> -----Original Message-----
> From: dhcp-v4@bucknell.edu [mailto:dhcp-v4@bucknell.edu]On Behalf Of
> Glenn Waters
> Sent: Monday, October 19, 1998 3:12 PM
> To: Multiple recipients of list
> Subject: RE: Last Call: DHCP Option for User Authentication Protocol to
> (fwd)
>
>
> how do you tell if a space is separating two URLs or whether the space is
> part of the URL?
>
> /gww
>
> > -----Original Message-----
> > From: Mike Carney - SNT Internet Engineering
> > [mailto:Michael.Carney@East.Sun.COM]
> > Sent: Monday, October 19, 1998 10:28
> > To: Glenn Waters
> > Cc: Multiple recipients of list
> > Subject: RE: Last Call: DHCP Option for User Authentication Protocol to
> > (fwd)
> >
> >
> > > this spec proposes that URLs be separated by a space character.
> >  is that not
> > > problematic if a URL contains a space?
> > >
> > > /gww
> > >
> >
> > Hi glenn,
> > 	The space is used to differentiate one URL from another.
> > The client would
> > need to parse this into a list of URLs (simple, since it can
> use the space
> > character as the separator).
> >
> >
> >
> > Mike Carney
> > SNT Internet Engineering
> > Sun Microsystems, Inc.
> >
> >
> >
>
>



From dhcp-v4@bucknell.edu  Mon Oct 19 16:27:37 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29101
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 16:27:32 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA12416;
	Mon, 19 Oct 1998 16:18:01 -0400 (EDT)
Date: Mon, 19 Oct 1998 16:18:01 -0400 (EDT)
Message-Id: <63D30D6E10CFD11190A90000F805FE8656998C@lespaul.process.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: Steve Gonczi <Gonczi@process.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to (f
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain
X-Mailer: Internet Mail Service (5.0.1460.8)
Mime-Version: 1.0

I guess the idea is:  Un-encoded spaces are not allowed in URL-s,  hence any
such encountered IS a separator.

sG

> ----------
> From:
> Glenn_Waters@BayNetworks.COM[SMTP:Glenn_Waters@BayNetworks.COM]
> Reply To: 	dhcp-v4@bucknell.edu
> Sent: 	Monday, October 19, 1998 3:11 PM
> To: 	Multiple recipients of list
> Subject: 	RE: Last Call: DHCP Option for User Authentication Protocol
> to (fwd)
> 
> how do you tell if a space is separating two URLs or whether the space is
> part of the URL?
> 
> /gww
> 


From dhcp-v4@bucknell.edu  Mon Oct 19 16:38:04 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29028
	for <dhc-archive@odin.ietf.org>; Mon, 19 Oct 1998 16:24:50 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id QAA30590;
	Mon, 19 Oct 1998 16:18:36 -0400 (EDT)
Date: Mon, 19 Oct 1998 16:18:36 -0400 (EDT)
Message-Id: <001b01bdfb96$505d4d40$48146c3e@a2000.nl>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "metin" <metin@cable.A2000.nl>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Last Call: DHCP Option for User Authentication Protocol to (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook Express 5.00.0518.4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0

unsubscribe
-----Original Message-----
From: Glenn Waters <Glenn_Waters@BayNetworks.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Date: Monday, October 19, 1998 9:16 PM
Subject: RE: Last Call: DHCP Option for User Authentication Protocol to
(fwd)


>how do you tell if a space is separating two URLs or whether the space is
>part of the URL?
>
>/gww
>
>> -----Original Message-----
>> From: Mike Carney - SNT Internet Engineering
>> [mailto:Michael.Carney@East.Sun.COM]
>> Sent: Monday, October 19, 1998 10:28
>> To: Glenn Waters
>> Cc: Multiple recipients of list
>> Subject: RE: Last Call: DHCP Option for User Authentication Protocol to
>> (fwd)
>>
>>
>> > this spec proposes that URLs be separated by a space character.
>>  is that not
>> > problematic if a URL contains a space?
>> >
>> > /gww
>> >
>>
>> Hi glenn,
>> The space is used to differentiate one URL from another.
>> The client would
>> need to parse this into a list of URLs (simple, since it can use the
space
>> character as the separator).
>>
>>
>>
>> Mike Carney
>> SNT Internet Engineering
>> Sun Microsystems, Inc.
>>
>>
>>
>



From dhcp-v4@bucknell.edu  Tue Oct 20 17:13:18 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA03308
	for <dhc-archive@odin.ietf.org>; Tue, 20 Oct 1998 17:13:15 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id RAA00806;
	Tue, 20 Oct 1998 17:04:33 -0400 (EDT)
Date: Tue, 20 Oct 1998 17:04:33 -0400 (EDT)
Message-Id: <1303205534-4960946@mail.clarityconnect.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: "Brad Goodwin (Computer Technician)" <fes@clarityconnect.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: New to networking, need some info
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
Mime-Version: 1.0
X-Mailer: Microsoft Internet Mail 4.70.1155

I have a bunch of windows 95 computers, and one NT server.  We have a ISDN
line running to another network which dynamically assigned the IP addresses
to my computers.  This has worked fine, but there is some concern about
people accessing the network from the outside. I want to configure my
server to assign the addresses instead so I can have more control over
outside access.  Any information will be greatly appreciated.

28 P2s, running windows 95, fast ethernet, one server running NT 4.0. 

Thanks for your help.

 -Brad Goodwin
  Computer Technician
  Dryden Central Schools
  (607)844-8694 ext 517
  mysonscool@aol.com



From dhcp-v4@bucknell.edu  Thu Oct 22 07:35:12 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17704
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 07:35:12 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA29353;
	Thu, 22 Oct 1998 07:32:01 -0400 (EDT)
Date: Thu, 22 Oct 1998 07:32:01 -0400 (EDT)
Message-Id: <v0401170fb254079c3f17@[134.82.114.24]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Last Call: Procedure for Defining New DHCP Options to BCP
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


The IESG has received a request from the Dynamic Host Configuration
Working Group to consider Procedure for Defining New DHCP Options
<draft-ietf-dhc-new-options-04.txt> as a BCP.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by November 3, 1998.

Files can be obtained via
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-new-options-04.txt


From dhcp-v4@bucknell.edu  Thu Oct 22 07:35:15 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17714
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 07:35:15 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA22059;
	Thu, 22 Oct 1998 07:31:14 -0400 (EDT)
Date: Thu, 22 Oct 1998 07:31:14 -0400 (EDT)
Message-Id: <v0401170db25407723520@[134.82.114.24]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: I-D ACTION:draft-ietf-dhc-ipv4-autoconfig-01.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group
of the IETF.

	Title		: Automaticly Choosing an IP Address in
                          an Ad-Hoc IPv4 Network
	Author(s)	: R. Troll
	Filename	: draft-ietf-dhc-ipv4-autoconfig-01.txt
	Pages		: 8
	Date		: 19-Oct-98

     With operating systems appearing in more and more devices, as well
     as computers appearing in more and more aspects of everyday life,
     communication between networked devices is increasingly important.
     The communication mechanism between these devices must be able to
     not only support the office LAN environment, but must also scale to
     larger WANS and the internet.

     This draft describes a method by which a host may automaticly give
     itself a link-local IPv4 address, so that it will be able to use IP
     applications in the absence of an IP address management mechanism,
     such as DHCP.  This mechanism is in use today by a few operating
     systems, and additional information on those implementations is
     also provided.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-ipv4-autoconfig-01.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-ipv4-autoconfig-01.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za

	Europe: ftp.nordu.net
		ftp.nis.garr.it

	Pacific Rim: munnari.oz.au

	US East Coast: ftp.ietf.org

	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-ipv4-autoconfig-01.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


[The following attachment must be fetched by mail. Command-click the URL
below and send the resulting message to get the attachment.]
<mailto:mailserv@ietf.org?body=ENCODING%20mime%0D%0AFILE%20/internet-drafts/draf
t-ietf-dhc-ipv4-autoconfig-01.txt>
[The following attachment must be fetched by ftp.  Command-click the URL
below to ask your ftp client to fetch it.]
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-ipv4-autoconfig-01.txt>


From dhcp-v4@bucknell.edu  Thu Oct 22 07:37:04 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17733
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 07:37:04 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA26191;
	Thu, 22 Oct 1998 07:30:52 -0400 (EDT)
Date: Thu, 22 Oct 1998 07:30:52 -0400 (EDT)
Message-Id: <v0401170cb254075b2fbe@[134.82.114.24]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: I-D ACTION:draft-ietf-dhc-autoconfig-02.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group
of the IETF.

	Title		: DHCP Option to Disable Stateless Auto-Configuration
                          in IPv4 Clients
	Author(s)	: R. Troll
	Filename	: draft-ietf-dhc-autoconfig-02.txt
	Pages		: 9
	Date		: 19-Oct-98

     Operating Systems are now attempting to support ad-hoc networks of
     two or more systems, while keeping user configuration at a minimum.
     To accommodate this, in the absence of a central configuration
     mechanism (DHCP), some OS's are automaticly choosing an IP address
     which will allow them to communicate with other hosts running the
     same OS.  However, some sites depend on the fact that a host with
     no DHCP response will have no IP address.  This draft describes a
     mechanism by which DHCP servers are able to tell clients that they
     do not have an IP address to offer, and that the client should not
     auto-configure it's own.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-autoconfig-02.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-autoconfig-02.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za

	Europe: ftp.nordu.net
		ftp.nis.garr.it

	Pacific Rim: munnari.oz.au

	US East Coast: ftp.ietf.org

	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-autoconfig-02.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


[The following attachment must be fetched by mail. Command-click the URL
below and send the resulting message to get the attachment.]
<mailto:mailserv@ietf.org?body=ENCODING%20mime%0D%0AFILE%20/internet-drafts/draf
t-ietf-dhc-autoconfig-02.txt>
[The following attachment must be fetched by ftp.  Command-click the URL
below to ask your ftp client to fetch it.]
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-autoconfig-02.txt>


From dhcp-v4@bucknell.edu  Thu Oct 22 07:37:39 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17744
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 07:37:38 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA30609;
	Thu, 22 Oct 1998 07:31:37 -0400 (EDT)
Date: Thu, 22 Oct 1998 07:31:37 -0400 (EDT)
Message-Id: <v0401170eb25407883a4a@[134.82.114.24]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: I-D ACTION:draft-ietf-dhc-new-options-04.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group
of the IETF.

	Title		: Procedure for Defining New DHCP Options
	Author(s)	: R. Droms
	Filename	: draft-ietf-dhc-new-options-04.txt
	Pages		: 5
	Date		: 19-Oct-98

   The Dynamic Host Configuration Protocol (DHCP) provides a framework
   for passing configuration information to hosts on a TCP/IP network.
   Configuration parameters and other control information are carried in
   tagged data items that are stored in the 'options' field of the DHCP
   message.  The data items themselves are also called 'options.'

   New DHCP options may be defined after the publication of the DHCP
   specification to accommodate requirements for conveyance of new
   configuration parameters.  This document describes the procedure for
   defining new DHCP options.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-new-options-04.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-new-options-04.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za

	Europe: ftp.nordu.net
		ftp.nis.garr.it

	Pacific Rim: munnari.oz.au

	US East Coast: ftp.ietf.org

	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-new-options-04.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


[The following attachment must be fetched by mail. Command-click the URL
below and send the resulting message to get the attachment.]
<mailto:mailserv@ietf.org?body=ENCODING%20mime%0D%0AFILE%20/internet-drafts/draf
t-ietf-dhc-new-options-04.txt>
[The following attachment must be fetched by ftp.  Command-click the URL
below to ask your ftp client to fetch it.]
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-new-options-04.txt>


From dhcp-v4@bucknell.edu  Thu Oct 22 07:38:34 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA17756
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 07:38:33 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA24136;
	Thu, 22 Oct 1998 07:28:37 -0400 (EDT)
Date: Thu, 22 Oct 1998 07:28:37 -0400 (EDT)
Message-Id: <v0401170ab25406f918c4@[134.82.114.24]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: I-D ACTION:draft-ietf-dhc-slp-04.txt
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

Note: This revision reflects comments received during the last call period.

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group
of the IETF.

	Title		: DHCP Options for Service Location Protocol
	Author(s)	: C. Perkins, E. Guttman
	Filename	: draft-ietf-dhc-slp-04.txt
	Pages		: 5
	Date		: 15-Oct-98

   The Dynamic Host Configuration Protocol provides a framework for
   passing configuration information to hosts on a TCP/IP network.
   Entities using the Service Location Protocol need to find out the
   address of Directory Agents in order to transact messages.  Another
   option provides an assignment of scope for configuration of SLP User
   and Service Agents.

Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-slp-04.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-slp-04.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za

	Europe: ftp.nordu.net
		ftp.nis.garr.it

	Pacific Rim: munnari.oz.au

	US East Coast: ftp.ietf.org

	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-slp-04.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

Content-Type: text/plain
Content-ID:	<19981015170245.I-D@ietf.org>

[This attachment must be fetched by mail.
Open the stationery below and send the resulting
message to get the attachment.]
Attachment converted: untitled:Get Error Condition Re- I-D ACT (EuSn/CSOm)
(00001793)
Content-Type: Message/External-body;
	name="draft-ietf-dhc-slp-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

[This attachment must be fetched by ftp.
 Open the document below to ask your ftp client to fetch it.]
Attachment converted: untitled:Get draft-ietf-dhc-slp-04.txt (AURL/Arch)
(00001794)
Content-Type: text/plain
Content-ID:	<19981015170245.I-D@ietf.org>


From dhcp-v4@bucknell.edu  Thu Oct 22 12:21:25 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA24779
	for <dhc-archive@odin.ietf.org>; Thu, 22 Oct 1998 12:21:25 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id MAA09974;
	Thu, 22 Oct 1998 12:12:35 -0400 (EDT)
Date: Thu, 22 Oct 1998 12:12:35 -0400 (EDT)
Message-Id: <4FD6422BE942D111908D00805F3158DF080C90EE@RED-MSG-52>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ye Gu <yegu@microsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Microsoft NT4 DHCP problems with Docsis
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Internet Mail Service (5.5.2232.9)

FYI.  NT 4.0 Service Pack 4 was released on Monday and is now downloadable
from
http://www.microsoft.com/ntserver/nts/downloads/recommended/NT4SvcPk4/defaul
t.asp.

Cheers,

Ye

-----Original Message-----
From: Ye Gu 
Sent: Friday, October 09, 1998 2:14 PM
To: 'Michael W. Patrick'; docsis-oss@cablelabs.com;
docsis-macup@cablelabs.com
Cc: dhcp-v4@bucknell.edu; Peter Ford; astheime@dma.isg.mot.com
Subject: RE: Microsoft NT4 DHCP problems with Docsis


The patch that Mike mentioned below has been rolled into Microsoft
NT 4.0 Service Pack 4, which will be available shortly.

Thanks!

Ye

-----Original Message-----
From: Michael W. Patrick [mailto:mpatrick@dma.isg.mot.com]
Sent: Friday, October 09, 1998 2:05 PM
To: docsis-oss@cablelabs.com; docsis-macup@cablelabs.com
Cc: dhcp-v4@bucknell.edu; Peter Ford; Ye Gu; mpatrick@dma.isg.mot.com;
astheime@dma.isg.mot.com
Subject: Microsoft NT4 DHCP problems with Docsis


I had heard that Microsoft NT's 4.0 DHCP server"couldn't be used" in a
Docsis cable modem network and we recently discovered why.  (If this
is old news, my apologies.)

For other reasons, Service Pack 3 must be installed on the DHCP 4.0
server.  Unfortunately, the SP3 software does not correctly return the
(next) Server IP Address (siaddr) field of the BOOTP header. The
siaddr field of the BOOTP header is required by Docsis to be the IP
address of the configuration file TFTP server.  Microsoft NT SP3
documentation says that the IP value resolved for the DNS name in DHCP
option 67 "Bootfile Name" is placed into siaddr, but this doesn't work
in the shipped SP3. (Either a DNS name or dotted decimal notation may
be entered as the Option 67 value.)

This problem is documented in Microsoft Support article #Q175035
"Diskless Workstations Cannot Find BOOTP Server with DHCP".
The article calls for applying the patch "dhcpssvc.dll" on top of SP3.

Motorola has tested this patch and found it to work for Docsis
operation. We are using NT server successfully as the DHCP server
for our Docsis modem and CMTS system testing.  Our thanks to 
Ye Gu and Peter Ford of Microsoft for assistance with this problem.

Regards,
-mike








From dhcp-v4@bucknell.edu  Fri Oct 23 07:18:07 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA21818
	for <dhc-archive@odin.ietf.org>; Fri, 23 Oct 1998 07:18:07 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA24440;
	Fri, 23 Oct 1998 07:13:18 -0400 (EDT)
Date: Fri, 23 Oct 1998 07:13:18 -0400 (EDT)
Message-Id: <v04011711b25609b503bf@[134.82.7.103]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ralph Droms <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: NT 3.51 Server and Linux DHCP Client
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0

message sent to dhcp-v4@bucknell.edu by RHANDEEV@COMP.NUS.EDU.SG follows.
-------------------------------------------------------------------------
There are bugs in NT; can't remember what they are.  Every SP they seem to
fix something.  There's another DHCP fix in the upcoming SP4 for NT4.0.
Seriously NT3.51 is a bit old.

Sieve the DHCPv4 Working Group list for the details, to see if NT bugs are
causing the problem.  There's a Micro$oft guy on the list, so these issues
pop up from time to time.

Then again, it could be a config thing.  Does everything work with static
IP?

---
Rhandeev Singh                          rhandeev@comp.nus.edu.sg
Linux User Group                        http://linux.comp.nus.edu.sg
School of Computing                     http://www.comp.nus.edu.sg
National University of Singapore


On Mon, 12 Oct 1998, Daniel Thelen wrote:

> Hello,
>
> I am trying to connect a Linux computer with a Win NT 3.51 server.
> According to the manual of the client it works with that kind of server.
> I identify with MAC Address the Linux computer, but it hasn't any name.
> After a short time the Linux computer is shutting down the network.
> Before it shuts down 'ifconfig' reports 0.0.0.0 as IP address. Probably
> the computer is waiting for the NT server to get his dynamic IP. Does
> anybody know how to solve that problem ??? Thanx a lot.
>
> D.Thelen
>


From dhcp-v4@bucknell.edu  Fri Oct 23 13:39:16 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA02261
	for <dhc-archive@odin.ietf.org>; Fri, 23 Oct 1998 13:39:15 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id NAA07306;
	Fri, 23 Oct 1998 13:26:54 -0400 (EDT)
Date: Fri, 23 Oct 1998 13:26:54 -0400 (EDT)
Message-Id: <4FD6422BE942D111908D00805F3158DF080C9104@RED-MSG-52>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ye Gu <yegu@microsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: NT 3.51 Server and Linux DHCP Client
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Internet Mail Service (5.5.2232.9)

Are you running NT 3.51 SP5?  What's your server configuration?  The
quickest way to find out whether this is a server or client problem is to
sniff the wire for all DHCP packets.  After the sniff, if you still think
it's the server causing the problem, you can search the KnowledgeBase on
http://www.microsoft.com for known issues or contact our product support.

Cheers,

Ye

-----Original Message-----
From: Ralph Droms [mailto:droms@bucknell.edu]
Sent: Friday, October 23, 1998 4:15 AM
To: Multiple recipients of list
Subject: Re: NT 3.51 Server and Linux DHCP Client


message sent to dhcp-v4@bucknell.edu by RHANDEEV@COMP.NUS.EDU.SG follows.
-------------------------------------------------------------------------
There are bugs in NT; can't remember what they are.  Every SP they seem to
fix something.  There's another DHCP fix in the upcoming SP4 for NT4.0.
Seriously NT3.51 is a bit old.

Sieve the DHCPv4 Working Group list for the details, to see if NT bugs are
causing the problem.  There's a Micro$oft guy on the list, so these issues
pop up from time to time.

Then again, it could be a config thing.  Does everything work with static
IP?

---
Rhandeev Singh                          rhandeev@comp.nus.edu.sg
Linux User Group                        http://linux.comp.nus.edu.sg
School of Computing                     http://www.comp.nus.edu.sg
National University of Singapore


On Mon, 12 Oct 1998, Daniel Thelen wrote:

> Hello,
>
> I am trying to connect a Linux computer with a Win NT 3.51 server.
> According to the manual of the client it works with that kind of server.
> I identify with MAC Address the Linux computer, but it hasn't any name.
> After a short time the Linux computer is shutting down the network.
> Before it shuts down 'ifconfig' reports 0.0.0.0 as IP address. Probably
> the computer is waiting for the NT server to get his dynamic IP. Does
> anybody know how to solve that problem ??? Thanx a lot.
>
> D.Thelen
>


From dhcp-v4@bucknell.edu  Sat Oct 24 22:42:52 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id WAA28209
	for <dhc-archive@odin.ietf.org>; Sat, 24 Oct 1998 22:42:52 -0400 (EDT)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id WAA22202;
	Sat, 24 Oct 1998 22:27:28 -0400 (EDT)
Date: Sat, 24 Oct 1998 22:27:28 -0400 (EDT)
Message-Id: <Pine.GSO.4.03.9810242221330.26508-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Ralph E. Droms" <droms@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Problems with NT and AIX V4.31 DHCP (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0

message sent to dhcp-v4@bucknell.edu by SDEAN@POP.ULSTER.NET follows.
---------------------------------------------------------------------
I have a DHCP server running on an IBM F50 running AIX4.3.1.  It 
appears (tho sometimes, in this kind of situation, it can be 
difficult to distinguish which is cause and which is effect) that:
  1)  a Windows NT printer server we have is requesting all available 
DHCP addresses on after another.
  2) The AIX DHCP server stores a client ID that 2-3x longer than the 
one I see for a W85 machines
  3) When I try to drop some of these address (dadmin -d <clientID>), 
it doesn't drop and, about half the time, it hangs or blows away the 
dhcpsd daemon

Comments?  ideas for problem determination?
// Stewart Dean - sdean@ulster.net
//
// Machiavelli said (in essence):
//   Bad mercenaries will lose your country for you,
//   "good" ones will take it away from you....
//   Don't use mercenaries
// Dean's corollary:
//  Hiring temps or vendor employees may be all the rage...
//    but they're the same as mercenaries:
//  You give neither loyalty nor committment; 
//    the favor, if returned, should come as no surprise
//  Look to your own honor if you expect any from them.



From dhcp-v4@bucknell.edu  Mon Oct 26 09:49:11 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA20070
	for <dhc-archive@odin.ietf.org>; Mon, 26 Oct 1998 09:49:10 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id JAA12953;
	Mon, 26 Oct 1998 09:38:58 -0500 (EST)
Date: Mon, 26 Oct 1998 09:38:58 -0500 (EST)
Message-Id: <86CC4BA157E6D111ACCF0000C02C0500A98F86@honts318.homeoffice.wal-mart.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: Diana Lane <dblane@wal-mart.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Problems with NT and AIX V4.31 DHCP (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain
X-Mailer: Internet Mail Service (5.5.2232.9)
Mime-Version: 1.0

Is the NT print server running RAS?  I have seen RAS servers eat away at
DHCP pools and RAS servers do have long MAC addresses, starting with
52:41:53 H.  You might try supplying it completely unroutable addresses to
get it to stop requesting, or denying it addresses entirely based on a
hardware address mask.

I hope this helps!

Diana Lane, 501/277-3177
dblane@wal-mart.com
Sr. Network Engineer
Wal-Mart Stores, Inc.


	-----Original Message-----
	From:	Ralph E. Droms [SMTP:droms@bucknell.edu]
	Sent:	Saturday, October 24, 1998 9:32 PM
	To:	Multiple recipients of list
	Subject:	Problems with NT and AIX V4.31 DHCP (fwd)

	message sent to dhcp-v4@bucknell.edu by SDEAN@POP.ULSTER.NET
follows.
	
---------------------------------------------------------------------
	I have a DHCP server running on an IBM F50 running AIX4.3.1.  It 
	appears (tho sometimes, in this kind of situation, it can be 
	difficult to distinguish which is cause and which is effect) that:
	  1)  a Windows NT printer server we have is requesting all
available 
	DHCP addresses on after another.
	  2) The AIX DHCP server stores a client ID that 2-3x longer than
the 
	one I see for a W85 machines
	  3) When I try to drop some of these address (dadmin -d
<clientID>), 
	it doesn't drop and, about half the time, it hangs or blows away the

	dhcpsd daemon

	Comments?  ideas for problem determination?
	// Stewart Dean - sdean@ulster.net
	//
	// Machiavelli said (in essence):
	//   Bad mercenaries will lose your country for you,
	//   "good" ones will take it away from you....
	//   Don't use mercenaries
	// Dean's corollary:
	//  Hiring temps or vendor employees may be all the rage...
	//    but they're the same as mercenaries:
	//  You give neither loyalty nor committment; 
	//    the favor, if returned, should come as no surprise
	//  Look to your own honor if you expect any from them.


From dhcp-v4@bucknell.edu  Mon Oct 26 15:09:54 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA28373
	for <dhc-archive@odin.ietf.org>; Mon, 26 Oct 1998 15:09:53 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id OAA10438;
	Mon, 26 Oct 1998 14:56:33 -0500 (EST)
Date: Mon, 26 Oct 1998 14:56:33 -0500 (EST)
Message-Id: <199810261933.NAA31084@bears.austin.ibm.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: Greg Althaus <galthaus@austin.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Problems with NT and AIX V4.31 DHCP (fwd) 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
X-Mailer: exmh version 2.0gamma 1/27/96


I don't know about 1 or 2, but 3 is fixed and will soon be available on the
fixdist servers.  You can call the 1-800-call-aix number to request a fix.

If you have other questions, we can take this off the DHCP working group list.
I figure the others don't necessarily need this information.

Thanks,
Greg Althaus
AIX TCPIP Development and Support.
galthaus@austin.ibm.com


> ---------------------------------------------------------------------
> 	I have a DHCP server running on an IBM F50 running AIX4.3.1.  It 
> 	appears (tho sometimes, in this kind of situation, it can be 
> 	difficult to distinguish which is cause and which is effect) that:
> 	  1)  a Windows NT printer server we have is requesting all
> available 
> 	DHCP addresses on after another.
> 	  2) The AIX DHCP server stores a client ID that 2-3x longer than
> the 
> 	one I see for a W85 machines
> 	  3) When I try to drop some of these address (dadmin -d
> <clientID>), 
> 	it doesn't drop and, about half the time, it hangs or blows away the
> 
> 	dhcpsd daemon
> 
> 	Comments?  ideas for problem determination?
> 	// Stewart Dean - sdean@ulster.net
> 	//
> 	// Machiavelli said (in essence):
> 	//   Bad mercenaries will lose your country for you,
> 	//   "good" ones will take it away from you....
> 	//   Don't use mercenaries
> 	// Dean's corollary:
> 	//  Hiring temps or vendor employees may be all the rage...
> 	//    but they're the same as mercenaries:
> 	//  You give neither loyalty nor committment; 
> 	//    the favor, if returned, should come as no surprise
> 	//  Look to your own honor if you expect any from them.




From dhcp-v4@bucknell.edu  Thu Oct 29 07:04:52 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA00840
	for <dhc-archive@odin.ietf.org>; Thu, 29 Oct 1998 07:04:52 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id HAA29021;
	Thu, 29 Oct 1998 07:00:45 -0500 (EST)
Date: Thu, 29 Oct 1998 07:00:45 -0500 (EST)
Message-Id: <00d901be032d$36ca6cc0$9a9d9fc2@black-pudding.intranet-solutions.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: "Paul Roberts" <paul.roberts@intranet-solutions.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCP and spanning tree on switches
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
X-Mailer: Microsoft Outlook Express 4.72.3110.5
Mime-Version: 1.0

Hi,

I'm not an expert on switches so I am wondering if anyone can help me (and
please correct me if I am wrong)...

The way I understand switches work with DHCP, is when the client sends a
DHCPDISCOVER it takes a while for the switch port to learn the topology of
the network and it runs the spanning tree alogorithm to make sure there are
no loops. This takes a few seconds during which time the port is blocked.
The client will send another DHCPDISCOVER, and hopefully the switch port has
now come up, learnt where the client is trying to get to and switches the
packet across, and everything works fine.

However, I am seeing a situation where laptops moving to a different subnet
are having difficulty obtaining the correct IP address for that subnet. What
I think is happening is that the client broadcasts a DHCPREQUEST (during
INIT-REBOOT) to try and renew the old IP address. Because the switch port is
blocking for a few seconds while it learns the topology, the DHCPREQUEST
never makes it to the DHCP server (via an ip-helper on the switch), so the
client never gets a DHCPNAK. The client then tries to use it's old IP
address, which of course is invalid now that it has changed subnets.

I have heard that Cisco switch ports can be set to "fast port" mode, which
disables spanning tree, but isn't disabling spanning tree a bit dangerous?
In this case there aren't single workstations on each port, but lan segments
(each in a different subnet, so the switch is effectively routing).

What is the solution in this case? I guess this isn't a problem with desktop
PC's that don't move around and stay on the same port, but I haven't got a
clue how to get this working for laptops that move around onto different
ports, other than disabling spanning tree, which I'm not sure is a safe
thing to do.

Regards,

Paul

+---------------------------------------------+
|    Paul Roberts, Professional Services,     |
|     Internet & Intranet Solutions Ltd.      |
|  Tel: +44 1256 346344 Fax: +44 1256 346355  |
| E-mail: paul.roberts@intranet-solutions.com |
|    WWW: http://www.intranet-solutions.com   |
|      AOL Instant Messenger: PRoberts11      |
+---------------------------------------------+




From dhcp-v4@bucknell.edu  Thu Oct 29 11:37:41 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA06047
	for <dhc-archive@odin.ietf.org>; Thu, 29 Oct 1998 11:37:34 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id LAA12831;
	Thu, 29 Oct 1998 11:24:59 -0500 (EST)
Date: Thu, 29 Oct 1998 11:24:59 -0500 (EST)
Message-Id: <199810291553.KAA02289@bcn.East.Sun.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: Radia Perlman - Boston Center for Networking <Radia.Perlman@East.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP and spanning tree on switches
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc 
Content-Type: TEXT/plain; charset=us-ascii
Mime-Version: 1.0

Re: Paul Roberts question..

I was wondering why people wanted to disable the spanning tree
algorithm. Thank you for your example. It's not the algorithm
that's bothering them...it's the preforwarding delay.

It does seem dangerous to turn off the algorithm
completely. However, if you know that
the port does not contain a switch, but rather contains a laptop,
it should be fine to start forwarding immediately. Perhaps
there could be some sort of switch-switch protocol in which switches could
let each other know that they are switches. Of course if that
message got lost, you could still have temporary loops.

Also, I'd think that an alternative to disabling the spanning tree
algorithm would be to set pre-forwarding delay to zero. That way
the algorithm would still break loops if there were any, but
there might be temporary loops if you plugged switches into switches
into switches...

Is it possible to keep spanning tree on but just eliminate the
preforwarding delay (which I just put in because I was paranoid
about loops with no hop count and no limit to how many copies of
a packet could get spawned)? People survive loops today, because
they can be caused by a repeater coming up. It's possible that
the preforwarding delay is not really necessary, and certainly
way too conservatively set as the default.

Radia



From dhcp-v4@bucknell.edu  Fri Oct 30 06:52:25 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id GAA22008
	for <dhc-archive@odin.ietf.org>; Fri, 30 Oct 1998 06:52:25 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id GAA11869;
	Fri, 30 Oct 1998 06:47:44 -0500 (EST)
Date: Fri, 30 Oct 1998 06:47:44 -0500 (EST)
Message-Id: <v03007800b25f4df5bf2b@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Problems with NT and AIX V4.31 DHCP (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


message sent to dhcp-v4@bucknell.edu by SDEAN@POP.ULSTER.NET follows.
---------------------------------------------------------------------
Great Greg...thanks for answering....send commo on this to
sdean@bard.edu....I'm the sysdadm there in a trueblue AIX
shop....something I don't care to advert widely.  My phone is
914-758-7475.  I have bos.net.tcp.client and server at 4.3.1.3; am
downloading 4.3.1.4....anything else.


MUCH thanbks!



>
> I don't know about 1 or 2, but 3 is fixed and will soon be available on the
> fixdist servers.  You can call the 1-800-call-aix number to request a fix.
>
> If you have other questions, we can take this off the DHCP working group
>list.
> I figure the others don't necessarily need this information.
>
> Thanks,
> Greg Althaus
> AIX TCPIP Development and Support.
> galthaus@austin.ibm.com
>
>
> > ---------------------------------------------------------------------
> > 	I have a DHCP server running on an IBM F50 running AIX4.3.1.  It
> > 	appears (tho sometimes, in this kind of situation, it can be
> > 	difficult to distinguish which is cause and which is effect) that:
> > 	  1)  a Windows NT printer server we have is requesting all
> > available
> > 	DHCP addresses on after another.
> > 	  2) The AIX DHCP server stores a client ID that 2-3x longer than
> > the
> > 	one I see for a W85 machines
> > 	  3) When I try to drop some of these address (dadmin -d
> > <clientID>),
> > 	it doesn't drop and, about half the time, it hangs or blows away the
> >
> > 	dhcpsd daemon
> >
> > 	Comments?  ideas for problem determination?
> > 	// Stewart Dean - sdean@ulster.net
> > 	//
> > 	// Machiavelli said (in essence):
> > 	//   Bad mercenaries will lose your country for you,
> > 	//   "good" ones will take it away from you....
> > 	//   Don't use mercenaries
> > 	// Dean's corollary:
> > 	//  Hiring temps or vendor employees may be all the rage...
> > 	//    but they're the same as mercenaries:
> > 	//  You give neither loyalty nor committment;
> > 	//    the favor, if returned, should come as no surprise
> > 	//  Look to your own honor if you expect any from them.
>
>
>
// "I build my cars to go, not to stop", Ettore Bugatti
// Stewart Dean Kingston, NY




From dhcp-v4@bucknell.edu  Fri Oct 30 06:55:54 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id GAA22028
	for <dhc-archive@odin.ietf.org>; Fri, 30 Oct 1998 06:55:54 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id GAA20597;
	Fri, 30 Oct 1998 06:51:55 -0500 (EST)
Date: Fri, 30 Oct 1998 06:51:55 -0500 (EST)
Message-Id: <v03007803b25f4ee6f7de@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: DHCP and spanning tree on switches
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


message sent to dhcp-v4@bucknell.edu by TERRY.GLANCY@CDOTT.COM follows.
-----------------------------------------------------------------------


> -----Original Message-----
> From:	Paul Roberts [SMTP:paul.roberts@intranet-solutions.com]
> Sent:	Thursday, October 29, 1998 7:04 AM
> To:	Multiple recipients of list
> Subject:	DHCP and spanning tree on switches
>
> Hi,
>
> I'm not an expert on switches so I am wondering if anyone can help me (and
> please correct me if I am wrong)...
>
> The way I understand switches work with DHCP, is when the client sends a
> DHCPDISCOVER it takes a while for the switch port to learn the topology of
> the network and it runs the spanning tree alogorithm to make sure there
> are
> no loops. This takes a few seconds during which time the port is blocked.
> The client will send another DHCPDISCOVER, and hopefully the switch port
> has
> now come up, learnt where the client is trying to get to and switches the
> packet across, and everything works fine.
>
> However, I am seeing a situation where laptops moving to a different
> subnet
> are having difficulty obtaining the correct IP address for that subnet.
> What
> I think is happening is that the client broadcasts a DHCPREQUEST (during
> INIT-REBOOT) to try and renew the old IP address. Because the switch port
> is
> blocking for a few seconds while it learns the topology, the DHCPREQUEST
> never makes it to the DHCP server (via an ip-helper on the switch), so the
> client never gets a DHCPNAK. The client then tries to use it's old IP
> address, which of course is invalid now that it has changed subnets.
>
> I have heard that Cisco switch ports can be set to "fast port" mode, which
> disables spanning tree, but isn't disabling spanning tree a bit dangerous?
> In this case there aren't single workstations on each port, but lan
> segments
> (each in a different subnet, so the switch is effectively routing).
	[Glancy, Terry]   Fast port does not disable Spantree, Just reduces
the listen time so the network login and DHCP can function. Not required in
shared segments with concentrators as the port is always active. If you are
not planning on connecting others switch to these ports there is NO danger.
New Cisco hardware such as the 1900 come with the client ports in fast mode
and the up links in learning mode
	We have now turned spanning tree completely off as we have true star
topology with no chance of loops


>  What is the solution in this case? I guess this isn't a problem with
> desktop
> PC's that don't move around and stay on the same port, but I haven't got a
> clue how to get this working for laptops that move around onto different
> ports, other than disabling spanning tree, which I'm not sure is a safe
> thing to do.
>
> Regards,
>
> Paul
>
> +---------------------------------------------+
> |    Paul Roberts, Professional Services,     |
> |     Internet & Intranet Solutions Ltd.      |
> |  Tel: +44 1256 346344 Fax: +44 1256 346355  |
> | E-mail: paul.roberts@intranet-solutions.com |
> |    WWW: http://www.intranet-solutions.com   |
> |      AOL Instant Messenger: PRoberts11      |
> +---------------------------------------------+
>




From dhcp-v4@bucknell.edu  Fri Oct 30 06:58:27 1998
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id GAA22040
	for <dhc-archive@odin.ietf.org>; Fri, 30 Oct 1998 06:58:27 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.8.8/8.8.8) with SMTP id GAA19913;
	Fri, 30 Oct 1998 06:52:15 -0500 (EST)
Date: Fri, 30 Oct 1998 06:52:15 -0500 (EST)
Message-Id: <v03007805b25f4f490f22@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP and spanning tree on switches
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0


message sent to dhcp-v4@bucknell.edu by MELLON@GROSSE.FUGUE.COM follows.
------------------------------------------------------------------------

Spanning tree is most important if there's a possibility of a bridge
loop on your network.   If you don't have a bridge loop, then spanning
tree is still a nice thing, because it reduces congestion, but not
having it is not "dangerous," as long as your network isn't overly
congested.

			       _MelloN_




