From dhcp-v4@bucknell.edu  Mon Feb  1 12:40:34 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA25906
	for <dhc-archive@odin.ietf.org>; Mon, 1 Feb 1999 12:40: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 MAA21448;
	Mon, 1 Feb 1999 12:35:32 -0500 (EST)
Date: Mon, 1 Feb 1999 12:35:32 -0500 (EST)
Message-Id: <000901be4dfe$0f2816b0$8a50fb8d@net-gwaters.corpnorth.baynetworks.com>
Errors-To: droms@bucknell.edu
Reply-To: gww@nortelnetworks.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Glenn Waters" <gww@nortelnetworks.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call on DHCP Options for SLP
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

> > Do you object to the option going forward because you fear a precedent
> > which will allow arbitrarily formatted options to be standardized?  I
> > am certainly not attempting to open the door to that.  I explicitely
> > asked the WG if they thought this particular format would be easy to
> > implement on existing servers; the answer in Orlando was "Yes."
>
> I did say in Orlando that this format is easy to implement, and
> several of the other DHCP server implementors nodded and mmm-hmmed
> sagely.

i concur with this observation.

> The objection previously was with putting bit-fields into an
> option, not with putting more than one data type into the option.
> There's no really special interpretation needed here - just two data
> items of different types, concatenated.
>
> I will admit that this is a bit harder than interpreting a single data
> item, but I really think it's going too far to say that this is adding
> another data type, or arguing that it shouldn't be done because it is
> somehow hard to implement.

i am not saying that this is a new data type or that this is hard to
implement.  i am saying that i would like to implement option handling code
once and that code will be able to handle all options -- existing and new
ones.

there is no good way to keep a implementation up to date with all of the new
options if the only way to configure the option is too add some code.  my
impression was that dhcp supported a number of basic data types in an
option. only one of those data types could appear in a single option; in
scalar or array form.  now, none of the RFCs specifically state that rule,
however all existing options to date observe that rule. also, the dhcp panel
work implies (but does not directly state) that a only single data type in
scalar or array form can be encoded in an option.

since solution are good here is what i propose.

1. let option 79 go through as is.

2. have the dhcp panel define how data is allowed to be packed into an
option.  i want to ship a product that can be extended to support new
options without having to send my customers a new version each time a new
option is defined with a new combination of the basic data types.

> I suppose the counter-proposal would be to have two options, one of
> which contains the boolean and one of which contains the the
> UTF8-encoded name.  Given our determination to motivate ourselves to
> implement wider option codes, I guess this isn't an entirely bad idea,
> but we've been talking about this option for a *long* time.  The
> current proposal is perfectly reasonable and implementable.  Requiring
> Erik to go through yet another revision for the stated reason strikes
> me as being unreasonable.
>
> 			       _MelloN_

/gww



From dhcp-v4@bucknell.edu  Mon Feb  1 12:47:45 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA26343
	for <dhc-archive@odin.ietf.org>; Mon, 1 Feb 1999 12:47:44 -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 MAA14221;
	Mon, 1 Feb 1999 12:43:21 -0500 (EST)
Date: Mon, 1 Feb 1999 12:43:21 -0500 (EST)
Message-Id: <000a01be4dff$025e0d30$8a50fb8d@net-gwaters.corpnorth.baynetworks.com>
Errors-To: droms@bucknell.edu
Reply-To: gww@nortelnetworks.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Glenn Waters" <gww@nortelnetworks.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call on DHCP Options for SLP
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

> Glenn,
>
> I want to make sure I fully understand the context of your consideration.
> I am therefore going to state the nature of things as completely
> as possible
> so that we can figure out what to do.
>
> Currently it looks like there are the following types transmitted:
>
> OPTION #   TYPE USED
> ========   =========
>  0,255      NOTHING (Pad, END)
>  1,2        LEN (4), 4 byte data (Subnet mask, Time offset, ...)
>  3,4,...    LEN (4n), n 4 byte addresses follow (Router, Time Server, ...)
>  12         LEN (n), n restricted ASCII bytes (Hostname)
>  13,26      LEN (2), 2 byte data, unsigned, (Boot File Size,
> Interface MTU)
>  20,27      LEN (1), 0/1 binary value, (Non-Local Source Routing Enable,
>                      All Subnets are Local, ...)
>  21,58      LEN (8n), n times 4 bytes of address then 4 bytes of mask
>                      (Policy Filter Option, Static Route Option
> is similar)
>  22         LEN (1), 1 byte of unsigned data (Default IP Time to live)
>
> draft-ietf-dhc-slp-06.txt includes two options:
>
> Option 78 is of type 3 above:
>
>   +------+-----+------+------+------+------+------+------+------+-----
>   |  78  |  n  |  a1  |  a2  |  a3  |  a4  |  a1  |  a2  |  a3  | ...
>   +------+-----+------+------+------+------+------+------+------+-----
>
> This is therefore OK.  Option 79 is the one you are concerned about.
> It has the form:
>
>   +------+-----+------+------+------+------+------+------+------+-----
>   |  79  |  n  | BOOL |  s1  |  s2  |  s3  |  s4  |  s5  |  s6  |  ...
>   +------+-----+------+------+------+------+------+------+------+-----
>
> BOOL is a 0 or nonzero.  s1-s(n-1) are the bytes of a UTF-8 encoded
> string.  Thus, there are two values encoded.  Further it is possible
> that the value of n will be 1, which is to say the string may be
> omitted from this option.
>
> One question is:  How is this different than options 21 or 58
> which include
> n pairs of 4 byte data.  This includes one pair of boolean and
> string data?

i would claim that both options 21 and 58 include one data type (IP address)
in array form. i.e.: the syntax of the elements are identical, the semantics
are different (address versus a mask).

see my response to ted's last message for a more detailed response and a
proposed solution.

/gww



From dhcp-v4@bucknell.edu  Mon Feb  1 16:03:48 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA03456
	for <dhc-archive@odin.ietf.org>; Mon, 1 Feb 1999 16:03:46 -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 PAA21494;
	Mon, 1 Feb 1999 15:59:03 -0500 (EST)
Date: Mon, 1 Feb 1999 15:59:03 -0500 (EST)
Message-Id: <199902011851.NAA29748@funnel.cisco.com>
Errors-To: droms@bucknell.edu
Reply-To: kkinnear@cisco.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Kim Kinnear <kkinnear@cisco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Last Call on DHCP Options for SLP
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: QUALCOMM Windows Eudora Pro Version 4.0.2 

At 12:39 PM 2/1/99 -0500, Glenn Waters wrote:
[...]
>i am not saying that this is a new data type or that this is hard to
>implement.  i am saying that i would like to implement option handling code
>once and that code will be able to handle all options -- existing and new
>ones.
>
>there is no good way to keep a implementation up to date with all of the new
>options if the only way to configure the option is too add some code.  my
>impression was that dhcp supported a number of basic data types in an
>option. only one of those data types could appear in a single option; in
>scalar or array form.  now, none of the RFCs specifically state that rule,
>however all existing options to date observe that rule. also, the dhcp panel
>work implies (but does not directly state) that a only single data type in
>scalar or array form can be encoded in an option.
>
>since solution are good here is what i propose.
>
>1. let option 79 go through as is.
>
>2. have the dhcp panel define how data is allowed to be packed into an
>option.  i want to ship a product that can be extended to support new
>options without having to send my customers a new version each time a new
>option is defined with a new combination of the basic data types.
>
[...]
>/gww
> 


I strongly concur with Glenn -- thanks Glenn for taking the time
to be so clear on this.  I'll echo Glenn's final comment:

    "I want to ship a product that can be extended to support new
    options without having to send my customers a new version each 
    time a new option is defined with a new combination of the basic
    data types."

Cheers -- Kim


From dhcp-v4@bucknell.edu  Tue Feb  2 07:12:54 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA19163
	for <dhc-archive@odin.ietf.org>; Tue, 2 Feb 1999 07:12: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 HAA23419;
	Tue, 2 Feb 1999 07:10:29 -0500 (EST)
Date: Tue, 2 Feb 1999 07:10:29 -0500 (EST)
Message-Id: <v04011706b2dc939838c2@[134.82.250.4]>
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: Two DHCP servers on a network
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 JAMIE.BOYCE@MISYS.CO.UK follows.
-----

Hello,
my name is Jamie Boyce,  I am an IT Specialist at Misys Plc, and at present
have a few queries with DHCP.  I have installed one DHCP server on our LAN,
and would like to know if it is possible to install a second DHCP server as
a backup.  I have attempted this but when the second DHCP server came online
it gave out replicated IP addresses.  Is there anyway of replicating the
DHCP database.

many thanks


Jamie Boyce



From dhcp-v4@bucknell.edu  Tue Feb  2 07:20:18 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA19191
	for <dhc-archive@odin.ietf.org>; Tue, 2 Feb 1999 07:20:17 -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 HAA17469;
	Tue, 2 Feb 1999 07:16:03 -0500 (EST)
Date: Tue, 2 Feb 1999 07:16:03 -0500 (EST)
Message-Id: <v04011708b2dc94305c7e@[134.82.250.4]>
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: Last Call on DHCP Options for SLP
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.
------------------------------------------------------------------------

> my impression was that dhcp supported a number of basic data types
> in an option. only one of those data types could appear in a single
> option; in scalar or array form.

This is probably a result of my days of hacking on gcc, but I've
always interpreted the spec as saying that any number of data elements
of varying types could be present in an option.  My server code is
written that way - it uses a trivial stack language to parse option
data.  Admittedly, in browsing through my table of options, I don't
see any that take advantage of this, other than options that take
arrays of pairs of IP addresses.

> 1. let option 79 go through as is.

Sounds good.

> 2. have the dhcp panel define how data is allowed to be packed into an
> option.  i want to ship a product that can be extended to support new
> options without having to send my customers a new version each time a new
> option is defined with a new combination of the basic data types.

This also sounds like a good idea, within reason: we shouldn't
restrict the sorts of data types that might be added in the future,
although we may want to explicitly differentiate options that add new
data types from options that do not.   The current draft already
explicitly differentiates options that require protocol changes from
options that do not, so this wouldn't be a surprising change.

			       _MelloN_


From dhcp-v4@bucknell.edu  Tue Feb  2 08:00:48 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA19363
	for <dhc-archive@odin.ietf.org>; Tue, 2 Feb 1999 08:00:48 -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 HAA14188;
	Tue, 2 Feb 1999 07:56:35 -0500 (EST)
Date: Tue, 2 Feb 1999 07:56:35 -0500 (EST)
Message-Id: <014b01be4ea7$15c21b20$969d9fc2@egg.intranet-solutions.com>
Errors-To: droms@bucknell.edu
Reply-To: paul.roberts@intranet-solutions.com
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: Re: Two DHCP servers on a network
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

You could either use DHCP servers that implement the new failover protocol,
but this is currently only an IETF draft so may not be fully implemented on
your chosen server, or you could use a second server with a separate address
range. Traditionally, servers have not been able to communicate lease
binding information with each other so it has not been possible to share
duplicate address ranges. This is what the failover draft attempts to fix.

For now, you will probably have to use a different address range on the
second server.

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   |
+---------------------------------------------+


-----Original Message-----
From: by way of Ralph Droms <dhcp-v4@bucknell.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Date: 02 February 1999 12:17
Subject: Two DHCP servers on a network


>message sent to dhcp-v4@bucknell.edu by JAMIE.BOYCE@MISYS.CO.UK follows.
>-----
>
>Hello,
>my name is Jamie Boyce,  I am an IT Specialist at Misys Plc, and at present
>have a few queries with DHCP.  I have installed one DHCP server on our LAN,
>and would like to know if it is possible to install a second DHCP server as
>a backup.  I have attempted this but when the second DHCP server came
online
>it gave out replicated IP addresses.  Is there anyway of replicating the
>DHCP database.
>
>many thanks
>
>
>Jamie Boyce
>



From dhcp-v4@bucknell.edu  Tue Feb  2 16:04:29 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA04623
	for <dhc-archive@odin.ietf.org>; Tue, 2 Feb 1999 16:04:28 -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 PAA31985;
	Tue, 2 Feb 1999 15:55:17 -0500 (EST)
Date: Tue, 2 Feb 1999 15:55:17 -0500 (EST)
Message-Id: <4.0.2.19990201134649.00e00bb0@funnel>
Errors-To: droms@bucknell.edu
Reply-To: rwoundy@cisco.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Rich Woundy <rwoundy@cisco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Please comment on my draft:  DHCP Option for Call Control
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: QUALCOMM Windows Eudora Pro Version 4.0.2 

Henry,

I am one of many folks that are anticipating deployments of millions of
voice over IP hosts for residential phone service. These hosts are often
called "residential gateways". It does make sense for most of these
residential gateways to obtain call gateway/call agent information from
DHCP. Many of these gateways may be devices such as cable modems that
already obtain configuration from DHCP (other examples of residential
gateways include set-top boxes, xDSL devices, and broadband wireless devices).

While I like the concept of your draft, this draft looks like it supports
"NBX Call Control Servers" only, which I assume is a vendor product. What
protocol(s) do these NBX servers support? I would think that the Internet
community needs support in this realm for more standard VoIP protocols,
such as H.323 and MGCP, as well as other up-and-coming protocols (DOSA?).

While I am not a VoIP expert, I do know that there are several special
configuration considerations for MGCP:

1. The call agents are identified by *domain names*, not by IP addresses.
2. The residential gateway needs a "digit map" that tells it how to collect
the numbers dialed on the phone, before it sends them to the call agent.
3. The residential gateway may support several RJ-11 ports on one IP host.
Each port is identified by an endpoint name, xxx@yyy, which is supposed to
emulate an email address. Each RJ-11 port may get its own call agent and
digit map.

Should we work on this together? Who else is interested?

-- Rich

P.S. More information about MGCP can be found at:

http://search.ietf.org/internet-drafts/draft-huitema-mgcp-v0r1-02.txt
http://search.ietf.org/internet-drafts/draft-huitema-mgcp-flows-00.txt
http://sgcp.bellcore.com

At 05:37 PM 1/26/99 -0500, Henry Houh wrote:
>
>Hi,
>
>I'm new to this process so I don't know the procedure, though I have
>read the info for new IETF folks and other info that I have been able
>to find.  If I have submitted this in an improper fashion or not named
>it correctly, please let me know the correct way to get this in front
>of the working group.
>
>I would like to introduce a draft for a new DHCP option to support
>location of call control servers (like an H.323 gatekeeper).  There
>are many new products available that have stand-alone IP-telephone
>endpoints.  This option would facilitate the setup of these endpoints
>so as to eliminate any configuration necessary for these IP telephones
>to locate their call control servers.
>
>I have tried to do this in a way that allows other vendors with
>products to add to this option, but I would like comments on whether
>the method to add a new sub-option is acceptable - I have tried to
>mirror the method new options are added, and this may be too
>heavyweight a method.  Also, I have not made any assumptions on who
>else would like to use this option.
>
>Comments on the draft are appreciated,
>
>Thanks,
>
>Henry Houh
>NBX Corporation
>
>
>
>
>Internet Engineering Task Force                               Henry Houh
>INTERNET DRAFT                                           NBX Corporation
>                                                           November 1998
>                                                        Expires May 1999
>
>
>               DHCP Options for Call Control Servers
>              <draft-ietf-dhc-callcontrolserv-00.txt>
>
>Status of This Memo
>
>   This document is a submission to the Dynamic Host Configuration
>   Working Group of the Internet Engineering Task Force (IETF). Comments
>   should be submitted to the dhcp-v4@bucknell.edu mailing list.
>
>   Distribution of this memo is unlimited.
>
>   This document is an Internet-Draft.  Internet-Drafts are working
>   documents of the Internet Engineering Task Force (IETF), its areas,
>   and its working groups.  Note that other groups may also distribute
>   working documents as Internet-Drafts.
>
>   Internet-Drafts are draft documents valid for a maximum of six months
>   and may be updated, replaced, or obsoleted by other documents at
>   any time.  It is inappropriate to use Internet-Drafts as reference
>   material or to cite them other than as ``work in progress.''
>
>   To learn the current status of any Internet-Draft, please check
>   the ``1id-abstracts.txt'' listing contained in the Internet-Drafts
>   Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (North
>   Europe), ftp.nis.garr.it (South Europe), munnari.oz.au (Pacific Rim),
>   ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast).
>
>Abstract
>
>   This document defines a new DHCP option for delivering configuration
>   information to telephony enabled hosts in order to locate a call
>   control/signalling server.  The option carries several operational
>   parameters that allow multiple call control vendors to utilize this
>   field.
>
>1. Introduction
>
>   Telephony is emerging as a network-based application.  The Call
>   Control Server option allows telephony or gateway devices which
>   cannot independently setup up and signal calls to automatically
>   discover an address of a call control server.
>
>
>
>
>Houh                        Expires May 1999                    [Page 1]
>
>Internet Draft   DHCP Option for Call Control Servers      November 1998
>
>
>   This specification describes a DHCP option [1] that can carry one or
>   several Call Control Server sub-options.  Each sub-option is
>   treated as a separate potential call control server by the hosts.
>
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
>   document are to be interpreted as described in RFC 2119. [2]
>
>2. Call Control Server Option
>
>   This option specifies one or more fields carrying Call Control
>   Server information.  The fields that can be carried by this option
>   are described in the sections that follow.
>
>   The code for this option is TBD, and its maximum length is 255 octets.
>
>      Code   Len        Sub-Option 1               Sub-Option 2
>     +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+--
>     | TBD |  n  |  a1 |  a2 |  a3 |  a4 |  a1 |  a2 |  a3 |  a4 |  ...
>     +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+--
>
>   The 'Len' field specifies the number of octets containing sub-option
>   information within the DHCP option.
>
>   Each sub-option will contain a code followed by a length that
>   specifies the number of octets containing configuration parameter
>   information within the sub-option.
>
>      Sub    Sub 
>      Code   Len        Configuration Parameter(s)
>     +-----+-----+-----+-----+-----+-----+-----+-----+--
>     |  x  |  n  |  a1 |  a2 |  a3 |  a4 |  a6 |  a7 |  ...
>     +-----+-----+-----+-----+-----+-----+-----+-----+--
>
>2.1. Call Control Servers
>
>   This section describes the vendor-specific sub-options.
>
>   Other types/vendors of call control servers can be added by using 
>   new sub-option fields.  See section 2.2 for the procedure for
>   adding sub-option fields.
>
>2.1.1 NBX Call Control Server Sub-option
>
>   This sub-option specifies the network address of an NBX Call
>   Control Server.
>
>
>
>
>
>Houh                        Expires May 1999                    [Page 2]
>
>Internet Draft   DHCP Option for Call Control Servers      November 1998
>
>
>   The code for this sub-option is 1. The length specified in the 'Len'  
>   field of this sub-option MUST always be 4 octets.
>
>      Code   Len    NBX Server Address
>     +-----+-----+-----+-----+-----+-----+
>     |  1  |  4  |  a1 |  a2 |  a3 |  a4 |
>     +-----+-----+-----+-----+-----+-----+
>
>2.2 Procedure for adding call control server types
>
>   A vendor may add a new sub-option field by issuing an internet
>   draft that contains the new sub-option.  The new sub-option field
>   code MUST be labeled "TBD."  This draft will then be submitted to
>   the DHC working group, and, if accepted for inclusion in the DHCP
>   specification, a sub-option field code is assigned and the
>   sub-option specification is published as an RFC which updates this
>   RFC.
>
>3. Using Multiple Sub-options
>
>   More than one sub-option field MAY be returned to the host.
>   In addition, more than one of any sub-option type MAY be present.
>   This allows the host to select the call control server appropriate
>   to own its signaling protocol, allowing a single DHCP server to
>   support multiple homogeneous call control servers as well as
>   heterogeneous telephony and gateway devices.
>
>4. References
>
>   [1] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
>       Extensions", RFC-2132, March 1997.
>
>   [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
>       Levels", RFC-2119, March 1997.
>
>   [3] Droms, R., "Dynamic Host Configuration Protocol", RFC-2131,
>       March 1997.
>
>5. Security Considerations
>
>   DHCP currently provides no authentication or security mechanisms.
>   Potential exposures to attack are discussed in section 7 of the DHCP
>   protocol specification [3]. In particular, these DHCP options allow
>   an unauthorized DHCP server to misdirect a telephone or gateway
>   host to an unauthorized call control server.
>
>
>
>
>
>
>Houh                        Expires May 1999                    [Page 3]
>
>Internet Draft   DHCP Option for Call Control Servers      November 1998
>
>
>6. Author's Address
>
>   Henry Houh   
>   NBX Corporation
>   100 Brickstone Square
>   Andover, MA  01810
>
>   Phone: +1 978 740 0000 x257
>
>   EMail: hhouh@nbxcorp.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Houh                        Expires May 1999                    [Page 4]
> 






From dhcp-v4@bucknell.edu  Tue Feb  2 18:45:55 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA08711
	for <dhc-archive@odin.ietf.org>; Tue, 2 Feb 1999 18:45: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 SAA03137;
	Tue, 2 Feb 1999 18:41:29 -0500 (EST)
Date: Tue, 2 Feb 1999 18:41:29 -0500 (EST)
Message-Id: <199902022257.RAA29855@wasabi.lcs.mit.edu>
Errors-To: droms@bucknell.edu
Reply-To: hhh@wasabi.lcs.mit.edu
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Henry Houh <hhh@wasabi.lcs.mit.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCP Option for Call Control Servers
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


Rich Woundy <rwoundy@cisco.com> writes:

>  These hosts are often called "residential gateways". It does make
>  sense for most of these residential gateways to obtain call
>  gateway/call agent information from DHCP. Many of these gateways
>  may be devices such as cable modems that already obtain
>  configuration from DHCP (other examples of residential gateways
>  include set-top boxes, xDSL devices, and broadband wireless
>  devices).

>  While I like the concept of your draft, this draft looks like it
>  supports "NBX Call Control Servers" only, which I assume is a
>  vendor product. What protocol(s) do these NBX servers support? I
>  would think that the Internet community needs support in this realm
>  for more standard VoIP protocols, such as H.323 and MGCP, as well
>  as other up-and-coming protocols (DOSA?).

Yes, the sub-option in the draft is for a specific vendor.  NBX (my
company) has a proprietary signaling protocol.  I really would like to
include other protocols as more sub-fields, but I don't know what else
to put in.  That's also why I tried to add a section on adding new
sub-option fields.

Someone on DHC mentioned using vendor OUIs to identify who owns a
sub-option field for another option.  That might be a good thing to do
here, if we also define specific OUIs that represent standard
protocols.

>  While I am not a VoIP expert, I do know that there are several special
>  configuration considerations for MGCP:

>  1. The call agents are identified by *domain names*, not by IP addresses.

Yes, in MGCP, the call agents are identified by their domain names for
improved reliability.  From perspective of Call Agents locating other
Call Agents, it's surely better this way, but that doesn't mean that
we must pass domain names of the Call Agent in DHCP options during the
boot-up process of a gateway.

I believe that from the boot-up perspective of a gateway, it's better
to use the network address.  This network address is controlled by the
administrator of the DHCP server serving the gateway, same as all
other server addresses that may be returned as a DHCP option.  Plus,
not all gateway devices will be capable of performing DNS queries at
boot-up time - or at all ever (maybe the MGC does this for you in some
systems to lower the gateway costs).

I tried to follow the standard options as closely as possible.  In all
the server type options listed in RFC 2132, the servers are identified
by IP addresses, for the reason above, I believe (someone interject if
they know the history).

>  Should we work on this together? Who else is interested?

Sounds good to me, anyone else interested?

>  -- Rich

>  P.S. More information about MGCP can be found at:

>  http://search.ietf.org/internet-drafts/draft-huitema-mgcp-v0r1-02.txt
>  http://search.ietf.org/internet-drafts/draft-huitema-mgcp-flows-00.txt
>  http://sgcp.bellcore.com

Wen-Ping Ying <wying@att.com> also responded:

>  Digitmaps are passed as part of the MGCP protocol
>  (EndpointConfiguration) and should not require DHCP
>  provisioning. Call Agents (MGC) and Gateway names are stored as
>  part of the DNS and may not need DHCP provisioning either. I don't
>  think MGCP provides a mechanism to allow a gateway to report to the
>  Call Agent/MGC the resources it manages. With this, there may be a
>  registration process required before an MGC can manage and control
>  the calls to/from the residential gateways.

I'm somewhat familiar with MGCP/SGCP and have been following megaco,
but I'm missing the part where the gateway "boots up" and figures out
which Media Gateway Controller to bind to.  I think that's why this is
necessary.  

Say your cable company comes in and installs a new cable box that your
phone plugs into.  You turn your cable box on, and maybe it already
uses DHCP to get an IP address, so we also add the call control server
option to get a MGC IP address as well.  

I'm not sure how gateway names being stored in the DNS helps the MGC
find the cable box residential gateway when it's turned on.  Shouldn't
it be up the the cable box to register with the MGC as opposed to the
MGC polling every device in a DNS domain?  You turn on the cable box,
it gets the MGC IP address via DHCP (no DNS indirection necessary
here), it notifies the MGC it has just been turned on, and then the
MGC sends it configuration information, including its own domain name,
digit collection string and such.

Comments?

Henry


From dhcp-v4@bucknell.edu  Thu Feb  4 07:15:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA25742
	for <dhc-archive@odin.ietf.org>; Thu, 4 Feb 1999 07:15:12 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA18343;
	Thu, 4 Feb 1999 07:11:31 -0500 (EST)
Date: Thu, 4 Feb 1999 07:11:31 -0500 (EST)
Message-Id: <v04011708b2df388aab98@[134.82.250.4]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: JDHCP1.0.1 released
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

Jay Goldsmith (jgoldsch@bucknell.edu) has released JDHCP1.0.1 at
http://www.eg.bucknell.edu/~jgoldsch/dhcp  From the intro page:

 "Welcome to the JDHCP Project homepage. The goal of JDHCP is to add Dynamic
  Host Configuration Protocal (as specified in RFC 2131) handling to Java(tm).
  We have created a set of APIs for sending, receiving and representing DHCP
  Messages in Java(tm). This API will allow programmers to easily write DHCP
  clients, servers and applications."

For details on changes in this release, check out
http://www.eg.bucknell.edu/~jgoldsch/dhcp/download/CHANGELOG

- Ralph


From dhcp-v4@bucknell.edu  Thu Feb  4 11:25:56 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA28932
	for <dhc-archive@odin.ietf.org>; Thu, 4 Feb 1999 11:25:52 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id LAA09182;
	Thu, 4 Feb 1999 11:16:47 -0500 (EST)
Date: Thu, 4 Feb 1999 11:16:47 -0500 (EST)
Message-Id: <v04011723b2df51347711@[134.82.250.4]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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 Auto-Configure Option Draft
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

Having seen no response to Ryan's message, I will issue a last call for the
current version of "DHCP Option to Disable Stateless Auto-Configuration in
IPv4 Clients" <draft-ietf-dhc-autoconfig-03.txt> today...

- Ralph

=====

At 4:10 PM -0500 1/26/99, Ralph Droms wrote:
>At 9:21 PM -0500 1/24/99, Ryan Troll wrote:
>>I've submitted a new version of this draft to the archive.  This version
>>contains all of the requested changes per the IESG last call.  The only
>>outstanding issue I know of is Mike Carney's comment of 12/17/98:
>>
>>
>>	- Using DHCPOFFERs w/ a yiaddr of 0.0.0.0 violates RFC2131. Rather than
>>	  overloading a DHCPOFFER, why not define a new message type?
>>
>>
>>I know that what I'm suggesting is basicly a hack to get this
>>functionality into the existing protocol, with no major changes.  A new
>>option would be another way to go.  I can't say which would be better, if
>>there is a better way.
>>
>>What do the rest of you think?
>
>I would like to get this draft to last call in time for the IESG to
>consider it prior to the next IETF.  That means it should go to last call
>no later than early next week.  If you have any comments on Ryan's issue,
>please respond to the mailing list before this coming Friday, 1/29.
>
>- Ralph



From dhcp-v4@bucknell.edu  Thu Feb  4 11:34:34 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA29503
	for <dhc-archive@odin.ietf.org>; Thu, 4 Feb 1999 11:34:34 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id LAA04866;
	Thu, 4 Feb 1999 11:25:54 -0500 (EST)
Date: Thu, 4 Feb 1999 11:25:54 -0500 (EST)
Message-Id: <v04011724b2df53aa0afc@[134.82.250.4]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Last Call on DHCP Options for SLP
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 comments on "DHCP Option to Disable Stateless
Auto-Configuration in IPv4 Clients" <draft-ietf-dhc-autoconfig-03.txt>.
Please respond to the dhcp-v4@bucknell.edu mailing list with comments by
2/10/99.  If there are no comments, the draft will be submitted for
acceptance as a Proposed Standard.

- Ralph Droms


From dhcp-v4@bucknell.edu  Thu Feb  4 14:16:35 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA08946
	for <dhc-archive@odin.ietf.org>; Thu, 4 Feb 1999 14:16:35 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id OAA20316;
	Thu, 4 Feb 1999 14:10:22 -0500 (EST)
Date: Thu, 4 Feb 1999 14:10:22 -0500 (EST)
Message-Id: <v04011703b2df7c65d22d@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: 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 message is a resend of the previous "last call" with the correct
Subject: line. - RD)

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

