draft-ietf-dhc-server-mib-06.txt   draft-ietf-dhc-server-mib-07.txt 
Network Working Group Barr Hibbs Network Working Group Barr Hibbs
INTERNET-DRAFT (no affiliation) INTERNET-DRAFT (no affiliation)
Category: Standards Track Glenn Waters Category: Standards Track Glenn Waters
Nortel Networks Nortel Networks
February 2002 November 2002
Dynamic Host Configuration Protocol (DHCP) Server MIB Dynamic Host Configuration Protocol (DHCP) Server MIB
<draft-ietf-dhc-server-mib-06.txt> <draft-ietf-dhc-server-mib-07.txt>
Saved Thursday, February 14, 2002, 11:26:01 AM Saved Monday, November 04, 2002, 4:29:26 AM
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 9 skipping to change at page 2, line 9
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in Information Base (MIB) for use with network management protocols in
the Internet Community. In particular, it defines objects used for the Internet Community. In particular, it defines objects used for
the management of Dynamic Host Configuration Protocol (DHCP) and the management of Dynamic Host Configuration Protocol (DHCP) and
Bootstrap Protocol (BOOTP) servers. Bootstrap Protocol (BOOTP) servers.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. Overview.......................................................3 2. Overview.......................................................3
2.1. Relationship to Other MIBs.................................4 2.1. Relationship to Other MIBs.................................5
2.1.1. DHCP MIB Extensions...................................4 2.1.1. DHCP MIB Extensions...................................5
2.1.2. Host System MIB Extensions............................4 2.1.2. Host System MIB Extensions............................5
2.1.3. DHCPv6 Server MIB Extensions..........................4 2.1.3. DHCPv6 Server MIB Extensions..........................5
2.1.4. DHCP Client MIB Extensions............................5 2.1.4. DHCP Client MIB Extensions............................6
2.1.5. DHCP Relay Agent MIB Extensions.......................5 2.1.5. DHCP Relay Agent MIB Extensions.......................6
2.2. Textual Conventions Introduced in this MIB.................5 2.2. Textual Conventions Introduced in this MIB.................6
2.2.1. DhcpTimeInterval......................................5 2.2.1. DhcpTimeInterval......................................6
2.2.2. HardwareAddressType...................................5 2.2.2. HardwareAddressType...................................6
2.2.3. HardwareAddressLength.................................5 2.2.3. HardwareAddressLength.................................6
2.2.4. MacAddress............................................5 2.2.4. MacAddress............................................6
2.2.5. PhysicalAddress.......................................5 2.2.5. PhysicalAddress.......................................6
2.2.6. DhcpLabel.............................................6 2.2.6. DhcpLabel.............................................7
2.3. BOOTP and DHCP Counter Groups..............................6 2.3. BOOTP and DHCP Counter Groups..............................7
2.4. BOOTP and DHCP Optional Statistics Group...................6 2.4. BOOTP and DHCP Optional Statistics Group...................7
2.5. Response Times and ICMP Echo...............................8 2.5. Response Times and ICMP Echo...............................9
3. Definitions....................................................8 3. Definitions....................................................9
4. Intellectual Property.........................................39 4. Intellectual Property.........................................42
5. Notes.........................................................40 5. Notes.........................................................42
5.1. Issues....................................................40 5.1. Issues....................................................43
5.2. Changes from Prior Drafts.................................41 5.2. Changes from Prior Drafts.................................43
6. Acknowledgements..............................................42 6. Acknowledgements..............................................45
7. Security Considerations.......................................42 7. Security Considerations.......................................45
8. References....................................................43 8. References....................................................46
9. Editors' Addresses............................................44 9. Editors' Addresses............................................48
10. Full Copyright Statement.....................................44 10. Full Copyright Statement.....................................49
1. Introduction 1. Introduction
This memo was produced by the DHCP Working Group and defines a This memo was produced by the DHCP Working Group and defines a
portion of the Management Information Base (MIB) for use with network portion of the Management Information Base (MIB) for use with network
management protocols in the Internet community. In particular, it management protocols in the Internet community. In particular, it
describes a set of extensions that DHCP and Bootstrap Protocol describes a set of extensions that DHCP and Bootstrap Protocol
(BOOTP) servers implement. Many implementations support both DHCP (BOOTP) servers implement. Many implementations support both DHCP
and BOOTP within a single server and hence this memo describes the and BOOTP within a single server and hence this memo describes the
MIB for both DHCP and BOOTP servers. MIB for both DHCP and BOOTP servers.
This memo does not cover DHCP/BOOTP client nor relay agent MIB This memo does not cover DHCP/BOOTP client nor relay agent MIB
extensions: these are possibly the subjects of future investigation extensions: these are possibly the subjects of future investigation
[see discussion in section 2.1.] Also excluded from this MIB [see discussion in section 3.1.] Also excluded from this MIB
extension in the interest of simplicity are DHCP Dynamic DNS extension in the interest of simplicity are DHCP Dynamic DNS
Updating, Failover, Authentication, and Load Balancing: these Updating, Failover, Authentication, and Load Balancing: these
functions and features could be subjects of future MIB extensions. functions and features could be subjects of future MIB extensions.
Provision is also made for Standards-Track additions to the DHCP Provision is also made for Standards-Track additions to the DHCP
Message Type (option 61.) Message Type (option 61.)
This memo is based on the Internet-standard Network Management This memo is based on the Internet-standard Network Management
Framework as defined by documents [RFC2578, RFC2579, RFC2580]. Framework as defined by documents [RFC2578, RFC2579, RFC2580].
Objects defined in this MIB allow access to and control of DHCP Objects defined in this MIB allow access to and control of DHCP
Server Software. Servers MAY also provide additional management Server Software. Servers MAY also provide additional management
capabilities through the use of the Applications MIB [RFC2287]. capabilities through the use of the Applications MIB [RFC2287].
The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT,"
"SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this
document are to be interpreted as described in document [RFC2119]. document are to be interpreted as described in document [RFC2119].
2. Overview 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD
16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
[RFC1215]. The second version, called SMIv2, is described in STD
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58,
RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906]. The third version of the message
protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573 [RFC2573]
and the view-based access control mechanism described in RFC 2575
[RFC2575].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3. Overview
In the tradition of the Simple Network Management Protocol (SNMP) the In the tradition of the Simple Network Management Protocol (SNMP) the
minimum number of objects possible are defined in this MIB, while minimum number of objects possible are defined in this MIB, while
still providing as rich a set of management information as possible. 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 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, objects that are provided. Further to the tradition of the SNMP,
computationally intense operations are left to the domain of the computationally intense operations are left to the domain of the
management station. Thus, this MIB provides a set of objects from management station. Thus, this MIB provides a set of objects from
which other management information may be derived. which other management information may be derived.
The examples provided in sections 2.3 through 2.5 are not meant to be The examples provided in sections 3.3 through 3.5 are not meant to be
comprehensive but are illustrative of the potential uses of the comprehensive but are illustrative of the potential uses of the
objects defined by this MIB. objects defined by this MIB.
2.1. Relationship to Other MIBs 3.1. Relationship to Other MIBs
2.1.1. DHCP MIB Extensions 3.1.1. DHCP MIB Extensions
The DHCP MIB extensions will the "dhcp" branch of the standard MIB-2 The DHCP MIB extensions will be the "dhcp" branch of the standard
tree, as illustrated by the following diagram: MIB-2 tree, as illustrated by the following diagram:
+-------+ +-------+
| MIB-2 | | MIB-2 |
+---+---+ +---+---+
| |
| |
+---+---+ +---+---+
| dhcp | | dhcp |
+---+---+ +---+---+
| |
| |
+---------------+------+---------+---------------------+ + -- -- -- -- -- -- -- -+ -- -- -- + -- -- -- -- -+ -- -- -- --
-- -- -- -- -- -- -+
| | | | | | | |
+-----+-----+ +-----+----+ +-------+--------+ +------+------+ + -- -- -+ -- -- -+ + -- -- -+ -- -- + + -- -- -- -+ -- -- -- --
+ + -- -- -- + -- -- -- +
| dhcp-v4 | | dhcp-v4 | | dhcp-v4 | | dhcp-v6 MIB | | dhcp-v4 | | dhcp-v4 | | dhcp-v4 | | dhcp-v6 MIB |
|Server MIB | |Client MIB| |Relay Agent MIB | | Extensions | |Server MIB | |Client MIB| |Relay Agent MIB | | Extensions |
|(this memo)| | (future) | | (future work) | | (future) | |(this memo)| | (future) | | (future work) | | (future) |
+-----------+ +----------+ +----------------+ +-------------+ + -- -- -- -- -- -+ + -- -- -- -- -- + + -- -- -- -- -- -- -- --
+ + -- -- -- -- -- -- -+
The MIBs will share a common branching point, but are independently The MIBs will share a common branching point, but are independently
defined. defined.
2.1.2. Host System MIB Extensions 3.1.2. Host System MIB Extensions
The Host System MIB [RFC1123] provides for information, command, and The Host System MIB [RFC1123] provides for information, command, and
control of the host computer system on which a DHCP server resides. control of the host computer system on which a DHCP server resides.
The DHCP Server MIB specifically does not include any objects that The DHCP Server MIB specifically does not include any objects that
may be accessible using the Host System MIB. may be accessible using the Host System MIB.
2.1.3. DHCPv6 Server MIB Extensions 3.1.3. DHCPv6 Server MIB Extensions
When this set of MIB extensions is developed, it will share a common When this set of MIB extensions is developed, it will share a common
branch point in the MIB tree with the other DHCP MIB Extensions. branch point in the MIB tree with the other DHCP MIB Extensions.
2.1.4. DHCP Client MIB Extensions 3.1.4. DHCP Client MIB Extensions
If this set of MIB extensions is ever developed, it will share a 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 common branch point in the MIB tree with the other DHCP MIB
Extensions, and will use many of the same textual conventions. Extensions, and will use many of the same textual conventions.
2.1.5. DHCP Relay Agent MIB Extensions 3.1.5. DHCP Relay Agent MIB Extensions
If this set of MIB extensions is ever developed, it will share a 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 common branch point in the MIB tree with the other DHCP MIB
Extensions, and will use many of the same textual conventions. Extensions, and will use many of the same textual conventions.
2.2. Textual Conventions Introduced in this MIB 3.2. Textual Conventions Introduced in this MIB
Severaal conceptual data types have been introduced as textual Several conceptual data types have been introduced as textual
conventions in this DHCP MIB document. These additions will conventions in this DHCP MIB document. These additions will
facilitate the common understanding of information used by the DHCP facilitate the common understanding of information used by the DHCP
server. No changes to the SMI or the SNMP are necessary to support server. No changes to the SMI or the SNMP are necessary to support
these conventions. these conventions.
2.2.1. DhcpTimeInterval 3.2.1. DhcpTimeInterval
This data type measures time intervals since the beginning of some This data type measures time intervals since the beginning of some
epoch in milliseconds. epoch in milliseconds.
2.2.2. HardwareAddressType 3.2.2. HardwareAddressType
This data type contains the type of hardware address represented by This data type contains the type of hardware address represented by
MacAddress, as defined for ARP messages. MacAddress, as defined for ARP messages.
2.2.3. HardwareAddressLength 3.2.3. HardwareAddressLength
The length in octets of MacAddress is contained in this type. The length in octets of MacAddress is contained in this type.
2.2.4. MacAddress 3.2.4. MacAddress
The actual layer 1 hardware address is contained in this data type. The actual layer 1 hardware address is contained in this data type.
2.2.5. PhysicalAddress 3.2.5. PhysicalAddress
This data type combines the hardware type octet with the length and This data type combines the hardware type octet with the length and
hardware (NIC or MAC) address to produce a unique address type. hardware (NIC or MAC) address to produce a unique address type.
2.2.6. DhcpLabel 3.2.6. DhcpLabel
This data type contains labels used as identifiers by DHCP servers. This data type contains labels used as identifiers by DHCP servers.
2.3. BOOTP and DHCP Counter Groups 3.3. BOOTP and DHCP Counter Groups
This section describes some of the management information that may be This section describes some of the management information that may be
derived from the objects provided in the counter groups. derived from the objects provided in the counter groups.
The total number of valid DHCP packets received by the server is The total number of valid DHCP packets received by the server is
computed as the sum of the dhcpCountDiscovers, dhcpCountRequests, computed as the sum of the dhcpCountDiscovers, dhcpCountRequests,
dhcpCountReleases, dhcpCountDeclines, dhcpCountInforms and dhcpCountReleases, dhcpCountDeclines, dhcpCountInforms and
dhcpCountLeaseQueries objects. The total number of valid packets dhcpCountLeaseQueries objects. The total number of valid packets
(BOOTP and DHCP) received is computed as the total number of valid (BOOTP and DHCP) received is computed as the total number of valid
DHCP packets plus the value of the bootpCountRequests object. The DHCP packets plus the value of the bootpCountRequests object. The
skipping to change at page 6, line 32 skipping to change at page 7, line 32
dhcpCountInvalids. dhcpCountInvalids.
Similar to the received computations, the total number of DHCP Similar to the received computations, the total number of DHCP
packets sent by the server is computed as the sum of the packets sent by the server is computed as the sum of the
dhcpCountOffers, dhcpCountAcks, dhcpCountNacks, dhcpCountOffers, dhcpCountAcks, dhcpCountNacks,
dhcpCountForcedRenews, dhcpCountKnowns, and dhcpCountUnknowns dhcpCountForcedRenews, dhcpCountKnowns, and dhcpCountUnknowns
objects. The number of packets (BOOTP and DHCP) sent by the server 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 is computed as the total number of DHCP packets sent plus the value
of the bootpCountReplies object. of the bootpCountReplies object.
2.4. BOOTP and DHCP Optional Statistics Group 3.4. BOOTP and DHCP Optional Statistics Group
This section describes some of the management information that may be This section describes some of the management information that may be
derived from the objects provided in the optional statistics group. derived from the objects provided in the optional statistics group.
Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter- 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 arrival time of valid DHCP messages for the interval t1 to t2 can be
computed as (dhcpStatLastArrivalTime at t2 minus computed as (dhcpStatLastArrivalTime at t2 minus
dhcpStatLastArrivalTime at t1) divided by (valid DHCP received packet dhcpStatLastArrivalTime at t1) divided by (valid DHCP received packet
count at t2 minus valid DHCP received packet count at t1). count at t2 minus valid DHCP received packet count at t1).
skipping to change at page 8, line 23 skipping to change at page 9, line 23
out of use. Examples of server-reserved addresses are those out of use. Examples of server-reserved addresses are those
which have been declined (i.e., through a DHCPDECLINE) by a which have been declined (i.e., through a DHCPDECLINE) by a
client or those which have responded to an ICMP echo before they client or those which have responded to an ICMP echo before they
were assigned. were assigned.
The protocol used to allocate the address may be determined from the The protocol used to allocate the address may be determined from the
serverAddressServedProtocol object. This object indicates whether serverAddressServedProtocol object. This object indicates whether
the address has never been served, or whether BOOTP or DHCP was used the address has never been served, or whether BOOTP or DHCP was used
to allocate the address. to allocate the address.
2.5. Response Times and ICMP Echo 3.5. Response Times and ICMP Echo
According to [RFC2131], servers SHOULD try to determine if an address According to [RFC2131], servers SHOULD try to determine if an address
is in use before assigning it. Some servers choose not to perform is in use before assigning it. Some servers choose not to perform
this check, letting the client determine for itself if the address is this check, letting the client determine for itself if the address is
in use. Other servers perform an ICMP echo (Ping) just prior to in use. Other servers perform an ICMP echo (Ping) just prior to
assigning an address. Servers that perform a Ping before responding assigning an address. Servers that perform a Ping before responding
to a DHCPDISCOVER should not include in the response time the time to a DHCPDISCOVER should not include in the response time the time
from when the Ping was transmitted until the time that either a 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 was received or that the server timed out waiting for a
response. response.
3. Definitions 4. Definitions
-- definitions for a DHCP (Dynamic Host Configuration Protocol) -- definitions for a DHCP (Dynamic Host Configuration Protocol)
server server
DHCP-SERVER-MIB DEFINITIONS ::= BEGIN DHCP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter64, Counter32, Gauge32, Unsigned32, mib-2, MODULE-IDENTITY, Counter64, Counter32, Gauge32, Unsigned32, mib-2, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-IDENTITY, IpAddress OBJECT-TYPE, OBJECT-IDENTITY
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue, TEXTUAL-CONVENTION, RowStatus, TruthValue, DateAndTime
DateAndTime FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress, InetAddressIPv4,
InetAddressPrefixLength
FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
dhcp OBJECT-IDENTITY dhcp OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The dhcp branch in the standard network management framework." "The dhcp branch in the standard network management framework."
::= { mib-2 99 } -- IANA will make official assignment ::= { mib-2 99 } -- IANA will make official assignment
serverMIB MODULE-IDENTITY serverMIB MODULE-IDENTITY
LAST-UPDATED "2002-02-14 11:26" REVISION "2002-11-04 04:29Z÷
DESCRIPTION "Initial Version, published as RFC xxxx."
-- RFC Editor assigns xxxx
LAST-UPDATED "2002-11-04 04:29Z"
ORGANIZATION "IETF DHC Working Group" ORGANIZATION "IETF DHC Working Group"
General Discussion: dhcwg@ietf.org
Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
Archive: http://www1.ietf.org/mailman/listinfo/dhcwg
Chair: Ralph Droms, rdroms@cisco.com
CONTACT-INFO CONTACT-INFO
" Richard Barr Hibbs " Richard Barr Hibbs
Postal: 952 Sanchex Street Postal: 952 Sanchex Street
San Francisco, California 94114-3362 San Francisco, California 94114-3362
USA USA
Tel: +1-(415)-648-3920 Tel: +1-(415)-648-3920
Fax: +1-(415)-648-9017 Fax: +1-(415)-648-9017
E-mail: rbhibbs@pacbell.net E-mail: rbhibbs@pacbell.net
Glenn Waters Glenn Waters
skipping to change at page 10, line 35 skipping to change at page 11, line 48
serverConfiguration OBJECT-IDENTITY serverConfiguration OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that contain pre-configured and dynamic configuration "Objects that contain pre-configured and dynamic configuration
information." information."
::= { serverMIBObjects 6 } ::= { serverMIBObjects 6 }
bootpClients OBJECT-IDENTITY bootpClients OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that map bootp clients to IP addresses." "Objects that map BOOTP clients to IP addresses."
::= { serverMIBObjects 7 } ::= { serverMIBObjects 7 }
dhcpClients OBJECT-IDENTITY dhcpClients OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that map DHCP clients to IP addresses." "Objects that map DHCP clients to IP addresses."
::= { serverMIBObjects 8 } ::= { serverMIBObjects 8 }
-- Textual conventions defined by this memo -- Textual conventions defined by this memo
skipping to change at page 11, line 50 skipping to change at page 13, line 12
} }
DISPLAY-HINT "t,l,xx[:xx...]" DISPLAY-HINT "t,l,xx[:xx...]"
STATUS current STATUS current
REFERENCE "RFC 2131" REFERENCE "RFC 2131"
DESCRIPTION DESCRIPTION
"A Layer 1 address which includes the hardware type space as "A Layer 1 address which includes the hardware type space as
well as the usual MAC address. This encoding is intended to well as the usual MAC address. This encoding is intended to
mirror the representation of physical addresses in DHCP." mirror the representation of physical addresses in DHCP."
DhcpLabel ::= TEXTUAL-CONVENTION DhcpLabel ::= TEXTUAL-CONVENTION
SYNTAX DisplayString (SIZE (1..100)) SYNTAX SnmpAdminString (SIZE (1..100))
DISPLAY-HINT DISPLAY-HINT
STATUS current STATUS current
DESCRIPTION DESCRIPTION
-- serverSystem Group -- serverSystem Group
serverSystemDescr OBJECT-TYPE serverSystemDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255)) SYNTAX SnmpAdminString (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the server. This value should "A textual description of the server. This value should
include the full name and version identification of the include the full name and version identification of the
server." server."
::= { serverSystem 1 } ::= { serverSystem 1 }
serverSystemObjectID OBJECT-TYPE serverSystemObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
skipping to change at page 13, line 42 skipping to change at page 15, line 4
dhcpCountInforms OBJECT-TYPE dhcpCountInforms OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPINFORM (option 53 with value 8) packets "The number of DHCPINFORM (option 53 with value 8) packets
received." received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 5 } -- /*renumbered*/ ::= { dhcpCounters 5 } -- /*renumbered*/
dhcpCountLeaseQueries OBJECT-TYPE -- /*new*/ dhcpCountLeaseQueries OBJECT-TYPE -- /*new*/
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPLEASEQUERY (option 53 with value TBD) "The number of DHCPLEASEQUERY (option 53 with value 9) packets
packets received." received."
REFERENCE REFERENCE
"draft-ietf-dhc-leasequery-02.txt." "draft-ietf-dhc-leasequery-02.txt."
::= { dhcpCounters 6 } -- /*new*/ ::= { dhcpCounters 6 } -- /*new*/
dhcpCountPlaceHolder1 OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Placeholder for anticipated new DHCP option 53 message type."
REFERENCE
"None."
::= { dhcpCounters 7 } -- /*new*/
dhcpCountPlaceHolder2 OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Placeholder for anticipated new DHCP option 53 message type."
REFERENCE
"None."
::= { dhcpCounters 8 } -- /*new*/
-- DHCP sent packet counters -- DHCP sent packet counters
dhcpCountOffers OBJECT-TYPE dhcpCountOffers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPOFFER (option 53 with value 2) packets "The number of DHCPOFFER (option 53 with value 2) packets
sent." sent."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 11 } -- /*renumbered*/ ::= { dhcpCounters 9 } -- /*renumbered*/
dhcpCountAcks OBJECT-TYPE dhcpCountAcks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPACK (option 53 with value 5) packets sent." "The number of DHCPACK (option 53 with value 5) packets sent."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 12 } -- /*renumbered*/ ::= { dhcpCounters 10 } -- /*renumbered*/
dhcpCountNacks OBJECT-TYPE dhcpCountNacks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPNACK (option 53 with value 6) packets sent." "The number of DHCPNACK (option 53 with value 6) packets sent."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 13 } -- /*renumbered*/ ::= { dhcpCounters 11 } -- /*renumbered*/
dhcpCountForcedRenews OBJECT-TYPE -- /*new*/ dhcpCountForcedRenews OBJECT-TYPE -- /*new*/
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPFORCERENEW (option 53 with value TBD) "The number of DHCPFORCERENEW (option 53 with value TBD)
packets sent." packets sent."
REFERENCE REFERENCE
"draft-ietf-dhc-pv4-reconfigure-06.txt." "draft-ietf-dhc-pv4-reconfigure-06.txt."
::= { dhcpCounters 14 } -- /*new*/ ::= { dhcpCounters 12 } -- /*new*/
dhcpCountKnowns OBJECT-TYPE -- /*new*/ dhcpCountKnowns OBJECT-TYPE -- /*new*/
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPKNOWN (option 53 with value TBD) packets "The number of DHCPKNOWN (option 53 with value TBD) packets
sent." sent."
REFERENCE REFERENCE
"draft-ietf-dhc-leasequery-02.txt." "draft-ietf-dhc-leasequery-03.txt."
::= { dhcpCounters 12 } -- /*new*/ ::= { dhcpCounters 13 } -- /*new*/
dhcpCountUnknowns OBJECT-TYPE -- /*new*/ dhcpCountUnknowns OBJECT-TYPE -- /*new*/
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPUNKNOWN (option 53 with value TBD) packets "The number of DHCPUNKNOWN (option 53 with value TBD) packets
sent." sent."
REFERENCE REFERENCE
"draft-ietf-dhc-leasequery-02.txt." "draft-ietf-dhc-leasequery-03.txt."
::= { dhcpCounters 13 } -- /*new*/ ::= { dhcpCounters 14 } -- /*new*/
dhcpCountActives OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCPACTIVE (option 53 with value TBD) packets
sent."
REFERENCE
"draft-ietf-dhc-leasequery-03.txt."
::= { dhcpCounters 15 } -- /*new*/
dhcpCountUnimplementeds OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCPUNIMPLEMENTED (option 53 with value TBD)
packets sent."
REFERENCE
"draft-ietf-dhc-leasequery-03.txt."
::= { dhcpCounters 16 } -- /*new*/
dhcpCountPlaceHolder3 OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Placeholder for anticipated new DHCP option 53 message types."
REFERENCE
"None."
::= { dhcpCounters 17 } -- /*new*/
dhcpCountPlaceHolder4 OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Placeholder for anticipated new DHCP option 53 message types."
REFERENCE
"None."
::= { dhcpCounters 18 } -- /*new*/
-- DHCP packet error counters -- DHCP packet error counters
dhcpCountInvalids OBJECT-TYPE dhcpCountInvalids OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets received whose DHCP message type "The number of DHCP packets received whose DHCP message type
(i.e., option number 53) is not understood or handled by the (i.e., option number 53) is not understood or handled by the
server." server."
::= { dhcpCounters 17 } -- /*renumbered*/ ::= { dhcpCounters 19 } -- /*renumbered*/
dhcpCountDroppedUnknownClient OBJECT-TYPE dhcpCountDroppedUnknownClient OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets dropped due to the server not "The number of DHCP packets dropped due to the server not
recognizing or not providing service to the client-id and/or recognizing or not providing service to the client-id and/or
hardware address received in the incoming packet." hardware address received in the incoming packet."
::= { dhcpCounters 18 } -- /*renumbered*/ ::= { dhcpCounters 20 } -- /*renumbered*/
dhcpCountDroppedNotServingSubnet OBJECT-TYPE dhcpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets dropped due to the server not being "The number of DHCP packets dropped due to the server not being
configured or not otherwise able to serve addresses on the configured or not otherwise able to serve addresses on the
subnet from which this message was received." subnet from which this message was received."
::= { dhcpCounters 19 } -- /*renumbered*/ ::= { dhcpCounters 21 } -- /*renumbered*/
-- dhcpOptionalStatistics group -- dhcpOptionalStatistics group
dhcpStatMinArrivalInterval OBJECT-TYPE dhcpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time between receiving two DHCP "The minimum amount of time between receiving two DHCP
messages. A message is received at the server when the server messages. A message is received at the server when the server
is able to begin processing the message. This typically occurs is able to begin processing the message. This typically occurs
skipping to change at page 22, line 39 skipping to change at page 25, line 15
STATUS current STATUS current
INDEX { serverSharedNetworkName } INDEX { serverSharedNetworkName }
DESCRIPTION DESCRIPTION
"A logical row in the serverSharedNetworkTable." "A logical row in the serverSharedNetworkTable."
::= { serverSharedNetworkTable 1} ::= { serverSharedNetworkTable 1}
ServerSharedNetworkEntry ::= SEQUENCE { ServerSharedNetworkEntry ::= SEQUENCE {
serverSharedNetworkName DhcpLabel, serverSharedNetworkName DhcpLabel,
serverSharedNetworkFreeAddresses Unsigned32, serverSharedNetworkFreeAddresses Unsigned32,
serverSharedNetworkReservedAddresses Unsigned32,-- /*new*/ serverSharedNetworkReservedAddresses Unsigned32,-- /*new*/
serverSharedNetworkTotalAddresses Unsigned32-- /*renamed*/ serverSharedNetworkTotalAddresses Unsigned32 --
/*renamed*/
} }
serverSharedNetworkName OBJECT-TYPE serverSharedNetworkName OBJECT-TYPE
SYNTAX DhcpLabel-- /*modified*/ SYNTAX DhcpLabel-- /*modified*/
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the shared network, which uniquely identifies an "The name of the shared network, which uniquely identifies an
entry in the serverSharedNetworkTable." entry in the serverSharedNetworkTable."
::= { serverSharedNetworkEntry 1 } ::= { serverSharedNetworkEntry 1 }
skipping to change at page 24, line 4 skipping to change at page 26, line 29
serverSubnetEntry OBJECT-TYPE serverSubnetEntry OBJECT-TYPE
SYNTAX ServerSubnetEntry SYNTAX ServerSubnetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverSubnet } INDEX { serverSubnet }
DESCRIPTION DESCRIPTION
"A logical row in the serverSubnetTable." "A logical row in the serverSubnetTable."
::= { serverSubnetTable 1 } ::= { serverSubnetTable 1 }
ServerSubnetEntry ::= SEQUENCE { ServerSubnetEntry ::= SEQUENCE {
serverSubnet IpAddress, serverSubnet InetAddressIPv4,
serverSubnetMask IpAddress, serverSubnetMask InetAddressPrefixLength,
serverSubnetSharedNetworkName DhcpLabel,-- /*modified*/ serverSubnetSharedNetworkName DhcpLabel,-- /*modified*/
serverSubnetFreeAddressLowThreshold Unsigned32, serverSubnetFreeAddressLowThreshold Unsigned32,
serverSubnetFreeAddressHighThreshold Unsigned32, serverSubnetFreeAddressHighThreshold Unsigned32,
ServerSubnetFreeAddresses Unsigned32 -- /*renamed*/ ServerSubnetFreeAddresses Unsigned32 -- /*renamed*/
} }
serverSubnet OBJECT-TYPE serverSubnet OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only-- /*changed*/ MAX-ACCESS read-only-- /*changed*/
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the subnet." "The IP address of the subnet."
::= { serverSubnetEntry 1 } ::= { serverSubnetEntry 1 }
serverSubnetMask OBJECT-TYPE serverSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet mask of the subnet. This MUST be the same as the "The subnet mask of the subnet. This MUST be the same as the
value of DHCP option 1 offered to clients on this subnet." value of DHCP option 1 offered to clients on this subnet."
::= { serverSubnetEntry 2 } ::= { serverSubnetEntry 2 }
serverSubnetSharedNetworkName OBJECT-TYPE-- /*renamed*/ serverSubnetSharedNetworkName OBJECT-TYPE-- /*renamed*/
SYNTAX DhcpLabel-- /*modified*/ SYNTAX DhcpLabel-- /*modified*/
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The shared subnet name (used as an index into the server "The shared subnet name (used as an index into the server
shared subnet table) to which this subnet belongs. This value shared subnet table) to which this subnet belongs. This value
will be null for servers that do not organize or describe will be null for servers that do not organize or describe
networks in this manner." networks in this manner."
::= { serverSubnetEntry 3 } ::= { serverSubnetEntry 3 }
skipping to change at page 25, line 43 skipping to change at page 28, line 20
serverRangeEntry OBJECT-TYPE serverRangeEntry OBJECT-TYPE
SYNTAX ServerRangeEntry SYNTAX ServerRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverRangeStart } INDEX { serverRangeStart }
DESCRIPTION DESCRIPTION
"A logical row in the serverRangeTable." "A logical row in the serverRangeTable."
::= { serverRangeTable 1 } ::= { serverRangeTable 1 }
ServerRangeEntry ::= SEQUENCE { ServerRangeEntry ::= SEQUENCE {
serverRangeStart IpAddress, serverRangeStart InetAddressIPv4,
serverRangeEnd IpAddress, serverRangeEnd InetAddressIPv4,
serverRangeSubnetMask IpAddress, serverRangeSubnetMask InetAddressPrefixLength,
serverRangeInUse Gauge32, serverRangeInUse Gauge32,
serverRangeOutstandingOffers Gauge32 serverRangeOutstandingOffers Gauge32
} }
serverRangeStart OBJECT-TYPE serverRangeStart OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the first address in the range. The value "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 of range start must be less than or equal to the value of range
end." end."
::= { serverRangeEntry 1 } ::= { serverRangeEntry 1 }
serverRangeEnd OBJECT-TYPE serverRangeEnd OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last address in the range. The value of "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 range end must be greater than or equal to the value of range
start." start."
::= { serverRangeEntry 2 } ::= { serverRangeEntry 2 }
serverRangeSubnetMask OBJECT-TYPE serverRangeSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet address mask for this range." "The subnet address mask for this range."
::= { serverRangeEntry 3 } ::= { serverRangeEntry 3 }
serverRangeInUse OBJECT-TYPE serverRangeInUse OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of addresses in this range that are currently in "The number of addresses in this range that are currently in
use. This number includes those addresses whose lease has not use. This number includes those addresses whose lease has not
expired and addresses which have been reserved (either by the expired and addresses which have been reserved (either by the
server or through configuration)." server or through configuration)."
::= { serverRangeEntry 4 } ::= { serverRangeEntry 4 }
skipping to change at page 27, line 30 skipping to change at page 30, line 7
serverAddressEntry OBJECT-TYPE serverAddressEntry OBJECT-TYPE
SYNTAX ServerAddressEntry SYNTAX ServerAddressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverAddress } INDEX { serverAddress }
DESCRIPTION DESCRIPTION
"A logical row in the serverAddressTable." "A logical row in the serverAddressTable."
::= { serverAddressTable 1 } ::= { serverAddressTable 1 }
ServerAddressEntry ::= SEQUENCE { ServerAddressEntry ::= SEQUENCE {
serverAddress IpAddress, serverAddress InetAddressIPv4,
serverAddressSubnetMask IpAddress, serverAddressSubnetMask InetAddressPrefixLength,
serverAddressRange IpAddress, serverAddressRange InetAddressIPv4,
serverAddressType INTEGER, serverAddressType INTEGER,
serverAddressTimeRemaining Unsigned32, serverAddressTimeRemaining Unsigned32,
serverAddressAllowedProtocol INTEGER, serverAddressAllowedProtocol INTEGER,
serverAddressServedProtocol INTEGER, serverAddressServedProtocol INTEGER,
serverAddressMacAddress OCTET STRING, serverAddressMacAddress OCTET STRING,
serverAddressClientId OCTET STRING, serverAddressClientId OCTET STRING,
serverAddressHostName DisplayString, serverAddressHostName SnmpAdminString,
serverAddressDomainName DisplayString serverAddressDomainName SnmpAdminString
} }
serverAddress OBJECT-TYPE serverAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the entry." "The IP address of the entry."
::= { serverAddressEntry 1 } ::= { serverAddressEntry 1 }
serverAddressSubnetMask OBJECT-TYPE serverAddressSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet mask (DHCP option 1) provided to the client offered "The subnet mask (DHCP option 1) provided to the client offered
this address. The subnet, resulting from logically ANDing the this address. The subnet, resulting from logically ANDing the
subnet mask with the entry's IP address, must be configured on subnet mask with the entry's IP address, must be configured on
this server and appear as a row in the dhcpSubnetTable." this server and appear as a row in the dhcpSubnetTable."
::= { serverAddressEntry 2 } ::= { serverAddressEntry 2 }
serverAddressRange OBJECT-TYPE serverAddressRange OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting IP address (serverRangeStart object) of the range "The starting IP address (serverRangeStart object) of the range
to which this address belongs. If the address does not fall to which this address belongs. If the address does not fall
into one of the configured ranges (e.g., a statically into one of the configured ranges (e.g., a statically
configured address on a subnet) the range may be 0.0.0.0." configured address on a subnet) the range may be 0.0.0.0."
::= { serverAddressEntry 3 } ::= { serverAddressEntry 3 }
serverAddressType OBJECT-TYPE serverAddressType OBJECT-TYPE
skipping to change at page 28, line 36 skipping to change at page 31, line 12
static(1), static(1),
dynamic(2), dynamic(2),
expired(3), -- /*new*/ expired(3), -- /*new*/
configuration-reserved(4), -- /*renumbered*/ configuration-reserved(4), -- /*renumbered*/
server-reserved(5) -- /*renumbered*/ server-reserved(5) -- /*renumbered*/
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of this address. Types are: "The type of this address. Types are:
(1) static addresses defined by the server configuration. (1) Static addresses defined by the server configuration.
(2) dynamic addresses defined by the server configuration (2) Dynamic addresses defined by the server configuration
AND actually assigned by the server. AND actually assigned by the server.
(3) expired dynamic addresses, previously assigned by the (3) Expired dynamic addresses, previously assigned by the
server and 'remembered' for subsequent assignment to the server and 'remembered' for subsequent assignment to the
same host. same host.
(4) Addresses reserved (i.e., not assignable) by the server (4) Addresses reserved (i.e., not assignable) by the server
configuration. configuration.
(5) Addresses previously assigned by the server, but (5) Addresses previously assigned by the server, but
temporarily or permanently removed from assignable state temporarily or permanently removed from assignable state
for some reason, e.g., the server received an ICMP for some reason, e.g., the server received an ICMP
ECHOREPLY for the IP address or a DHCPDECLINE message ECHOREPLY for the IP address or a DHCPDECLINE message
has been received for the IP address." has been received for the IP address."
::= { serverAddressEntry 4 } ::= { serverAddressEntry 4 }
skipping to change at page 30, line 19 skipping to change at page 32, line 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The client-id of the client that has been assigned this lease. "The client-id of the client that has been assigned this lease.
The client-id is the value specified in option 61 (client-id The client-id is the value specified in option 61 (client-id
option) when the lease was assigned. This object may be empty option) when the lease was assigned. This object may be empty
if the lease has not been previously assigned or if the client- if the lease has not been previously assigned or if the client-
id option was not specified when the address was assigned." id option was not specified when the address was assigned."
::= { serverAddressEntry 9 } ::= { serverAddressEntry 9 }
serverAddressHostName OBJECT-TYPE serverAddressHostName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..255)) SYNTAX SnmpAdminString (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The host name (DHCP option 12) the client is configured to "The host name (DHCP option 12) the client is configured to
use, or if no host name was configured then the host name that use, or if no host name was configured then the host name that
the client supplied when requesting an address. While this the client supplied when requesting an address. While this
object has a maximum size of 255 octets, a Fully-Qualified object has a maximum size of 255 octets, a Fully-Qualified
Domain Name (FQDN) consisting of a Host Name part and a Domain Domain Name (FQDN) consisting of a Host Name part and a Domain
Name part is currently limited to 255 octets. Therefore, the Name part is currently limited to 255 octets. Therefore, the
sum of the string lengths for this object and the sum of the string lengths for this object and the
serverAddressDomainName must, in practice, be less than 256 serverAddressDomainName must, in practice, be less than 256
octets." octets."
::= { serverAddressEntry 10 } ::= { serverAddressEntry 10 }
serverAddressDomainName OBJECT-TYPE serverAddressDomainName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..255)) SYNTAX SnmpAdminString (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The domain name (DHCP option 15) assigned to the client. "The domain name (DHCP option 15) assigned to the client.
While this object has a maximum size of 255 octets, a Fully- While this object has a maximum size of 255 octets, a Fully-
Qualified Domain Name (FQDN) consisting of a Host Name part and Qualified Domain Name (FQDN) consisting of a Host Name part and
a Domain Name part is currently limited to 255 octets, less the a Domain Name part is currently limited to 255 octets, less the
separator (".") character. Therefore, the sum of the string separator (".") character. Therefore, the sum of the string
lengths for this object and the serverAddressHostName must, in lengths for this object and the serverAddressHostName must, in
practice, be less than 256 octets." practice, be less than 256 octets."
skipping to change at page 31, line 34 skipping to change at page 34, line 10
(e.g., not authorized).Servers MAY track these types of clients (e.g., not authorized).Servers MAY track these types of clients
if desired and may choose to remove such client entries using a if desired and may choose to remove such client entries using a
server defined algorithm. As an example, a server may choose server defined algorithm. As an example, a server may choose
to keep client request that does not map to an address for a to keep client request that does not map to an address for a
one hour time period before removing that entry from this one hour time period before removing that entry from this
table." table."
::= { serverClientTable 1 } ::= { serverClientTable 1 }
ServerClientEntry ::= SEQUENCE { ServerClientEntry ::= SEQUENCE {
serverClientHardwareAddress PhysicalAddress serverClientHardwareAddress PhysicalAddress
serverClientSubnetMask IpAddress, serverClientAddress InetAddressIPv4,
serverClientAddress IpAddress, serverClientSubnetMask InetAddressPrefixLength,
serverClientLastRequestTime DateAndTime, serverClientLastRequestTime DateAndTime,
serverClientLastRequestType INTEGER, serverClientLastRequestType INTEGER,
serverClientLastResponseType INTEGER serverClientLastResponseType INTEGER
} }
serverClientHardwareAddress OBJECT-TYPE serverClientHardwareAddress OBJECT-TYPE
SYNTAX PhysicalAddress SYNTAX PhysicalAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hardware type and hardware address of the client that has "The hardware type and hardware address of the client that has
been assigned this lease. The first octet of this object been assigned this lease. The first octet of this object
contains the hardware type from the 'htype' field of the BOOTP contains the hardware type from the 'htype' field of the BOOTP
packet and the remaining octets contain the hardware address packet and the remaining octets contain the hardware address
from the 'chaddr' field of the BOOTP packet." from the 'chaddr' field of the BOOTP packet."
::= { serverClientEntry 1 } ::= { 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 serverClientAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the entry. May be used to index into the "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 serverAddressTable. May be 0.0.0.0 if an address is not
associated with this client." associated with this client."
::= { serverClientEntry 2 }
serverClientSubnetMask OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The subnet mask (DHCP option 1) applied to
serverClientAddress."
::= { serverClientEntry 3 } ::= { serverClientEntry 3 }
serverClientLastRequestTime OBJECT-TYPE serverClientLastRequestTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp of the last request received, to millisecond "The timestamp of the last request received, to millisecond
precision if available on the server." precision if available on the server."
::= { serverClientEntry 4 } ::= { serverClientEntry 4 }
skipping to change at page 33, line 24 skipping to change at page 35, line 51
"The type of the last response message sent to this client. If "The type of the last response message sent to this client. If
the server does not capture this information, the value 32,767 the server does not capture this information, the value 32,767
is returned." is returned."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6;draft-ietf-dhc-pv4-reconfigure- "RFC2131; RFC2132, section 9.6;draft-ietf-dhc-pv4-reconfigure-
06.txt;draft-ietf-dhc-leasequery-02.txt" 06.txt;draft-ietf-dhc-leasequery-02.txt"
::= { serverClientEntry 6 } ::= { serverClientEntry 6 }
--serverNotifyObjects: Objects which are used only in notifications --serverNotifyObjects: Objects which are used only in notifications
serverNotifyDuplicateIPAddress OBJECT-TYPE serverNotifyDuplicateIpAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address found to be a duplicate. Duplicates are "The IP address found to be a duplicate. Duplicates are
detected by servers which issue an ICMP ECHOREQUEST prior to detected by servers which issue an ICMP ECHOREQUEST prior to
offering an IP address lease." offering an IP address lease."
::= { serverNotifyObjects 1 } ::= { serverNotifyObjects 1 }
serverNotifyDuplicateMAC OBJECT-TYPE serverNotifyDuplicateMAC OBJECT-TYPE
SYNTAX PhysicalAddress SYNTAX PhysicalAddress
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The offending MAC address which caused a duplicate IP address "The offending MAC address which caused a duplicate IP address
to be detected, if captured by the server, else 00-00-00-00-00- to be detected, if captured by the server, else 00-00-00-00-00-
00." 00."
::= { serverNotifyObjects 2 } ::= { serverNotifyObjects 2 }
serverNotifyClientDuplicateIP OBJECT-TYPE-- /*renamed*/ serverNotifyClientDuplicateIP OBJECT-TYPE-- /*renamed*/
SYNTAX IpAddress SYNTAX InetAddressIPv4
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP Address offered by a server that the requesting client "The IP Address offered by a server that the requesting client
has determined to be a duplicate, detected by means of a has determined to be a duplicate, detected by means of a
gratuitous ARP message and reported through a DHCPDECLINE gratuitous ARP message and reported through a DHCPDECLINE
message." message."
::= { serverNotifyObjects 3 } ::= { serverNotifyObjects 3 }
-- Notifications -- Notifications
skipping to change at page 35, line 11 skipping to change at page 37, line 36
OBJECTS { serverNotifyClientDuplicateIP } OBJECTS { serverNotifyClientDuplicateIP }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the server of the specified "This notification signifies that the server of the specified
type has stopped normally on the host from which this type has stopped normally on the host from which this
notification has been sent." notification has been sent."
::= { serverMIBNotifications 4 } ::= { serverMIBNotifications 4 }
serverDuplicateAddress NOTIFICATION-TYPE serverDuplicateAddress NOTIFICATION-TYPE
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIpAddress,
serverNotifyDuplicateMAC, serverNotifyDuplicateMAC,
serverNotifyClientDuplicateMAC serverNotifyClientDuplicateMAC
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that a duplicate IP address has "This notification signifies that a duplicate IP address has
been detected. The DHCP server can detect this condition been detected. The DHCP server can detect this condition
through the ping-before-offer mechanism. Alternatively, the through the ping-before-offer mechanism. Alternatively, the
client may have sent a DHCPDECLINE back to the server; this is client may have sent a DHCPDECLINE back to the server; this is
assumed to be the result of the client detecting that the assumed to be the result of the client detecting that the
skipping to change at page 37, line 5 skipping to change at page 39, line 30
"Objects belonging to the bootpBountersGroup." "Objects belonging to the bootpBountersGroup."
::= { serverMIBGroups 2 } ::= { serverMIBGroups 2 }
dhcpCountersGroup OBJECT-GROUP dhcpCountersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpCountDiscovers, dhcpCountDiscovers,
dhcpCountRequests, dhcpCountRequests,
dhcpCountReleases, dhcpCountReleases,
dhcpCountDeclines, dhcpCountDeclines,
dhcpCountInforms, dhcpCountInforms,
dhcpCountInvalids, dhcpCountLeaseQueries
dhcpCountPlaceHolder1
dhcpCountPlaceHolder2
dhcpCountOffers, dhcpCountOffers,
dhcpCountAcks, dhcpCountAcks,
dhcpCountNacks, dhcpCountNacks,
dhcpCountForcedRenews
dhcpCountKnowns
dhcpCountUnknowns
dhcpCountActives
dhcpCountUnimplementeds
dhcpCountPlaceHolder3
dhcpCountPlaceHolder4
dhcpCountInvalids,
dhcpCountDroppedUnknownClient, dhcpCountDroppedUnknownClient,
dhcpCountDroppedNotServingSubnet dhcpCountDroppedNotServingSubnet
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpCountersGroup." "Objects belonging to the dhcpCountersGroup."
::= { serverMIBGroups 3 } ::= { serverMIBGroups 3 }
bootpOptionalStatisticsGroup OBJECT-GROUP bootpOptionalStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 38, line 53 skipping to change at page 41, line 38
serverSharedNetworkFreeAddressHighThreshold, serverSharedNetworkFreeAddressHighThreshold,
serverSharedNetworkFreeAddressValue serverSharedNetworkFreeAddressValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects used in shared networks." "DHCP Server MIB objects used in shared networks."
::= { serverMIBGroups 8 } ::= { serverMIBGroups 8 }
serverNotifyObjectsGroup OBJECT-GROUP serverNotifyObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIpAddress,
serverNotifyDuplicateMAC, serverNotifyDuplicateMAC,
serverNotifyClientDuplicateMAC, serverNotifyClientDuplicateMAC,
serverNotifyClientDuplicateIP, serverNotifyClientDuplicateIP,
serverNotifyContestedIpAddress serverNotifyContestedIpAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects used in notifications." "DHCP Server MIB objects used in notifications."
::= { serverMIBGroups 9 } ::= { serverMIBGroups 9 }
skipping to change at page 39, line 34 skipping to change at page 42, line 19
serverOtherServerResponding, serverOtherServerResponding,
serverFailoverConfigMismatch serverFailoverConfigMismatch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications that are implemented by the DHCP Server agent." "Notifications that are implemented by the DHCP Server agent."
::= { serverMIBGroups 10 } ::= { serverMIBGroups 10 }
END END
4. Intellectual Property 5. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. standards-related documentation can be found in BCP-11.
skipping to change at page 40, line 11 skipping to change at page 42, line 42
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
5. Notes 6. Notes
This section will be removed when this memo goes to Working Group This section will be removed when this memo goes to Working Group
Last Call. Last Call.
5.1. Issues 6.1. Issues
Not all of these issues have been resolved, even in the latest (-07) Not all of these issues have been resolved, even in the latest (-07)
draft. Some may become items for future study, while some will draft. Some may become items for future study, while some will
probably be dropped. probably be dropped.
o Are placeholders for expected DHCP option values a good or bad o Are placeholders for expected DHCP option values a good or bad
idea? idea?
o Ryan Troll proposed four or five traps that Nathan Lane o Ryan Troll proposed four or five traps that Nathan Lane
enthusiastically supported, but it has been difficult to achieve enthusiastically supported, but it has been difficult to achieve
skipping to change at page 41, line 8 skipping to change at page 43, line 46
o Perhaps we should develop a common vocabulary (and glossary) for o Perhaps we should develop a common vocabulary (and glossary) for
terms such as "abandoned" so that the objects defined and their terms such as "abandoned" so that the objects defined and their
descriptions aren't misinterpreted by implementers. descriptions aren't misinterpreted by implementers.
o Do we need to be concerned about the potential size of some of the o Do we need to be concerned about the potential size of some of the
configuration data tables? Wouldn't it be better to maintain configuration data tables? Wouldn't it be better to maintain
counters for things like number of leases assigned than to expect counters for things like number of leases assigned than to expect
the management station to calculate the values by reading very the management station to calculate the values by reading very
large tables to count the number of leases in that state? large tables to count the number of leases in that state?
5.2. Changes from Prior Drafts 6.2. Changes from Prior Drafts
The "-01" revision removed the Server Identity section from the The "-01" revision removed the Server Identity section from the
proposed MIB, relying on the Application MIB to accomplish the same proposed MIB, relying on the Application MIB to accomplish the same
result. result.
The min/max (inter-arrival and response times) were changed to The min/max (inter-arrival and response times) were changed to
Unsigned32 so that they could be reset. Sums of inter-arrival and Unsigned32 so that they could be reset. Sums of inter-arrival and
response times were deleted since the management station can easily response times were deleted since the management station can easily
calculate them. The last arrival time objects were added. calculate them. The last arrival time objects were added.
skipping to change at page 42, line 5 skipping to change at page 44, line 42
not adequately describe the "scoping" of address pools as is common not adequately describe the "scoping" of address pools as is common
with many current server implementations. Also updated the authorĂs with many current server implementations. Also updated the authorĂs
address and contact information, and incorporated a number of address and contact information, and incorporated a number of
corrections and amplifications suggested by various readers of the "- corrections and amplifications suggested by various readers of the "-
04" draft, including a missing OID for serverNotifyObjects and a 04" draft, including a missing OID for serverNotifyObjects and a
syntax error for PhysicalAddress. syntax error for PhysicalAddress.
The "-06" version corrects a number of flaws reported by Rick Geesen The "-06" version corrects a number of flaws reported by Rick Geesen
and Jin Tao, mostly caused by typographical errors in the "-05" and Jin Tao, mostly caused by typographical errors in the "-05"
version as well as some unintentionally omitted text for version as well as some unintentionally omitted text for
serverNotifyObjects. serverNotifyObjects. The "-06" version also 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. Finally, some of the boilerplate text was brought
in line with standard requirements for Internet-Drafts.
The "-07" version changes BOOTP and DHCP statistics from mandatory to The "-07" version fixes a few typographical errors (wrong
optional, renaming object identifiers as required to match. All capitalization of object identifiers and table entry values, spacing
objects, tables, and groups in previous drafts for Dynamic DNS of comments, and misspelled words) in preparation for Working Group
updating and Failover have been removed. All tables were carefully Last Call. Many thanks to Rich Woundy for his detailed and extremely
examined to be certain that they really could be simply implemented. helpful suggestions on the prior draft. The standard boilerplate
Many items were renamed or renumbered. Placeholder definitions of (˘The SNMP Management Framework÷) for all new MIBs was added as
message types (both requests and responses) were added to support section 2 and the standard references not previously included in
DHCPFORCERENEW, DHCPQUERY, DHCPKNOWN, and DHCPUNKNOWN. A few [more] section 9 were added. DisplayString objects were recast as
typographical errors were found and fixed. Because of an error SnmpAdminString types to be consistent with current practice. The
posting the ű07 draft to the editor's queue it was not accepted in IpAddress type was replaced by IpAddressIPv4 and
time for IETF-52 and is being submitted to the Internet-Drafts editor IpAddressPrefixLength as appropriate for true addresses and subnet
with one change identified by Alan Hackert. Finally, some of the masks throughout the MIB. Numbering of OIDs was made consistent, and
initial text was brought in line with standard requirements for place holders for anticipated new DHCP message type codes were
Internet-Drafts. explicitly added, eliminating gaps in the OID numbering scheme.
6. Acknowledgements 7. Acknowledgements
This document is the result of work undertaken the by DHCP working This document is the result of work undertaken the by DHCP working
group. The editors would like to particularly acknowledge the group. The editors would like to particularly acknowledge the
development team from Carnegie-Mellon University whose work creating development team from Carnegie-Mellon University whose work creating
a private MIB for their DHCP server inspired the development of this a private MIB for their DHCP server inspired the development of this
proposal. In particular, many thanks to Ryan Troll who provided a proposal. In particular, many thanks to Ryan Troll who provided a
great deal of useful feedback during the development of this MIB. great deal of useful feedback during the development of this MIB.
Thanks to Ryan Troll, Nathan Lane, Kim Kinnear, Yannick Koehler, Thanks to Nathan Lane, Kim Kinnear, Yannick Koehler, Nathan Lane,
Nathan Lane, Rick Geesen, Jin Tao, James Brister, and Alan Hackert Rick Geesen, Jin Tao, James Brister, Alan Hackert, and Patrick Cosmo
for their review, comments, and contributions. for their review, comments, and contributions. Special thanks to
Rich Woundy for his excellent suggestions that contributed to the ű07
draft: any lingering errors are to be blamed solely on me.
7. Security Considerations 8. Security Considerations
There are no management objects defined in this MIB that have a MAX- There are no management objects defined in this MIB that have a MAX-
ACCESS clause of read-write or read-create. Such objects may be ACCESS clause of read-write or read-create. Such objects may be
considered sensitive or vulnerable in some environments. The support considered sensitive or vulnerable in some environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. Many protection can have a negative effect on network operations. Many
network administrators object to settable management objects because network administrators object to settable management objects because
of the limited security features of SNMPv1 and SNMPv2. We have of the limited security features of SNMPv1 and SNMPv2. We have
chosen not to fight that battle in constructing this MIB. chosen not to fight that battle in constructing this MIB. So, if
this MIB is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB via
direct SNMP SET operations.
-- for all MIBs you must evaluate
There are a number of managed objects in this MIB that may contain
sensitive information. These are:
o serverRangeTable
o serverAddressTable
These two objects, in conjunction, provide an observer with a current
view of the available and assigned addresses allocated by this
server. Such knowledge can be used to manually configure a host
computer with a valid IP address for the network managed by the DHCP
server. This could be part of either a Theft of Service scheme or a
Denial of Service attack wherein rogue (pseudo-)hosts simply claim
and defend IP addresses either to subvert accounting for their use or
to disrupt the network for legitimate hosts.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending
them over the network via SNMP. Not all versions of SNMP provide
features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSEC), there is no control as itself is secure (for example by using IPSec), even then, there is no
to who on the secure network is allowed to access and GET / SET (read control as to who on the secure network is allowed to access and
/ change / create / delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv2 communities provide a minimal level of access control, but it It is recommended that the implementers consider the security
is recommended that the implementers consider the security features features as provided by the SNMPv3 framework. Specifically, the use
as provided by the SNMPv3 framework. Specifically, the use of the of the User-based Security Model RFC 2574 [RFC2574] and the View-
User-based Security Model [RFC2274] and the View-based Access Control based Access Control Model RFC 2575 [RFC2575] is recommended.
Model [RFC2275] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
Denial of Service attacks on a DHCP server are conceivable by Denial of Service attacks on a DHCP server are conceivable by
flooding the SNMP (sub-)agent with requests, tying up host system and flooding the SNMP (sub-)agent with requests, tying up host system and
server resources processing SNMP messages. The authors know of no server resources processing SNMP messages. The authors know of no
way to wholly prevent such attacks, but have attempted to construct way to wholly prevent such attacks, but have attempted to construct
relatively simple tables to minimize the work required to respond to relatively simple tables to minimize the work required to respond to
messages. messages.
8. References 9. References
[DEN] Directory Enabled Networks Working Group, [DEN] Directory Enabled Networks Working Group,
http://www.universe.digex.net/~murchiso/den. http://www.universe.digex.net/~murchiso/den.
[RFC1123] R. Braden, "Requirements for Internet Hosts -- Application [RFC1123] R. Braden, "Requirements for Internet Hosts -- Application
and Support," RFC 1123, October 1989. and Support," RFC 1123, October 1989.
[RFC2287] Krupczak, R., and J. Saperia, "Definitions of System-Level [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
Managed Objects for Applications," RFC 2287, February 1998. of Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990.
[RFC2578] Case, J., McCloghrie, K., Perkins, D., Rose, M., [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Schoenwaelder, J., and S. Waldbusser, "Structure of Management Network Management Protocol", STD 15, RFC 1157, May 1990.
Information for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 2578, April 1999.
[RFC2579] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
S. Waldbusser, "Textual Conventions for Version 2 of the Simple 16, RFC 1212, March 1991.
Network Management Protocol (SNMPv2)," RFC 2579, April 1999.
[RFC2580] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and [RFC1215] M. Rose, "A Convention for Defining Traps for use with the
S. Waldbusser, "Conformance Statements for Version 2 of the Simple SNMP", RFC 1215, March 1991.
Network Management Protocol (SNMPv2)," RFC 2580, April 1999.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119, BCP 14, March 1997. Requirement Levels," RFC 2119, BCP 14, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol," RFC 2131, [RFC2131] Droms, R., "Dynamic Host Configuration Protocol," RFC 2131,
March 1997. March 1997.
[RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor [RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor
Extensions," RFC 2132, March 1997. Extensions," RFC 2132, March 1997.
[RFC2287] Krupczak, C. and Saperia, J., "Definitions of System-Level [RFC2287] Krupczak, C. and Saperia, J., "Definitions of System-Level
Managed Objects for Applications," RFC 2287, February 1998. Managed Objects for Applications," RFC 2287, February 1998.
<draft-ietf-dhc-pv4-reconfigure-06.txt>, Yves T'Joens and Christian [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
Hublet, Peter De Schrijver, "The DHCP Reconfigure Extension," July "Introduction to Version 3 of the Internet-standard Network
2001 Management Framework", RFC 2570, April 1999.
<draft-ietf-dhc-leasequery-02.txt>, Rich Woundy and Kim Kinnear, [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
"DHCP Lease Query," July 2001 Architecture for Describing SNMP Management Frameworks", RFC 2571,
April 1999.
9. Editors' Addresses [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)", RFC 2572, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Management
Protocol (SNMP)", RFC 2575, April 1999.
[RFC2578] Case, J., McCloghrie, K., Perkins, D., Rose, M.,
Schoenwaelder, J., and S. Waldbusser, "Structure of Management
Information for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 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)," RFC 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)," RFC 2580, April 1999.
[RFC3203 , Yves T'Joens and Christian Hublet, Peter De Schrijver,
"The DHCP Reconfigure Extension," July 2001
<draft-ietf-dhc-leasequery-03.txt> Rich Woundy and Kim Kinnear, "DHCP
Lease Query," March 2002
10. Editors' Addresses
Richard Barr Hibbs Richard Barr Hibbs
952 Sanchez Street 952 Sanchez Street
San Francisco, California 94114-3362 San Francisco, California 94114-3362
USA USA
Phone: +1-(415)-648-3920 Phone: +1-(415)-648-3920
Fax: +1-(415)-648-9017 Fax: +1-(415)-648-9017
Email: rbhibbs@pacbell.net Email: rbhibbs@pacbell.net
Glenn Waters Glenn Waters
Nortel Networks Nortel Networks
310-875 Carling Avenue, 310-875 Carling Avenue,
Ottawa, Ontario K1S 5P1 Ottawa, Ontario K1S 5P1
Canada Canada
Phone: +1-(613)-798-4925 Phone: +1-(613)-798-4925
Email: gww@NortelNetworks.com Email: gww@NortelNetworks.com
11. Full Copyright Statement
10. Full Copyright Statement
Copyright (C) The Internet Society, 2002.All Rights Reserved. Copyright (C) The Internet Society, 2002.All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works.However, this included on all such copies and derivative works.However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/