Network Working Group                                       R. B.                                      Barr Hibbs
     INTERNET-DRAFT                                           UltraDNS Corp.                                       (no affiliation)
     Category:  Standards Track                                    G.                               Glenn Waters
                                                           Nortel Networks
                                                                    November 2000
                                                             February 2002

                Dynamic Host Configuration Protocol (DHCP) Server MIB

                             <draft-ietf-dhc-server-mib-05.txt>
                             Monday, November 13, 2000, 3:50 PM

                         <draft-ietf-dhc-server-mib-06.txt>
                   Saved Thursday, February 14, 2002, 11:26:01 AM

     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. progress."

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

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

            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) 2002, The Internet Society (2000). Society.  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: Nov 2000 + 6 months             [Page 1]

     Table of Contents

        1. Introduction......................................................2 Introduction...................................................2
        2. Overview..........................................................2 Overview.......................................................3
          2.1. Relationship to Other MIBs.................................4
            2.1.1. DHCP MIB Extensions...................................4
            2.1.2. Host System MIB Extensions............................4
            2.1.3. DHCPv6 Server MIB Extensions..........................4
            2.1.4. DHCP Client MIB Extensions............................5
            2.1.5. DHCP Relay Agent MIB Extensions.......................5
          2.2. Textual Conventions Introduced in this MIB.................5
            2.2.1. DhcpTimeInterval......................................5
            2.2.2. HardwareAddressType...................................5
            2.2.3. HardwareAddressLength.................................5
            2.2.4. MacAddress............................................5
            2.2.5. PhysicalAddress.......................................5
            2.2.6. DhcpLabel.............................................6
          2.3. BOOTP and DHCP Counter Groups.................................3
             2.2. Groups..............................6
          2.4. BOOTP and DHCP Optional Statistics Group...............................3
             2.3. Server Configuration Group....................................3
             2.4. Group...................6
          2.5. Response Times and ICMP Echo..................................5 Echo...............................8
        3. Definitions.......................................................5 Definitions....................................................8
        4. Intellectual Property............................................31 Property.........................................39
        5. Notes............................................................31 Notes.........................................................40
          5.1. Issues.......................................................31 Issues....................................................40
          5.2. Changes from Prior Drafts....................................32 Drafts.................................41
        6. Acknowledgements.................................................33 Acknowledgements..............................................42
        7. Security Considerations..........................................33 Considerations.......................................42
        8. References.......................................................33 References....................................................43
        9. Editors' Addresses...............................................34 Addresses............................................44
        10. Full Copyright Statement........................................34 Statement.....................................44

     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 does not cover DHCP/BOOTP client nor relay agent MIB
        extensions:  these are possibly the subjects of future investigation. investigation
        [see discussion in section 2.1.]  Also excluded from this MIB
        extension in the interest of simplicity are DHCP Dynamic DNS
        Updating, Failover, Authentication, and Load Balancing:  these
        functions and features could be subjects of future MIB extensions.

        Provision is also made for Standards-Track additions to the DHCP
        Message Type (option 61.)

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

        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," "MUST NOT", "REQUIRED", "SHALL", NOT," "REQUIRED," "SHALL," "SHALL NOT",
            "SHOULD", NOT,"
        "SHOULD," "SHOULD NOT", "RECOMMENDED",  "MAY", NOT," "RECOMMENDED,"  "MAY," and "OPTIONAL" in this
        document are to be interpreted as described in document [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
        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.

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 2]

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

     2.1. BOOTP and Relationship to Other MIBs

     2.1.1. DHCP Counter Groups

            This section describes some MIB Extensions

        The DHCP MIB extensions will the "dhcp" branch of the management information standard MIB-2
        tree, as illustrated by the following diagram:

                                 +-------+
                                 | MIB-2 |
                                 +---+---+
                                     |
                                     |
                                 +---+---+
                                 |  dhcp |
                                 +---+---+
                                     |
                                     |
              +---------------+------+---------+---------------------+
              |               |                |                     |
        +-----+-----+   +-----+----+   +-------+--------+     +------+------+
        |  dhcp-v4  |   |  dhcp-v4 |   |    dhcp-v4     |     | dhcp-v6 MIB |
        |Server MIB |   |Client MIB|   |Relay Agent MIB |     | Extensions  |
        |(this memo)|   | (future) |   | (future work)  |     |   (future)  |
        +-----------+   +----------+   +----------------+     +-------------+

        The MIBs will share a common branching point, but are independently
        defined.

     2.1.2. Host System MIB Extensions

        The Host System MIB [RFC1123] provides for information, command, and
        control of the host computer system on which a DHCP server resides.
        The DHCP Server MIB specifically does not include any objects that
        may be derived from accessible using the objects provided Host System MIB.

     2.1.3. DHCPv6 Server MIB Extensions

        When this set of MIB extensions is developed, it will share a common
        branch point in the counter groups.

            The total number of valid DHCP packets received by MIB tree with the server other DHCP MIB Extensions.

     2.1.4. DHCP Client MIB Extensions

        If this set of MIB extensions is
            computed as ever developed, it will share a
        common branch point in the sum of MIB tree with the dhcpCountDiscovers, dhcpCountRequests,
            dhcpCountReleases, dhcpCountDeclines, other DHCP MIB
        Extensions, and dhcpCountInforms objects.
            The total number will use many of the same textual conventions.

     2.1.5. DHCP Relay Agent MIB Extensions

        If this set of MIB extensions is ever developed, it will share a
        common branch point in the MIB tree with the other DHCP MIB
        Extensions, and will use many of the same textual conventions.

     2.2. Textual Conventions Introduced in this MIB

        Severaal conceptual data types have been introduced as textual
        conventions in this DHCP MIB document.  These additions will
        facilitate the common understanding of information used by the DHCP
        server.  No changes to the SMI or the SNMP are necessary to support
        these conventions.

     2.2.1. DhcpTimeInterval

        This data type measures time intervals since the beginning of some
        epoch in milliseconds.

     2.2.2. HardwareAddressType

        This data type contains the type of hardware address represented by
        MacAddress, as defined for ARP messages.

     2.2.3. HardwareAddressLength

        The length in octets of MacAddress is contained in this type.

     2.2.4. MacAddress

        The actual layer 1 hardware address is contained in this data type.

     2.2.5. PhysicalAddress

        This data type combines the hardware type octet with the length and
        hardware (NIC or MAC) address to produce a unique address type.

     2.2.6. DhcpLabel

        This data type contains labels used as identifiers by DHCP servers.

     2.3. 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, dhcpCountInforms and
        dhcpCountLeaseQueries 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 the sum of 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, dhcpCountNacks,
        dhcpCountForcedRenews, dhcpCountKnowns, and dhcpCountNacks dhcpCountUnknowns
        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.

     2.4. BOOTP and DHCP Optional Statistics Group

        This section describes some of the management information that may be
        derived from the objects provided in the optional 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.

        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
        bootpOptionalStatistics group are used instead of the objects from dhcpStatistics group.

          2.3. Server
        dhcpOptionalStatistics group.server Configuration Group

        The server configuration group contains objects that describe the
        configuration information that is contained in the server.  Some of

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 3]
        the configuration information is static (e.g.: (e.g., a statically
        configured IP address) and some of the configuration is dynamic
            (e.g.:
        (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.: (e.g., vendor
        defined solutions) and are being standardized (e.g.: (e.g., the Directory
        Enabled Networks [DEN] initiative) to update a server's
        configuration.

        The configuration information provides defines 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 network segment as some
        other subnet.

        The serverRangeTable lists the start and end IP addresses of the
        ranges and the subnet of which the range is a member of. member.  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 and
            it is currently in the address
              list; active use by a host;

          o Configuration-reserved, Expired, in which case the address is not
              available server had previously assigned for
            which the lease time has expired, but is retained by the server to allocate to
            for possible future use by the same client;
          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.: (e.g., statically assigned), and the address is within a
            DHCP range;  and, and

          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.: (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, served, or whether BOOTP or DHCP was used
        to allocate the address.

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 4] 
          2.4.

     2.5. 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

        -- definitions for a DHCP (Dynamic Host Configuration Protocol)
        server

        DHCP-SERVER-MIB DEFINITIONS ::= 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, NOTIFICATION-GROUP  #
            /*modified*/
              FROM SNMPv2-CONF;

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

            dhcpServerMIB

        serverMIB  MODULE-IDENTITY  # /*renamed*/
           LAST-UPDATED "9910060000Z"   "2002-02-14 11:26"
           ORGANIZATION   "IETF DHCP DHC Working Group"
           CONTACT-INFO
              "        Richard Barr Hibbs
              Postal: UltraDNS Corporation
                        800 North  952 Sanchex Street
                       San Mateo Drive
                        San Mateo, CA 94401-2261 Francisco, California 94114-3362
                       USA
                 Tel:  +1 650-227-2678  +1-(415)-648-3920
                 Fax:  +1 650-227-2662
                  Email:  rbhibbs@ultraDNS.com  +1-(415)-648-9017
              E-mail:  rbhibbs@pacbell.net

                       Glenn Waters
              Postal:  Nortel Networks, Inc.
                       310-875 Carling Avenue

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 5]
                       Ottawa, Ontario K1S 5P1
                       Canada
                 Tel:  +1 613-765-0249
                  Email:  gww@nortelnetworks.com"  +1-(613)-798-4925
              E-mail:  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).  This MIB does not include support for Dynamic DNS
              (DDNS) updating nor for the DHCP Failover Protocol."
           ::= { dhcp 1 }

            dhcpServerMIBObjects

        serverMIBObjects  OBJECT-IDENTITY
           STATUS      current
           DESCRIPTION
              "DHCP Server MIB objects are all defined in this branch."
        ::= { dhcpServerMIB serverMIB 1 }

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

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

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

            bootpStatistics

        bootpOptionalStatistics  OBJECT-IDENTITY -- /*renamed*/
           STATUS      current
           DESCRIPTION
              "Group of objects that measure various BOOTP statistics."
        ::= { dhcpServerMIBObjects serverMIBObjects 4 }

            dhcpStatistics

        dhcpOptionalStatistics  OBJECT-IDENTITY  -- /*renamed*/
           STATUS      current
           DESCRIPTION
              "Group of objects that measure various DHCP statistics."
        ::= { dhcpServerMIBObjects serverMIBObjects 5 }

        serverConfiguration  OBJECT-IDENTITY
           STATUS      current
           DESCRIPTION
              "Objects that contain pre-configured and dynamic configuration
              information."

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 6]
        ::= { dhcpServerMIBObjects serverMIBObjects 6 }

            clientGroup

        bootpClients  OBJECT-IDENTITY
           STATUS      current
           DESCRIPTION
              "Objects that map DHCP and BOOTP bootp clients to IP addresses."
        ::= { dhcpServerMIBObjects serverMIBObjects 7 }

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

        -- Textual conventions defined by this memo

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

            PhysicalAddress

        HardwareAddressType ::= TEXTUAL-CONVENTION
               DISPLAY-HINT "t,xx[:xx...]"
           SYNTAX         OCTET
           STATUS         current
           REFERENCE      "RFC 2131"
           DESCRIPTION
                  "A harware type and hardware address.  This object is
                  encoded as
                        <type ><address>
                     where
                        <type> is the
              "The value of the hardware type space field, as used in ARP messages
              (e.g., 1 for Ethernet, 6 for token ring).  IANA maintains the
              list of registered numbers for this field. The value for
                             this field comes from field."

        HardwareAddressLength ::= TEXTUAL-CONVENTION
           SYNTAX         OCTET
           STATUS         current
           REFERENCE      "RFC 2131"
           DESCRIPTION
              "The length in octets of the 'htype' hardware address field in (e.g., 6
              for Ethernet).  IANA maintains the
            BOOTP
                             packet header.
                        <address> is list of registered numbers
              for this field."

        MacAddress ::= TEXTUAL-CONVENTION
           SYNTAX         OCTET STRING (SIZE (1..16))
           DISPLAY-HINT   "t,l,xx[:xx...]"
           STATUS         current
           REFERENCE      "RFC 2131"
           DESCRIPTION
              "A Layer 1 address, the hardware address of the MAC (Media
              Adapter Card) interface.  The value address length is fixed for this field
                             comes from a
              given hardware address type, but varies by type."

        PhysicalAddress ::= TEXTUAL-CONVENTION
           SYNTAX         SEQUENCE OF {
              HardwareAddressType,
              HardwareAddressLength,
              MacAddress
           }
           DISPLAY-HINT   "t,l,xx[:xx...]"
           STATUS         current
           REFERENCE      "RFC 2131"
           DESCRIPTION
              "A Layer 1 address which includes the 'chaddr' field in hardware type space as
              well as the BOOTP packet
                             header." usual MAC address.  This encoding is intended to
              mirror the representation of physical addresses in DHCP."

        DhcpLabel ::= TEXTUAL-CONVENTION
           SYNTAX                            OCTET STRING         DisplayString (SIZE (0 | 2..17)) (1..100))
           DISPLAY-HINT
           STATUS         current
           DESCRIPTION
        -- serverSystem Group

        serverSystemDescr  OBJECT-TYPE
           SYNTAX      DisplayString (SIZE (0..255))
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "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."
              server."
           ::= { serverSystem 1 }

        serverSystemObjectID  OBJECT-TYPE

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 7]
           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.' is 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'."
           ::= { serverSystem 2 }

        -- bootpCounters dhcpCounters Group

            bootpCountRequests

        -- DHCP received packet counters

        dhcpCountDiscovers  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPDISCOVER (option 53 with value 1) 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."
               ::= { bootpCounters
              received."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { dhcpCounters 1 }

            bootpCountInvalids

        dhcpCountRequests  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPREQUEST (option 53 with value 3) 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)."
              received."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { bootpCounters dhcpCounters 2 }

            bootpCountReplies

        dhcpCountReleases  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 DHCPRELEASE (option 53 (DHCP Message Type) in the options." with value 7) packets
              received."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { bootpCounters dhcpCounters 3 }

            bootpCountDroppedUnknownClients

        dhcpCountDeclines  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of BOOTP DHCPDECLINE (option 53 with value 4) packets dropped due to the server not
                  recognizing or not providing service to the hardware address
                  received in the incoming packet."

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 8]
              received."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { bootpCounters dhcpCounters 4 }

            bootpCountDroppedNotServingSubnet

        dhcpCountInforms  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of BOOTP DHCPINFORM (option 53 with value 8) 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."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { bootpCounters dhcpCounters 5 }  -- dhcpCounters Group

            dhcpCountDiscovers /*renumbered*/

        dhcpCountLeaseQueries  OBJECT-TYPE  -- /*new*/
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPDISCOVER DHCPLEASEQUERY (option 53 with value 1) TBD)
              packets received."
           REFERENCE
              "draft-ietf-dhc-leasequery-02.txt."
           ::= { dhcpCounters 1 6 }

            dhcpCountRequests  -- /*new*/
        -- DHCP sent packet counters

        dhcpCountOffers  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPREQUEST DHCPOFFER (option 53 with value 3) 2) packets
                  received."
              sent."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { dhcpCounters 2 11 }

            dhcpCountReleases  -- /*renumbered*/

        dhcpCountAcks  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPRELEASE DHCPACK (option 53 with value 7) 5) packets
                  received." sent."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { dhcpCounters 3 12 }

            dhcpCountDeclines  -- /*renumbered*/

        dhcpCountNacks  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPDECLINE DHCPNACK (option 53 with value 4) 6) packets
                  received." sent."
           REFERENCE
              "RFC2131; RFC2132, section 9.6."
           ::= { dhcpCounters 4 13 }

            dhcpCountInforms  -- /*renumbered*/

        dhcpCountForcedRenews  OBJECT-TYPE  -- /*new*/
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPINFORM DHCPFORCERENEW (option 53 with value 8) packets

          Hibbs & Waters        Expires: Nov 2000 + 6 months             [Page 9] 
                  received."
               ::= { dhcpCounters 5 }

            dhcpCountInvalids OBJECT-TYPE
               SYNTAX                         Counter32
               MAX-ACCESS  read-only
               STATUS                         current
               DESCRIPTION
                  "The number of DHCP TBD)
              packets received whose DHCP message type
                  (i.e., option number 53) is not understood or handled by the
                  server." sent."
           REFERENCE
              "draft-ietf-dhc-pv4-reconfigure-06.txt."
           ::= { dhcpCounters 6 14 }

            dhcpCountOffers  -- /*new*/

        dhcpCountKnowns  OBJECT-TYPE  -- /*new*/
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPOFFER DHCPKNOWN (option 53 with value 2) TBD) packets
              sent."
           REFERENCE
              "draft-ietf-dhc-leasequery-02.txt."
           ::= { dhcpCounters 7 12 }

            dhcpCountAcks  -- /*new*/

        dhcpCountUnknowns  OBJECT-TYPE  -- /*new*/
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPACK DHCPUNKNOWN (option 53 with value 5) TBD) packets
              sent."
           REFERENCE
              "draft-ietf-dhc-leasequery-02.txt."
           ::= { dhcpCounters 8 13 }

            dhcpCountNacks  -- /*new*/

        -- DHCP packet error counters

        dhcpCountInvalids  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCPNACK (option 53 with value 6) DHCP packets
            sent." received whose DHCP message type
              (i.e., option number 53) is not understood or handled by the
              server."
           ::= { dhcpCounters 9 17 }  -- /*renumbered*/

        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."
           ::= { dhcpCounters 10 18 }  -- /*renumbered*/

        dhcpCountDroppedNotServingSubnet  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of DHCP packets dropped due to the server not being

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 10]
              configured or not otherwise able to serve addresses on the
              subnet from which this message was received."
           ::= { dhcpCounters 11 19 }  -- bootpStatistics /*renumbered*/
        -- dhcpOptionalStatistics group

            bootpStatMinArrivalInterval

        dhcpStatMinArrivalInterval  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The minimum amount of time between receiving two BOOTP 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."
           ::= { bootpStatistics dhcpOptionalStatistics 1 }

            bootpStatMaxArrivalInterval  -- /*renamed*/

        dhcpStatMaxArrivalInterval  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The maximum amount of time between receiving two BOOTP 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."
           ::= { bootpStatistics dhcpOptionalStatistics 2 }

            bootpStatLastArrivalTime  -- /*renamed*/

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

            bootpStatSumSquaresArrivalTime

        dhcpStatSumSquaresArrivalTime  OBJECT-TYPE
           SYNTAX      Counter64
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The sum of the squared BOOTP DHCP packet inter-arrival times in
                  micro-seconds.
              microseconds.  This value may be used to compute the variance

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 11]
              and standard deviation of the BOOTP DHCP arrival times.  Note that a
                  micro-second
              microsecond resolution of this object requires a clock
              resolution to the milli-second millisecond since the square of a milli-
                  second millisecond
              value produces a value with micro-second microsecond resolution."
           ::= { bootpStatistics dhcpOptionalStatistics 4 }

            bootpStatMinResponseTime }-- /*renamed*/

        dhcpStatMinResponseTime  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The smallest time interval measured as the difference between
              the arrival of a BOOTP 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."
           ::= { bootpStatistics dhcpOptionalStatistics 5 }

            bootpStatMaxResponseTime }-- /*renamed*/

        dhcpStatMaxResponseTime  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The largest time interval measured as the difference between
              the arrival of a BOOTP 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."
           ::= { bootpStatistics 6 }

            bootpStatSumResponseTime OBJECT-TYPE

          Hibbs & Waters        Expires: Nov 2000 + dhcpOptionalStatistics 6 months            [Page 12] }-- /*renamed*/

        dhcpStatSumResponseTime  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The sum of the response time intervals in milli-seconds milliseconds where a
              response time interval is measured as the difference between
              the arrival of a BOOTP 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."
           ::= { bootpStatistics dhcpOptionalStatistics 7 }

            bootpStatSumSquaresResponseTime }-- /*renamed*/

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

        -- 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."
           REFERENCE
              "RFC-1541."
           ::= { bootpCounters 1 }-- /*renamed*/

        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)."
           ::= { bootpCounters 2 }-- /*renamed*/

        bootpCountReplies  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The number of packets sent that contain a Message Type of 2
              (BOOTREPLY) in the first octet and do not contain option number
              53 (DHCP Message Type) in the options."
           REFERENCE
              "RFC-1541."
           ::= { bootpCounters 3 }-- /*renamed*/

        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."
           ::= { bootpCounters 4 }-- /*renamed*/

        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."
           ::= { bootpCounters 5 }-- /*renamed*/

        -- dhcpStatistics bootpOptionalStatistics group

            dhcpStatMinArrivalInterval

        bootpStatMinArrivalInterval  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The minimum amount of time between receiving two DHCP 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."
           ::= { dhcpStatistics bootpOptionalStatistics 1 }

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 13] 
            dhcpStatMaxArrivalInterval }-- /*renamed*/

        bootpStatMaxArrivalInterval  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The maximum amount of time between receiving two DHCP 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."
           ::= { dhcpStatistics bootpOptionalStatistics 2 }

            dhcpStatLastArrivalTime }-- /*renamed*/

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

            dhcpStatSumSquaresArrivalTime  -- /*renamed*/

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

            dhcpStatMinResponseTime }-- /*renamed*/

        bootpStatMinResponseTime  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The smallest time interval measured as the difference between
              the arrival of a DHCP 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: Nov 2000 + 6 months            [Page 14]

              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."
           ::= { dhcpStatistics bootpOptionalStatistics 5 }

            dhcpStatMaxResponseTime }-- /*renamed*/

        bootpStatMaxResponseTime  OBJECT-TYPE
           SYNTAX      DhcpTimeInterval
           MAX-ACCESS  read-write  read-only
           STATUS      current
           DESCRIPTION
              "The largest time interval measured as the difference between
              the arrival of a DHCP 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."
           ::= { dhcpStatistics bootpOptionalStatistics 6 }

            dhcpStatSumResponseTime }-- /*renamed*/

        bootpStatSumResponseTime  OBJECT-TYPE
           SYNTAX      Counter32
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The sum of the response time intervals in milli-seconds milliseconds where a
              response time interval is measured as the difference between
              the arrival of a DHCP 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."
           ::= { dhcpStatistics bootpOptionalStatistics 7 }

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 15] 
            dhcpStatSumSquaresResponseTime }-- /*renamed*/

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

        -- server configurationgroup

        -- server shared network table

        serverSharedNetworkTable  OBJECT-TYPE
           SYNTAX      SEQUENCE OF serverSharedNetworkEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
              "A list of shared networks that are configured in the server.
              A shared network is the logical aggregation of one or more
              subnets that share a common network segment (e.g., multi-tapped
              coaxial cable, wiring hub, or switch).  This table is present
              ONLY for those servers that organize the ranges of addresses
              available for assignment where a higher-level grouping (i.e.,
              the "shared" network) exists above ranges and subnets."
           ::= { serverConfiguration 1 }

        serverSharedNetworkEntry  OBJECT-TYPE
           SYNTAX      ServerSharedNetworkEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           INDEX       { serverSharedNetworkName }
           DESCRIPTION
              "A logical row in the serverSharedNetworkTable."
           ::= { serverSharedNetworkTable 1}

        ServerSharedNetworkEntry ::= SEQUENCE {
              serverSharedNetworkName                DhcpLabel,
              serverSharedNetworkFreeAddresses       Unsigned32,
              serverSharedNetworkReservedAddresses   Unsigned32,-- /*new*/
              serverSharedNetworkTotalAddresses      Unsigned32-- /*renamed*/
           }

        serverSharedNetworkName  OBJECT-TYPE
           SYNTAX      DhcpLabel-- /*modified*/
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
              "The name of the shared network, which uniquely identifies an
              entry in the serverSharedNetworkTable."
           ::= { serverSharedNetworkEntry 1 }

        serverSharedNetworkFreeAddresses  OBJECT-TYPE-- /*renamed*/
           SYNTAX      Unsigned32
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The number of IP addresses which are available within this
              shared network.  If the server does not count free addresses by
              shared network segment, this value will be zero."
           ::= { serverSharedNetworkEntry 2 }-- /*renumbered*/

        serverSharedNetworkReservedAddresses  OBJECT-TYPE-- /*new*/
           SYNTAX      Unsigned32
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The number of IP addresses which are reserved (not available
              for assignement) within this shared network.  If the server
              does not count reserved addresses by shared network segment,
              this value will be zero."
           ::= { serverSharedNetworkEntry 3 }

        serverSharedNetworkTotalAddresses  OBJECT-TYPE-- /*new*/
           SYNTAX      Unsigned32
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The number of IP addresses which are available within this object requires a clock
                  resolution to the milli-second since
              shared network.  If the square of a milli-
                  second value produces a server does not count total addresses
              by shared network segment, this value with micro-second resolution." will be zero."
           ::= { dhcpStatistics 8 serverSharedNetworkEntry 4 }

        -- serverConfiguration group server subnet table

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

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

        ServerSubnetEntry ::= SEQUENCE {
           serverSubnet                           IpAddress,
           serverSubnetMask                       IpAddress,
               serverSubnetSharedNet                  IpAddress,
               serverSubnetConfiguredAddresses        Unsigned32,
               serverSubnetAvailableAddresses         Unsigned32,
           serverSubnetSharedNetworkName          DhcpLabel,-- /*modified*/
           serverSubnetFreeAddressLowThreshold    Unsigned32,
           serverSubnetFreeAddressHighThreshold   Unsigned32,
           ServerSubnetFreeAddresses              Unsigned32  -- /*renamed*/
           }

        serverSubnet  OBJECT-TYPE
           SYNTAX      IpAddress
           MAX-ACCESS  not-accessible  read-only-- /*changed*/
           STATUS      current
           DESCRIPTION
              "The IP address of the subnet."
           ::= { serverSubnetEntry 1 }

        serverSubnetMask  OBJECT-TYPE
           SYNTAX      IpAddress
           MAX-ACCESS  read-only
           STATUS      current

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 16]
           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."
           ::= { serverSubnetEntry 2 }

            serverSubnetSharedNet OBJECT-TYPE

        serverSubnetSharedNetworkName  OBJECT-TYPE-- /*renamed*/
           SYNTAX                         IpAddress      DhcpLabel-- /*modified*/
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The IP address of another subnet that is on the same shared
                  media subnet name (used as this subnet.  The address of an index into the server
              shared subnet MUST
                  also be configured on this server.  The address 0.0.0.0
            should
                  be used if this subnet is not shared."
               ::= { serverSubnetEntry 3 }

            serverSubnetConfiguredAddresses OBJECT-TYPE
               SYNTAX                         Unsigned32
               MAX-ACCESS  read-only
               STATUS                         current
               DESCRIPTION
                   "The number of IP addresses that are configured table) to be served
                   on this subnet."
               ::= { serverSubnetEntry 4 }

            serverSubnetAvailableAddresses OBJECT-TYPE
               SYNTAX                         Unsigned32
               MAX-ACCESS  read-only
               STATUS                         current
               DESCRIPTION
                   "The number of IP addresses on which this subnet belongs.  This value
              will be null for servers that are do not
                   currently assigned to a client." organize or describe
              networks in this manner."
           ::= { serverSubnetEntry 5 3 }

        serverSubnetFreeAddressLowThreshold  OBJECT-TYPE  # /*new*/
           SYNTAX      Unsigned32
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The low threshold for available free addresses in this subnet.
              If the value for available free addresses in this subnet
              becomes equal to or less than this value, a
              serverSubnetFreeAddressLowThreshold event is generated for this
              shared network.  No more serverSubnetFreeAddressLowThreshold
              events will be generated for this subnet during this execution
              of the DHCP server until the value for available free addresses
              has exceeded the value of serverSubnetFreeAddressHighThreshold.

                  This value may be expressed as either an absolute value or a
                  percentage; the units are specified by the value of
                  serverSubnetFreeAddressUnits."
              serverSubnetFreeAddressHighThreshold."
           ::= { serverSubnetEntry 6 4 }

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 17] 
            serverSubnetFreeAddressHighThreshold

        serverSharedNetworkFreeAddressHighThreshold  OBJECT-TYPE  # /*new*/
           SYNTAX      Unsigned32
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The high threshold for available free addresses in this
              subnet.  If a serverSubnetFreeAddressLowThreshold event has
              been generated for this subnet, and the value for available
              free addresses has exceeded the value of
              serverSubnetFreeAddressHighThreshold, then a
              serverFreeAddressessHigh event will be generated.  No more
              serverFreeAddressessHigh events will be generated for this
              subnet during this execution of the DHCP server until the value
              for available free addresses becomes equal to or less than the
              value of  serverSubnetFreeAddressHighThreshold.

                  This value may be expressed as either an absolute value or a
                  percentage; the units are specified by the value of
                  serverSubnetFreeAddressUnits." serverSubnetFreeAddressHighThreshold."
           ::= { serverSubnetEntry 7 5 }

        -- server range table

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

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

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

        serverRangeStart  OBJECT-TYPE
           SYNTAX      IpAddress
           MAX-ACCESS  not-accessible  read-only
           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."

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 18]
           ::= { 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."
           ::= { serverRangeEntry 2 }

            serverRangeSubnetAddress

        serverRangeSubnetMask  OBJECT-TYPE
           SYNTAX      IpAddress
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The subnet address mask for this range."
           ::= { 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)."
           ::= { serverRangeEntry 4 }

        serverRangeOutstandingOffers  OBJECT-TYPE
           SYNTAX      Gauge32
           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."
           ::= { serverRangeEntry 5 }
        -- server address table

        serverAddressTable  OBJECT-TYPE
           SYNTAX      SEQUENCE OF ServerAddressEntry serverAddressEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           DESCRIPTION
                  "A
              "An optional list of addresses that are known by this server.
              The list

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 19] 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 for a subnet)." host).  Expired leases MAY appear
              during the time they are 'remembered' by the server for
              subsequent assignment to the same host."
           ::= { serverConfiguration 3 4 }

        serverAddressEntry  OBJECT-TYPE
           SYNTAX      ServerAddressEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           INDEX       { serverAddress }
           DESCRIPTION
              "A logical row in the serverAddressTable."
           ::= { serverAddressTable 1 }

        ServerAddressEntry ::= SEQUENCE {
           serverAddress                 IpAddress,
           serverAddressSubnetMask       IpAddress,
           serverAddressRange            IpAddress,
           serverAddressType             INTEGER,
           serverAddressTimeRemaining    Unsigned32,
           serverAddressAllowedProtocol  INTEGER,
           serverAddressServedProtocol   INTEGER,
               serverAddressHardwareAddress      PhysicalAddress,
           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."
           ::= { 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."
           ::= { serverAddressEntry 2 }

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

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 20]
              "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."
           ::= { serverAddressEntry 3 }

        serverAddressType  OBJECT-TYPE
           SYNTAX      INTEGER {
               static(1),
               dynamic(2),
                           configuration-reserved(3),
                           server-reserved(4)
               expired(3),  -- /*new*/
               configuration-reserved(4),  -- /*renumbered*/
               server-reserved(5)  -- /*renumbered*/
              }
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The type of this address.  Types are:
                (1) static addresses defined by the server configuration.
                (2) dynamic addresses defined by the server configuration
                    AND actually assigned by the server.
                (3) expired dynamic addresses, previously assigned by the
                    server and 'remembered' for subsequent assignment to the
                    same host.
                (4) Addresses reserved (i.e., not assignable) by the server
                    configuration.
                (5) Addresses previously assigned by the server, but
                    temporarily or permanently removed from assignable state
                    for some reason, e.g., the server received an ICMP
                    ECHOREPLY for the IP address or a DHCPDECLINE message
                    has been received for the IP address."
           ::= { 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."
           ::= { 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) none (1) indicates that the address is not
              available to be served (e.g., a reserved address)." address).Type (2) are
              reserved for BOOTP only devices, while type (3) are reserved
              for DHCP only devices.  A type of bootp-or-dhcp (4) may be
              offered to any type of client."
           ::= { 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) none (1) if the

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 21]
              address has not been served."
           ::= { serverAddressEntry 7 }

        serverAddressHardwareAddress  OBJECT-TYPE
           SYNTAX      PhysicalAddress
           MAX-ACCESS  read-only
           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.  This object may
              be empty if the address has not been previously served."
           ::= { 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."
           ::= { serverAddressEntry 9 }

        serverAddressHostName  OBJECT-TYPE
           SYNTAX      DisplayString (SIZE (0..255)) (1..255))
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The host name (DHCP option 12) the client is configured to
              use, or if no host name was configured then the host name that
              the client supplied when requesting an address.  While this
              object has a maximum size of 255 octets, a Fully-Qualified
              Domain Name (FQDN) consisting of a Host Name part and a Domain
              Name part is currently limited to 255 octets.  Therefore, the
              sum of the string lengths for this object and the
              serverAddressDomainName must, in practice, be less than 256
              octets."
           ::= { serverAddressEntry 10 }

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

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 22]
           DESCRIPTION
              "The domain name (DHCP option 15) assigned to the client.
              While this object has a maximum size of 255 octets, a Fully-
              Qualified Domain Name (FQDN) consisting of a Host Name part and
              a Domain Name part is currently limited to 255 octets, less the
              separator
                  ('.') (".") character.  Therefore, the sum of the string
              lengths for this object and the serverAddressHostName must, in
              practice, be less than 256 octets."
           ::= { serverAddressEntry 11 }

        -- Server Client Table

        serverClientTable  OBJECT-TYPE
           SYNTAX      SEQUENCE OF ServerClientEntry 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 serverClientHardwareAddress and
              serverClientAddress object. objects.  This table is indexed first by
              the physical MAC address of the client and then by the subnet address on
              which the client resides.  The subnet is included as an index
              since the physical a MAC address is only guaranteed to be unique within a
              subnet (i.e., a physical MAC address is not globally unique)."
           ::= { clientConfiguration 1 serverConfiguration 5 }

        serverClientEntry  OBJECT-TYPE
           SYNTAX      ServerClientEntry
           MAX-ACCESS  not-accessible
           STATUS      current
           INDEX    { serverClientHardwareAddress,
                  serverClientSubnetMask serverClientAddress }
           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 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."
           ::= { serverClientTable 1 }

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 23]

        ServerClientEntry ::= SEQUENCE {
              serverClientHardwareAddress       PhsicalAddress      PhysicalAddress
              serverClientSubnetMask           IpAddress,
              serverClientAddress              IpAddress,
              serverClientLastRequestTime      DateAndTime,
              serverClientLastRequestType      INTEGER,
              serverClientLastResponseType     INTEGER
           }

        serverClientHardwareAddress  OBJECT-TYPE
           SYNTAX      PhysicalAddress
           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. This value of
                   this object MUST NOT be zero length." packet."
           ::= { serverClientEntry 1 }

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

        serverClientAddress  OBJECT-TYPE
           SYNTAX      IpAddress
           MAX-ACCESS  read-only
           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."
           ::= { serverClientEntry 3 }

        serverClientLastRequestTime  OBJECT-TYPE
           SYNTAX                         DateAndTime      DhcpTimeInterval
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The time when timestamp of the last request was received." received, to millisecond
              precision if available on the server."
           ::= { serverClientEntry 4 }

        serverClientLastRequestType  OBJECT-TYPE
           SYNTAX      INTEGER {
              bootprequest(0)
              dhcpdiscover(1),
                           bootp(2),
              dhcprequest(3),

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 24]
              dhcpdecline(4),
                           unknown(5),
              dhcprelease(7),
              dhcpinform(8)
              dhcpleasequery(TBD),-- /*new*/
           }
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The type of the last request that was message received for this
                  client."
              client.If the server does not capture this information, the
              value 32,767 is returned."
           REFERENCE
              "RFC2131; RFC2132, section 9.6; draft-ietf-dhc-leasequery-
              02.txt."
           ::= { serverClientEntry 5 }

        serverClientLastResponseType  OBJECT-TYPE
           SYNTAX      INTEGER {
                           bootp(1),
              bootpreply(1),
              dhcpoffer(2),
                           unknown(3),
              dhcpack(5),
              dhcpnak(6)
              dhcpknown(TBD),-- /*new*/
              dhcpunknown(TBD)-- /*new*/
           }
           MAX-ACCESS  read-only
           STATUS      current
           DESCRIPTION
              "The type of the last response that was message sent to this client." client.  If
              the server does not capture this information, the value 32,767
              is returned."
           REFERENCE
              "RFC2131; RFC2132, section 9.6;draft-ietf-dhc-pv4-reconfigure-
              06.txt;draft-ietf-dhc-leasequery-02.txt"
           ::= { serverClientEntry 6 }

            --  serverNotifyObjects:

        --serverNotifyObjects: Objects which are used only in notifications

        serverNotifyDuplicateIPAddress  OBJECT-TYPE  # /*new*/
           SYNTAX      IpAddress
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The IP address which was found to be a duplicate." duplicate.  Duplicates are
              detected by servers which issue an ICMP ECHOREQUEST prior to
              offering an IP address lease."
           ::= { serverNotifyObjects 1 }

            serverNotifyMACAddress

        serverNotifyDuplicateMAC  OBJECT-TYPE  # /*new*/
           SYNTAX      PhysicalAddress
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The offending MAC address which caused a duplicate IP address
              to be detected." detected, if captured by the server, else 00-00-00-00-00-
              00."
           ::= { serverNotifyObjects 2 }

            serverNotifyServer  OBJECT-TYPE  # /*new*/

        serverNotifyClientDuplicateIP  OBJECT-TYPE-- /*renamed*/
           SYNTAX      IpAddress
           MAX-ACCESS  accessible-for-notify
           STATUS      current
           DESCRIPTION
              "The IP Address of offered by a server with which that the DHCP server
                  is attempting requesting client
              has determined to communicate."
               ::= { serverNotifyObjects 3 }

            serverNotifyDuplicateIPAddressDetectedBy OBJECT-TYPE  # /*new*/

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 25] 
               SYNTAX                         INTEGER {dhcpClient(1), dhcpServer(2)}
               MAX-ACCESS  accessible-for-notify
               STATUS                         current
               DESCRIPTION
                  "For be a serverDuplicateAddress notification, this
                  object indicates whether the client or server duplicate, detected
                  the condition.  DHCP servers detect a duplicate address
                  by an unexpected reply to an ICMPECHOREQUEST (ping)
                  message, while DHCP clients detect duplicates by an
                  unexpected reply to means of a
              gratuitous ARP message, message and report
                  this condition to a DHCP server reported through a DHCPDECLINE
              message."
           ::= { serverNotifyObjects 5 }

            serverNotifyContestedIpAddress OBJECT-TYPE  # /*new*/
               SYNTAX                         IpAddress
               MAX-ACCESS  accessible-for-notify
               STATUS                         current
               DESCRIPTION
                  "The IP address for which ownership is claimed by two or
                  more DHCP servers."
               ::= { serverNotifyObjects 6 3 }

        -- Notifications

            dhcpServerMIBNotificationPrefix

        serverMIBNotificationPrefix  OBJECT IDENTIFIER  # /*new*/
        ::= { dhcpServerMIB serverMIB 2 }  # /*renamed*/
            dhcpServerMIBNotifications }serverMIBNotifications OBJECT IDENTIFIER  # /*new*/
        ::= { dhcpServerMIBNotificationPrefix serverMIBNotificationPrefix 0 }

        serverFreeAddressLow  NOTIFICATION-TYPE  # /*new*/
           OBJECTS {
              serverSharedNetworkFreeAddressLowThreshold,
                  serverSharedNetworkFreeAddressValue,
                  serverSharedNetworkFreeAddressUnits
              serverSharedNetworkFreeAddresses
           }
           STATUS      current
           DESCRIPTION
              "This notification signifies that the number of available IP
              addresses for a particular shared network has fallen below the
              value of serverSharedNetworkFreeAddressLowThreshold for that
              shared network."
        ::= { dhcpServerMIBNotifications serverMIBNotifications 1 }

        serverFreeAddressHigh  NOTIFICATION-TYPE  # /*new*/
           OBJECTS {
              serverSharedNetworkFreeAddressHighThreshold,
                  serverSharedNetworkFreeAddressValue,
                  serverSharedNetworkFreeAddressUnits
              serverSharedNetworkFreeAddresses
           }
           STATUS      current
           DESCRIPTION
              "This notification signifies that the number of available IP
              addresses for a particular shared network has risen above the

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 26]
              value of serverSharedNetworkFreeAddressHighThreshold for that
              shared network."
        ::= { dhcpServerMIBNotifications serverMIBNotifications 2 }

        serverServerStart  NOTIFICATION-TYPE  # /*new*/
           OBJECTS     { serverNotifyServerType serverNotifyClientDuplicateIP }
           STATUS      current
           DESCRIPTION
              "This notification signifies that the server of the specified
              type has started on the host from which this notification has
              been sent."
        ::= { dhcpServerMIBNotifications serverMIBNotifications 3 }

        serverServerStop  NOTIFICATION-TYPE  # /*new*/
           OBJECTS  { serverNotifyServerType serverNotifyClientDuplicateIP }
           STATUS         current
           DESCRIPTION
              "This notification signifies that the server of the specified
              type has stopped normally on the host from which this
              notification has been sent."
        ::= { dhcpServerMIBNotifications serverMIBNotifications 4 }

        serverDuplicateAddress NOTIFICATION-TYPE  # /*new*/
           OBJECTS {
              serverNotifyDuplicateIPAddress,
                  serverNotifyMACAddress,
                  serverNotifyDuplicateIPAddressDetectedBy
              serverNotifyDuplicateMAC,
              serverNotifyClientDuplicateMAC
           }
           STATUS      current
           DESCRIPTION
              "This notification signifies that a duplicate IP address has
              been detected.  The DHCP server can detect this condition
              through the ping-before-offer mechanism.  Alternatively, the
              client may have sent a DHCPDECLINE back to the server; this is
              assumed to be the result of the client detecting that the
              address was in use.  In either case, the DHCP server marks the
              IP address as unavailable for leasing to clients.  The
                  serverNotifyDuplicateIPAddressDetectedBy
              serverNotifyClientDuplicateMAC object indicates whether the
              client or server detected this condition."
        ::= { dhcpServerMIBNotifications 7 serverMIBNotifications 5 }-- /*renumbered*/

        serverAddressConflict NOTIFICATION-TYPE
           OBJECTS     { serverNotifyClientDuplicateIP }
           STATUS      current
           DESCRIPTION
        ::= { serverMIBNotifications 6 }-- /*renumbered*/

        -- Conformance

            dhcpServerMIBConformance OBJECT-IDENTITY  # /*renamed*/

        serverMIBConformanceOBJECT-IDENTITY
           STATUS      current
           DESCRIPTION
              "DHCP Server MIB objects are all defined in this branch."
        ::= { dhcpServerMIB serverMIB 3 }  # /*renamed*/

            dhcpServerMIBCompliances OBJECT

        serverMIBCompliancesOBJECT IDENTIFIER
        ::= { dhcpServerMIBConformance serverMIBConformance 1 }  # /*renamed*/

            dhcpServerMIBGroups  OBJECT

        serverMIBGroupsOBJECT IDENTIFIER
        ::= { dhcpServerMIBConformance serverMIBConformance 2 }  # /*renamed*/

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 27]

        -- Compliance groups

            dhcpServerMIBCompliance

        serverMIBCompliance MODULE-COMPLIANCE
               MODULE  --
           MODULE-- this module
           MANDATORY-GROUPS {
              serverSystemGroup,
              bootpCountersGroup,
              dhcpCountersGroup,
                  bootpStatisticsGroup,
                  dhcpStatisticsGroup,
              serverConfigurationGroup,
              serverClientsGroup
           }
           OPTIONAL-GROUPS {
              bootpOptionalStatisticsGroup,
              dhcpOptionalStatisticsGroup
           }
           STATUS      current
           DESCRIPTION
              "Describes the requirements for conformance to the DCHP Server
              MIB"
        ::= { dhcpServerMIBCompliances serverMIBCompliances 1 }

        -- Object groups

        serverSystemGroup OBJECT-GROUP
           OBJECTS {
              serverSystemDescr,
              serverSystemObjectID
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the serverSystemGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 1 }

        bootpCountersGroup OBJECT-GROUP
           OBJECTS {
              bootpCountRequests,
              bootpCountInvalids,
              bootpCountReplies,
              bootpCountDroppedUnknownClients,
              bootpCountDroppedNotServingSubnet
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the bootpBountersGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 2 }

        dhcpCountersGroup OBJECT-GROUP
           OBJECTS {
              dhcpCountDiscovers,
              dhcpCountRequests,
              dhcpCountReleases,
              dhcpCountDeclines,
              dhcpCountInforms,
              dhcpCountInvalids,
              dhcpCountOffers,
              dhcpCountAcks,
              dhcpCountNacks,
              dhcpCountDroppedUnknownClient,
              dhcpCountDroppedNotServingSubnet

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 28]
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the dhcpCountersGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 3 }

            bootpStatisticsGroup

        bootpOptionalStatisticsGroup OBJECT-GROUP
           OBJECTS {
              bootpStatMinArrivalInterval,
              bootpStatMaxArrivalInterval,
              bootpStatLastArrivalTime,
                  bootpStatSunSquaresArrivalTime,
              bootpStatSumSquaresArrivalTime,
              bootpStatMinResponseTime,
              bootpStatMaxResponseTime,
              bootpStatSumReponseTime,
              bootpStatSumSquaresResponseTime
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the bootpStatisticsGroup." bootpOptionalStatisticsGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 4 }

            dhcpStatisticsGroup

        dhcpOptionalStatisticsGroup OBJECT-GROUP
           OBJECTS {
              dhcpStatMinArrivalInterval,
              dhcpStatMaxArrivalInterval,
              dhcpStatLastArrivalTime,
              dhcpStatSumSquaresArrivalTime,
              dhcpStatMinResponseTime,
              dhcpStatMaxResponseTime,
              dhcpStatSumResponseTime,
              dhcpStatSumSquaresResponseTime
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the dhcpStatisticsGroup." dhcpOptionalStatisticsGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 5 }

        serverConfigurationGroup OBJECT-GROUP
           OBJECTS {
              serverSubnet,
              serverSubnetMask,
                  serverSubnetSharedNet,
              serverSubnetSharedNetwork,
              serverRangeStart,
              serverRangeEnd,
                  serverRangeSubnet,
              serverRangeSubnetMask,
              serverRangeInUse,
              serverRangeOutstandingOffers,
              serverAddress,
                  serverAddressSubnet,
            --    serverAddressRange,  # /*duplicate*/
              serverAddressSubnetMask,
              serverAddressRange,
              serverAddressType,
              serverAddressTimeRemaining,
              serverAddressAllowedProtocol,
              serverAddressServedProtocol,
              serverAddressHardwareAddress,  # /*renamed*/

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 29]
              serverAddressClientId,
              serverAddressHostName,
              serverAddressDomainName
              }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the serverConfigurationGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 6 }

        serverClientsGroup OBJECT-GROUP
           OBJECTS {
              serverClientHardwareAddress,  # /*renamed*/
                  serverClientSubnet,
              serverClientSubnetMask,
              serverClientAddress,
              serverClientLastRequestTime,
              serverClientLastRequestType,
              serverClientLastResponseType
           }
           STATUS      current
           DESCRIPTION
              "Objects belonging to the serverClientsGroup."
        ::= { dhcpServerMIBGroups serverMIBGroups 7 }

        serverSharedNetworkObjectsGroup OBJECT-GROUP  # /*new*/
           OBJECTS {
                  serverSharedNetworkFreeAddrLowThreshold,
                  serverSharedNetworkFreeAddrHighThreshold,
                  serverSharedNetworkFreeAddrValue,
                  serverSharedNetworkFreeAddrUnits
              serverSharedNetworkFreeAddressLowThreshold,
              serverSharedNetworkFreeAddressHighThreshold,
              serverSharedNetworkFreeAddressValue
           }
           STATUS      current
           DESCRIPTION
              "DHCP Server MIB objects used in shared networks."
        ::= { dhcpServerMIBGroups serverMIBGroups 8 }

        serverNotifyObjectsGroup OBJECT-GROUP  # /*new*/
           OBJECTS {
              serverNotifyDuplicateIPAddress,
                  serverNotifyMACAddress,
                  serverNotifyDuplicateIPAddressDetectedBy,
                  serverNotifyServer,
                  serverNotifyServerType,
              serverNotifyDuplicateMAC,
              serverNotifyClientDuplicateMAC,
              serverNotifyClientDuplicateIP,
              serverNotifyContestedIpAddress
           }
           STATUS      current
           DESCRIPTION
              "DHCP Server MIB objects used in notifications."
        ::= { dhcpServerMIBGroups serverMIBGroups 9 }

            serverNotifyicationsGroup

        serverNotificationsGroup NOTIFICATION-GROUP  # /*new*/
           NOTIFICATIONS {
              serverFreeAddressLow,
              serverFreeAddressHigh,
              serverServerStart,
              serverServerStop,
              serverDNSQueueTooBig,
              serverOtherServerNotResponding,

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 30]
              serverDuplicateAddress,
              serverAddressConflict,
              serverOtherServerResponding,
              serverFailoverConfigMismatch
           }
           STATUS      current
           DESCRIPTION
                  "Notifyications which
              "Notifications that are implemented by the DHCP Server agent."
        ::= { dhcpServerMIBGroups serverMIBGroups 10 }

        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.

        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 that 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. goes to Working Group
        Last Call.

     5.1. Issues

        Not all of these issues have been resolved, even in the latest (-07)
        draft.  Some may become items for future study, while some will
        probably be dropped.

        o  Are placeholders for expected DHCP option values a good or bad
           idea?

        o  Ryan Troll proposed four or five traps that Nathan Lane
           enthusiastically supported.  If traps are supported, but it has been difficult to be included, achieve
           any consensus (or, for that
              should be done soon. matter, much interest) in them.

        o what  What is the best way to reset counters and statistics?

              o do  Is it
           necessary to reset them at all?  The -07 draft does not declare
           any counters as read-write or read-create, primarily to avoid
           these questions, as well as to provide fundamental security over
           objects.

           -- Do we need to reset them individually, as groups, or as a
              whole?

              o

           -- Do we need a timestamp of when they were reset

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 31] reset?

        o should  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  If counted by error type, what is the set of errors that we should
           use?

        o perhaps  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  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  Sums of inter-arrival and
        response times was were deleted since the management station can easily
        calculate them.  The last arrival time objects were added.

        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.

            The "-03b"  This version also incorporated an address
        change for one of the authors, revisions to standard text required by
        the IETF, and some editorial clarifications.

        The "-04" version changed the maximum size of the object
        serverAddressHostName from 64 to 255 octets, and added clarifying
        text to both that object and to serverAddressDomainName regarding the
        practical values for the length of both objects.

        The "-05" version added a number of traps suggested by Kim Kinnear,
        made a number of small renaming and renumbering changes (annotated in
        the MIB itself) and added the Shared Network concept to describe
        shared network segments: several subnetworks that coexist on one
        medium.  This was done partly because the Address Range concept did
        not adequately describe the "scoping" of address pools as is common
        with many current server implementations.  Also updated the authors

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 32]
        address and contact information, and incorporated a number of
        corrections and amplifications suggested by various readers of the
            -04 "-
        04" draft, including a missing OID for serverNotifyObjects and a
        syntax error for PhysicalAddress.

        The "-06" version corrects a number of flaws reported by Rick Geesen
        and Jin Tao, mostly caused by typographical errors in the "-05"
        version as well as some unintentionally omitted text for
        serverNotifyObjects.

        The "-07" version changes BOOTP and DHCP statistics from mandatory to
        optional, renaming object identifiers as required to match.  All
        objects, tables, and groups in previous drafts for Dynamic DNS
        updating and Failover have been removed.  All tables were carefully
        examined to be certain that they really could be simply implemented.
        Many items were renamed or renumbered.  Placeholder definitions of
        message types (both requests and responses) were added to support
        DHCPFORCERENEW, DHCPQUERY, DHCPKNOWN, and DHCPUNKNOWN.  A few [more]
        typographical errors were found and fixed.  Because of an error
        posting the 07 draft closes several issues raised during peer review
            discussions on to the DHC mailing list, incorporates several new
            elements, editor's queue it was not accepted in
        time for IETF-52 and makes a number is being submitted to the Internet-Drafts editor
        with one change identified by Alan Hackert.  Finally, some of small revisions based on comments
            from reviewers. the
        initial text was brought in line with standard requirements for
        Internet-Drafts.

     6. Acknowledgements

        This document is the result of work undertaken the by DHCP working
        group.  The authors editors 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.

        Thanks to Ryan Troll, Nathan Lane, Kim Kinnear, Yannick Koehler, and
        Nathan Lane Lane, Rick Geesen, Jin Tao, James Brister, and Alan Hackert
        for their review, comments, and contributions.

     7. Security Considerations

        There are a number of no management objects defined in this MIB that have a MAX-ACCESS MAX-
        ACCESS clause of read-write and/or 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.  Many
        network administrators object to settable management objects because
        of the limited security features of SNMPv1 and SNMPv2.  We have
        chosen not to fight that battle in constructing this MIB.

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

            It

        SNMPv2 communities provide a minimal level of access control, but 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 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.

        Denial of Service attacks on a DHCP server are conceivable by
        flooding the SNMP (sub-)agent with requests, tying up host system and
        server resources processing SNMP messages.  The authors know of no
        way to wholly prevent such attacks, but have attempted to construct
        relatively simple tables to minimize the work required to respond to
        messages.

     8. References

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

            [RFC1902]

       [RFC1123] R. Braden, "Requirements for Internet Hosts -- Application
          and Support," RFC 1123, October 1989.

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

       [RFC2578] Case, J., McCloghrie, K., Perkins, D.,  Rose, M.,
          Schoenwaelder, J., and S. Waldbusser, "Structure of Management
          Information for Version 2 of the

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 33] Simple Network Management Protocol (SNMPv2)",
          (SNMPv2)," RFC 1902, January
                 1996.

            [RFC1903] 2578, April 1999.

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

            [RFC1904] 2579, April 1999.

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

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

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

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

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

       <draft-ietf-dhc-pv4-reconfigure-06.txt>, Yves T'Joens and Christian
          Hublet, Peter De Schrijver, "The DHCP Reconfigure Extension," July
          2001

       <draft-ietf-dhc-leasequery-02.txt>, Rich Woundy and Kim Kinnear,
          "DHCP Lease Query," July 2001

     9. Editors' Addresses

        Richard Barr Hibbs
            UltraDNS Corporation
            800 North San Mateo Drive
        952 Sanchez Street
        San Mateo, CA 94401-2261 Francisco, California 94114-3362
        USA

        Phone:  +1 650-227-2678  +1-(415)-648-3920
        Fax:    +1 650-227-2662  +1-(415)-648-9017
        Email:  rbhibbs@ultraDNS.com  rbhibbs@pacbell.net

        Glenn Waters
        Nortel Networks
        310-875 Carling Avenue,
        Ottawa, Ontario K1S 5P1
        Canada

        Phone:  +1 613-765-0249  +1-(613)-798-4925
        Email:  gww@nortelnetworks.com  gww@NortelNetworks.com

     10. Full Copyright Statement

        Copyright (C) The Internet Society (2000).  All Society, 2002.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, works.However, this

          Hibbs & Waters        Expires: Nov 2000 + 6 months            [Page 34]
        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: Nov 2000 + 6 months            [Page 35]