- Ralph Droms


From dhcp-v4@bucknell.edu  Tue Feb  9 03:58:47 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA17382
	for <dhc-archive@odin.ietf.org>; Tue, 9 Feb 1999 03:58:47 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id DAA27245;
	Tue, 9 Feb 1999 03:52:40 -0500 (EST)
Date: Tue, 9 Feb 1999 03:52:40 -0500 (EST)
Message-Id: <Roam.SIMC.2.0.6.918547436.14394.erikg@sun-ffm.germany>
Errors-To: droms@bucknell.edu
Reply-To: Erik.Guttman@Germany.Sun.COM
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Erik Guttman <Erik.Guttman@Germany.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: New SLP DHC Option draft and discussion
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: MULTIPART/MIXED; BOUNDARY="-LA_F2155733230R-1A-918547505=:306NCE.IlHAFeR"
Mime-Version: 1.0

---LA_F2155733230R-1A-918547505=:306NCE.IlHAFeR
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII


A DHC WG last call recently concluded for draft-ietf-dhc-slp-06.txt.
During that last call period there was an issue raised concerning
prior deployment of draft-ietf-dhc-slp-03.txt.  This presented a
backward compatibility problem for a very large installed base of
Netware customers.

I have included a proposed internet draft which addresses these 
concerns.  I ask that you all (especially those of you at Novell)
look at it and decide if you think it:

 (a) solves the problem.
 (b) is an acceptable specification.

The changes made from draft 06 to draft 07 are the following:

  1. A 'MANDATORY' flag has been added to Option 78 exactly in
     the same position as in Option 79.  

  2. This flag, if set to 1, disables active and passive multicast
     directory agent discovery on agents which are so configured.

  3. This flag MUST NOT be set to a byte value such that the
     high order bit (0x80) is set, for backward compatibility.

  4. The Length field of Option 79 is now 1 plus 4 per address
     not simply 4 per address following.

The reasons for this change are:

  1. In draft-ietf-dhc-slp-03.txt the format of the option was:

                         1   1   1   1   1   2   2   2   2   2   3   
     0   2   4   6   8   0   2   4   6   8   0   2   4   6   8   0
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- -   -   
 |78 (SLP DA opt)|      LEN      |d f m s  FLAGS |     DA Len    | DA 
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- -   -   

     In every case, the 'd' flag was set.  As long as this flag is
     never set, the old clients will never accept the option with 
     the new format.

  2. This draft allowed the 'm' bit to be set, which disabled passive
     and active DA discovery.   Administrators found this to be a 
     very useful feature. 

Thus, the solution I propose satisfies both backward compatibility 
and adds a useful feature.  The use of the 'MANDATORY' byte is 
consistent in both option 78 and 79 so it should not be onerous
as far as adding new code.

I hope you agree that this is a reasonable proposal.

Erik Guttman

     

---LA_F2155733230R-1A-918547505=:306NCE.IlHAFeR
Content-Type: TEXT/plain; name="draft-ietf-dhc-slp-07.txt"; charset=us-ascii
Content-Description: default


Internet Engineering Task Force                               C. Perkins
INTERNET DRAFT                                                E. Guttman
                                                        Sun Microsystems
                                                       10 February  1999


               DHCP Options for Service Location Protocol
                       draft-ietf-dhc-slp-07.txt


Status of This Memo

   This document is a submission by the Dynamic Host Configuration
   Working Group of the Internet Engineering Task Force (IETF).
   Comments should be submitted to the dhcp-v4@bucknell.edu mailing
   list.

   Distribution of this memo is unlimited.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at
   any time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


Abstract

   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.









Perkins, Guttman             Expires 10 August 1999             [Page i]

Internet Draft    DHCP Options for Service Location    10 February  1999


1. Introduction

   The Dynamic Host Configuration Protocol [2] provides a framework
   for passing configuration information to hosts on a TCP/IP network.
   Entities using the Service Location Protocol, Version 2 [3] and
   Service Location Protocol, Version 1 [4] need to obtain the address
   of Directory Agents and Scope configuration.  The Service Location
   Protocol (SLP) provides a default configuration for Scopes and
   Directory Agents may be discovered using multicast or broadcast.  It
   is useful in a larger deployment to be able to configure SLP Agents
   using DHCP, so as to centralize the administration and to deploy SLP
   in networks where multicast routing is not available.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [1].


2. Introduction

   The DHCP options described below are used to configure Agents using
   the Service Location Protocol, Version 2 [3] and Version 1 [4].

   The SLP Directory Agent option is used to configure User Agents and
   Service Agents with the location of Directory Agents in the network.

   The SLP Scope Option takes precedence over both default and static
   scope configuration of SLP agents.


3. SLP Directory Agent Option

   This option specifies the location of one or more SLP Directory
   Agents.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Code = 78   |    Length     |   MANDATORY   |      a1       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      a2       |       a3      |       a4      |      ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The SLP Directory Agent Option specifies a list of IP addresses
   for Directory Agents.  Directory Agents MUST be listed in order of
   preference, if there is an order of preference.

   The Length value must include one for the 'MANDATORY' byte and
   include four for each Directory Agent address which follows.  Thus,



Perkins, Guttman             Expires 10 August 1999             [Page 1]

Internet Draft    DHCP Options for Service Location    10 February  1999


   the Length minus one of the option MUST always be divisible by 4 and
   has a minimum value of 5.

   The address of the Directory Agent is given in network byte order.

   The 'MANDATORY' flag in the Directory Agent option may be set to
   either 0 or 1.  If it is set to 1, the SLP User Agent or Service
   Agent so configured MUST NOT employ either active or passive
   multicast discovery of Directory Agents.

   Note that for backward compatibility with some deployed software the
   MANDATORY flag MUST NOT be set to any byte value for which the high
   order bit (0x80) is set.

   The Directory Agents listed in this option MUST be configured with
   the a non-empty subset of the scope list that the Agent receiving the
   Directory Agent Option is configured with.  See the notes below.

   The SLPv2 specification [3] defines how to use this option.


4. SLP Service Scope Option

   The scope list is a comma delimited list which indicates the scopes
   that a SLP Agent is configured to use.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Code = 79   |     Length    |   MANDATORY   | <Scope List>...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The Length indicates the number of bytes which follow.  Since the
   Scope-List String is encoded using UTF-8 [5] characters, it may be
   the cast that the Length is not the same as the number of characters
   in the Scope-List String.  The Length value must include one for the
   'MANDATORY' byte.

   The 'MANDATORY' byte determines whether SLP Agents override their
   static configuration for scopes with the <Scope List> string
   provided by the option.  This allows DHCP administrators to
   implement a policy of assigning a set of scopes to Agents for service
   provision.  If the MANDATORY byte is 0, static configuration takes
   precedence over the DHCP provided scope list.  If the MANDATORY byte
   is 1, the <Scope List> provided in this option MUST be used by the
   SLP Agent.

   The Scope List String syntax and usage are defined in the SLPv2
   specification [3].



Perkins, Guttman             Expires 10 August 1999             [Page 2]

Internet Draft    DHCP Options for Service Location    10 February  1999


4.1. Zero Length Scope-List String Configuration

   A SLP Service Scope Option which indicates a Length of 1 (in other
   words, omitting the <Scope List> string entirely) validly configures
   the SLP User Agent to use "User Selectable Scopes."

   The SLP Agent will use the aggregated list of scopes of all known
   DAs.  If no DAs are known, the UA will use SA discovery to determine
   the list of scopes on the network, as defined in  [3].

   Note that this configuration is tantamount to removing all
   centralized control of the scope configuration of hosts on the
   network.  This makes it possible for every User Agent to see every
   service.  This may not be desirable as users may not be able to or
   desire to decide which services are appropriate for them.


5. Security Considerations

   If a malicious host is able to insert fraudulent information in
   DHCPOFFER packets sent to a prospective SLP Agent then the SLP Agent
   will be unable to obtain service, or may unwittingly be directed to
   use the incorrect services.

   Many opportunities for denial of service exist.  A service agent
   could find that it might rely on fraudulent or otherwise malicious
   directory agents to advertise its services.  DHCPOFFERs could prevent
   the regular SLP framework from functioning by directing clients to
   not use multicast, to use nonexistent directory agents and so on.

   These difficulties are inherited from the much larger and more
   serious problem, viz.  securing or authenticating any information
   whatsoever from a DHCP server (or client!)  is not possible in common
   DHCP deployments.


















Perkins, Guttman             Expires 10 August 1999             [Page 3]

Internet Draft    DHCP Options for Service Location    10 February  1999


6. Full Copyright Statement

   Copyright (C) The Internet Society (1997).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph
   are included on all such copies and derivative works.  However,
   this document itself may not be modified in any way, such as by
   removing the copyright notice or references to the Internet Society
   or other Internet organizations, except as needed for the purpose
   of developing Internet standards in which case the procedures
   for copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."


References

   [1] S. Bradner.  Key words for use in RFCs to Indicate Requirement
       Levels.  RFC 2119, March 1997.

   [2] R. Droms.  Dynamic Host Configuration Protocol.  RFC 2131, March
       1997.

   [3] E. Guttman, C. Perkins, J. Veizades, and M. Day.  Service
       Location Protocol version 2.  draft-ietf-svrloc-protocol-v2-12.txt,
       February 1999.  (work in progress).

   [4] J. Veizades, E. Guttman, C. Perkins, and S. Kaplan.  Service
       Location Protocol.  RFC 2165, July 1997.

   [5] F. Yergeau.  UTF-8, a transformation format of unicode and ISO
       10646.  RFC 2279, October 1998.






Perkins, Guttman             Expires 10 August 1999             [Page 4]

Internet Draft    DHCP Options for Service Location    10 February  1999


Author's Address

   Questions about this memo can be directed to:

  Charles E. Perkins                       Erik Guttman
  Technology Development Group             Technology Development Group
  Mail Stop MPK15-214                      Mail Stop UFRA02
  Sun Microsystems, Inc.                   Sun Microsystems, Inc.
  15 Network Circle                        Bahnstr. 2
  Menlo Park, CA  94025                    74915 Waibstadt, Germany
  phone: +1 650-786-6464            phone: +49 7263 911 701
  fax:   +1 650-786-6445               or:  +1 650 786 5992
  email: Charles.Perkins@Sun.Com           Erik.Guttman@Sun.Com
  Web: http://www.svrloc.org/~charliep






































Perkins, Guttman             Expires 10 August 1999             [Page 5]

---LA_F2155733230R-1A-918547505=:306NCE.IlHAFeR--


From dhcp-v4@bucknell.edu  Wed Feb 10 11:03:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA16513
	for <dhc-archive@odin.ietf.org>; Wed, 10 Feb 1999 11:02:56 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id KAA23391;
	Wed, 10 Feb 1999 10:54:57 -0500 (EST)
Date: Wed, 10 Feb 1999 10:54:57 -0500 (EST)
Message-Id: <Roam.SIMC.2.0.6.918636852.11259.erikg@sun-ffm.germany>
Errors-To: droms@bucknell.edu
Reply-To: Erik.Guttman@Germany.Sun.COM
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Erik Guttman <Erik.Guttman@Germany.Sun.COM>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: New SLP DHC Option draft and discussion 
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

> 
> Yup, that looks good to me, except that I'd capitalize Mandatory
> rather than putting it in ALL CAPS.   :')   When you put it in all
> caps, it tends to say to me that the field is mandatory, rather than
> that the field name is "mandatory", which is mildly confusing.
> 
> 			       _MelloN_

I'll change it to Mandatory.  

Thanks.

Erik



From dhcp-v4@bucknell.edu  Wed Feb 10 17:06:41 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA24374
	for <dhc-archive@odin.ietf.org>; Wed, 10 Feb 1999 17:06:39 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id QAA15585;
	Wed, 10 Feb 1999 16:57:28 -0500 (EST)
Date: Wed, 10 Feb 1999 16:57:28 -0500 (EST)
Message-Id: <v04011707b2e79192e6f7@[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: New SLP DHC Option draft and discussion
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 JLERWIN@NOVELL.COM follows.
-------------------------------------------------------------------
Erik,

We at Novell have looked at your proposed draft 7 of the SLP DHCP options
78 and 79 (draft-ietf-dhc-slp-07.txt).  Our consensus is that it will
provide what we need.  We can distinguish between this format and the draft
3 format which is implemented in some of our products.

So go for it!  And thanks for addressing our concerns.

--Jim Erwin  <JLErwin@Novell.com>


From dhcp-v4@bucknell.edu  Wed Feb 10 17:14:32 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA24646
	for <dhc-archive@odin.ietf.org>; Wed, 10 Feb 1999 17:14:30 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id RAA15403;
	Wed, 10 Feb 1999 17:00:43 -0500 (EST)
Date: Wed, 10 Feb 1999 17:00:43 -0500 (EST)
Message-Id: <v04011709b2e792370da2@[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: New SLP DHC Option draft and discussion
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.
------------------------------------------------------------------------

Yup, that looks good to me, except that I'd capitalize Mandatory
rather than putting it in ALL CAPS.   :')   When you put it in all
caps, it tends to say to me that the field is mandatory, rather than
that the field name is "mandatory", which is mildly confusing.

			       _MelloN_


From dhcp-v4@bucknell.edu  Fri Feb 12 03:22:40 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id DAA06627
	for <dhc-archive@odin.ietf.org>; Fri, 12 Feb 1999 03:22:40 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id DAA03294;
	Fri, 12 Feb 1999 03:17:52 -0500 (EST)
Date: Fri, 12 Feb 1999 03:17:52 -0500 (EST)
Message-Id: <3.0.2.32.19990212084824.013c5500@dokka.maxware.no>
Errors-To: droms@bucknell.edu
Reply-To: Harald@Alvestrand.no
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: My worries about the DHCP Relay Agent Information Option
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: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)

I have reviewed the "DHCP Relay Agent Information Option", and must
admit that I do not like it.

My worries are not so much about the Relay Agent Information Option
itself (although specifying Yet Another Option Without Security is
kind of worrisome), but about the deployment model for Internet service
suggested and faciliated by this memo.

The distinguishing characteristics of this scenario are:

- The DHCP client and the DHCP server are controlled by different
  organizations, who do not necessarily trust each other fully.
  The client is at a "customer", the server is at an "ISP".
- More than one host at the customer site, interconnected by LAN
- Connectivity device ("modem") directly connected to the customer LAN
- Several customers on one Logical IP Subnet managed by the ISP.
- IP address assignment done at ISP central office.

The connection technologies suggested include (from 3.3):

- Dial-up
- ATM
- Cable (presumably CATV networks)
- Frame Relay (3.1)
- X.25

There are two worrisome aspects of this; one is a cost/reliability one,
and the other one is in security; the security is more important.

Cost/reliability first:

- When using dial-up, the customer MUST make a telephone call to boot
  his PC before accessing another device, such as a net-connected printer.
  If the remote server is busy, telephone service is out of order, or
  anything else is broken, his LAN will not work.

I already know people who hate their Windows boxes because they incur
a call setup charge from their autodial router when they boot - the
Windows box does some interesting DNS queries at boot.
The scheme suggested here would make that call required.
(Local call setup charges in Norway are around USD 0.07)

I would think that it's appropriate to add something like this:

  "Reliability concerns dictate that this scenario should ONLY be used
  when the CO connection is expected to be available 100% of the time.
  It is NOT appropriate for use with analog modem connections, and MAY
  be inapplicable to ISDN and switched ATM".

Now to the security issue.

- Since several customers share the same Logical IP Subnet, a naive
  implementation will let them SEE EACH OTHERS' BROADCAST PACKETS.

  This means that if any of them
  use (for instance) the filesystem export facilities in Windows 98 with
  permissions appropriate for in-house use, all other customers on the same
  LIS will get enough information to access those devices.

- Since several customers share the same logical subnet, it seems logical
  that they see each others' DHCP requests. It is then trivial to spoof
  a reply in such a way that "interesting" services can be redirected through
  another customer's site, leading to "interesting" cases of man-in-the-middle
  attacks.

- If the "obvious" filter rules for disallowing packets between customers
  are applied, one may easily get the silly state where you are able to
  contact any Internet site in the whole world, EXCEPT your neighbour's
  house.
  (Don't laugh - I know ISPs who have done exactly that in other contexts!)

I would prefer to see this document revised to have a rather draconian
security section, saying something like:

- This deployment scenario MUST have appropriate inter-customer firewalls.
  The firewalls erected MUST ensure that two customers sharing a LIS
  cannot see each others' broadcast packets by default, yet are able
  to communicate no worse than the connection to other parts of the
  Internet.

- Note that the scheme gives absolutely no protection against all the
  normal attacks that can be launched against a DHCP client.
  Since the area the DHCP request/response crosses is larger, and includes
  more than one trust environment, care must be taken to ensure that
  it's reasonably hard for a customer to launch denial-of-service or
  security attacks against other customers of the same service.

What do people think?

                  Harald A


-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@maxware.no



From dhcp-v4@bucknell.edu  Fri Feb 12 14:46:09 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA14223
	for <dhc-archive@odin.ietf.org>; Fri, 12 Feb 1999 14:46:07 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id OAA27667;
	Fri, 12 Feb 1999 14:38:23 -0500 (EST)
Date: Fri, 12 Feb 1999 14:38:23 -0500 (EST)
Message-Id: <Roam.SIMC.2.0.6.918840147.19736.mwc@atlantic.east.sun.com.>
Errors-To: droms@bucknell.edu
Reply-To: Michael.Carney@East.Sun.COM
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: Reminder: DHCPv4 interoperability testing at Connectathon '99
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 folks,

	RE: Connectathon '99, www.connectathon.org

	We've got a number of people signed up for DHCP testing; some which
	haven't made it "official".

	DHCP testing will be taking place 3/8-3/10. (monday-wednesday)
	The hotel room block with the reduced rate expires on 2/17, so be sure
	to make your reservations. If you haven't registered, please do so
	as soon as possible so that we get an appropriate booth count and can
	organize things such that the DHCP participant booths are adjacent to
	one another.

	See you in March.


Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.
Mailstop UBUR02-212
One Network Drive
Burlington, MA 01803




From dhcp-v4@bucknell.edu  Wed Feb 17 13:52:41 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA08536
	for <dhc-archive@odin.ietf.org>; Wed, 17 Feb 1999 13:52:39 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id NAA31648;
	Wed, 17 Feb 1999 13:43:34 -0500 (EST)
Date: Wed, 17 Feb 1999 13:43:34 -0500 (EST)
Message-Id: <Roam.SIMC.2.0.6.919276110.10093.mwc@atlantic.east.sun.com.>
Errors-To: droms@bucknell.edu
Reply-To: Michael.Carney@East.Sun.COM
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: Apple / MacOS - short packets
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 folks,
	Some Apple versions generate DHCP packets that are less than the
BOOTP frame size of 300 bytes, whereas others don't. Is there version of
MacOS or patch that is available for this problem?

TIA,


Mike Carney
SNT Internet Engineering
Sun Microsystems, Inc.
Mailstop UBUR02-212
One Network Drive
Burlington, MA 01803




From dhcp-v4@bucknell.edu  Thu Feb 18 07:13:14 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id HAA27688
	for <dhc-archive@odin.ietf.org>; Thu, 18 Feb 1999 07:13:12 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA08755;
	Thu, 18 Feb 1999 07:05:20 -0500 (EST)
Date: Thu, 18 Feb 1999 07:05:20 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9902180702500.10077-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Re: Coding Clients and Servers (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 netbook@bucknell.edu by AMD0978@ACF2.NYU.EDU follows.
---------------------------------------------------------------------
Yes, it's a whopper.  But it's also a great debugging too, and
something that's very worthwhile to get to know closely.

Adam

On Wed, 17 Feb 1999, Ralph E. Droms wrote:

>Adam,
>
> >> >   If you want to find out which ports are currently used on the local
> >> >computer, the answer is 'no'.
> >> There is a utility, lsof, that lets you see this information.  One of
> >> the options retrieves a listing of all open ports.
>
>   Thanks for pointing that out.  You might also mention that lsof (list
>open files) is a UNIX program, and that the manual page is over 2500 lines
>long!
>
>Cheers,
>Doug
>
>




From dhcp-v4@bucknell.edu  Thu Feb 18 16:46:06 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA19114
	for <dhc-archive@odin.ietf.org>; Thu, 18 Feb 1999 16:46:04 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id QAA25568;
	Thu, 18 Feb 1999 16:35:53 -0500 (EST)
Date: Thu, 18 Feb 1999 16:35:53 -0500 (EST)
Message-Id: <v04011707b2f21a716397@[134.82.250.4]>
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-07.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 Options for Service Location Protocol
	Author(s)	: C. Perkins, E. Guttman
	Filename	: draft-ietf-dhc-slp-07.txt
	Pages		: 5
	Date		: 17-Feb-99

   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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-slp-07.txt

Internet-Drafts are also 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-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-slp-07.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-slp-07.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-slp-07.txt>


From dhcp-v4@bucknell.edu  Thu Feb 18 16:55:41 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA19889
	for <dhc-archive@odin.ietf.org>; Thu, 18 Feb 1999 16:55:39 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id QAA15457;
	Thu, 18 Feb 1999 16:47:49 -0500 (EST)
Date: Thu, 18 Feb 1999 16:47:49 -0500 (EST)
Message-Id: <3.0.32.19990218145220.006e4eec@ajax>
Errors-To: droms@bucknell.edu
Reply-To: lazear@mitre.org
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Walt Lazear <lazear@mitre.org>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Win98 DHCP servers?????
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: Windows Eudora Pro Version 3.0 (32)

Does anyone know of a free or shareware DHCP server that
runs under Win98?  I've got a project desperate for one.
Thanks in advance for any tips.

	Walt




From dhcp-v4@bucknell.edu  Thu Feb 18 21:07:31 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA02149
	for <dhc-archive@odin.ietf.org>; Thu, 18 Feb 1999 21:07:30 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id VAA12062;
	Thu, 18 Feb 1999 21:01:38 -0500 (EST)
Date: Thu, 18 Feb 1999 21:01:38 -0500 (EST)
Message-Id: <199902190143.TAA03724@bokassa.tele.com>
Errors-To: droms@bucknell.edu
Reply-To: julian@bokassa.tele.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Julian Macassey <julian@bokassa.tele.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Win98 DHCP servers?????
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Mail User's Shell (7.2.6 beta(1) 2/28/96)

On Feb 18 at 16:47, lazear@mitre.org Walt Lazear writes:
> Does anyone know of a free or shareware DHCP server that
> runs under Win98?  I've got a project desperate for one.
> Thanks in advance for any tips.

	Here's a tip:

	Take a beaten up '486 with say 8 med of RAM. Load Linux
and have a DHCP server that never crashes.

	Then you can keep everyone happy with Windows 98 while in
a closet sits a an abandoned piece of hardware keeping it all
running.



-- 
In fact, I pity anybody who has Julian for a friend.  "Dragon" 
<skennedy@byelectric.com>


From dhcp-v4@bucknell.edu  Thu Feb 18 21:49:33 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA02663
	for <dhc-archive@odin.ietf.org>; Thu, 18 Feb 1999 21:49:32 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id VAA21713;
	Thu, 18 Feb 1999 21:42:37 -0500 (EST)
Date: Thu, 18 Feb 1999 21:42:37 -0500 (EST)
Message-Id: <36CCCB90.C6035412@lmms.lmco.com>
Errors-To: droms@bucknell.edu
Reply-To: paul@lmms.lmco.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Paul Gademsky <paul@lmms.lmco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: UNIX DHCP Client ?
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=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
X-Mailer: Mozilla 4.5 (Macintosh; U; PPC)
Mime-Version: 1.0


Has anyone put together a matrix of which UNIX clients support DHCP
(either directly with vendor software or ISC dhcp client) based on OS
revisions?  I'm also interested in which if any will support DDNS from a

client standpoint (succesfully passing a host name field with the DHCP
request, and getting the correct info back from the DHCP server that is
running with DDNS).

Main platforms of interest are Sun (SunOS and Solaris), SGI (IRIX), HP
(HPUX 9.x and up)

Information that I've gathered so far is listed below.

Sun Solaris 2.5.1 and below, no bundled client, 2.6 and above, bundled
client

HPUX 10.01 and below, no bundled client, 10.10 server only, 10.20 and
up, bundled client

SGI 5.2 and below, unknow, 5.3 and up (separate package called
Proclaim).

I know ISC has made clients that cover these platforms, but not sure
what OS versions have been tested/used, and what success people have
had.

Any more details would be very usefull.

Paul Gademsky
DHCP Project Manager
Lockheed Martin/EIS
paul@lmms.lmco.com, (408) 756-1661



From dhcp-v4@bucknell.edu  Fri Feb 19 05:16:08 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.8.5/8.8.7a) with ESMTP id FAA14731
	for <dhc-archive@odin.ietf.org>; Fri, 19 Feb 1999 05:16:07 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id FAA19821;
	Fri, 19 Feb 1999 05:10:53 -0500 (EST)
Date: Fri, 19 Feb 1999 05:10:53 -0500 (EST)
Message-Id: <36CDF468@msgate.future.futsoft.com>
Errors-To: droms@bucknell.edu
Reply-To: harshavj@future.futsoft.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: harshavj <harshavj@future.futsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: RFC 2131 clarification (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Mail V3.0


Hi shashi,

There is a criteria for bootp relay agents to give higher priority to the   
pkts which have higher 'sec's value; assuming that they were waiting for   
a long time. But I hope there is no mapping and data maintained by relay   
agents which contained mapping of secs and some client info (xids/Client   
ID) to a particular server/s. I have not used such a mapping for our   
inhouse Dhcp Relay agent after confirming that this was not needed. I   
have raised a similar question before dealing this issue on this list   
sometime back.
I would appreciate if some one point out that this is required.

You can go through RFC 1542 which gives some clarifications on these   
issues. But Ted says this RFC is absolate. I am not sure whether this   
behaviour was retained in the latest RFC. Here is a draft which addresses   
some of your needs.

http://search.ietf.org/internet-drafts/draft-ietf-dhc-agent-options-04.txt  


But a Dynamic database containing some client info (such as CIient   
identifier & Xid) to Server inside will definitly help the relay agent to   
simply send the H/W unicast to the particular client in return path from   
Server. This will also help the Relay agents to quickly fwd the   
BOOTPREQUESTS and OFFERS before the Client will timeout. I appreciate   
your comments.

Thanks & Regards,

Harsha
 --------------------------------------------------------------------------  
 --------------------------------------------------------
Future Software Pvt Ltd.,
481, Mt Road,
Nandanam,
Mt Road,
Chennai
INDIA
 --------------------------------------------------------------------------  
 --------------------------------------------------------


 -----Original Message-----
From: shashi@demthu.saomai.org [SMTP:shashi@demthu.saomai.org]
Sent: Friday, February 19, 1999 3:11 AM
To: dhcp-client@fugue.com
Subject: RFC 2131 clarification (fwd)

    *** From dhcp-client -- To unsubscribe, see the end of this message.   
***

 ---------- Forwarded message ----------
Date: Thu, 18 Feb 1999 15:33:55 -0600 (CST)
From: shashi@demthu.saomai.org
To: dhcp-client@fugue.com
Subject: RFC 2131 clarification

Hi
In the RFC 2131 under section 3 Client-Server Protocol Page 15 item 3

"To help
     ensure that any BOOTP relay agents forward the DHCPREQUEST message
     to the same set of DHCP servers that received the original
     DHCPDISCOVER message, the DHCPREQUEST message MUST use the same
     value in the DHCP message header's 'secs' field and be sent to the
     same IP broadcast address as the original DHCPDISCOVER message.
     The client times out and retransmits the DHCPDISCOVER message if
     the client receives no DHCPOFFER messages."

Why should the 'secs' field be the same, what purpose this serve ?

Can anyone please explain

cheers
shashi





 --------------------------------------------------------------------------  
 ----
To unsubscribe from this list, please visit   
http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web   
page,
please send mail to dhcp-request@fugue.com.   Please try to use the web
page first - it will take a long time for your request to be processed by   
hand.
 --------------------------------------------------------------------------  
 ----  


From dhcp-v4@bucknell.edu  Fri Feb 19 18:24:40 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03591
	for <dhc-archive@odin.ietf.org>; Fri, 19 Feb 1999 18:24:29 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id SAA17706;
	Fri, 19 Feb 1999 18:14:56 -0500 (EST)
Date: Fri, 19 Feb 1999 18:14:56 -0500 (EST)
Message-Id: <003701be5c55$432b0160$8a50fb8d@net-gwaters.corpnorth.baynetworks.com>
Errors-To: droms@bucknell.edu
Reply-To: gww@nortelnetworks.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Glenn Waters" <gww@nortelnetworks.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: new version of the dhcp server mib
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-Type: multipart/mixed;
Mime-Version: 1.0

This is a multi-part message in MIME format.

------=_NextPart_000_0038_01BE5C2B.5A54F960
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

the new draft is attached for perusal.  any comments would be gratefully
appreciated. this work is close to moving to proposed.  we would like to
discuss this draft at the next ietf meeting.

/gww

---
Glenn Waters, Nortel Networks, Ottawa ON, Canada

------=_NextPart_000_0038_01BE5C2B.5A54F960
Content-Type: text/plain;
	name="draft-ietf-dhc-server-mib-03.txt"
Content-Disposition: attachment;
	filename="draft-ietf-dhc-server-mib-03.txt"
Content-Transfer-Encoding: quoted-printable


 Network Working Group                                       R. B. Hibbs
 INTERNET-DRAFT                                             Pacific Bell
                                                               G. Waters
                                                         Nortel Networks
                                                           February 1999



           Dynamic Host Configuration Protocol (DHCP) Server MIB


                     <draft-ietf-dhc-server-mib-03.txt>
                     Friday, February 19, 1999, 3:39 PM

 Status of this Memo

   This document is an Internet-Draft and is in full conformance with =
all
   provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering =
Task
   Force (IETF), its areas, and its working groups.  Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   To learn the current status of any Internet-Draft, please check the
   "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
   Directories on ds.internic.net (US East Coast), nic.nordu.net
   (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific =
Rim).

 Copyright Notice

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

 Abstract

   This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   the Internet Community.  In particular, it defines objects used for
   the management of Dynamic Host Configuration Protocol (DHCP) and
   Bootstrap Protocol (BOOTP) servers.












 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 1]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   Table of Contents

   1. =
Introduction......................................................2
   2. =
Overview..........................................................2
      2.1. BOOTP and DHCP Counter =
Groups................................3
      2.2. BOOTP and DHCP Statistics =
Group..............................3
      2.3. Server Configuration =
Group...................................4
      2.4. Response Times and ICMP =
Echo.................................5
   3. =
Definitions.......................................................5
   4. Intellectual =
Property............................................25
   5. =
Notes............................................................26
      5.1. =
Issues......................................................26
      5.2. Changes from Prior =
Drafts...................................26
   6. =
Acknowledgements.................................................27
   7. Security =
Considerations..........................................27
   8. =
References.......................................................28
   9. Editors' =
Addresses...............................................28
   10. Full Copyright =
Statement........................................29



 1. Introduction

   This memo was produced by the DHCP Working Group and defines a =
portion
   of the Management Information Base (MIB) for use with network
   management protocols in the Internet community.  In particular, it
   describes a set of extensions that DHCP and Bootstrap Protocol =
(BOOTP)
   servers implement.  Many implementations support both DHCP and BOOTP
   within a single server and hence this memo describes the MIB for both
   DHCP and BOOTP servers.

   This memo is applicable only to IPv4 addresses.

   This memo does not cover DHCP/BOOTP client nor relay agent =
extensions:
   these are possibly the subjects of future investigation.

   This memo is based on the Internet-standard Network Management
   Framework as defined by [RFC1902, RFC1903, RFC1904].

   Objects defined in this MIB allow access to and control of DHCP =
Server
   Software.  Servers MAY also provide additional management =
capabilities
   through the use of the Applications MIB [RFC2287].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].


 2. Overview

   In the tradition of the Simple Network Management Protocol (SNMP) the
   minimum number of objects possible are defined in this MIB, while


 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 2]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   still providing as rich a set of management information as possible.
   An object is left out of this MIB when it can be derived from other
   objects that are provided.  Further to the tradition of the SNMP,
   computationally intense operations are left to the domain of the
   management station.  Thus, this MIB provides a set of objects from
   which other management information may be derived.

   The examples provided in the following sections are not meant to be
   comprehensive, they are merely illustrative of the potential uses of
   the objects defined by this MIB.

 2.1. BOOTP and DHCP Counter Groups

   This section describes some of the management information that may be
   derived from the objects provided in the counter groups.

   The total number of valid DHCP packets received by the server is
   computed as the sum of the dhcpCountDiscovers, dhcpCountRequests,
   dhcpCountReleases, dhcpCountDeclines, and dhcpCountInforms objects.
   The total number of valid packets (BOOTP and DHCP) received is
   computed as the total number of valid DHCP packets plus the value of
   the bootpCountRequests object.  The total number of packets received
   is computed as the total number of valid packets plus
   bootpCountInvalids and dhcpCountInvalids.

   Similar to the received computations, the total number of DHCP =
packets
   sent by the server is computed as the sum of the dhcpCountOffers,
   dhcpCountAcks, and dhcpCountNacks objects.  The number of packets
   (BOOTP and DHCP) sent by the server is computed as the total number =
of
   DHCP packets sent plus the value of the bootpCountReplies object.

 2.2. BOOTP and DHCP Statistics Group

   This section describes some of the management information that may be
   derived from the objects provided in the statistics group.

   Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter-
   arrival time of valid DHCP messages for the interval t1 to t2 can be
   computed as (dhcpStatLastArrivalTime at t2 minus
   dhcpStatLastArrivalTime at t1) divided by (valid DHCP received packet
   count at t2 minus valid DHCP received packet count at t1).

   Under the simplifying assumption that the capture of packet counts =
and
   times is discontinuous (that is, for the measurement interval the
   captured data represents the complete set for the server) the =
variance
   of the mean may be computed as (dhcpStatSumSquaresArrivalTime at t2
   less dhcpStatSumSquaresArrivalTime at t1) divided by (valid DHCP
   received packet count at t2 less valid DHCP received packet count at
   t1).  Standard deviation of the mean is the square root of the
   variance.




 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 3]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   Calculation of statistics for message response time is entirely
   similar to the calculations for inter-arrival time, except that the
   response time objects are used for the calculations.

   Calculation of statistics for BOOTP is similar to the calculations =
for
   DHCP, except that the similar objects from the bootStatistics group
   are used instead of the objects from dhcpStatistics group.

 2.3. Server Configuration Group

   The server configuration group contains objects that describe the
   configuration information that is contained in the server.  Some of
   the configuration information is static (e.g.: a statically =
configured
   IP address) and some of the configuration is dynamic (e.g.: an
   assigned DHCP lease).  The intent of the server configuration group =
is
   to be able to read the server's configuration. Mechanisms outside of
   the SNMP are currently in use (e.g.: vendor defined solutions) and =
are
   being standardized (e.g.: the Directory Enabled Networks [DEN]
   initiative) to update a server's configuration.

   The configuration information provides a minimal set of information
   that most servers should be able to provide.  Each row of the
   serverSubnetTable lists the subnet, the subnet mask, and the subnet
   that is equivalent to this subnet.  Equivalence is defined as more
   than one subnet being present on the same physical media as some =
other
   subnet.

   The serverRangeTable lists the start and end IP addresses of the
   ranges and the subnet which the range is a member of.  The
   serverRangeInUse object indicates the amount of the range that is
   currently in use, either through dynamic allocation or being =
reserved.
   The range size can be computed by taking the difference of the
   serverRangeStart and serverRangeEnd objects.

   The serverAddressTable provides information about the static and
   dynamic addresses that the server contains in its configuration.
   Addresses may be:

   o Static, in which case they are predefined though the server's
     configuration.  Static addresses may or may not have been
     previously served by the server;

   o Dynamic, in which case the server has served the addresses at least
     once.  Leases which have expired MAY appear in the address list;

   o Configuration-reserved, in which case the address is not available
     for the server to allocate to a client.  A configuration-reserved
     address is one that has been reserved by the administrator. An
     example of a configuration-reserved address is an address that is
     assigned to a client, not through DHCP (e.g.: statically assigned),
     and the address is within a DHCP range;  and,



 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 4]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   o Server-reserved, in which case the server has taken the address out
     of use.  Examples of server-reserved addresses are those which have
     been declined (i.e.: through a DHCPDECLINE) by a client or those
     which have responded to an ICMP echo before they were assigned.

   The protocol used to allocate the address may be determined from the
   serverAddressServedProtocol object.  This object indicates whether =
the
   address has never been served (value of none(1)), or, whether BOOTP =
or
   DHCP was used to allocate the address.

 2.4. Response Times and ICMP Echo

   According to [RFC2131], servers SHOULD try to determine if an address
   is in use before assigning it.  Some servers choose not to perform
   this check, letting the client determine for itself if the address is
   in use.  Other servers perform an ICMP echo (Ping) just prior to
   assigning an address.  Servers that perform a Ping before responding
   to a DHCPDISCOVER should not include in the response time the time
   from when the Ping was transmitted until the time that either a
   response was received or that the server timed out waiting for a
   response.


 3. Definitions

   DHCP-SERVER-MIB DEFINITIONS ::=3D BEGIN

   IMPORTS
       Counter64, Counter32, Gauge32, Unsigned32, mib-2,
       MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress
           FROM SNMPv2-SMI

       TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue,
       DateAndTime
           FROM SNMPv2-TC

       MODULE-COMPLIANCE, OBJECT-GROUP
           FROM SNMPv2-CONF;


   dhcp OBJECT-IDENTITY
       STATUS  current
       DESCRIPTION
          "The dhcp branch in the standard network management =
framework."
       ::=3D { mib-2 ?? }  -- IANA will make official assignment

   dhcpServerMib MODULE-IDENTITY
       LAST-UPDATED    "9902190000Z"
       ORGANIZATION    "IETF DHCP Working Group"
       CONTACT-INFO
          "        Richard Barr Hibbs



 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 5]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          Postal:  Pacific Bell
                   666 Folsom Street, Room 1225
                   San Francisco, CA 94107-1384
                   USA
          Tel:     +1 415-545-1576
          Fax:     +1 415-543-3539
          Email:   rbhibbs@pacbell.com

                   Glenn Waters
          Postal:  Nortel Networks, Inc.
                   310-875 Carling Avenue
                   Ottawa, Ontario K1S 5P1
                   Canada
          Tel:     +1 613-798-4925
          Email:   gww@nortelnetworks.com "
       DESCRIPTION
          "The MIB module for entities implementing the server side of
          the Bootstrap Protocol (BOOTP) and the Dynamic Host
          Configuration protocol (DHCP) for Internet Protocol version 4
          (IPv4)."
       ::=3D { dhcp 1 }

   dhcpServerMibObjects OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "DHCP Server MIB objects are all defined in this branch."
       ::=3D { dhcpServerMib 1 }

   serverSystem OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Group of objects that are related to the overall system."
       ::=3D { dhcpServerMibObjects 1 }

   bootpCounters OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Group of objects that count various BOOTP events."
       ::=3D { dhcpServerMibObjects 2 }

   dhcpCounters OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Group of objects that count various DHCP events."
       ::=3D { dhcpServerMibObjects 3 }

   bootpStatistics OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Group of objects that measure various BOOTP statistics."
       ::=3D { dhcpServerMibObjects 4 }



 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 6]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   dhcpStatistics OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Group of objects that measure various DHCP statistics."
       ::=3D { dhcpServerMibObjects 5 }

   serverConfiguration OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Objects that contain pre-configured and dynamic configuration
          information."
       ::=3D { dhcpServerMibObjects 6 }

   bootpClients OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Objects that map bootp clients to IP addresses."
       ::=3D { dhcpServerMibObjects 7 }

   dhcpClients OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "Objects that map DHCP clients to IP addresses."
       ::=3D { dhcpServerMibObjects 8 }

   dhcpServerConformance OBJECT-IDENTITY
       STATUS        current
       DESCRIPTION
          "DHCP Server MIB objects are all defined in this branch."
       ::=3D { dhcpServerMib 1 }


   -- Textual conventions defined by this memo

   DhcpTimeInterval ::=3D TEXTUAL-CONVENTION
       STATUS        current
       DESCRIPTION
          "The number of milli-seconds that has elapsed since some =
epoch.
          Systems that cannot measure events to the milli-second
          resolution SHOULD round this value to the next available
          resolution that the system supports."
       SYNTAX        Unsigned32


   -- serverSystem Group

   serverSystemDescr OBJECT-TYPE
       SYNTAX        DisplayString (SIZE (0..255))
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION



 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 7]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          "A textual description of the server.  This value should
          include the full name and version identification of the =
server.
          This string MUST contain only printable NVT ASCII characters."
       ::=3D { serverSystem 1 }

   serverSystemObjectID OBJECT-TYPE
       SYNTAX        OBJECT IDENTIFIER
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The vendor's authoritative identification of the network
          management subsystem contained in this entity.  This value is
          allocated within the SMI enterprise subtree (1.3.6.1.4.1) and
          provides an easy and unambiguous means for determining 'what
          kind of server' is being managed.  For example, if vendor
          'VeryBigServers, Inc.' was assigned the subtree
          1.3.6.1.4.1.4242, it may assign the identifier
          1.3.6.1.4.1.4242.1.1 to its `Hercules DHCP Server'."
       ::=3D { serverSystem 2 }


   -- bootpCounters Group

   bootpCountRequests OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of packets received that contain a Message Type of
          1 (BOOTREQUEST) in the first octet and do not contain option
          number 53 (DHCP Message Type) in the options."
       ::=3D { bootpCounters 1 }

   bootpCountInvalids OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of packets received that do not contain a Message
          Type of 1 (BOOTREQUEST) in the first octet or are not valid
          BOOTP packets (e.g.: too short, invalid field in packet
          header)."
       ::=3D { bootpCounters 2 }

   bootpCountReplies OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of packets sent that contain a Message Type of 1
          (BOOTREQUEST) in the first octet and do not contain option
          number 53 (DHCP Message Type) in the options."


 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 8]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       ::=3D { bootpCounters 3 }

   bootpCountDroppedUnknownClients OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of BOOTP packets dropped due to the server not
          recognizing or not providing service to the hardware address
          received in the incoming packet."
       ::=3D { bootpCounters 4 }

   bootpCountDroppedNotServingSubnet OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of BOOTP packets dropped due to the server not
          being configured or not otherwise able to serve addresses on
          the subnet from which this message was received."
       ::=3D { bootpCounters 5 }


   -- dhcpCounters Group

   dhcpCountDiscovers OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPDISCOVER (option 53 with value 1) packets
          received."
       ::=3D { dhcpCounters 1 }

   dhcpCountRequests OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPREQUEST (option 53 with value 3) packets
          received."
       ::=3D { dhcpCounters 2 }

   dhcpCountReleases OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPRELEASE (option 53 with value 7) packets
          received."
       ::=3D { dhcpCounters 3 }



 Hibbs & Waters        Expires: Feb 1999 + 6 months             [Page 9]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   dhcpCountDeclines OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPDECLINE (option 53 with value 4) packets
          received."
       ::=3D { dhcpCounters 4 }

   dhcpCountInforms OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPINFORM (option 53 with value 8) packets
          received."
       ::=3D { dhcpCounters 5 }

   dhcpCountInvalids OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCP packets received whose DHCP message type
          (i.e.: option number 53) is not understood or handled by the
          server."
       ::=3D { dhcpCounters 6 }

   dhcpCountOffers OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPOFFER (option 53 with value 2) packets
          sent."
       ::=3D { dhcpCounters 7 }

   dhcpCountAcks OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPACK (option 53 with value 5) packets sent."
       ::=3D { dhcpCounters 8 }

   dhcpCountNacks OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCPNACK (option 53 with value 6) packets =
sent."
       ::=3D { dhcpCounters 9 }


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 10]
=0C
 Internet Draft              DHCP Server MIB               February 1999



   dhcpCountDroppedUnknownClient OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCP packets dropped due to the server not
          recognizing or not providing service to the client-id and/or
          hardware address received in the incoming packet."
       ::=3D { dhcpCounters 10 }

   dhcpCountDroppedNotServingSubnet OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of DHCP packets dropped due to the server not =
being
          configured or not otherwise able to serve addresses on the
          subnet from which this message was received."
       ::=3D { dhcpCounters 11 }


   -- bootpStatistics group

   bootpStatMinArrivalInterval OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The minimum amount of time between receiving two BOOTP
          messages.  A message is received at the server when the server
          is able to begin processing the message.  This typically =
occurs
          immediately after the message is read into server memory.  If
          no messages have been received, then this object contains a
          zero value."
       ::=3D { bootpStatistics 1 }

   bootpStatMaxArrivalInterval OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The maximum amount of time between receiving two BOOTP
          messages.  A message is received at the server when the server
          is able to begin processing the message.  This typically =
occurs
          immediately after the message is read into server memory.  If
          no messages have been received, then this object contains a
          zero value."
       ::=3D { bootpStatistics 2 }

   bootpStatLastArrivalTime OBJECT-TYPE
       SYNTAX        DateAndTime


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 11]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The date and time that the last valid BOOTP message was
          received by the server.  Invalid messages do not cause this
          value to change.  If valid no messages have been received, =
then
          this object contains a date and time that is all zero."
       ::=3D { bootpStatistics 3 }

   bootpStatSumSquaresArrivalTime OBJECT-TYPE
       SYNTAX        Counter64
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the squared BOOTP packet inter-arrival times in
          micro-seconds. This value may be used to compute the variance
          and standard deviation of the BOOTP arrival times.  Note that =
a
          micro-second resolution of this object requires a clock
          resolution to the milli-second since the square of a milli-
          second value produces a value with micro-second resolution."
       ::=3D { bootpStatistics 4 }

   bootpStatMinResponseTime OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The smallest time interval measured as the difference between
          the arrival of a BOOTP message at the server and the =
successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.
          The operating system queue time is not to be considered as =
part
          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { bootpStatistics 5 }

   bootpStatMaxResponseTime OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The largest time interval measured as the difference between
          the arrival of a BOOTP message at the server and the =
successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 12]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          The operating system queue time is not to be considered as =
part
          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { bootpStatistics 6 }

   bootpStatSumResponseTime OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the response time intervals in milli-seconds where
          a response time interval is measured as the difference between
          the arrival of a BOOTP message at the server and the =
successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.
          The operating system queue time is not to be considered as =
part
          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { bootpStatistics 7 }

   bootpStatSumSquaresResponseTime OBJECT-TYPE
       SYNTAX        Counter64
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the squared BOOTP packet response times in micro-
          seconds.  This value may be used to compute the variance and
          standard deviation of the BOOTP response times. Note that a
          micro-second resolution of this object requires a clock
          resolution to the milli-second since the square of a milli-
          second value produces a value with micro-second resolution."
       ::=3D { bootpStatistics 8 }


   -- dhcpStatistics group

   dhcpStatMinArrivalInterval OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The minimum amount of time between receiving two DHCP
          messages.  A message is received at the server when the server
          is able to begin processing the message.  This typically =
occurs
          immediately after the message is read into server memory.  If
          no messages have been received, then this object contains a
          zero value."


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 13]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       ::=3D { dhcpStatistics 1 }

   dhcpStatMaxArrivalInterval OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The maximum amount of time between receiving two DHCP
          messages.  A message is received at the server when the server
          is able to begin processing the message.  This typically =
occurs
          immediately after the message is read into server memory.  If
          no messages have been received, then this object contains a
          zero value."
       ::=3D { dhcpStatistics 2 }

   dhcpStatLastArrivalTime OBJECT-TYPE
       SYNTAX        DateAndTime
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The date and time that the last valid DHCP message was
          received by the server.  Invalid messages do not cause this
          value to change.  If no valid messages have been received, =
then
          this object contains a date and time that is all zero."
       ::=3D { dhcpStatistics 3 }

   dhcpStatSumSquaresArrivalTime OBJECT-TYPE
       SYNTAX        Counter64
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the squared DHCP packet inter-arrival times in
          micro-seconds.  This value may be used to compute the variance
          and standard deviation of the DHCP arrival times.   Note that =
a
          micro-second resolution of this object requires a clock
          resolution to the milli-second since the square of a milli-
          second value produces a value with micro-second resolution."
       ::=3D { dhcpStatistics 4 }

   dhcpStatMinResponseTime OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The smallest time interval measured as the difference between
          the arrival of a DHCP message at the server and the successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.
          The operating system queue time is not to be considered as =
part


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 14]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { dhcpStatistics 5 }

   dhcpStatMaxResponseTime OBJECT-TYPE
       SYNTAX        DhcpTimeInterval
       MAX-ACCESS    read-write
       STATUS        current
       DESCRIPTION
          "The largest time interval measured as the difference between
          the arrival of a DHCP message at the server and the successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.
          The operating system queue time is not to be considered as =
part
          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { dhcpStatistics 6 }

   dhcpStatSumResponseTime OBJECT-TYPE
       SYNTAX        Counter32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the response time intervals in milli-seconds where
          a response time interval is measured as the difference between
          the arrival of a DHCP message at the server and the successful
          transmission of the response to that message.  A message is
          received at the server when the server is able to begin
          processing the message.  A message is transmitted after the
          server has no further use for the message.  Note that the
          operating system may still have the message queued internally.
          The operating system queue time is not to be considered as =
part
          of the response time.  Invalid messages do not cause this =
value
          to change.  If no valid messages have been received, then this
          object contains a zero value."
       ::=3D { dhcpStatistics 7 }

   dhcpStatSumSquaresResponseTime OBJECT-TYPE
       SYNTAX        Counter64
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The sum of the squared DHCP packet response times in micro-
          seconds.  This value may be used to compute the variance and
          standard deviation of the DHCP response times. Note that a
          micro-second resolution of this object requires a clock



 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 15]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          resolution to the milli-second since the square of a milli-
          second value produces a value with micro-second resolution."
       ::=3D { dhcpStatistics 8 }


   -- serverConfiguration group

   serverSubnetTable OBJECT-TYPE
       SYNTAX        SEQUENCE OF ServerSubnetEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A list of subnets that are configured in this server."
       ::=3D { serverConfiguration 1 }

   serverSubnetEntry OBJECT-TYPE
       SYNTAX        ServerSubnetEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A logical row in the serverSubnetTable."
       INDEX            { serverSubnet }
       ::=3D { serverSubnetTable 1 }

   ServerSubnetEntry ::=3D SEQUENCE {
       serverSubnet                  IpAddress,
       serverSubnetMask              IpAddress,
       serverSubnetSharedNet         IpAddress
   }

   serverSubnet OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "The IP address of the subnet."
       ::=3D { serverSubnetEntry 1 }

   serverSubnetMask OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The subnet mask of the subnet.  This MUST be the same as the
          value of DHCP option 1 offered to clients on this subnet."
       ::=3D { serverSubnetEntry 2 }

   serverSubnetSharedNet OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 16]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          "The IP address of another subnet that is on the same shared
          media as this subnet.  The address of the shared subnet MUST
          also be configured on this server.  The address 0.0.0.0 should
          be used if this subnet is not shared."
       ::=3D { serverSubnetEntry 3 }

   serverRangeTable OBJECT-TYPE
       SYNTAX        SEQUENCE OF ServerRangeEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A list of ranges that are configured on this server."
       ::=3D { serverConfiguration 2 }

   serverRangeEntry OBJECT-TYPE
       SYNTAX        ServerRangeEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A logical row in the serverRangeTable."
       INDEX            { serverRangeStart }
       ::=3D { serverRangeTable 1 }

   ServerRangeEntry ::=3D SEQUENCE {
       serverRangeStart             IpAddress,
       serverRangeEnd               IpAddress,
       serverRangeSubnetMask        IpAddress,
       serverRangeInUse             Gauge32,
       serverRangeOutstandingOffers Gauge32
   }

   serverRangeStart OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "The IP address of the first address in the range. The value =
of
          range start must be less than or equal to the value of range
          end."
       ::=3D { serverRangeEntry 1 }

   serverRangeEnd OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The IP address of the last address in the range. The value of
          range end must be greater than or equal to the value of range
          start."
       ::=3D { serverRangeEntry 2 }

   serverRangeSubnetMask OBJECT-TYPE


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 17]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The subnet mask (DHCP option 1) provided to any client =
offered
          an address from this range."
       ::=3D { serverRangeEntry 3 }

   serverRangeInUse OBJECT-TYPE
       SYNTAX        Gauge32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of addresses in this range that are currently in
          use.  This number includes those addresses whose lease has not
          expired and addresses which have been reserved (either by the
          server or through configuration)."
       ::=3D { serverRangeEntry 4 }

   serverRangeOutstandingOffers OBJECT-TYPE
      SYNTAX    Guage32
      MAX-ACCESS    read-only
      STATUS    current
      DESCRIPTION
         "The number of outstanding DHCPOFFER messages for this range is
         reported with this value.  An offer is outstanding if the
         server has sent a DHCPOFFER message to a client, but has not
         yet received a DHCPREQUEST message from the client nor has the
         server-specific timeout (limiting the time in which a client
         can respond to the offer message) for the offer message
         expired."
      ::=3D { serverRangeEntry 5 }


   serverAddressTable OBJECT-TYPE
       SYNTAX        SEQUENCE OF ServerAddressEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A list of addresses that are known by this server.  The list
          MUST contain addresses that have not expired.  The list MUST
          NOT contain addresses that have never been assigned by the
          server UNLESS the lease is pre-configured in the server (e.g.:
          a static lease on a subnet)."
       ::=3D { serverConfiguration 3 }

   serverAddressEntry OBJECT-TYPE
       SYNTAX        ServerAddressEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A logical row in the serverAddressTable."


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 18]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       INDEX            { serverAddress }
       ::=3D { serverAddressTable 1 }

   ServerAddressEntry ::=3D SEQUENCE {
       serverAddress                IpAddress,
       serverAddressSubnetMask      IpAddress,
       serverAddressRange           IpAddress,
       serverAddressType            INTEGER,
       serverAddressTimeReminaing   Unsigned32,
       serverAddressAllowedProtocol INTEGER,
       serverAddressServedProtocol  INTEGER,
       serverAddressMacAddress      OCTET STRING,
       serverAddressClientId        OCTET STRING,
       serverAddressHostName        DisplayString,
       serverAddressDomainName      DisplayString
   }

   serverAddress OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "The IP address of the entry."
       ::=3D { serverAddressEntry 1 }

   serverAddressSubnetMask OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The subnet mask (DHCP option 1) provided to the client =
offered
          this address.  The subnet, resulting from logically ANDing the
          subnet mask with the entry's IP address, must be configured on
          this server and appear as a row in the dhcpSubnetTable."
       ::=3D { serverAddressEntry 2 }

   serverAddressRange OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The starting IP address (serverRangeStart object) of the =
range
          to which this address belongs.  If the address does not fall
          into one of the configured ranges (e.g.: a statically
          configured address on a subnet) the range may be 0.0.0.0."
       ::=3D { serverAddressEntry 3 }

   serverAddressType OBJECT-TYPE
       SYNTAX        INTEGER {
                         static(1),
                         dynamic(2),
                         configuration-reserved(3),


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 19]
=0C
 Internet Draft              DHCP Server MIB               February 1999


                         server-reserved(4)
                     }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The type of this address."
       ::=3D { serverAddressEntry 4 }

   serverAddressTimeRemaining OBJECT-TYPE
       SYNTAX        Unsigned32
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The number of seconds until the lease expires. A value of
          4294967295 (i.e.: 0xFFFFFFFF) should be used for leases that
          have a lease time which is 'infinite' and for BOOTP leases."
       ::=3D { serverAddressEntry 5 }

   serverAddressAllowedProtocol OBJECT-TYPE
       SYNTAX        INTEGER {
                         none(1),
                         bootp(2),
                         dhcp(3),
                         bootp-or-dhcp(4)
                     }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The type of protocol that is allowed to be used to serve this
          address.  A type of none(1) indicates that the address is not
          available to be served (e.g.: a reserved address)."
       ::=3D { serverAddressEntry 6 }

   serverAddressServedProtocol OBJECT-TYPE
       SYNTAX        INTEGER {
                         none(1),
                         bootp(2),
                         dhcp(3)
                     }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The type of protocol that was used when this address was
          assigned.  This object will have the value of none(1) if the
          address has not been served."
       ::=3D { serverAddressEntry 7 }

   serverAddressMacAddress OBJECT-TYPE
       SYNTAX        OCTET STRING (SIZE (0 | 2..17))
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 20]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          "The hardware type and hardware address of the client that has
          been assigned this lease.  The first octet of this object
          contains the hardware type from the 'htype' field of the BOOTP
          packet and the remaining octets contain the hardware address
          from the 'chaddr' field of the BOOTP packet.  This object may
          be empty if the address has not been previously served."
       ::=3D { serverAddressEntry 8 }

   serverAddressClientId OBJECT-TYPE
       SYNTAX        OCTET STRING (SIZE (0..255))
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The client-id of the client that has been assigned this =
lease.
          The client-id is the value specified in option 61 (client-id
          option) when the lease was assigned.  This object may be empty
          if the lease has not been previously assigned or if the =
client-
          id option was not specified when the address was assigned."
       ::=3D { serverAddressEntry 9 }

   serverAddressHostName OBJECT-TYPE
       SYNTAX        DisplayString (SIZE (0..64))
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The host name (DHCP option 12) the client is configured with
          or if no host name was configured then the host name that the
          client supplied when requesting an address."
       ::=3D { serverAddressEntry 10 }

   serverAddressDomainName OBJECT-TYPE
       SYNTAX        DisplayString (SIZE (0..255))
                               -- need correct maximum length
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The domain name (DHCP option 15) assigned to the client."
       ::=3D { serverAddressEntry 11 }


   serverClientTable OBJECT-TYPE
       SYNTAX        SEQUENCE OF ServerClientEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A list of clients that are known by this server. Details =
about
          the clients may be found by indexing into the
          serverAddressTable using the serverClientAddress object. This
          table is indexed first by the MAC address of the client and
          then by the subnet address on which the client resides. The
          subnet is included as an index since a MAC address is only



 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 21]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          guaranteed to be unique within a subnet (i.e.: a MAC address =
is
          not globally unique)."
       ::=3D { bootpClients 1 }

   serverClientEntry OBJECT-TYPE
       SYNTAX        ServerClientEntry
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "A logical row in the serverClientTable. An entry in this =
table
          may be a client that requested an address but was refused
          (e.g.: not authorized). Servers MAY track these types of
          clients if desired and may choose to remove such client =
entries
          using a server defined algorithm. As an example, a server may
          choose to keep client request that does not map to an address
          for a one hour time period before removing that entry from =
this
          table."
       INDEX            { serverClientMacAddress, serverClientSubnet }
       ::=3D { bootpClientTable 1 }

   ServerClientEntry ::=3D SEQUENCE {
       serverClientTypeAndMacAddress  OCTET STRING,
       serverClientSubnetMask         IpAddress,
       serverClientAddress            IpAddress,
       serverClientLastRequestTime    DateAndTime,
       serverClientLastRequestType    INTEGER,
       serverClientLastResponseType   INTEGER
   }

   serverClientTypeAndMacAddress OBJECT-TYPE
       SYNTAX        OCTET STRING (SIZE (2..17))
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "The hardware type and hardware address of the client that has
          been assigned this lease.  The first octet of this object
          contains the hardware type from the 'htype' field of the BOOTP
          packet and the remaining octets contain the hardware address
          from the 'chaddr' field of the BOOTP packet."
       ::=3D { serverClientEntry 1 }

   serverClientSubnetMask OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    not-accessible
       STATUS        current
       DESCRIPTION
          "The subnet mask (DHCP option 1) applied to the client IP."
       ::=3D { serverClientEntry 2 }

   serverClientAddress OBJECT-TYPE
       SYNTAX        IpAddress
       MAX-ACCESS    read-only


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 22]
=0C
 Internet Draft              DHCP Server MIB               February 1999


       STATUS        current
       DESCRIPTION
          "The IP address of the entry. May be used to index into the
          serverAddressTable. May be 0.0.0.0 if an address is not
          associated with this client."
       ::=3D { serverClientEntry 3 }

   serverClientLastRequestTime OBJECT-TYPE
       SYNTAX        DateAndTime
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The time when the last request was received."
       ::=3D { serverClientEntry 4 }

   serverClientLastRequestType OBJECT-TYPE
       SYNTAX        INTEGER {
                         dhcpdiscover(1),
                         bootp(2),
                         dhcprequest(3),
                         dhcpdecline(4),
                         unknown(5),
                         dhcprelease(7),
                         dhcpinform(8)
                     }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The type of the last request that was received for this
          client."
       ::=3D { serverClientEntry 5 }

   serverClientLastResponseType OBJECT-TYPE
       SYNTAX        INTEGER {
                         bootp(1),
                         dhcpoffer(2),
                         unknown(3),
                         dhcpack(5),
                         dhcpnak(6)
                     }
       MAX-ACCESS    read-only
       STATUS        current
       DESCRIPTION
          "The type of the last response that was sent to this client."
       ::=3D { serverClientEntry 6 }


   -- Compliance groups

   dhcpServerMIBCompliances  OBJECT IDENTIFIER ::=3D {
   dhcpServerConformance 1 }



 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 23]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   dhcpServerMIBGroups       OBJECT IDENTIFIER ::=3D {
   dhcpServerConformance 2 }

   dhcpServerMIBCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
          "Describes the requirements for conformance to the System
          Application MIB"
       MODULE  -- this module
       MANDATORY-GROUPS
          { serverSystemGroup, bootpCountersGroup, dhcpCountersGroup,
          bootpStatisticsGroup, dhcpStatisticsGroup,
          serverConfigurationGroup, serverClientsGroup }
       ::=3D { dhcpServerMIBCompliances 1 }

   serverSystemGroup OBJECT-GROUP
       OBJECTS       { serverSystemDescr, serverSystemObjectID }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 1 }

   bootpCountersGroup OBJECT-GROUP
       OBJECTS
          { bootpCountRequests, bootpCountInvalids, bootpCountReplies,
          bootpCountDroppedUnknownClients,
          bootpCountDroppedNotServingSubnet }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 2 }

   dhcpCountersGroup OBJECT-GROUP
       OBJECTS
          { dhcpCountDiscovers, dhcpCountRequests, dhcpCountReleases,
          dhcpCountDeclines, dhcpCountInforms, dhcpCountInvalids,
          dhcpCountOffers, dhcpCountAcks, dhcpCountNacks,
          dhcpCountDroppedUnknownClint, dhcpCountDroppedNotServingSubnet
          }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 3 }

   bootpStatisticsGroup OBJECT-GROUP
       OBJECTS
          { bootpStatMinArrivalInterval, bootpStatMaxArrivalInterval,
          bootpStatLastArrivalTime, bootpStatSunSquaresArrivalTime,
          bootpStatMinResponseTime, bootpStatMaxResponseTime,
          bootpStatSumReponseTime, bootpStatSumSquaresResponseTime }
       STATUS        current
       DESCRIPTION


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 24]
=0C
 Internet Draft              DHCP Server MIB               February 1999


          ""
       ::=3D { dhcpServerMIBGroups 4 }

   dhcpStatisticsGroup OBJECT-GROUP
       OBJECTS
          { dhcpStatMinArrivalInterval, dhcpStatMaxArrivalInterval,
          dhcpStatLastArrivalTime, dhcpStatSumSquaresArrivalTime,
          dhcpStatMinResponseTime, dhcpStatMaxResponseTime,
          dhcpStatSumResponseTime, dhcpStatSumSquaresResponseTime }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 5 }

   serverConfigurationGroup OBJECT-GROUP
       OBJECTS
          { serverSubnet, serverSubnetMask, serverSubnetSharedNet,
          serverRangeStart, serverRangeEnd, serverRangeSubnet,
          serverRangeInUse, serverRangeOutstandingOffers, serverAddress,
          serverAddressSubnet, serverAddressRange, serverAddressRange,
          serverAddressType, serverAddressTimeRemaining,
          serverAddressAllowedProtocol, serverAddressServedProtocol,
          serverAddressTypeAndMacAddress, serverAddressClientId,
          serverAddressHostName, serverAddressDomainName }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 6 }

   serverClientsGroup OBJECT-GROUP
       OBJECTS
          { serverClientMacAddress, serverClientSubnet,
          serverClientAddress, serverClientLastRequestTime,
          serverClientLastRequestType, serverClientLastResponseType }
       STATUS        current
       DESCRIPTION
          ""
       ::=3D { dhcpServerMIBGroups 7 }

   END

 4. Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to =
pertain
   to the implementation or use of the technology described in this
   document or the extent to which any license under such rights might =
or
   might not be available; neither does it represent that it has made =
any
   effort to identify any such rights.  Information on the IETF's
   procedures with respect to rights in standards-track and standards-
   related documentation can be found in BCP-11.



 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 25]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   Copies of claims of rights made available for publication and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this =
specification
   can be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.


 5. Notes

   This section will be removed when this memo is published as an RFC.

 5.1. Issues

   o what is the best way to reset statistics?

     o do we need to reset them individually, as groups, or as a whole?

   o we need a timestamp of when they were reset

   o should all invalid packets received be collapsed into a single
      counter for each protocol type (BOOTP and DHCP), or broken out by
      type of error?

   o if counted by error type, what is the set of errors that we should
      use?

   o perhaps we should develop a common vocabulary (and glossary) for
      terms such as "abandoned" so that the objects defined and their
      descriptions aren't misinterpreted by implementers.

   o do we need to be concerned about the potential size of some of the
      configuration data tables?  Wouldn't it be better to maintain
      counters for things like number of leases assigned than to expect
      the management station to calculate the values by reading very
      large tables to count the number of leases in that state?

 5.2. Changes from Prior Drafts

   The "-01" revision removed the Server Identity section from the
   proposed MIB, relying on the Application MIB to accomplish the same
   result.

   The min/max (inter-arrival and response times) were changed to
   Unsigned32 so that they could be reset.  Sum of inter-arrival and
   response times was deleted since the management station can easily
   calculate them.  The last arrival time objects were added.


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 26]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   The "-03" version incorporated the proposed configuration tables
   suggested by Ryan Troll of CMU.  The "01" revision of this version
   added three elements to the server subnet table, number of =
outstanding
   offers, number of addresses in use, and number of free addresses, as
   well as changing subnet address to subnet mask in the server address,
   server range, and client address tables.  The client MAC address
   element of the client address table was separated into a 1-octet
   hardware type and a 16-octet client hardware address, causing a
   renumbering of the elements in this table.  Clarifying text was added
   to several element descriptions, and limitations on values, and the
   reported value when the server did not support the data element were
   also specified.


 6. Acknowledgements

   This document is the result of work undertaken the by DHCP working
   group.  The authors would like to particularly acknowledge the
   development team from Carnegie-Mellon University whose work creating =
a
   private MIB for their DHCP server inspired the development of this
   proposal. In particular, many thanks to Ryan Troll who provided a
   great deal of useful feedback during the development of this MIB.


 7. Security Considerations

   There are a number of management objects defined in this MIB that =
have
   a MAX-ACCESS clause of read-write and/or read-create. Such objects =
may
   be considered sensitive or vulnerable in some environments.  The
   support for SET operations in a non-secure environment without proper
   protection can have a negative effect on network operations.

   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security =
features
   as provided by the SNMPv3 framework.  Specifically, the use of the
   User-based Security Model RFC 2274 [RFC2274] and the View-based =
Access
   Control Model RFC 2275 [RFC2275] is recommended.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those principals
   (users) that have legitimate rights to indeed GET or SET
   (change/create/delete) them.







 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 27]
=0C
 Internet Draft              DHCP Server MIB               February 1999


 8. References

   [DEN] Directory Enabled Networks Working Group,
     http://www.universe.digex.net/~murchiso/den.

   [RFC1902] Case, J., McCloghrie, K., Rose, M., and S.  Waldbusser,
     "Structure of Management Information for Version 2 of the Simple
     Network Management Protocol (SNMPv2)", RFC 1902, January 1996.

   [RFC1903] Case, J., McCloghrie, K., Rose, M., and S.  Waldbusser,
     "Textual Conventions for Version 2 of the Simple Network Management
     Protocol (SNMPv2)", RFC 1903, January 1996.

   [RFC1904] Case, J., McCloghrie, K., Rose, M., and S.  Waldbusser,
     "Conformance Statements for Version 2 of the Simple Network
     Management Protocol (SNMPv2)", RFC 1904, January 1996.

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
     Requirement Levels", RFC 2119, BCP 14, March 1997.

   [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
     March 1997.

   [RFC2132] Alexander, S.  and Droms, R., "DHCP Options and BOOTP =
Vendor
     Extensions", RFC 2132, March 1997.

   [RFC2274] Blumenthal, U., and B. Wijnen, "User-based Security Model
     (USM) for version 3 of the Simple Network Management Protocol
     (SNMPv3)", RFC 2274, January 1998.

   [RFC2275] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
     Access Control Model for the Simple Network Management Protocol
     (SNMP)", RFC 2275, January 1998.

   [RFC2287] Krupczak, C.  and Saperia, J., "Definitions of System-Level
     Managed Objects for Applications", RFC 2287, February 1998.


 9. Editors' Addresses

   Richard Barr Hibbs
   Pacific Bell
   666 Folsom Street, Room 1225
   San Francisco, CA 94107-1384
   USA

   Phone:  +1 415-545-1576
   Fax:    +1 415-543-3539
   Email:  rbhibbs@pacbell.com

   Glenn Waters
   Nortel Networks


 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 28]
=0C
 Internet Draft              DHCP Server MIB               February 1999


   310-875 Carling Avenue,
   Ottawa, Ontario K1S 5P1
   Canada

   Phone:  +1 613-798-4925
   Email:  gww@nortelnetworks.com


 10. Full Copyright Statement

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published =
and
   distributed, in whole or in part, without restriction of any kind,
   provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of =
developing
   Internet standards in which case the procedures for copyrights =
defined
   in the Internet Standards process must be followed, or as required to
   translate it into languages other than English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING =
BUT
   NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
   WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.




















 Hibbs & Waters        Expires: Feb 1999 + 6 months            [Page 29]
=0C
------=_NextPart_000_0038_01BE5C2B.5A54F960--

-------


From dhcp-v4@bucknell.edu  Sat Feb 20 02:57:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17305
	for <dhc-archive@odin.ietf.org>; Sat, 20 Feb 1999 02:57:12 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id CAA05527;
	Sat, 20 Feb 1999 02:52:25 -0500 (EST)
Date: Sat, 20 Feb 1999 02:52:25 -0500 (EST)
Message-Id: <04ee01be5ca0$b4ba8d00$098939cc@E1KJ2>
Errors-To: droms@bucknell.edu
Reply-To: aboba@internaut.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Bernard Aboba" <aboba@internaut.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: new version of the dhcp server mib
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Outlook Express 5.00.2013.600
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


Some comments on the DHCP server MIB:

1. Since MIB counters roll over, they are used for measuring differences and
rates. Can you explain how counters such as bootpStatSumSquaresArrivalTime
would be used to compute a difference or rate? After these counters roll, it
would seem to me that they would be useless for computing the variance and
standard deviation.

2. There are no MIB variables that are relevant to diagnosing authenticated
DHCP. Some of the things you might want to measure include:
a. Bad authenticators by protocol and algorithm
b. Unknown algorithms or protocols

3. There are no MIB variables relevant to DHCP relay agents. While a relay
agent is a separate entity it doesn't seem worthwhile to have a separate MIB
for them. I'd suggest a separate conformance group for variables relevant to
relay agents.

4. This MIB has IPv4 dependencies. Rather than using the IpAddress type,
 it would be preferrable to use the NetworkAddress type, which would allow
 the MIB to be useful for IPv6 as well.




From dhcp-v4@bucknell.edu  Sat Feb 20 23:10:04 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25559
	for <dhc-archive@odin.ietf.org>; Sat, 20 Feb 1999 23:10:04 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id XAA19839;
	Sat, 20 Feb 1999 23:04:32 -0500 (EST)
Date: Sat, 20 Feb 1999 23:04:32 -0500 (EST)
Message-Id: <v04011705b2f4b999bae0@[209.173.86.26]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: RFC 2131 clarification (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

At 3:41 PM -0600 2/18/99, shashi@demthu.saomai.org wrote:
>In the RFC 2131 under section 3 Client-Server Protocol Page 15 item 3
>
>"To help
>     ensure that any BOOTP relay agents forward the DHCPREQUEST message
>     to the same set of DHCP servers that received the original
>     DHCPDISCOVER message, the DHCPREQUEST message MUST use the same
>     value in the DHCP message header's 'secs' field and be sent to the
>     same IP broadcast address as the original DHCPDISCOVER message.
>     The client times out and retransmits the DHCPDISCOVER message if
>     the client receives no DHCPOFFER messages."
>
>Why should the 'secs' field be the same, what purpose this serve ?
>
>Can anyone please explain

In general, this text was included to guarantee that the REQUEST message
would reach and be processed by the server from which the selected OFFER
was received.  In particular, when we wrote the original DHCP spec, there
were BOOTP relay agents that would perform load balancing by forwarding
DHCP messages to different servers based, in part, on the value of the
'secs' field. There was no state kept for each message; rather, there was
an algorithm in the relay agent that would compute the destination based on
the contents of the message to be forwaarded.  So, the specific text was
added to ensure that the contents of the REQUEST message would cause it to
be forwarded to the same server or servers as the original DISCOVER
message, which would include the server from which the selected OFFER was
received.

Servers may also filter messages based on the 'secs field, as Philip
Guenther pointed out:

>Some servers and gateways can be configured to not respond to request
>packets with a secs field below a given value.  This allows for the
>easy implementation of fall-back servers and 'expanding ring' style
>searches.

- Ralph



From dhcp-v4@bucknell.edu  Sun Feb 21 13:15:19 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03141
	for <dhc-archive@odin.ietf.org>; Sun, 21 Feb 1999 13:15:16 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id NAA03622;
	Sun, 21 Feb 1999 13:09:03 -0500 (EST)
Date: Sun, 21 Feb 1999 13:09:03 -0500 (EST)
Message-Id: <199902211757.MAA00895@grosse.fugue.com>
Errors-To: droms@bucknell.edu
Reply-To: mellon@isc.org
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ted Lemon <mellon@isc.org>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: RFC 2131 clarification (fwd) 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


Hm.  The current ISC DHCP client doesn't implement the behaviour as
specified, and it looked like about five minute's work to implement
it, so just now I tried.  While I was doing so, it occurred to me that
we don't actually have a way to match DHCPDISCOVER and DHCPOFFER
messages precisely - we don't know that a particular offer was a
response to a particular discover, if we've been retransmitting.  So
if we use, e.g., the secs value from the last DHCPDISCOVER we sent,
this might be *different* than the secs value that got us the
DHCPOFFER we chose.

The only way to reliably make sure we use the secs value that got us a
particular offer is to have the server send the secs value from the
client's DHCPDISCOVER back in the secs field of its DHCPOFFER.
Unfortunately, rfc2131 says quite unequivocally that the server is
always supposed to send back a secs value of zero.

IMHO, this breaks the functionality that you are describing pretty
badly - it's not at all uncommon in my experience, because of the Echo
Request and the fast timeout on Microsoft clients, for the first
DHCPOFFER a Microsoft client receives to be the response to its first
DHCPDISCOVER, even though it's subsequently *sent* a second
DHCPDISCOVER.   I've even seen this happen with a slow server and the
ISC client at times, even though the ISC client has a much slower
initial timeout.

So how do we fix this?   I'd suggest that we either give up on having
this feature in the current protocol, that is, take out the section
that says the secs field in the DHCPREQUEST has to be the same as the
secs field in the DHCPDISCOVER, or specify different behaviour and
accept that it will not initially be widely implemented.

My suggestion is that we take out the current language and put it back
in the DHCPv4ng protocol specification, whenever that happens, with
the following changes:

	 - when the server generates a DHCPOFFER, it sets secs to the
	   value it found in the DHCPDISCOVER packet.
	 - When the client sends a DHCPREQUEST in response to a
	   DHCPOFFER, it uses the secs field from the DHCPOFFER, NOT
	   the secs field from its most recent DHCPDISCOVER.

For now, my plan is to not implement the behaviour specified in
rfc2131 - I unfortunately can't see any way to make it work.  Is
anybody currently using (as opposed to implementing) the behaviour
currently specified in rfc2131?

			       _MelloN_


From dhcp-v4@bucknell.edu  Mon Feb 22 12:59:18 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20415
	for <dhc-archive@odin.ietf.org>; Mon, 22 Feb 1999 12:59:15 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id MAA15981;
	Mon, 22 Feb 1999 12:17:35 -0500 (EST)
Date: Mon, 22 Feb 1999 12:17:35 -0500 (EST)
Message-Id: <21839C593E75D211BF7800805FCCD0264B0727@msgsrv03.srv.PacBell.COM>
Errors-To: droms@bucknell.edu
Reply-To: RBHIBBS@msg.pacbell.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Hibbs, R BARR (PB-rbhibbs)" <RBHIBBS@msg.pacbell.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: new version of the dhcp server mib
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



----------
From:  Bernard Aboba [SMTP:aboba@internaut.com]
Sent:  Friday, February 19, 1999 11:53 PM
To:  Multiple recipients of list
Subject:  Re: new version of the dhcp server mib


Some comments on the DHCP server MIB:

1. Since MIB counters roll over, they are used for measuring differences and
rates. Can you explain how counters such as bootpStatSumSquaresArrivalTime
would be used to compute a difference or rate? After these counters roll, it
would seem to me that they would be useless for computing the variance and
standard deviation.

..in particular, all of the sum of squares variables are useful only for
computation of the variance and standard deviation.  While someone,
somewhere might employ statisticians as network administrators, it seems
highly unlikely to the authors that any measures of these statistics that
involve rate of change with respect to time (essentially the second
derivative of message counters) will have practical application.

..for example, the inter-arrival rate for, say, BOOTP messages in general
can be computed from the sum of BOOTP message inter-arrival time and number
of messages received during a measurement interval (the interval itself
calculated from the difference in SysUpTime).  To ensure completely
comparable statistics, the authors proposed that the server capture both the
sum of inter-arrival times and the sum-of-squares.  By making a single
simplifying assumption, that the samples in question represent the entire
series of samples (which, for the interval in question is completely
correct), the variance can be calculated directly from the sum-of-squares
variable and number of messages.

..what more will most system or network administrators want?  In the
authors' experience, if an administrator even asks once a month what the
"average" of some message rate is, that shows a great interest in the
subject.  While we don't intend to be flippant on the topic, our reason for
inclusion of these variables was to give the administrators some reliable
tools for determining server utilization -- the statistics for calculating
mean and variance serve as "confidence builders" for the various first-order
rates that may be calculated from message counters rather than an end in
themselves.

..the authors will re-examine the language used to describe the variables
and their usage to ensure that when counters roll-over all related variables
are appropriately reset (roll over) as well to maintain consistent
statistics 

2. There are no MIB variables that are relevant to diagnosing authenticated
DHCP. Some of the things you might want to measure include:
	a. Bad authenticators by protocol and algorithm
	b. Unknown algorithms or protocols

..I'm not sure what you mean by "authenticated DHCP."  As we have, as yet,
no RFCs to cover authentication of DHCP, it seems inappropriate to introduce
any variables that refer to as yet undefined parameters.

3. There are no MIB variables relevant to DHCP relay agents. While a relay
agent is a separate entity it doesn't seem worthwhile to have a separate MIB
for them. I'd suggest a separate conformance group for variables relevant to
relay agents.

..yes, the MIB was intended only to cover DHCP servers -- if that
limitation was not discussed in the introductory matters, we will correct
the omission

4. This MIB has IPv4 dependencies. Rather than using the IpAddress type,
 it would be preferrable to use the NetworkAddress type, which would allow
 the MIB to be useful for IPv6 as well.

..this is intended only for IPv4 and DHCPv4 servers -- as that limitation
is apparently not clear, we will reexamine the wording of the introductory
matters to clarify the restriction.


--Barr



From dhcp-v4@bucknell.edu  Fri Feb 26 07:17:06 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17719
	for <dhc-archive@odin.ietf.org>; Fri, 26 Feb 1999 07:17:06 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA12251;
	Fri, 26 Feb 1999 07:10:39 -0500 (EST)
Date: Fri, 26 Feb 1999 07:10:39 -0500 (EST)
Message-Id: <v04011704b2fc32abf7ac@[198.200.138.51]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-server-mib-03.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		: Dynamic Host Configuration Protocol (DHCP) Server MIB
	Author(s)	: R. Hibbs, G. Waters
	Filename	: draft-ietf-dhc-server-mib-03.txt
	Pages		: 28
	Date		: 22-Feb-99

   This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   the Internet Community.  In particular, it defines objects used for
   the management of Dynamic Host Configuration Protocol (DHCP) and
   Bootstrap Protocol (BOOTP) servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-server-mib-03.txt

Internet-Drafts are also 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-server-mib-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-server-mib-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.


[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-server-mib-03.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-server-mib-03.txt>


From dhcp-v4@bucknell.edu  Fri Feb 26 07:19:02 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17730
	for <dhc-archive@odin.ietf.org>; Fri, 26 Feb 1999 07:19:01 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA15054;
	Fri, 26 Feb 1999 07:16:49 -0500 (EST)
Date: Fri, 26 Feb 1999 07:16:49 -0500 (EST)
Message-Id: <v04011703b2fc32a6f6a3@[198.200.138.51]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: ErroI-D ACTION:draft-ietf-dhc-subnet-option-00.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		: The Subnet Selection Option for DHCP
	Author(s)	: G. Waters
	Filename	: draft-ietf-dhc-subnet-option-00.txt
	Pages		: 5
	Date		: 22-Feb-99

   This memo defines a new DHCP option for selecting the subnet on which
   to allocate an address. This option would override a DHCP server's
   normal methods of selecting which subnet on which to allocate an
   address for a client.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-subnet-option-00.txt

Internet-Drafts are also 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-subnet-option-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-subnet-option-00.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-subnet-option-00.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-subnet-option-00.txt>


From dhcp-v4@bucknell.edu  Fri Feb 26 07:20:21 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17745
	for <dhc-archive@odin.ietf.org>; Fri, 26 Feb 1999 07:20:20 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA10757;
	Fri, 26 Feb 1999 07:18:34 -0500 (EST)
Date: Fri, 26 Feb 1999 07:18:34 -0500 (EST)
Message-Id: <v04011701b2fc329ef4c0@[198.200.138.51]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-autoconfig-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.

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

	Title		: DHCP Option to Disable Stateless
                          Auto-Configuration in IPv4 Clients
	Author(s)	: R. Troll
	Filename	: draft-ietf-dhc-autoconfig-04.txt
	Pages		: 9
	Date		: 23-Feb-99

    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 automatically choosing a link-local
    IP address which will allow them to communicate only with other
    hosts on the same link.  This address will not allow the OS to
    communicate with anything beyond a router.  However, some sites
    depend on the fact that a host with no DHCP response will have no IP
    address.  This document 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 generate an IP address it's
    own.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-autoconfig-04.txt

Internet-Drafts are also 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-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-autoconfig-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-autoconfig-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-autoconfig-04.txt>


From dhcp-v4@bucknell.edu  Sat Feb 27 07:42:27 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11621
	for <dhc-archive@odin.ietf.org>; Sat, 27 Feb 1999 07:42:26 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id HAA17706;
	Sat, 27 Feb 1999 07:39:14 -0500 (EST)
Date: Sat, 27 Feb 1999 07:39:14 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9902270717340.2983-120000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-callcontrolserv-00.txt (fwd)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-920118034=:2983"
Mime-Version: 1.0

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-851401618-920118034=:2983
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.03.9902270717342.2983@leo>


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 Call Control Servers
	Author(s)	: H. Houh
	Filename	: draft-ietf-dhc-callcontrolserv-00.txt
	Pages		: 4
	Date		: 25-Feb-99
	
   This document defines a new DHCP option for delivering configuration
   information to telephony enabled hosts in order to locate a call
   control/signalling server.  The option carries several operational
   parameters that allow multiple call control vendors to utilize this
   field.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-callcontrolserv-00.txt

Internet-Drafts are also 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-callcontrolserv-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-callcontrolserv-00.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.

---559023410-851401618-920118034=:2983
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="-559023410-1804928587-920118034=:2983"
Content-ID: <Pine.GSO.4.03.9902270717343.2983@leo>
Content-Description: 

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-1804928587-920118034=:2983
Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="mailserv@ietf.org"
Content-ID: <Pine.GSO.4.03.9902270717344.2983@leo>

---559023410-1804928587-920118034=:2983
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="draft-ietf-dhc-callcontrolserv-00.txt"; SITE="ftp.ietf.org"; ACCESS-TYPE=anon-ftp; DIRECTORY=internet-drafts
Content-ID: <Pine.GSO.4.03.9902270717345.2983@leo>

---559023410-1804928587-920118034=:2983--
---559023410-851401618-920118034=:2983--


From dhcp-v4@bucknell.edu  Mon Mar  1 21:02:16 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11724
	for <dhc-archive@odin.ietf.org>; Mon, 1 Mar 1999 21:02:14 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id UAA05401;
	Mon, 1 Mar 1999 20:54:51 -0500 (EST)
Date: Mon, 1 Mar 1999 20:54:51 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9903012025570.4538-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-dhcpv6-14.txt (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


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		: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
	Author(s)	: J. Bound, C. Perkins
	Filename	: draft-ietf-dhc-dhcpv6-14.txt
	Pages		: 41
	Date		: 26-Feb-99
	
   The Dynamic Host Configuration Protocol (DHCPv6) enables DHCP
   servers to pass configuration information, via extensions, to IPv6
   nodes.  It offers the capability of automatic allocation of reusable
   network addresses and additional configuration flexibility.  This
   protocol is a stateful counterpart to the IPv6 Stateless Address
   Autoconfiguration protocol, and can be used separately or together
   with the latter to obtain configuration information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-14.txt

Internet-Drafts are also 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-dhcpv6-14.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-dhcpv6-14.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.



From dhcp-v4@bucknell.edu  Mon Mar  1 21:06:18 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11994
	for <dhc-archive@odin.ietf.org>; Mon, 1 Mar 1999 21:06:15 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id VAA32182;
	Mon, 1 Mar 1999 21:01:46 -0500 (EST)
Date: Mon, 1 Mar 1999 21:01:46 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9903012028070.4538-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-v6exts-11.txt (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


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		: Extensions for the Dynamic Host 
                          Configuration Protocol for IPv6
	Author(s)	: C. Perkins, J. Bound
	Filename	: draft-ietf-dhc-v6exts-11.txt
	Pages		: 36
	Date		: 26-Feb-99
	
   The Dynamic Host Configuration Protocol for IPv6 [4] (DHCPv6)
   provides a framework for passing configuration information to hosts
   on a TCP/IP network.  Configuration parameters and other control
   information are carried in typed data items that are stored in the
   'extensions' field of the DHCPv6 message.  The data items themselves
   are also called 'extensions.' This document specifies the current
   set of DHCPv6 extensions, which will be periodically updated as new
   extensions are defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-v6exts-11.txt

Internet-Drafts are also 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-v6exts-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-v6exts-11.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.



From dhcp-v4@bucknell.edu  Wed Mar  3 05:59:46 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05484
	for <dhc-archive@odin.ietf.org>; Wed, 3 Mar 1999 05:59:46 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id FAA28298;
	Wed, 3 Mar 1999 05:55:09 -0500 (EST)
Date: Wed, 3 Mar 1999 05:55:09 -0500 (EST)
Message-Id: <19990303114917.A6240@xray.mpe.mpg.de>
Errors-To: droms@bucknell.edu
Reply-To: hmb@xray.mpe.mpg.de
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Harald Baumgartner <hmb@xray.mpe.mpg.de>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: dhcp beginner question
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Mutt 0.95i
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0

Sorry,

i'm a newbie.

i got a Tektronix Printer and want to setup dhcp on joind at DEC-Unix V4.0B.

I want to use this printer at a permanent IP-Address with active ip snapshot
in the xjoin program.


When i boot the printer i got the error message: old lease, extended lease
and the printer got not his dhcp parameter.

Which times did it compare: provisional time, default lease time, Lease Granted, Lease Expiration = ...2038, Renewal Eligible At or Last Transaction (which
i cannot change)?

Any help would be appreciated.

			Thanks, H. Baumgartner


-- 
Harald Baumgartner Max-Planck-Inst. fuer Extraterrestrische Physik
                   Postf. 1603, D-85740, Garching bei Muenchen, Germany
                   Phone :(Country Code 49) 89 3299-3346 (Fax: -3569)
                   e-mail: hmb@mpe.mpg.de, MPE::HMB
		   http://www.xray.mpe.mpg.de/~hmb/


From dhcp-v4@bucknell.edu  Thu Mar  4 15:28:41 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12124
	for <dhc-archive@odin.ietf.org>; Thu, 4 Mar 1999 15:28:34 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id PAA25783;
	Thu, 4 Mar 1999 15:19:55 -0500 (EST)
Date: Thu, 4 Mar 1999 15:19:55 -0500 (EST)
Message-Id: <19990304194512.A16757@xray.mpe.mpg.de>
Errors-To: droms@bucknell.edu
Reply-To: hmb@xray.mpe.mpg.de
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Harald Baumgartner <hmb@xray.mpe.mpg.de>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCP beginner question
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Mutt 0.95i
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0

Hi Administrators,

could someone me explain why i got the error message: old lease   ?

I'm running joind on DEC-Unix 4.0B machine. I'm using xjoin to change the pa-
rameters, but i don't know why i got not the printer assigning ip-adddress
and got this error message above.

			Thanks, Harald
-- 
Harald Baumgartner Max-Planck-Inst. fuer Extraterrestrische Physik
                   Postf. 1603, D-85740, Garching bei Muenchen, Germany
                   Phone :(Country Code 49) 89 3299-3346 (Fax: -3569)
                   e-mail: hmb@mpe.mpg.de, MPE::HMB
		   http://www.xray.mpe.mpg.de/~hmb/


From dhcp-v4@bucknell.edu  Thu Mar  4 15:30:55 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12145
	for <dhc-archive@odin.ietf.org>; Thu, 4 Mar 1999 15:30:53 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id PAA18261;
	Thu, 4 Mar 1999 15:27:48 -0500 (EST)
Date: Thu, 4 Mar 1999 15:27:48 -0500 (EST)
Message-Id: <199903041928.OAA17460@cichlid.raleigh.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: narten@raleigh.ibm.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Thomas Narten <narten@raleigh.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: FYI: Remote Boot Protocol BOF (remboot)
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

Remote Boot Protocol BOF (remboot)

Thursday, March 18 at 1530-1730
===============================

Chair:  Michael Henry <mike.henry@intel.com>

DESCRIPTION:

The Remote Boot Protocol Working Group is chartered to define a standard 
protocol between the remote boot client and the responding server. The 
Working Group objective is to produce a protocol that insures remote boot 
clients, of arbitrary platform and instruction set architecture, will be
able to choose and obtain an appropriate boot program from a arbitrary 
variety of boot servers, without the necessity of site specific 
pre-configuration of the client.

The working group will consider existing remote boot methods. The protocol 
defined by the working group will be consistent with DHCP and the Service 
Location Protocol. The working group will coordinate with both the Dynamic 
Host Configuration Protocol and the Service Location Protocol Working
Groups.  The output of this WG will consist of a base architectural document 
that provides the framework for how remote boot will be done (i.e., defines 
the protocol), together with one or more documents defining the required 
capabilities of the remote boot client and the responding server. The 
protocol document will describe how the remote boot client will discover an 
appropriate boot server, how the client will identify itself to the boot 
server, and how the remote boot client will obtain a boot program. If 
possible, an existing protocol to locate a boot service (e.g. Service 
Location Protocol) will be used. IANA registration for types of remote boot 
clients and types of boot servers will be specified as part of the base 
protocol. Documenting necessary capabilities of the remote boot client and 
boot server will be done elsewhere (i.e., in standalone documents).

AGENDA:

1. Introduction and Agenda review
2. Problem Statement: Limitations of DHCP/bootfile remote boot - WG charter
   review
3. Review PXE boot protocol ID (draft-viswanathan-remote_boot-protocol-00.txt)
4. Review Multicast use in PXE boot protocol ID (draft-viswanathan-remote_boot-mtftp-00.txt)
5. Decision on consensus to pursue working group status.

Mailing Lists: 

REMOTE_BOOT@MAILBAG.INTEL.COM



From dhcp-v4@bucknell.edu  Thu Mar  4 18:56:57 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17472
	for <dhc-archive@odin.ietf.org>; Thu, 4 Mar 1999 18:56:56 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id SAA05525;
	Thu, 4 Mar 1999 18:53:44 -0500 (EST)
Date: Thu, 4 Mar 1999 18:53:44 -0500 (EST)
Message-Id: <D5E932F578EBD111AC3F00A0C96B1E6F02334080@orsmsx31.jf.intel.com>
Errors-To: droms@bucknell.edu
Reply-To: mike.henry@intel.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Henry, Mike" <mike.henry@intel.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: Remote Boot Protocol BOF (remboot)
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.2448.0)
Mime-Version: 1.0

FYI

To be added to the Remote_Boot mailing list associated w/ this BOF, send
mail to:

LISTSERV@MAILBAG.INTEL.COM (no subject line)
First line of message body:  SUBSCRIBE remote_boot  "your name"

 - Mike H.  3/4
-----------------
   Michael D. Henry
   Intel Architecture Lab / MPL, Intel Corp.
   (503) 264-9689
   mike.henry@intel.com



-----Original Message-----
From: Thomas Narten [mailto:narten@raleigh.ibm.com]
Sent: Thursday, March 04, 1999 12:28
To: Multiple recipients of list
Subject: FYI: Remote Boot Protocol BOF (remboot)


Remote Boot Protocol BOF (remboot)

Thursday, March 18 at 1530-1730
===============================

Chair:  Michael Henry <mike.henry@intel.com>

DESCRIPTION:

The Remote Boot Protocol Working Group is chartered to define a standard 
protocol between the remote boot client and the responding server. The 
Working Group objective is to produce a protocol that insures remote boot 
clients, of arbitrary platform and instruction set architecture, will be
able to choose and obtain an appropriate boot program from a arbitrary 
variety of boot servers, without the necessity of site specific 
pre-configuration of the client.

The working group will consider existing remote boot methods. The protocol 
defined by the working group will be consistent with DHCP and the Service 
Location Protocol. The working group will coordinate with both the Dynamic 
Host Configuration Protocol and the Service Location Protocol Working
Groups.  The output of this WG will consist of a base architectural document

that provides the framework for how remote boot will be done (i.e., defines 
the protocol), together with one or more documents defining the required 
capabilities of the remote boot client and the responding server. The 
protocol document will describe how the remote boot client will discover an 
appropriate boot server, how the client will identify itself to the boot 
server, and how the remote boot client will obtain a boot program. If 
possible, an existing protocol to locate a boot service (e.g. Service 
Location Protocol) will be used. IANA registration for types of remote boot 
clients and types of boot servers will be specified as part of the base 
protocol. Documenting necessary capabilities of the remote boot client and 
boot server will be done elsewhere (i.e., in standalone documents).

AGENDA:

1. Introduction and Agenda review
2. Problem Statement: Limitations of DHCP/bootfile remote boot - WG charter
   review
3. Review PXE boot protocol ID
(draft-viswanathan-remote_boot-protocol-00.txt)
4. Review Multicast use in PXE boot protocol ID
(draft-viswanathan-remote_boot-mtftp-00.txt)
5. Decision on consensus to pursue working group status.

Mailing Lists: 

REMOTE_BOOT@MAILBAG.INTEL.COM


From dhcp-v4@bucknell.edu  Thu Mar  4 19:00:17 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17590
	for <dhc-archive@odin.ietf.org>; Thu, 4 Mar 1999 19:00:16 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id SAA20834;
	Thu, 4 Mar 1999 18:58:48 -0500 (EST)
Date: Thu, 4 Mar 1999 18:58:48 -0500 (EST)
Message-Id: <v04011707b304bb2fa7b6@[134.82.7.116]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Agenda for WG meetings in Minneapolis
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 DHC WG will meet twice in Minneapolis.  On Thursday, 3/18, the WG will
meet at 0900-1130 to discuss the latest DHCPv6 drafts.  The WG will meet
again at 1300-1500 to discuss DHCPv4 issues.  Here is the current agenda
for the DHCPv4 meeting:

Report from LDAP Schema interim meeting		Bernie Volz, Process Software
Report from Failover Protocol interim meeting	Kim Kinnear, Cisco
DHCP authentication				Bill Arbaugh, UPenn
DHCP-DNS interaction				Mark Stapp, Cisco

If you would like time on the agenda, please send me a request for a slot.
If you've sent me a request and I don't currently have you on the agenda,
please let me know...

- Ralph



From dhcp-v4@bucknell.edu  Mon Mar  8 13:02:19 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05285
	for <dhc-archive@odin.ietf.org>; Mon, 8 Mar 1999 13:02:18 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id MAA14410;
	Mon, 8 Mar 1999 12:56:08 -0500 (EST)
Date: Mon, 8 Mar 1999 12:56:08 -0500 (EST)
Message-Id: <00007240.@framatome.fr>
Errors-To: droms@bucknell.edu
Reply-To: jylebouc@framatome.fr
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: jylebouc@framatome.fr (Jean-Yves LEBOUC)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: IP address problem with HP printer G.07.03 and Solaris 2.5
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
Content-Transfer-Encoding: 7bit

     I use dhcp with all of my TCP/IP nodes. The implementation of the dhcp 
     server is on a SUN SparcStation 1000 in Solaris 2.5, version 1.0, 
     revision 96.10.10.20.35.
     I have a problem with a HP printer client, HP4000N in G.07.03 microlog 
     revision. The ulterior version, G.07.17, have the same problem, the 
     previous version, G.05.35, have no problem.
     I use dhcp in static mode, one IP address for one MAC address. The 
     problem :
     - in response to the printer dhcp request the dhcp server give the
     TCP/IP parameters,
     - then the printer is correctly set,
     - after a few time (between few second and one minute) the printer
     take its default IP address (192.0.0.192) without lost any other 
     TCP/IP parameters (gateway, subnetmask, server address, ...).
     The lease is negociable and the value affected is 43200 secondes (12 
     hours).
     Can you help me ?
     Thank's in advance.
     Jean-Yves.


From dhcp-v4@bucknell.edu  Tue Mar  9 06:22:10 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09525
	for <dhc-archive@odin.ietf.org>; Tue, 9 Mar 1999 06:22:09 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id GAA20373;
	Tue, 9 Mar 1999 06:14:02 -0500 (EST)
Date: Tue, 9 Mar 1999 06:14:02 -0500 (EST)
Message-Id: <v04011702b30aaba97c3f@[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: dhcp-v4@bucknell.edu (by way of Ralph Droms)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Protocol Action: 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


The IESG has approved the Internet-Draft 'DHCP Option to Disable
Stateless Auto-Configuration in IPv4 Clients'
<draft-ietf-dhc-autoconfig-04.txt> as a Proposed Standard.  This
document is the product of the Dynamic Host Configuration Working
Group.  The IESG contact persons are Jeffrey Burgan and Thomas Narten.


Technical Summary

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 automatically generating a link-local IP address
which will allow them to communicate with other hosts on the same
link.  This address will not allow the OS to communicate with anything
beyond a router.  However, some sites depend on the fact that a host
with no DHCP response will have no IP address.  This document
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 generate an IP address it's own.

Working Group Summary

There was strong consensus within WG for moving this document forward.

Protocol Quality

This document has been reviewed for the IESG by Thomas Narten.


From dhcp-v4@bucknell.edu  Tue Mar  9 18:47:01 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21803
	for <dhc-archive@odin.ietf.org>; Tue, 9 Mar 1999 18:47:00 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id SAA03820;
	Tue, 9 Mar 1999 18:42:40 -0500 (EST)
Date: Tue, 9 Mar 1999 18:42:40 -0500 (EST)
Message-Id: <D5E932F578EBD111AC3F00A0C96B1E6F023340D7@orsmsx31.jf.intel.com>
Errors-To: droms@bucknell.edu
Reply-To: mike.henry@intel.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Henry, Mike" <mike.henry@intel.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Remote Boot Protocol BOF (remboot) and  PXE Info source
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.2448.0)
Mime-Version: 1.0

My apologies in advance to those who have already received some or all of
this information.

Per a number of requests, here, in one place, are links to various sources
of information on the Wired for Management PXE remote boot protocol, IDs
related to remote boot from the PXE developers, and the BOF meeting on
Remote Boot.

The Wired for Managment specifications (WfM 2.0 Baseline, PXE 2.0, and BIS
1.0), Product Development Kits, and Sowftware Development Kits, can be found
at http://developer.intel.com/ial/wfm/tools/index.htm .

Related Internet Drafts submitted so far may be found at:
http://www.ietf.org/internet-drafts/draft-viswanathan-remote_boot-protocol-0
0.txt
http://www.ietf.org/internet-drafts/draft-viswanathan-remote_boot-mtftp-00.t
xt
http://www.ietf.org/internet-drafts/draft-dittert-host-sys-char-03.txt

We have started a mailing list for remote boot.  The mailing list is to
provide a forum to comment on Internet Drafts related to remote boot, and on
the possible formation of a Remote_Boot IETF Working Group to, hopefully,
shepherd some of the drafts in to Internet Standards.

There will be a BOF (Birds of Feather) meeting at the upcoming IETF meeting
in Minneapolis (week of 3/15) to determine interest in pursuing this
objective.  A BOF meeting schedule, agenda, and draft charter for the group
are included below.


To be added to the Remote_Boot mailing list, send mail to:

LISTSERV@MAILBAG.INTEL.COM (no subject line)
First line of message body:  SUBSCRIBE remote_boot  "your name"  (no, you do
not include the quote marks)



 - Mike H.  3/9
-----------------
   Michael D. Henry
   Intel Architecture Lab / MPL, Intel Corp.
   (503) 264-9689
   mike.henry@intel.com



-----Original Message-----
From: Thomas Narten [mailto:narten@raleigh.ibm.com]
Sent: Thursday, March 04, 1999 12:28
To: Multiple recipients of list
Subject: FYI: Remote Boot Protocol BOF (remboot)


Remote Boot Protocol BOF (remboot)

Thursday, March 18 at 1530-1730
===============================

Chair:  Michael Henry <mike.henry@intel.com>

DESCRIPTION:

The Remote Boot Protocol Working Group is chartered to define a standard 
protocol between the remote boot client and the responding server. The 
Working Group objective is to produce a protocol that insures remote boot 
clients, of arbitrary platform and instruction set architecture, will be
able to choose and obtain an appropriate boot program from a arbitrary 
variety of boot servers, without the necessity of site specific 
pre-configuration of the client.

The working group will consider existing remote boot methods. The protocol 
defined by the working group will be consistent with DHCP and the Service 
Location Protocol. The working group will coordinate with both the Dynamic 
Host Configuration Protocol and the Service Location Protocol Working
Groups.  The output of this WG will consist of a base architectural document

that provides the framework for how remote boot will be done (i.e., defines 
the protocol), together with one or more documents defining the required 
capabilities of the remote boot client and the responding server. The 
protocol document will describe how the remote boot client will discover an 
appropriate boot server, how the client will identify itself to the boot 
server, and how the remote boot client will obtain a boot program. If 
possible, an existing protocol to locate a boot service (e.g. Service 
Location Protocol) will be used. IANA registration for types of remote boot 
clients and types of boot servers will be specified as part of the base 
protocol. Documenting necessary capabilities of the remote boot client and 
boot server will be done elsewhere (i.e., in standalone documents).

AGENDA:

1. Introduction and Agenda review
2. Problem Statement: Limitations of DHCP/bootfile remote boot - WG charter
   review
3. Review PXE boot protocol ID
(draft-viswanathan-remote_boot-protocol-00.txt)
4. Review Multicast use in PXE boot protocol ID
(draft-viswanathan-remote_boot-mtftp-00.txt)
5. Decision on consensus to pursue working group status.

Mailing Lists: 

REMOTE_BOOT@MAILBAG.INTEL.COM


From dhcp-v4@bucknell.edu  Wed Mar 10 12:43:40 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14684
	for <dhc-archive@odin.ietf.org>; Wed, 10 Mar 1999 12:43:39 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id MAA18342;
	Wed, 10 Mar 1999 12:40:38 -0500 (EST)
Date: Wed, 10 Mar 1999 12:40:38 -0500 (EST)
Message-Id: <v0401170bb30c5b52d003@[134.82.7.102]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Agenda for Minneapolis DHC wg meetings
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

I've posted the agenda for the two meetings at
http://www.dhcp.org/9903-meeting.html

- Ralph



From dhcp-v4@bucknell.edu  Wed Mar 10 21:42:20 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20577
	for <dhc-archive@odin.ietf.org>; Wed, 10 Mar 1999 21:42:19 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id VAA09649;
	Wed, 10 Mar 1999 21:40:35 -0500 (EST)
Date: Wed, 10 Mar 1999 21:40:35 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9903102058460.525-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Re: Agenda for Minneapolis DHC wg meetings 
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

On Wed, 10 Mar 1999, Jim Bound wrote:
> tried to get to this URL..
> 
> was trying to connect to www.dhc.org but got no ack.
> 
> Is it down.. my other web stuff is working..

Our network folks renumbered in December, but the old DNS entry for
www.dhcp.org may still be cached.  The correct IP address is
134.82.56.120.

- Ralph






From dhcp-v4@bucknell.edu  Fri Mar 12 08:06:19 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01347
	for <dhc-archive@odin.ietf.org>; Fri, 12 Mar 1999 08:06:18 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id IAA08913;
	Fri, 12 Mar 1999 08:03:20 -0500 (EST)
Date: Fri, 12 Mar 1999 08:03:20 -0500 (EST)
Message-Id: <v04011703b30eba99e9f2@[134.82.7.109]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: www.dhcp.org unreachable
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

Thanks to Matt Crawford for correctly diagnosing the problem - I've sent a
request to Internic to update their records about the new address for
www.dhcp.org.

For now, Rhandeev Singh suggests using dns.dhcp.org to access the DHCP web
site...

- Ralph



From dhcp-v4@bucknell.edu  Tue Mar 16 14:54:13 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13119
	for <dhc-archive@odin.ietf.org>; Tue, 16 Mar 1999 14:54:12 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id OAA28945;
	Tue, 16 Mar 1999 14:46:22 -0500 (EST)
Date: Tue, 16 Mar 1999 14:46:22 -0500 (EST)
Message-Id: <199903161928.OAA23186@funnel.cisco.com>
Errors-To: droms@bucknell.edu
Reply-To: kkinnear@cisco.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Kim Kinnear <kkinnear@cisco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Interim Failover Meeting Minutes
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: QUALCOMM Windows Eudora Pro Version 4.0.2 

	
I just sent out on the dhcp-serve@bucknell.edu list
the minutes from the failover meeting held here at
the Cisco facilities in Chelmsford MA on February
10/11, 1999.

Since they are something like 8 pages in length, I
thought that perhaps sending them all to dhcp-v4
would not be the best idea.

Any of you that are not on the dhcp-serve list
(i.e., that haven't already received the minutes)
that want them, just send me mail and I'll send them
to you.  

In the fullness of time, I'll probably prevail on 
Ralph to put them up on the DHCP web site he
maintains, but until then just let me know
if you want a copy.

Cheers -- Kim



From dhcp-v4@bucknell.edu  Thu Mar 18 00:27:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11329
	for <dhc-archive@odin.ietf.org>; Thu, 18 Mar 1999 00:27:11 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id AAA04760;
	Thu, 18 Mar 1999 00:22:34 -0500 (EST)
Date: Thu, 18 Mar 1999 00:22:34 -0500 (EST)
Message-Id: <v04011716b31623ffd8b8@[134.82.56.56]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: Upon DHCPRELEASE, client starts at INIT-REBOOT or INIT state?
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:52 PM -0500 12/14/98, Greg Padden wrote:
>After reading RFC 2131 it was unclear to me of the behavior of the client
>software after the client has issued a DHCPRELEASE?
>
>Will it start at the INIT-REBOOT or the INIT state?

The client should start in INIT state after a DHCPRELEASE.  I had a brief
conversation with Apple about their client behavior and they will fix the
client to fo to INIT state after a DHCPRELEASE.

- Ralph



From dhcp-v4@bucknell.edu  Sat Mar 20 17:53:10 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07389
	for <dhc-archive@odin.ietf.org>; Sat, 20 Mar 1999 17:53:07 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id RAA14190;
	Sat, 20 Mar 1999 17:48:51 -0500 (EST)
Date: Sat, 20 Mar 1999 17:48:51 -0500 (EST)
Message-Id: <199903202228.RAA07051@grosse.fugue.com>
Errors-To: droms@bucknell.edu
Reply-To: mellon@isc.org
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Ted Lemon <mellon@isc.org>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCPRELEASE policy (specifically WRT OpenTransport)...
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


At the IETF WG meeting on Thursday, somebody from Apple whose name I
have of course spaced got up and talked a bit about the OpenTransport
DHCPRELEASE policy, and said that in the next release of
OpenTransport, the user would be able to configure the policy that the
OT client would use when powering down - whether it would send a
DHCPRELEASE and then power back on into the INIT state, or not send a
DHCPRELEASE and, if possible, power back on into the INIT-REBOOT
state.

It occurs to me that this is something that a site administrator might
want to control as a global policy.   The OpenTransport client also
has a setting to decide whether or not it should get a lease when it
first needs an IP address, or always maintain a lease.   Again, this
is something that some sites might want to administer centrally.

I'd like to suggest that we create an option that controls these two
configuration settings, and possibly others if people can think of
them.  Essentially, when the OT client (and hopefully other clients)
acquires a lease, it sets these two flags based on an option sent in
the DHCPACK packet.  The send-dhcprelease flag would take effect on
the current lease, and the relinquish-address flag would as well.  The
relinquish-address flag would remain in effect until a DHCPACK was
received that had a different setting.

Naturally, it would also be useful to hack the UI to allow the user to
override these settings (maybe with a "allow DHCP server to modify
these settings" toggle), but I think that exposing this functionality
to the DHCP server administrator would be a big win - otherwise,
people who don't know any better are likely to wind up with the wrong
policy configured in their client.

If this seems agreeable, I'd like to whip up a draft and get it
rolling quickly, so that the time during which reconfiguring clients
with respect to these two settings involves having somebody touch the
client machine is minimized.

So what do folks at Apple and Microsoft (as well as other WG
participants) think of this?  If the answer is "sounds good, but don't
have time to push the draft," I still want to hear from you.

Thanks!

			       _MelloN_


From dhcp-v4@bucknell.edu  Mon Mar 22 00:48:37 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08482
	for <dhc-archive@odin.ietf.org>; Mon, 22 Mar 1999 00:48:29 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id AAA27921;
	Mon, 22 Mar 1999 00:42:19 -0500 (EST)
Date: Mon, 22 Mar 1999 00:42:19 -0500 (EST)
Message-Id: <3.0.6.32.19990321215416.00919100@postoffice.worldnet.att.net>
Errors-To: droms@bucknell.edu
Reply-To: robertgcole@worldnet.att.net
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Robert G. Cole" <robertgcole@worldnet.att.net>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCPv4 interoperability testing at Connectathon '99
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: QUALCOMM Windows Eudora Light Version 3.0.6 (32)

Hi Mike,

During the meeting last week you mentioned wanting to stimulate customer
interest
in Connectathon.  Have you considered writing an article in a trade rag
like Network
World?  You could cover the recent work in the working group, e.g., MIB
development for
manageability, interserver for reliability, dynamic DNS updates, security,
IPv6, and support 
for Connectathon for interoperability testing.  You could wrap up with a
table or list 
of questions for potential customers to ask of their prospective vendors.

It has been my experience that when articles like this are written, the
"questions to ask vendors"
will end up in RFPs, etc.

Just an idea.

Bob


AT&T

330 St. Johns Street, 2nd Floor
Havre de Grace, MD
		21078

robertgcole@worldnet.att.net
+1 410 939-8732


From dhcp-v4@bucknell.edu  Mon Mar 22 15:25:16 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27990
	for <dhc-archive@odin.ietf.org>; Mon, 22 Mar 1999 15:25:15 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id PAA26564;
	Mon, 22 Mar 1999 15:15:49 -0500 (EST)
Date: Mon, 22 Mar 1999 15:15:49 -0500 (EST)
Message-Id: <21839C593E75D211BF7800805FCCD0264B077D@msgsrv03.srv.PacBell.COM>
Errors-To: droms@bucknell.edu
Reply-To: RBHIBBS@msg.pacbell.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "HIBBS, BARR (PB)" <RBHIBBS@msg.pacbell.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: DHCPRELEASE policy (specifically WRT OpenTransport)...
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


Ted, et al.,

while I haven't thought through all of the implications of doing this, my
first reaction is to support the concept.  This, of course, presupposes that
client stack vendors would incorporate support for such an option.

In our recent experience with renumbering and conversion of formerly static
clients to dynamic addressing, we've occasionally been frustrated to find
that on the night of the conversion, despite our most careful planning, we
might be 3-7 addresses short of what we need to convert an entire office,
meaning middle-of-the-night conference calls, database reconfiguration, and
two or three people who don't get to sleep because they must baby-sit the
troubled clients.  This has a cascading effect on the next night's
conversion, so even a small problem of insufficient addresses can be a big
deal for us.

The use of the proposed option won't, of course, completely fix our
conversion problem, but combined with the other things we already do should
actually improve our particular situation.

--Barr


> ----------
> From: 	Ted Lemon[SMTP:mellon@isc.org]
> Sent: 	Saturday, March 20, 1999 2:51 PM
> To: 	Multiple recipients of list
> Subject: 	DHCPRELEASE policy (specifically WRT OpenTransport)...
> 
> 
[ ... stuff deleted ... ]

> I'd like to suggest that we create an option that controls these two
> configuration settings, and possibly others if people can think of
> them.  Essentially, when the OT client (and hopefully other clients)
> acquires a lease, it sets these two flags based on an option sent in
> the DHCPACK packet.  The send-dhcprelease flag would take effect on
> the current lease, and the relinquish-address flag would as well.  The
> relinquish-address flag would remain in effect until a DHCPACK was
> received that had a different setting.
> 
[ ... more stuff deleted ... ]



From dhcp-v4@bucknell.edu  Mon Mar 22 20:23:37 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06201
	for <dhc-archive@odin.ietf.org>; Mon, 22 Mar 1999 20:23:37 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id UAA13651;
	Mon, 22 Mar 1999 20:16:53 -0500 (EST)
Date: Mon, 22 Mar 1999 20:16:53 -0500 (EST)
Message-Id: <199903230032.QAA00229@goose.prod.itd.earthlink.net>
Errors-To: droms@bucknell.edu
Reply-To: rabreen@earthlink.net
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: "Robert Breen" <rabreen@earthlink.net>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCPRELEASE policy (specifically WRT OpenTransport)...
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
Content-Transfer-Encoding: 7bit

I was at that session.  Ted, I totally agree with your thoughts.  I was the
person who indicated we ran over 120,000 DHCP clients on our network (I
wish I could publish the name of the company, but they lawyers go crazy)
and I had thought about way in which our Windows 95, Windows NT and various
flavors of Unix clients handled this same situation.  For instance, the
pre-winsock 2.0 Windows 95 clients do not perform a release when shutting
down, but the post-winsock 2.0 Windows 95 clients do.  For some subnets
this makes sense.  Our remote subnets were we know we have a lot of mobile
users (read laptops...) could be configured to release their IP address
upon shutdown, but it doesn't make sense on our subnets composed mostly of
desktop machines that seldomly move.  The organization I work for is lucky,
we can say with some certainty which subnets fall in which categories.  

	It might also be nice, for instance, to configure a subnet that was
particularly tight on IP addresses to have clients release their IP address
upon shutdown (in addition to shorter lease times), so that address could
be thrown back in the available pool quicker than waiting for lease times
to expire.  I see lots of uses for this option.

I'm not up on how to write drafts, but I'd be happy to help in any way
possible.

Bob Breen
rabreen@earthlink.net

----------
> From: Ted Lemon <mellon@isc.org>
> To: Multiple recipients of list <dhcp-v4@bucknell.edu>
> Subject: DHCPRELEASE policy (specifically WRT OpenTransport)...
> Date: Saturday, March 20, 1999 4:54 PM
> 
> 
> At the IETF WG meeting on Thursday, somebody from Apple whose name I
> have of course spaced got up and talked a bit about the OpenTransport
> DHCPRELEASE policy, and said that in the next release of
> OpenTransport, the user would be able to configure the policy that the
> OT client would use when powering down - whether it would send a
> DHCPRELEASE and then power back on into the INIT state, or not send a
> DHCPRELEASE and, if possible, power back on into the INIT-REBOOT
> state.
> 
> It occurs to me that this is something that a site administrator might
> want to control as a global policy.   The OpenTransport client also
> has a setting to decide whether or not it should get a lease when it
> first needs an IP address, or always maintain a lease.   Again, this
> is something that some sites might want to administer centrally.
> 
> I'd like to suggest that we create an option that controls these two
> configuration settings, and possibly others if people can think of
> them.  Essentially, when the OT client (and hopefully other clients)
> acquires a lease, it sets these two flags based on an option sent in
> the DHCPACK packet.  The send-dhcprelease flag would take effect on
> the current lease, and the relinquish-address flag would as well.  The
> relinquish-address flag would remain in effect until a DHCPACK was
> received that had a different setting.
> 
> Naturally, it would also be useful to hack the UI to allow the user to
> override these settings (maybe with a "allow DHCP server to modify
> these settings" toggle), but I think that exposing this functionality
> to the DHCP server administrator would be a big win - otherwise,
> people who don't know any better are likely to wind up with the wrong
> policy configured in their client.
> 
> If this seems agreeable, I'd like to whip up a draft and get it
> rolling quickly, so that the time during which reconfiguring clients
> with respect to these two settings involves having somebody touch the
> client machine is minimized.
> 
> So what do folks at Apple and Microsoft (as well as other WG
> participants) think of this?  If the answer is "sounds good, but don't
> have time to push the draft," I still want to hear from you.
> 
> Thanks!
> 
> 			       _MelloN_


From dhcp-v4@bucknell.edu  Tue Mar 23 12:46:39 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23660
	for <dhc-archive@odin.ietf.org>; Tue, 23 Mar 1999 12:46:34 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id MAA02493;
	Tue, 23 Mar 1999 12:38:29 -0500 (EST)
Date: Tue, 23 Mar 1999 12:38:29 -0500 (EST)
Message-Id: <8525673D.005C7B77.00@d54mta04.raleigh.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: pratikg@us.ibm.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: pratikg@us.ibm.com
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: DHCPRELEASE policy (specifically WRT OpenTransport)...
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





Ted

 This is a good idea. OS/2 Clients have been doing this for a few years via
a client policy that the user or a site administrator( via a common client
config files distribution)  could  choose. It would be great if the DHCP
server served this policy.

The only thing to watch out for is that a server should not expect to have
a perfect cleanup solution since the DHCPRELEASE packet may be dropped or
the client may not be able to send it out in time due to the shutdown
process being initiated.

regards,

Pratik Gupta
pratikg@us.ibm.com



Ted Lemon <mellon@isc.org> on 03/20/99 05:51:38 PM

Please respond to mellon@isc.org

To:   Multiple recipients of list <dhcp-v4@bucknell.edu>
cc:    (bcc: Pratik Gupta/Raleigh/IBM)
Subject:  DHCPRELEASE policy (specifically WRT OpenTransport)...






At the IETF WG meeting on Thursday, somebody from Apple whose name I
have of course spaced got up and talked a bit about the OpenTransport
DHCPRELEASE policy, and said that in the next release of
OpenTransport, the user would be able to configure the policy that the
OT client would use when powering down - whether it would send a
DHCPRELEASE and then power back on into the INIT state, or not send a
DHCPRELEASE and, if possible, power back on into the INIT-REBOOT
state.

It occurs to me that this is something that a site administrator might
want to control as a global policy.   The OpenTransport client also
has a setting to decide whether or not it should get a lease when it
first needs an IP address, or always maintain a lease.   Again, this
is something that some sites might want to administer centrally.

I'd like to suggest that we create an option that controls these two
configuration settings, and possibly others if people can think of
them.  Essentially, when the OT client (and hopefully other clients)
acquires a lease, it sets these two flags based on an option sent in
the DHCPACK packet.  The send-dhcprelease flag would take effect on
the current lease, and the relinquish-address flag would as well.  The
relinquish-address flag would remain in effect until a DHCPACK was
received that had a different setting.

Naturally, it would also be useful to hack the UI to allow the user to
override these settings (maybe with a "allow DHCP server to modify
these settings" toggle), but I think that exposing this functionality
to the DHCP server administrator would be a big win - otherwise,
people who don't know any better are likely to wind up with the wrong
policy configured in their client.

If this seems agreeable, I'd like to whip up a draft and get it
rolling quickly, so that the time during which reconfiguring clients
with respect to these two settings involves having somebody touch the
client machine is minimized.

So what do folks at Apple and Microsoft (as well as other WG
participants) think of this?  If the answer is "sounds good, but don't
have time to push the draft," I still want to hear from you.

Thanks!

                      _MelloN_








From dhcp-v4@bucknell.edu  Tue Mar 23 19:12:05 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02700
	for <dhc-archive@odin.ietf.org>; Tue, 23 Mar 1999 19:12:02 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id TAA10530;
	Tue, 23 Mar 1999 19:05:22 -0500 (EST)
Date: Tue, 23 Mar 1999 19:05:22 -0500 (EST)
Message-Id: <Pine.GSO.4.03.9903231830240.7368-100000@leo>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: I-D ACTION:draft-ietf-dhc-dhcp-dns-09.txt (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

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		: Interaction between DHCP and DNS
	Author(s)	: Y. Rekhter, M. Stapp
	Filename	: draft-ietf-dhc-dhcp-dns-09.txt
	Pages		: 13
	Date		: 22-Mar-98
	
   DHCP provides a powerful mechanism for IP host autoconfiguration.
   However, the autoconfiguration provided by DHCP does not include
   updating DNS, and specifically updating the name to address and
   address to name mappings maintained by DNS.
 
   This document specifies how DHCP clients and servers should use the
   Dynamic DNS Updates mechanism to update the DNS name to address and
   address to name mapping, so that the mappings for DHCP clients would
   be consistent with the IP addresses that the clients acquire via
   DHCP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcp-dns-09.txt

Internet-Drafts are also 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-dhcp-dns-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-dhcp-dns-09.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.



From dhcp-v4@bucknell.edu  Tue Mar 23 22:58:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09530
	for <dhc-archive@odin.ietf.org>; Tue, 23 Mar 1999 22:58:11 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id WAA11194;
	Tue, 23 Mar 1999 22:53:19 -0500 (EST)
Date: Tue, 23 Mar 1999 22:53:19 -0500 (EST)
Message-Id: <v04011709b31e06d54a97@[209.173.86.19]>
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: DHCPRELEASE policy (specifically WRT OpenTransport)...
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 CARL.SMITH@ENG.SUN.COM follows.
-----------------------------------------------------------------------
> I'd like to suggest that we create an option that controls these two
> configuration settings, and possibly others if people can think of
> them.

	Excellent idea.  The first of these (``send-dhcprelease'') is
definitely something that our IR folks could have used.  The fact that
we don't release addresses when shutting down was one of the first things
they complained about (and set out to work around) when converting to
use DHCP for a hotelling system they were deploying.

			Carl


From dhcp-v4@bucknell.edu  Tue Mar 23 22:58:12 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09531
	for <dhc-archive@odin.ietf.org>; Tue, 23 Mar 1999 22:58:11 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id WAA07664;
	Tue, 23 Mar 1999 22:54:34 -0500 (EST)
Date: Tue, 23 Mar 1999 22:54:34 -0500 (EST)
Message-Id: <v0401170ab31e070054b4@[209.173.86.19]>
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-dhcp-dns-09.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		: Interaction between DHCP and DNS
	Author(s)	: Y. Rekhter, M. Stapp
	Filename	: draft-ietf-dhc-dhcp-dns-09.txt
	Pages		: 13
	Date		: 22-Mar-98

   DHCP provides a powerful mechanism for IP host autoconfiguration.
   However, the autoconfiguration provided by DHCP does not include
   updating DNS, and specifically updating the name to address and
   address to name mappings maintained by DNS.

   This document specifies how DHCP clients and servers should use the
   Dynamic DNS Updates mechanism to update the DNS name to address and
   address to name mapping, so that the mappings for DHCP clients would
   be consistent with the IP addresses that the clients acquire via
   DHCP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcp-dns-09.txt

Internet-Drafts are also 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-dhcp-dns-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-dhcp-dns-09.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-dhcp-dns-09.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-dhcp-dns-09.txt>


From dhcp-v4@bucknell.edu  Tue Mar 23 22:58:44 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09561
	for <dhc-archive@odin.ietf.org>; Tue, 23 Mar 1999 22:58:42 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id WAA15691;
	Tue, 23 Mar 1999 22:55:06 -0500 (EST)
Date: Tue, 23 Mar 1999 22:55:06 -0500 (EST)
Message-Id: <v04011705b31e054eef1a@[209.173.86.19]>
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: DHCPNAK
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 HYUNG@YAGOSYS.COM follows.
------------------------------------------------------------------

[Previously sent to dhcp-impl but didn't get a response,
 so trying dhcp-v4 now...]

Hi,

I've read the RFCs already but there is something I am
not clear about the DHCPNAK packet.

If I am a relay agent and I receive a DHCPNAK packet from the
server, how should I forward the packet to the client if the
DHCPNAK packet has:

1. a broadcast bit of 0 (in the flag)
2. yiaddr is 0
3. ciaddr is 0

I am assuming that if the broadcast bit is 0, I should NOT
broadcast the reply but instead unicast it to the client.  Yet,
neither yiaddr nor ciaddr contains the client's IP address.
As a matter of fact, there is nothing in the packet indicating
the client's IP address.  It appears the only way I can send
the packet back is to broadcast it regardless of what the
broadcast bit says.  First, is that the right thing to do?
Second, is the server behaving correctly by sending me the
above DHCPNAK in the first place?

Please reply directly to me since I don't subscribe to this list.

Thanks in advance.

Hank


From dhcp-v4@bucknell.edu  Fri Mar 26 19:23:40 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08307
	for <dhc-archive@odin.ietf.org>; Fri, 26 Mar 1999 19:23:38 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id TAA28662;
	Fri, 26 Mar 1999 19:15:08 -0500 (EST)
Date: Fri, 26 Mar 1999 19:15:08 -0500 (EST)
Message-Id: <4.0.2.19990326182233.0116e2f0@funnel.cisco.com>
Errors-To: droms@bucknell.edu
Reply-To: mjs@cisco.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Mark Stapp <mjs@cisco.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: draft-ietf-dhc-dhcp-dns-09.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
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 

Robert,

Many thanks for the thorough comments. My responses are inline:

At 09:52 PM 3/26/99 +1100, Robert Elz wrote:
>I have a few difficulties with some of what is in
>
>	draft-ietf-dhc-dhcp-dns-09.txt
>
>Most importantly (and then in decreasing order thereafter), I think, is ...
>
>   In addition, if the Client FQDN option carried in the DHCPREQUEST
>   message has its Flags field set to 1, then the server MUST originate
>   an update for the A RR (associated with the FQDN carried in the
>   option).
>
[ ... ]
>  The MUST in the
>quoted text needs to be (at a minimum) qualified, to indicate that this need
>only be attempted if the the dhcp server has the necessary credentials for
>the FQDN supplied.

I'll try to make this clearer. The purpose of this flag is to allow the
client to indicate to the server that the client will _not_ perform an
update on the client's name. The draft certainly shouldn't imply that the
server should act in an arbitrary way in that case, especially if the
server knows that it cannot update a name like the one the client has sent.

>
>  It should probably actually say that it MUST NOT attempt
>to update the A record in any other case.
>
>

I don't think that's correct: the client might not send anything, or the
server might be configured to perform the update (possibly because only it
has the necessary credentials) whether the client sets this flag or not
(see section 3, para. 3).

>
>Then, something, somewhere, needs to actually say explicitly that each of
>the Flags, RCODE1 and RCODE2 fields is one byte long.   That's strongly
>suggested, but never actually stated.  
>

Will do.

>Also, the encoding of the domain name
>field isn't stated.  I'd strongly suggest encoding it using the same method
>that is used in DNS packets (without name compression, of course), rather
>than attempting to encode it as a text string (which leads to all kinds of
>complications).
>
>

The fqdn option is a DHCP option, and it's currently an ASCII string like
the existing host-name and domain-name options. I'm inclined to leave it
that way unless there's clear agreement that it's insufficient.

>
>Next most importantly, there seems to be no discussion about what should be
>done in the event of a conflict - that is, where a dhcp server has been 
>configured to supply a particular host name to the client, yet the client
>uses this new option to request a different fqdn.
>

This is really an administrative matter. Sites may choose to allow their
servers to accept clients' suggestions, or rely on the servers' own notions
of the names the clients should receive. I'll add words to that effect.

>
>Then wrt ...
>
>   If a server terminates a lease on an address prior to the lease
>   expiration time, the server SHOULD ...
>
>Is there actually a DHCP way that can be done? [...]
>

A server can reply to a client's request with a NAK, and the client will
give up its current lease and attempt to acquire a new one. If that occurs,
the server should clean up the DNS.

>
>Perhaps less serious ...
>
>   If a client that owns/maintains is own FQDN wants to be responsible
>   for updating the FQDN to IP address mapping for the FQDN and
>   address(es) used by the client, then the client MUST include the
>   Client FQDN option in the DHCPREQUEST message originated by the
>   client.
>
>I would have thought that if a client wants to maintain its FQDN to IP
>mapping, and doesn't care about the address -> name mapping, then it ought
>simply be able to update the A record itself, and there's no need to ever
>tell the DHCP server anything about it at all. [...]
>

The sentence you've quoted appears immediately after this one: "The
following describes behavior of a DHCP client that implements the Client
FQDN option." Sites whose administrators don't care about this option can
use clients which don't implement it. Hopefully, the cooperation that the
draft describes is useful, and clients will implement it.

>
>Next:
>
>   If a client releases its address lease prior to the lease expiration
>   time and the client is responsible for updating its A RR(s), the
>   client SHOULD delete the A RR
>
>I'd like to see a justification for that SHOULD (rather than just MAY).
>In practice, clients rarely release leases anyway, they mostly just switch
>off and go away, abandoning the lease (if it expires before they're ready
>to use it again). [...]
>

Dangling names are seen as a very real administrative problem in many
organizations. There are popular clients which do release their leases, and
their behavior needs to be accounted for in the draft. If a client accepts
responsibility for its name, it should make every effort not to leave the
name behind when it's no longer in use.

>
>I believe that the implication that a client using TSIG will automatically
>have authority to update any name in a zone is incorrect.   That might be
>true, but isn't necessarily true (as I understand TSIG).  A TSIG association
>is simply an agreement between a server and a client - that is, it is the
>evidence of that agreement having been made in the past.   Exactly what
>authority that grants to the client is stated nowhere at all, anything is
>possible to be contained in the agreement that TSIG is evidence of.
>It would be quite possible (if a maintenance nightmare) for a server to
>have established separate TSIG associations with every potential client,
>annd then to allow each TSIG association permission to update exactly one
>A record, and nothing else.
>

I believe you're right, and I think it's likely that sites which wish to
have secure dns updates initiated by clients will use DNSSEC. TSIG will be
very useful for sites whose dhcp servers are performing updates.

>
>I would also like to see an example of a complete DHCP/DynDNS transation
>(or perhaps 2, to cover the two models) - from the initial DHCPDISCOVER
>until everything is completed, showing all of the relevant fields (ie:
>addresses and names, omitting other DHCP options that would normally be
>included as they're not rrelevant here).   I think it would be also good
>to mention just what should be done when a lease is renewed - the doc as it
>stands seems to really only cover the case where a lease is initially being
>obtained (and also when it is released).
>
>In particular, I'd like this to tell me whether it is envisaged that there
>is any interaction in this area between what the server sends in its
>DHCPOFFER, and how the client uses the FQDN option of the DHCPREQUEST.
>

Do you mean that the text descriptions in 3.4.1 and 3.4.2 aren't complete,
or just that they aren't as clear as an example would be?

>
>Then, a request - I think it is quite common for clients to know the
>least significant element of the domain name that they want to own, but not
>to care much about what domain it is embedded into.   That is, it would be
>nice for the client to be able to supply just the hostname part, and have
>the server complete that by appending an appropriate domain name (and return
>the complete thing to the client). [...]
>

I agree. I'll make this clearer.

>
>Lastly, in this day and age, I think it would be appropriate to incorporate
>into the text for this option the appropriate language to indicate that the
>same thing applies to IPv6 just as it does for IPv4.   There's nothing
>specific to either of those in this option - if the DHCP server is supplying
>an IPv4 address to the client, it should do the appropriate IPv4 (A and PTR)
>updates, if it is supplying an IPv6 address to the client it should update
>the A6 (or AAAA) and whatever is chosen for the PTR equivalent for v6.
>To avoid having this draft hung up on normative references to fluctuating
>ipngwg drafts, I'd just use generalities indicating that if IPv6 addresses
are
>being assigned (using DHCPv6) then updates ought to be made "in a similar way
>to the appropriate RRs".
>
>kre

I'll add a sentence like the one you've quoted to section 2 at the
beginning of the draft.

>
>ps: There's an instance (at least one) of FQND in the text (a typo).
>There are a couple of references to section 7 being the security
>considerations, which is actually section 5 (7 is references, which
>could confuse someone who was sent there to look for security implications).
>

Thanks - I'll clean them up.

Mark



From dhcp-v4@bucknell.edu  Sun Mar 28 13:39:03 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03355
	for <dhc-archive@odin.ietf.org>; Sun, 28 Mar 1999 13:39:02 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id NAA11711;
	Sun, 28 Mar 1999 13:32:25 -0500 (EST)
Date: Sun, 28 Mar 1999 13:32:25 -0500 (EST)
Message-Id: <v04011700b3241f9d78fe@[134.82.7.102]>
Errors-To: droms@bucknell.edu
Reply-To: droms@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: wide-dhcp
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-impl@bucknell.edu by BERIM@RAVEL.UFRJ.BR follows.
---------------------------------------------------------------------


  Hello again,

 Dynamic allocation: like automatic allocation except that the server will
track
 leases and give IP addresses whose lease has expired to other DHCP clients.

  It's not happening: "give IP addresses whose lease has expired to other
DHCP clients..."

       Why ??

  wide-dhcp1.4p03
   default lease time: one hour
   maximum lease time: two hour


   Thank you very much, everyone.


From dhcp-v4@bucknell.edu  Sun Mar 28 13:42:19 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03382
	for <dhc-archive@odin.ietf.org>; Sun, 28 Mar 1999 13:42:18 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id NAA20313;
	Sun, 28 Mar 1999 13:39:07 -0500 (EST)
Date: Sun, 28 Mar 1999 13:39:07 -0500 (EST)
Message-Id: <v04011702b32423b36ecb@[134.82.7.102]>
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-subnet-option-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		: The Subnet Selection Option for DHCP
	Author(s)	: G. Waters
	Filename	: draft-ietf-dhc-subnet-option-01.txt
	Pages		: 5
	Date		: 24-Mar-99

   This memo defines a new DHCP option for selecting the subnet on which
   to allocate an address. This option would override a DHCP server's
   normal methods of selecting which subnet on which to allocate an
   address for a client.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-subnet-option-01.txt

Internet-Drafts are also 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-subnet-option-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-subnet-option-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-subnet-option-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-subnet-option-01.txt>


From dhcp-v4@bucknell.edu  Sun Mar 28 13:44:14 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03393
	for <dhc-archive@odin.ietf.org>; Sun, 28 Mar 1999 13:44:13 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id NAA01564;
	Sun, 28 Mar 1999 13:40:56 -0500 (EST)
Date: Sun, 28 Mar 1999 13:40:56 -0500 (EST)
Message-Id: <v04011703b3242442903e@[134.82.7.102]>
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: draft-ietf-dhc-dhcp-dns-09.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


message sent to dhcp-v4@bucknell.edu by KRE@MUNNARI.OZ.AU follows.
------------------------------------------------------------------
    Date:        Fri, 26 Mar 1999 18:39:39 -0500
    From:        Mark Stapp <mjs@cisco.com>
    Message-ID:  <4.0.2.19990326182233.0116e2f0@funnel.cisco.com>

  | I'll try to make this clearer. The purpose of this flag is to allow the
  | client to indicate to the server that the client will _not_ perform an
  | update on the client's name.

OK, that makes more sense.  I do think the text needs to be written more
with that slant in that case.

  | >  It should probably actually say that it MUST NOT attempt
  | >to update the A record in any other case.

  | I don't think that's correct: the client might not send anything, or the
  | server might be configured to perform the update (possibly because only it
  | has the necessary credentials) whether the client sets this flag or not
  | (see section 3, para. 3).

All I meant was that the server should never do any updates unless it has
the necessary credentials.   I would have thought that a self evident
restriction, though I may have phrased it badly.

  | The fqdn option is a DHCP option, and it's currently an ASCII string like
  | the existing host-name and domain-name options.

Is it?   I didn't see where the draft says that.   I'm also not sure
about the host-name option.   It's been a while since I checked, but I
had the impression that the host name in that option was just a counted
sequence of bytes (since it has no defined internal structure there's no
need for anything more, and no rationale for it either).

The domain name option I agree, that's a problem.

  | I'm inclined to leave it
  | that way unless there's clear agreement that it's insufficient.

By duplicating DNS format encoding you're guaranteeing that you can
represent any FQDN that the DNS can represent, which has to be sufficient.
As soon as you start altering the representation, difficulties can result
later.   Eg: there is some demand for a better specification of domain names
in international character sets, not just ascii (and also some resistance).
What will happen there isn't clear yet (it is pretty clear that basically
nothing needs to be done to the basic DNS spec to achieve it though).
It would be a pity if it turns out that limitations on DHCP restrict names
more than the DNS will allow.  One obvious example is that to use a pure
text form, some quoting scheme is needed to embed the "problem" characters
(like '.') when they form a part of a label, as distinct from being the
separator betwwwn labels.   The DNS allows that, its packet format doesn't
even notice, and it has defined quoting methods to embed such things in
zone files.   But a quoted name can be longer than 255 bytes (in its
quoted form), and would not fit in your fqdn option.   In DNS binary format
none of that can be an issue - whatever happens, the DNS binary packet limits
are pretty much set in concrete required to maintain compatability.

Unless there's a very good reason to use text formats (in which case the
actual text format to use needs to be precisely stated, don't just assume
it is "obvious", it isn't) using the DNS binary format in any protocol which
is basically carrying binary encoded date (which DHCP certainly is) seems
like an obvious "right" choice to me (even if it does mean an extra few lines
of code to deal with it).

  | A server can reply to a client's request with a NAK, and the client will
  | give up its current lease and attempt to acquire a new one. If that occurs,
  | the server should clean up the DNS.

Ah, I see what you mean, this occurs only when a client is attempting
to confirm (and usually extend) its lease.   I think it would not hurt to
add something to make that clear, lest anyone be tempted to read the text
as implying that servers have some mechanism for arbitrarily terminating
client leases, without client co-operation.   (It is a thing I occasionally
see people asking how to do, since it is basically impossible to achieve,
avoiding anyone being given a "but see RFCnnnn where it says ..." type
argument).


  | The sentence you've quoted appears immediately after this one: "The
  | following describes behavior of a DHCP client that implements the Client
  | FQDN option."

Sure, but "implements" and "desires to use" aren't the same thing.

  | Sites whose administrators don't care about this option can
  | use clients which don't implement it.

That is unreasonable.   As you say ...

  | Hopefully, the cooperation that the
  | draft describes is useful, and clients will implement it.

Yes, hopefully clients will implement it.   Hopefully all clients will
implement it.   That doesn't mean that all sites will desire to use it.
And if all clients implement it, the "use a client which doesn't implememt
it" option for the site goes away...

Avoid over specification - unless there is a very good operational reason
for a MUST, don't give one.    The only reason I can see for requiring
the client to include the FQDN option is when it is requesting the server
to do something with the data.   In that case, obviously the server needs
the value from the option to be able to function.   If the server isn't
required to do anything with the fqdn, then there's no reason for the
client to supply the data - regardless of whether or not the clients
implementation supports it, and regardless of what dynamic dns interactions
the client may intend to make.

  | Dangling names are seen as a very real administrative problem in many
  | organizations.

Sure, and they're seen as no problem at all in others.

  | There are popular clients which do release their leases, and
  | their behavior needs to be accounted for in the draft.

Yes, I agree.

  | If a client accepts responsibility for its name, it should make every
  | effort not to leave the name behind when it's no longer in use.

That's a value judgement, in what should be something left to individual
sites to determine which they prefer.   Some certainly prefer that stray
names be deleted when they're not in use.  Others may prefer that the names
be left as they were until they need to be updated to reflect the next address
they obtain.   Others may prefer that the A record be deleted, and replaced
by a TXT record (or something) as a placeholder, so the name is retained, but
the old A record isn't.    This is all for local site determination, and
need not be specified by this draft.

  | I believe you're right, and I think it's likely that sites which wish to
  | have secure dns updates initiated by clients will use DNSSEC. TSIG will be
  | very useful for sites whose dhcp servers are performing updates.

What will be useful in this area isn't clear yet.   I'm not sure that its
certain that the dnssec add on for secure updates (secupd) will survive
in anything like its current form, or ever be implemented.  Perhaps.  It
may just turn out that tsig (or something more like it) is sufficient to
cover all dynamic update cases.   Since none of this is deployed anywhere
yet, we just dont' know.

  | Do you mean that the text descriptions in 3.4.1 and 3.4.2 aren't complete,
  | or just that they aren't as clear as an example would be?

What started me wondering, was in attempting to determine whether the
server could provide any information which would assist the client in
sending the data for the fqdn option.   There's the easy case where the
client has simply been configured, via some other means, with its desired
fqdn (which may happen for workstations, and similar things, which have a
user sitting in front of them).  That is pretty straight forward.   But for
devices with no human around to configure the fqdn, but where the device
might just know enough of what it thinks it ought be called as a hostname
at least.   But the domain name in which that name ought be installed
is likely to be unknown.   The question is whether the server might supply
a domainname option in the dhcpoffer response to the dhcpdiscover,  and
then the client construct its full name for the fqdn in the dhcprequest
packet from that domain name.    Is that reasonable, simply wrong, ...

Sometimes it seems to me that seeing a simple example (the most simple
probably most common case) and a complex example (with everything done the
most perverse way that you can imagine it might be) can illustrate the
reasonable usage boundaries of the protocol.

Thanks for the response (and I'm still not on the dhcp-v4 list).

kre


From dhcp-v4@bucknell.edu  Wed Mar 31 16:32:33 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01256
	for <dhc-archive@odin.ietf.org>; Wed, 31 Mar 1999 16:32:32 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id QAA22293;
	Wed, 31 Mar 1999 16:24:37 -0500 (EST)
Date: Wed, 31 Mar 1999 16:24:37 -0500 (EST)
Message-Id: <199903311958.OAA13360@leo.eg.bucknell.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: dhcp-v4@bucknell.edu (by way of Ralph Droms <dhcp-v4@bucknell.edu>)
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: DHCP+WINS
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: QUALCOMM Windows Eudora Pro Version 4.0


message sent to dhcp-v4@bucknell.edu by MPAV@PURDUE.EDU follows.
----------------------------------------------------------------
I have three questions:

1) Can i push WINS addresses with a Linux DHCP server to win9x clients?

2) How can I have one DHCP server service 8 subnets?  

3) How can I set up a backup DHCP server?

Any help or documentation would be greatly appreciated.  I have not been
able to find answers to these questions through the usual channels.

-Matt
Asst. SysAdmin School of Liberal Arts.



From dhcp-v4@bucknell.edu  Wed Mar 31 16:37:15 1999
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.7.249])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01386
	for <dhc-archive@odin.ietf.org>; Wed, 31 Mar 1999 16:37:11 -0500 (EST)
Received: from reef.bucknell.edu (reef.bucknell.edu [134.82.7.6])
	by mail.bucknell.edu (8.9.2/8.9.2) with SMTP id QAA10943;
	Wed, 31 Mar 1999 16:33:29 -0500 (EST)
Date: Wed, 31 Mar 1999 16:33:29 -0500 (EST)
Message-Id: <199903312052.PAA00495@hygro.raleigh.ibm.com>
Errors-To: droms@bucknell.edu
Reply-To: narten@raleigh.ibm.com
Originator: dhcp-v4@bucknell.edu
Sender: dhcp-v4@bucknell.edu
Precedence: bulk
From: Thomas Narten <narten@raleigh.ibm.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: FWD: My worries about the DHCP Relay Agent Information Option
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4

This is a repost of an earlier message. This issue was also discussed
in Minneapolis. What's the WG's action plan? This document is currently
stuck within the IESG pending resolution.

Thomas

------- Forwarded Message

From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
To: dhcp-v4@bucknell.edu
Cc: narten@raleigh.ibm.com, burgan@corp.home.net
Date: Fri, 12 Feb 1999 08:48:24 +0100
Subject: My worries about the DHCP Relay Agent Information Option

I have reviewed the "DHCP Relay Agent Information Option", and must
admit that I do not like it.

My worries are not so much about the Relay Agent Information Option
itself (although specifying Yet Another Option Without Security is
kind of worrisome), but about the deployment model for Internet service
suggested and faciliated by this memo.

The distinguishing characteristics of this scenario are:

- The DHCP client and the DHCP server are controlled by different
  organizations, who do not necessarily trust each other fully.
  The client is at a "customer", the server is at an "ISP".
- More than one host at the customer site, interconnected by LAN
- Connectivity device ("modem") directly connected to the customer LAN
- Several customers on one Logical IP Subnet managed by the ISP.
- IP address assignment done at ISP central office.

The connection technologies suggested include (from 3.3):

- Dial-up
- ATM
- Cable (presumably CATV networks)
- Frame Relay (3.1)
- X.25

There are two worrisome aspects of this; one is a cost/reliability one,
and the other one is in security; the security is more important.

Cost/reliability first:

- When using dial-up, the customer MUST make a telephone call to boot
  his PC before accessing another device, such as a net-connected printer.
  If the remote server is busy, telephone service is out of order, or
  anything else is broken, his LAN will not work.

I already know people who hate their Windows boxes because they incur
a call setup charge from their autodial router when they boot - the
Windows box does some interesting DNS queries at boot.
The scheme suggested here would make that call required.
(Local call setup charges in Norway are around USD 0.07)

I would think that it's appropriate to add something like this:

  "Reliability concerns dictate that this scenario should ONLY be used
  when the CO connection is expected to be available 100% of the time.
  It is NOT appropriate for use with analog modem connections, and MAY
  be inapplicable to ISDN and switched ATM".

Now to the security issue.

- Since several customers share the same Logical IP Subnet, a naive
  implementation will let them SEE EACH OTHERS' BROADCAST PACKETS.

  This means that if any of them
  use (for instance) the filesystem export facilities in Windows 98 with
  permissions appropriate for in-house use, all other customers on the same
  LIS will get enough information to access those devices.

- Since several customers share the same logical subnet, it seems logical
  that they see each others' DHCP requests. It is then trivial to spoof
  a reply in such a way that "interesting" services can be redirected through
  another customer's site, leading to "interesting" cases of man-in-the-middle
  attacks.

- If the "obvious" filter rules for disallowing packets between customers
  are applied, one may easily get the silly state where you are able to
  contact any Internet site in the whole world, EXCEPT your neighbour's
  house.
  (Don't laugh - I know ISPs who have done exactly that in other contexts!)

I would prefer to see this document revised to have a rather draconian
security section, saying something like:

- This deployment scenario MUST have appropriate inter-customer firewalls.
  The firewalls erected MUST ensure that two customers sharing a LIS
  cannot see each others' broadcast packets by default, yet are able
  to communicate no worse than the connection to other parts of the
  Internet.

- Note that the scheme gives absolutely no protection against all the
  normal attacks that can be launched against a DHCP client.
  Since the area the DHCP request/response crosses is larger, and includes
  more than one trust environment, care must be taken to ensure that
  it's reasonably hard for a customer to launch denial-of-service or
  security attacks against other customers of the same service.

What do people think?

                  Harald A


-- 
Harald Tveit Alvestrand, Maxware, Norway
Harald.Alvestrand@maxware.no

------- End of Forwarded Message


