draft-ietf-dhc-server-mib-09.txt   draft-ietf-dhc-server-mib-10.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
October 2003 February 2004
Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB
<draft-ietf-dhc-server-mib-09.txt> <draft-ietf-dhc-server-mib-10.txt>
Saved Monday, October 27, 2003, 5:08:01 PM Saved Friday, February 06, 2004, 4:33:38 PM
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 11 skipping to change at page 2, line 11
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 for IPv4 the management of Dynamic Host Configuration Protocol for IPv4
(DHCPv4) and Bootstrap Protocol (BOOTP) servers. (DHCPv4) and Bootstrap Protocol (BOOTP) servers.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. The Internet-Standard Management Framework.....................3 2. The Internet-Standard Management Framework.....................3
3. Overview.......................................................3 3. Overview.......................................................3
3.1. Relationship to Other MIBs.................................4 3.1. Relationship to Other MIBs.................................4
3.1.1. DHCP MIB Extensions...................................4 3.1.1. DHCP MIB Extensions....................................4
3.1.2. Host System MIB Extensions............................4 3.1.2. Host System MIB Extensions.............................4
3.1.3. DHCP Client MIB Extensions............................4 3.1.3. DHCP Client MIB Extensions.............................4
3.1.4. DHCP Relay Agent MIB Extensions.......................5 3.1.4. DHCP Relay Agent MIB Extensions........................5
3.1.5. DHCPv6 MIB Extensions.................................5 3.1.5. DHCPv6 MIB Extensions..................................5
3.2. Textual Conventions Introduced in this MIB.................5 3.2. Textual Conventions Introduced in this MIB.................5
3.2.1. DhcpTimeInterval......................................5 3.2.1. Dhcpv4PhysicalAddress..................................5
3.2.2. DhcpPhysicalAddress...................................5
3.3. BOOTP and DHCP Counter Groups..............................5 3.3. BOOTP and DHCP Counter Groups..............................5
3.4. BOOTP and DHCP Optional Statistics Group...................6 3.3.1. Discontinuities........................................6
3.5. Response Times and ICMP Echo...............................8 3.3.2. Counter Rollover.......................................7
3.4. Server Configuration Group.................................7
4. Definitions....................................................9 4. Definitions....................................................9
5. Intellectual Property.........................................43 5. Intellectual Property.........................................33
6. Acknowledgements..............................................43 6. Acknowledgements..............................................33
7. IANA Considerations...........................................43 7. IANA Considerations...........................................33
8. Security Considerations.......................................44 8. Security Considerations.......................................34
9. References....................................................45 9. References....................................................35
9.1. Normative References......................................45 9.1. Normative References......................................35
9.2. Informative References....................................46 9.2. Informative References....................................35
10. Editors' Addresses...........................................46 10. Editors' Addresses...........................................36
11. Full Copyright Statement.....................................46 11. Full Copyright Statement.....................................36
1. Introduction 1. Introduction
This memo is a product of the DHCP Working Group and defines a This memo is a product of 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
management protocols in the Internet community. In particular, it network management protocols in the Internet community. In
describes a set of extensions that DHCPv4 and Bootstrap Protocol particular, it describes a set of extensions that DHCPv4 and
(BOOTP) servers implement. Many implementations support both DHCPv4 Bootstrap Protocol (BOOTP) servers implement. Many implementations
and BOOTP within a single server and hence this memo describes the support both DHCPv4 and BOOTP within a single server and hence this
MIB for both DHCPv4 and BOOTP servers. memo describes the MIB for both DHCPv4 and BOOTP servers.
This memo does not cover DHCPv4/BOOTP client nor relay agent MIB This memo does not cover DHCPv4/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 3.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 using the Applications MIB [RFC2287]. capabilities using 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
document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410], Managed objects are accessed via a virtual RFC 3410 [RFC3410], Managed objects are accessed via a virtual
information store, termed the Management Information Base or MIB. information store, termed the Management Information Base or MIB.
MIB objects are generally accessed through the Simple Network MIB objects are generally accessed through the Simple Network
Management Protocol (SNMP). Objects in the MIB are defined using the Management Protocol (SNMP). Objects in the MIB are defined using
mechanisms defined in the Structure of Management Information (SMI). the mechanisms defined in the Structure of Management Information
This memo specifies a MIB module that is compliant to the SMIv2, (SMI). This memo specifies a MIB module that is compliant to the
which is described in STD 58, [RFC2578], STD 58, [RFC2579] and STD SMIv2, which is described in STD 58, [RFC2578], STD 58, [RFC2579]
58, [RFC2580]. and STD 58, [RFC2580].
3. Overview 3. Overview
In the tradition of the Simple Network Management Protocol (SNMP), In the tradition of the Simple Network Management Protocol (SNMP),
the minimum number of objects possible is defined in this MIB, while the minimum number of objects possible is 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 can be derived.
Provision for future extensions to cover DHCPv4 clients and relay Provision for future extensions to cover DHCPv4 clients and relay
agents, and DHCPv6 extensions are implied by the top-level structure agents, and DHCPv6 extensions are implied by the top-level structure
illustrated in section 3.1.1. illustrated in section 3.1.1.
The examples provided in sections 3.3 through 3.5 are not meant to be The examples provided in sections 3.3 through 3.5 are not meant to
comprehensive but are illustrative of the potential uses of the be comprehensive but are illustrative of the potential uses of the
objects defined by this MIB. objects defined by this MIB.
3.1. Relationship to Other MIBs 3.1. Relationship to Other MIBs
3.1.1. DHCP MIB Extensions 3.1.1. DHCP MIB Extensions
The DHCP MIB extensions will be the "dhcp" branch of the standard The DHCP MIB extensions will be the "dhcp" branch of the standard
MIB-2 tree, as illustrated by the following diagram: MIB-2 tree, as illustrated by the following diagram:
+-------+ +-------+
skipping to change at page 4, line 30 skipping to change at page 4, line 30
| |
| |
+--------------+---------------+----------------+ +--------------+---------------+----------------+
| | | | | | | |
+-----+-----+ +-----+----+ +-------+-------+ +-----+-----+ +-----+-----+ +-----+----+ +-------+-------+ +-----+-----+
| 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 DHCP MIBs will share a common branching point but will be The DHCP MIBs share a common branching point but will be
independently defined by individual memos. independently defined by individual memos.
3.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.
3.1.3. DHCP Client MIB Extensions 3.1.3. DHCP Client MIB Extensions
Development of this set of MIB extensions is a natural path given the Development of this set of MIB extensions is a natural path given
increasing interest in desktop and client system management. It will the increasing interest in desktop and client system management. It
share a common branch point in the MIB tree with the other DHCP MIB will share a common branch point in the MIB tree with the other DHCP
Extensions, and may use many of the same textual conventions. MIB Extensions, and may use many of the same textual conventions.
3.1.4. DHCP Relay Agent MIB Extensions 3.1.4. 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.
3.1.5. DHCPv6 MIB Extensions 3.1.5. DHCPv6 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 likely use very different textual conventions as Extensions, and will likely use very different textual conventions
the protocol differs significantly from DHCPv4. as the protocol differs significantly from DHCPv4.
3.2. Textual Conventions Introduced in this MIB 3.2. Textual Conventions Introduced in this MIB
Several conceptual data types have been introduced as textual One conceptual data type has been introduced in this document. No
conventions in this DHCP MIB document. These additions will changes to the SMI or SNMP are necessary to support this convention.
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.
3.2.1. DhcpTimeInterval 3.2.1. Dhcpv4PhysicalAddress
This data type measures time intervals since the beginning of some This data type contains the type of hardware address represented by
epoch, measured in milliseconds. DhcpTimeInterval is intended MacAddress, as defined for ARP messages, the length in octets of
exclusively for use in various statistics, such as in the subtrees MacAddress, and the actual layer 1 hardware address.
"bootpOptionalStatistics" and "dhcpv4OptionalStatistics."
3.2.2. DhcpPhysicalAddress 3.3. BOOTP and DHCP Counter Groups
This data type contains the type of hardware address represented by This section describes some of the management information that can
MacAddress, as defined for ARP messages. be derived from the objects provided in the counter groups.
The length in octets of MacAddress is contained in this type. In this context, a "valid" packet is one which has an identifiable
message type and has passed all format and validation checks that
the DHCP server implements. Not all servers validate received
packets in the same way, so there will be differences in the counts
reported by different servers. It is appropriate to simply accept
the server's notion of what constitutes a valid packet.
The actual layer 1 hardware address is contained in this data type. The total number of valid DHCP packets received by the server is
computed as:
3.3. BOOTP and DHCP Counter Groups (dhcpv4CountDiscovers + dhcpv4CountRequests +
dhcpv4CountReleases + dhcpv4CountDeclines + dhcpv4CountInforms
+ dhcpv4CountLeaseQueries)
This section describes some of the management information that may be The total number of valid packets (BOOTP and DHCP) received is
derived from the objects provided in the counter groups. computed as:
The total number of valid DHCP packets received by the server is (total number of valid DHCP packets) + bootpCountRequests)
computed as the sum of the "dhcpv4CountDiscovers,"
"dhcpv4CountRequests," "dhcpv4CountReleases," "dhcpv4CountDeclines," The total number of packets received is computed as:
"dhcpv4CountInforms," and "dhcpv4CountLeaseQueries objects." The
total number of valid packets (BOOTP and DHCP) received is computed (total number of valid packets) + bootpCountInvalids +
as the total number of valid DHCP packets plus the value of the dhcpv4CountInvalids
"bootpCountRequests" object. The total number of packets received is
computed as the total number of valid packets plus the sum of
"bootpCountInvalids" and "dhcpv4CountInvalids."
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:
"dhcpv4CountOffers," "dhcpv4CountAcks," and "dhcpv4CountNaks"
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.
3.4. BOOTP and DHCP Optional Statistics Group dhcpv4CountOffers + dhcpv4CountAcks + dhcpv4CountNaks
This section describes some of the management information that may be The number of packets (BOOTP and DHCP) sent by the server is
derived from the objects provided in the optional statistics group. computed as:
Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter- (total number of DHCP packets sent) + (bootpCountReplies)
arrival time of valid DHCP messages for the interval t1 to t2 can be
computed as (dhcpv4StatLastArrivalTime at t2 minus
dhcpv4StatLastArrivalTime 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 3.3.1. Discontinuities
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
(dhcpv4StatSumSquaresArrivalTime at t2 less
dhcpv4StatSumSquaresArrivalTime 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 Hosts for DHCP servers, and the DHCP servers themselves, are
similar to the calculations for inter-arrival time, except that the generally quite reliable but occasionally counter values may be
response time objects are used for the calculations. discontinuous between successive GETs. There are several cases of
interest:
Calculation of statistics for BOOTP is similar to the calculations o Server fails and is restarted, resetting all counters to zero.
for DHCP, except that the similar objects from the
bootpOptionalStatistics group are used instead of the objects from o Server fails and is restarted, with counters in an unknown
dhcpv4OptionalStatistics group, server Configuration Group state.
o Server fails and is restarted, with counters restored to some
previously checkpointed value.
The first case MAY occur when a server and agent are incapable of
restarting to a "last known good" state, and a manager MUST be
capable of recognizing this case. There is little a manager can do
other than recognize a reset to zero has occurred and continue from
the point of restart.
The second case is currently the Best Current Practice for SNMP
managers. Because of the uncertain state of counters following a
server restart, a manager MUST discard data from the outage interval
and restart its calculations.
The third case SHOULD arise only if agents take periodic snapshots
at different intervals than responding to a GET request. While the
counts reported in the first GET response following the outage were
accurate at some time, they MAY NOT be completely current. If this
occurs, the manager MAY have to accept that data has been lost,
perhaps discarding accumulated data, and continue.
3.3.2. Counter Rollover
Counter objects increment at different rates. It can be expected
that some counter will reach its maximum value and rollover to zero
while others are nowhere near their maximum value. When a counter's
value at time t2 is less than its value at time t1, the manager
SHOULD initially assume that a discontinuity has occurred and
perform appropriate data validation to determine if the value has
rolled over. If a single rollover has occurred, the value used in
calculation SHOULD be:
[(maximum value of counter) - (value at time t1)] + (value at
time t2) + 1
Managers SHOULD be alert to the possibility of a counter rolling
over more than once during the sampling interval. If this is
likely to occur (due to very short leases, very large numbers of
clients, network topology, and the presence of unreliable clients
or intermediate network equipment) a manager SHOULD carefully
examine each detected counter rollover to determine if the data
can be used or should be discarded.
3.4. Server Configuration Group
The server configuration group contains objects that describe the The server configuration group contains objects that describe the
configuration information that is contained in the server. Some of client host configuration information that is held in the server to
the configuration information is static (e.g., a statically be offered to requesting clients. Some of the configuration
configured IP address) and some of the configuration is dynamic information is static (e.g., a statically configured IPv4 address)
(e.g., an assigned DHCP lease). The intent of the server and some of the configuration is dynamic (e.g., an assigned DHCP
configuration group is to be able to read the server's configuration. lease). The intent of the server configuration group is to be able
Mechanisms outside of the SNMP are currently in use (e.g., vendor to read the server's configuration.
defined solutions) and are being standardized (e.g., the Directory
Enabled Networks [DEN] initiative) to update a server's
configuration.
The configuration information defines a minimal set of information The configuration information defines a minimal set of information
that most servers should be able to provide. Each row of the that most servers should be able to provide. Each row of the
dhcpv4ServerSubnetTable lists the subnet, the subnet mask, and the dhcpv4ServerSubnetTable lists the subnet address, the subnet mask,
subnet that is equivalent to this subnet. Equivalence is defined as and the shared network name that is equivalent to the subnet.
more than one subnet being present on the same network segment as Equivalence is defined as more than one subnet being present on the
some other subnet. same network segment as some other subnet.
The dhcpv4ServerRangeTable lists the start and end IP addresses of The dhcpv4ServerRangeTable lists the start and end IPv4 addresses of
the ranges and the subnet of which the range is a member. The the ranges and the subnet of which the range is a member. The
dhcpv4ServerRangeInUse object indicates the amount of the range that dhcpv4ServerRangeInUse object indicates the amount of the range that
is currently in use, either through dynamic allocation or being is currently in use, either through dynamic allocation or being
reserved. The range size can be computed by taking the difference of reserved. The range size can be computed as:
the "dhcpv4ServerRangeStartAddress" and "dhcpv4ServerRangeEndAddress"
objects.
The dhcpv4ServerAddressTable provides information about the static dhcpv4ServerRangeStartAddress - dhcpv4ServerRangeEndAddress +
1
The dhcpv4ServerClientTable provides information about the static
and dynamic addresses that the server contains in its configuration. and dynamic addresses that the server contains in its configuration.
Addresses may be: Addresses can be:
o Static, in which case they are predefined though the server's o Static, in which case they are predefined though the server's
configuration. Static addresses may or may not have been configuration. Static addresses may or may not have been
previously served by the server; previously served by the server;
o Dynamic, in which case the server has served the addresses and o Dynamic, in which case the server has served the addresses and
it is currently in active use by a host; it is currently in active use by a host;
o Expired, in which case the server had previously assigned for o Expired, in which case the server had previously assigned the
which the lease time has expired, but is retained by the server address, but the lease time has expired and is retained by the
for possible future use by the same client; server for possible future use by the same client;
o Configuration-reserved, in which case the address is not o Configuration-reserved, in which case the address is not
available for the server to allocate to a client. A available for the server to allocate to a client. A
configuration-reserved address is one that has been reserved by configuration-reserved address is one that has been reserved by
the administrator. An example of a configuration-reserved the administrator. An example of a configuration-reserved
address is an address that is assigned to a client, not through address is an address that is assigned to a client, not through
DHCP (e.g., statically assigned), and the address is within a DHCP (e.g., statically assigned), and the address is within a
DHCP range; and DHCP range; and
o Server-reserved, in which case the server has taken the address o Server-reserved, in which case the server has taken the address
out of use. Examples of server-reserved addresses are those out of use. Examples of server-reserved addresses are those
that have been declined (i.e., through a DHCPDECLINE) by a that have been declined (i.e., through a DHCPDECLINE) by a
client or those that have responded to an ICMP echo before they client or those that 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 can be determined from the
"dhcpv4ServerAddressServedProtocol" object. This object indicates "dhcpv4ServerClientServedProtocol" object. This object indicates
whether the address has never been served, or whether BOOTP or DHCP whether the address has never been served, or whether BOOTP or DHCP
was used to allocate the address. was used to allocate the address.
3.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.
4. Definitions 4. Definitions
DHCP-SERVER-MIB DEFINITIONS ::= BEGIN DHCP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter64, Counter32, Gauge32, Unsigned32, MODULE-IDENTITY, Counter64, Gauge32, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE, mib-2 OBJECT-IDENTITY, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime FROM SNMPv2-TC TEXTUAL-CONVENTION, DateAndTime FROM SNMPv2-TC
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressIPv4, InetAddressPrefixLength InetAddressIPv4, InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
dhcp MODULE-IDENTITY dhcp MODULE-IDENTITY
LAST-UPDATED "200310271708Z" LAST-UPDATED "200402061633Z"
ORGANIZATION ORGANIZATION
"IETF DHC Working Group "IETF DHC Working Group
General Discussion: dhcwg@ietf.org General Discussion: dhcwg@ietf.org
Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
Archive: http://www1.ietf.org/mailman/listinfo/dhcwg Archive: http://www1.ietf.org/mailman/listinfo/dhcwg
Chair: Ralph Droms, rdroms@cisco.com" Chair: Ralph Droms, rdroms@cisco.com"
CONTACT-INFO CONTACT-INFO
" Richard Barr Hibbs " Richard Barr Hibbs
Postal: 952 Sanchez Street Postal: 952 Sanchez Street
San Francisco, California 94114-3362 San Francisco, California 94114-3362
skipping to change at page 10, line 12 skipping to change at page 10, line 12
the Bootstrap Protocol (BOOTP) and the Dynamic Host the Bootstrap Protocol (BOOTP) and the Dynamic Host
Configuration protocol (DHCP) for Internet Protocol version Configuration protocol (DHCP) for Internet Protocol version
4(IPv4). This MIB does not include support for Dynamic DNS 4(IPv4). This MIB does not include support for Dynamic DNS
(DDNS) updating nor for the DHCP Failover Protocol. (DDNS) updating nor for the DHCP Failover Protocol.
Copyright (C) The Internet Society (2003). This version of Copyright (C) The Internet Society (2003). This version of
this MIB module is part of RFC xxxx; see the RFC itself for this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices." full legal notices."
-- RFC Editor assigns xxxx and removes this comment -- RFC Editor assigns xxxx and removes this comment
REVISION "200310271708Z" -- 27 October 2003 REVISION "200402061633Z" -- 6 February 2004
DESCRIPTION "Initial Version, published as RFC xxxx." DESCRIPTION "Initial Version, published as RFC xxxx."
-- RFC Editor assigns xxxx and removes this comment -- RFC Editor assigns xxxx and removes this comment
::= { mib-2 TBD } -- IANA will make official assignment ::= { mib-2 9999 } -- IANA will make official assignment
-- Textual conventions defined by this memo -- Textual conventions defined by this memo
DhcpTimeInterval ::= TEXTUAL-CONVENTION Dhcpv4PhysicalAddress ::= TEXTUAL-CONVENTION
STATUS current DISPLAY-HINT "1d,1d,1x:1x:1x:1x:1x:1x"
DESCRIPTION
"The number of milliseconds that has elapsed since some epoch.
Systems that cannot measure events to the millisecond
resolution SHOULD round this value to the next available
resolution that the system supports."
SYNTAX Unsigned32
DhcpPhysicalAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d,1d,1x:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A DHCP-specific encoding of the physical address type and "A DHCP-specific encoding of the physical address type and
physical address, intended to mirror the representation of physical address, intended to mirror the representation of
physical addresses in DHCP messages. The first octet of this physical addresses in DHCP messages. The first octet of this
object contains the hardware type from the 'htype' field of the object contains the hardware type from the 'htype' field of
DHCP message, the second octet of this object contains the the DHCP message, the second octet of this object contains the
hardware length from the 'hlen' field, and the remaining octets hardware length from the 'hlen' field, and the remaining
contain the hardware address from the 'chaddr' field." octets contain the hardware address from the 'chaddr' field."
REFERENCE "RFC 2131" REFERENCE "RFC 2131"
SYNTAX OCTET STRING (SIZE(3..18)) SYNTAX OCTET STRING (SIZE(18))
-- declare top-level MIB objects -- declare top-level MIB objects
dhcpv4Server OBJECT-IDENTITY dhcpv4Server OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCPv4 Server MIB objects are defined in this branch." "DHCPv4 Server MIB objects are defined in this branch."
::= { dhcp 1 } ::= { dhcp 1 }
-- dhcpv4Client OBJECT-IDENTITY
-- STATUS future
-- DESCRIPTION
-- "DHCPv4 Client MIB objects are defined in this branch."
-- ::= { dhcp 2 }
-- dhcpv4Relay OBJECT-IDENTITY
-- STATUS future
-- DESCRIPTION
-- "DHCPv4 Relay Agent MIB objects are defined in this branch."
-- ::= { dhcp 3 }
-- dhcpv6Server OBJECT-IDENTITY
-- STATUS future
-- DESCRIPTION
-- "DHCPv6 Server MIB objects are defined in this branch."
-- ::= { dhcp 4 }
dhcpv4ServerObjects OBJECT-IDENTITY dhcpv4ServerObjects OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB server identification objects are all defined "DHCP Server MIB server identification objects are all defined
in this branch." in this branch."
::= { dhcpv4Server 1 } ::= { dhcpv4Server 1 }
dhcpv4ServerSystem OBJECT-IDENTITY dhcpv4ServerSystem OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 11, line 45 skipping to change at page 11, line 18
DESCRIPTION DESCRIPTION
"Group of objects that count various BOOTP events." "Group of objects that count various BOOTP events."
::= { dhcpv4ServerObjects 2 } ::= { dhcpv4ServerObjects 2 }
dhcpv4Counters OBJECT-IDENTITY dhcpv4Counters OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that count various DHCPv4 events." "Group of objects that count various DHCPv4 events."
::= { dhcpv4ServerObjects 3 } ::= { dhcpv4ServerObjects 3 }
bootpOptionalStatistics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Group of objects that measure various BOOTP statistics."
::= { dhcpv4ServerObjects 4 }
dhcpv4OptionalStatistics OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Group of objects that measure various DHCPv4 statistics."
::= { dhcpv4ServerObjects 5 }
dhcpv4ServerConfiguration OBJECT-IDENTITY dhcpv4ServerConfiguration 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."
::= { dhcpv4ServerObjects 6 } ::= { dhcpv4ServerObjects 6 }
dhcpv4ServerNotifyObjects OBJECT-IDENTITY dhcpv4ServerNotifyObjects OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that are used only in notifications." "Objects that are used only in notifications."
::= { dhcpv4ServerObjects 7 } ::= { dhcpv4ServerObjects 7 }
-- dhcpv4ServerSystemObjects Group -- dhcpv4ServerSystemObjects Group
dhcpv4ServerSystemDescr OBJECT-TYPE dhcpv4ServerSystemDescr OBJECT-TYPE
SYNTAX SnmpAdminString (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."
::= { dhcpv4ServerSystem 1 } ::= { dhcpv4ServerSystem 1 }
dhcpv4ServerSystemObjectID OBJECT-TYPE dhcpv4ServerSystemObjectID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor's authoritative identification of the network "The vendor's authoritative identification of the network
management subsystem contained in this entity. This value is management subsystem contained in this entity. This value is
allocated within the SMI enterprise subtree (1.3.6.1.4.1) and allocated within the SMI enterprise subtree (1.3.6.1.4.1) and
provides an easy and unambiguous means for determining what provides an easy and unambiguous means for determining what
kind of server is being managed. For example, if vendor Ohso kind of server is being managed. For example, if vendor Ohso
Soft, Inc. is assigned the subtree 1.3.6.1.4.1.4242, it may Soft, Inc. is assigned the subtree 1.3.6.1.4.1.4242, it might
assign the identifier 1.3.6.1.4.1.4242.1.1 to its Ursa DHCP assign the identifier 1.3.6.1.4.1.4242.1.1 to its Ursa DHCP
Server." Server."
::= { dhcpv4ServerSystem 2 } ::= { dhcpv4ServerSystem 2 }
-- bootpCounterObjects Group -- bootpCounterObjects Group
bootpCountRequests OBJECT-TYPE bootpCountRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received that contain a Message Type of "The number of packets received that contain a Message Type of
1 (BOOTREQUEST) in the first octet and do not contain option 1 (BOOTREQUEST) in the first octet and do not contain option
number 53 (DHCP Message Type) in the options." number 53 (DHCP Message Type) in the options."
REFERENCE REFERENCE
"RFC-2131." "RFC-2131."
::= { bootpCounters 1 } ::= { bootpCounters 1 }
bootpCountInvalids OBJECT-TYPE bootpCountInvalids OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received that do not contain a Message "The number of packets received that do not contain a Message
Type of 1 (BOOTREQUEST) in the first octet or are not valid Type of 1 (BOOTREQUEST) in the first octet or are not valid
BOOTP packets (e.g., too short, invalid field in packet BOOTP packets (e.g., too short, invalid field in packet
header)." header)."
::= { bootpCounters 2 } ::= { bootpCounters 2 }
bootpCountReplies OBJECT-TYPE bootpCountReplies OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets sent that contain a Message Type of 2 "The number of packets sent that contain a Message Type of 2
(BOOTREPLY) in the first octet and do not contain option number (BOOTREPLY) in the first octet and do not contain option
53 (DHCP Message Type) in the options." number 53 (DHCP Message Type) in the options."
REFERENCE REFERENCE
"RFC-2131." "RFC-2131."
::= { bootpCounters 3 } ::= { bootpCounters 3 }
bootpCountDroppedUnknownClients OBJECT-TYPE bootpCountDroppedUnknownClients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BOOTP packets dropped due to the server not "The number of BOOTP packets dropped due to the server not
recognizing or not providing service to the hardware address recognizing or not providing service to the hardware address
received in the incoming packet." received in the incoming packet."
::= { bootpCounters 4 } ::= { bootpCounters 4 }
bootpCountDroppedNotServingSubnet OBJECT-TYPE bootpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BOOTP packets dropped due to the server not "The number of BOOTP packets dropped due to the server not
being configured or not otherwise able to serve addresses on being configured or not otherwise able to serve addresses on
the subnet from which this message was received." the subnet from which this message was received."
::= { bootpCounters 5 } ::= { bootpCounters 5 }
-- DHCP Counters -- DHCP Counters Group
dhcpv4RecvdPacketCounters OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Counters for valid received DHCP message packets."
::= { dhcpv4Counters 1 }
dhcpv4SentPacketCounters OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Counters for valid sent DHCP message packets."
::= { dhcpv4Counters 2 }
dhcpv4ErrorPacketCounters OBJECT-IDENTITY
STATUS current
DESCRIPTION
"Counters for DHCP message packets received, but not processed
by the server due to configuration or other errors."
::= { dhcpv4Counters 3 }
-- dhcpv4RecvdPacketCounterObjects Group
dhcpv4CountDiscovers OBJECT-TYPE dhcpv4CountDiscovers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPDISCOVER (option 53 with value 1) packets "The number of DHCPDISCOVER (option 53 with value 1) packets
received." received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4RecvdPacketCounters 1 } ::= { dhcpv4Counters 1 }
dhcpv4CountRequests OBJECT-TYPE dhcpv4CountOffers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPREQUEST (option 53 with value 3) packets "The number of DHCPOFFER (option 53 with value 2) packets
received." sent."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4RecvdPacketCounters 2 } ::= { dhcpv4Counters 2 }
dhcpv4CountReleases OBJECT-TYPE dhcpv4CountRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPRELEASE (option 53 with value 7) packets "The number of DHCPREQUEST (option 53 with value 3) packets
received." received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4RecvdPacketCounters 3 } ::= { dhcpv4Counters 3}
dhcpv4CountDeclines OBJECT-TYPE dhcpv4CountDeclines OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPDECLINE (option 53 with value 4) packets "The number of DHCPDECLINE (option 53 with value 4) packets
received." received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4RecvdPacketCounters 4 } ::= { dhcpv4Counters 4 }
dhcpv4CountInforms OBJECT-TYPE dhcpv4CountAcks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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 DHCPACK (option 53 with value 5) packets sent."
received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4RecvdPacketCounters 5 } ::= { dhcpv4Counters 5 }
-- dhcpv4SentPacketCounterObjects Group
dhcpv4CountOffers OBJECT-TYPE dhcpv4CountNaks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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 DHCPNACK (option 53 with value 6) packets
sent." sent."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4SentPacketCounters 1 } ::= { dhcpv4Counters 6 }
dhcpv4CountAcks OBJECT-TYPE dhcpv4CountReleases OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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 DHCPRELEASE (option 53 with value 7) packets
received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4SentPacketCounters 2 } ::= { dhcpv4Counters 7 }
dhcpv4CountNaks OBJECT-TYPE dhcpv4CountInforms OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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 DHCPINFORM (option 53 with value 8) packets
received."
REFERENCE REFERENCE
"RFC2131; RFC2132, section 9.6." "RFC2131; RFC2132, section 9.6."
::= { dhcpv4SentPacketCounters 3 } ::= { dhcpv4Counters 8 }
dhcpv4CountForcedRenews OBJECT-TYPE dhcpv4CountForcedRenews OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPFORCERENEW (option 53 with value 9) packets "The number of DHCPFORCERENEW (option 53 with value 9) packets
sent." sent."
REFERENCE REFERENCE
" RFC 3203, DHCP reconfigure extension." " RFC 3203, DHCP reconfigure extension."
::= { dhcpv4SentPacketCounters 4 } ::= { dhcpv4Counters 9 }
-- dhcpv4ErrorPacketCounterObjects Group
dhcpv4CountInvalids OBJECT-TYPE dhcpv4CountInvalids OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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."
::= { dhcpv4ErrorPacketCounters 1 } ::= { dhcpv4Counters 10 }
dhcpv4CountDroppedUnknownClient OBJECT-TYPE dhcpv4CountDroppedUnknownClient OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter64
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."
::= { dhcpv4ErrorPacketCounters 2 } ::= { dhcpv4Counters 11 }
dhcpv4CountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCP packets dropped due to the server not being
configured or not otherwise able to serve addresses on the
subnet from which this message was received."
::= { dhcpv4ErrorPacketCounters 3 }
-- bootpOptionalStatisticObjects group
bootpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time between receiving two BOOTP
messages. A message is received at the server when the server
is able to begin processing the message. This typically occurs
immediately after the message is read into server memory. If
no messages have been received, then this object contains a
zero value."
::= { bootpOptionalStatistics 1 }
bootpStatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum amount of time between receiving two BOOTP
messages. A message is received at the server when the server
is able to begin processing the message. This typically occurs
immediately after the message is read into server memory. If
no messages have been received, then this object contains a
zero value."
::= { bootpOptionalStatistics 2 }
bootpStatLastArrivalTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time that the last valid BOOTP message was
received by the server. Invalid messages do not cause this
value to change. If valid no messages have been received, then
this object contains a date and time that is all zero."
::= { bootpOptionalStatistics 3 }
bootpStatSumSquaresArrivalTime OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the squared BOOTP packet inter-arrival times in
microseconds. This value may be used to compute the variance
and standard deviation of the BOOTP arrival times. Note that a
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 4 }
bootpStatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smallest time interval measured as the difference between
the arrival of a BOOTP message at the server and the successful
transmission of the response to that message. A message is
received at the server when the server is able to begin
processing the message. A message is transmitted after the
server has no further use for the message. Note that the
operating system may still have the message queued internally.
The operating system queue time is not to be considered as part
of the response time. Invalid messages do not cause this value
to change. If no valid messages have been received, then this
object contains a zero value."
::= { bootpOptionalStatistics 5 }
bootpStatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest time interval measured as the difference between
the arrival of a BOOTP message at the server and the successful
transmission of the response to that message. A message is
received at the server when the server is able to begin
processing the message. A message is transmitted after the
server has no further use for the message. Note that the
operating system may still have the message queued internally.
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."
::= { bootpOptionalStatistics 6 }
bootpStatSumResponseTime OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the response time intervals in milliseconds where a
response time interval is measured as the difference between
the arrival of a BOOTP message at the server and the successful
transmission of the response to that message. A message is
received at the server when the server is able to begin
processing the message. A message is transmitted after the
server has no further use for the message. Note that the
operating system may still have the message queued internally.
The operating system queue time is not to be considered as part
of the response time. Invalid messages do not cause this value
to change. If no valid messages have been received, then this
object contains a zero value."
::= { bootpOptionalStatistics 7 }
bootpStatSumSquaresResponseTime OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the squared BOOTP packet response times in micro-
seconds. This value may be used to compute the variance and
standard deviation of the BOOTP response times. Note that a
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 }
-- dhcpv4OptionalStatisticObjects group
dhcpv4StatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The minimum amount of time between receiving two DHCPv4
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."
::= { dhcpv4OptionalStatistics 1 }
dhcpv4StatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum amount of time between receiving two DHCPv4
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."
::= { dhcpv4OptionalStatistics 2 }
dhcpv4StatLastArrivalTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time that the last valid DHCPv4 message was
received by the server. Invalid messages do not cause this
value to change. If no valid messages have been received, then
this object contains a date and time that is all zero."
::= { dhcpv4OptionalStatistics 3 }
dhcpv4StatSumSquaresArrivalTime OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the squared DHCPv4 packet inter-arrival times in
microseconds. This value may be used to compute the variance
and standard deviation of the DHCPv4 arrival times. Note that
a 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."
::= { dhcpv4OptionalStatistics 4 }
dhcpv4StatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smallest time interval measured as the difference between
the arrival of a DHCPv4 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."
::= { dhcpv4OptionalStatistics 5 }
dhcpv4StatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The largest time interval measured as the difference between
the arrival of a DHCPv4 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."
::= { dhcpv4OptionalStatistics 6 }
dhcpv4StatSumResponseTime OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sum of the response time intervals in milliseconds where a
response time interval is measured as the difference between
the arrival of a DHCPv4 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."
::= { dhcpv4OptionalStatistics 7 }
dhcpv4StatSumSquaresResponseTime OBJECT-TYPE dhcpv4CountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the squared DHCPv4 packet response times in micro- "The number of DHCP packets dropped due to the server not
seconds. This value may be used to compute the variance and being configured or not otherwise able to serve addresses on
standard deviation of the DHCPv4 response times. Note that a the subnet from which this message was received."
microsecond resolution of this object requires a clock ::= { dhcpv4Counters 12 }
resolution to the millisecond since the square of a millisecond
value produces a value with microsecond resolution."
::= { dhcpv4OptionalStatistics 8 }
-- DHCP Server Configuration -- DHCP Server Configuration
-- dhcpv4ServerSharedNetObjects Group -- dhcpv4ServerSharedNetObjects Group
dhcpv4ServerSharedNetTable OBJECT-TYPE dhcpv4ServerSharedNetTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dhcpv4ServerSharedNetEntry SYNTAX SEQUENCE OF Dhcpv4ServerSharedNetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of shared networks that are configured in the server. "A list of shared networks that are configured in the server.
A shared network is the logical aggregation of one or more A shared network is the logical aggregation of one or more
subnets that share a common network segment (e.g., multi-tapped subnets that share a common network segment (e.g., multi-
coaxial cable, wiring hub, or switch). This table is present tapped coaxial cable, wiring hub, or switch). This table is
ONLY for those servers that organize the ranges of addresses present ONLY for those servers that organize the ranges of
available for assignment where a higher-level grouping (i.e., addresses available for assignment where a higher-level
the 'shared' network) exists above ranges and subnets." grouping (i.e., the 'shared' network) exists above ranges and
subnets."
::= { dhcpv4ServerConfiguration 1 } ::= { dhcpv4ServerConfiguration 1 }
dhcpv4ServerSharedNetEntry OBJECT-TYPE dhcpv4ServerSharedNetEntry OBJECT-TYPE
SYNTAX Dhcpv4ServerSharedNetEntry SYNTAX Dhcpv4ServerSharedNetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A logical row in the dhcpv4ServerSharedNetTable." "A logical row in the dhcpv4ServerSharedNetTable."
INDEX { INDEX {
dhcpv4ServerSharedNetName dhcpv4ServerSharedNetName
skipping to change at page 23, line 29 skipping to change at page 17, line 21
server until the value for available free addresses has server until the value for available free addresses has
exceeded the value of exceeded the value of
dhcpv4ServerSharedNetFreeAddrHighThreshold." dhcpv4ServerSharedNetFreeAddrHighThreshold."
::= { dhcpv4ServerSharedNetEntry 2 } ::= { dhcpv4ServerSharedNetEntry 2 }
dhcpv4ServerSharedNetFreeAddrHighThreshold OBJECT-TYPE dhcpv4ServerSharedNetFreeAddrHighThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The high threshold for available free addresses in this shared "The high threshold for available free addresses in this
network. If a dhcpv4ServerFreeAddressLow event was generated shared network. If a dhcpv4ServerFreeAddressLow event was
for this subnet, and the value for available free addresses has generated for this subnet, and the value for available free
exceeded the value of dhcpv4ServerSubnetFreeAddrHighThreshold, addresses has exceeded the value of
then a dhcpv4ServerFreeAddressHigh event will be generated. No dhcpv4ServerSubnetFreeAddrHighThreshold, then a
more dhcpv4ServerFreeAddressHigh events will be generated for dhcpv4ServerFreeAddressHigh event will be generated. No more
this subnet during this execution of the DHCP server until the dhcpv4ServerFreeAddressHigh 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 value for available free addresses becomes equal to or less
than the value of dhcpv4ServerSubnetFreeAddrLowThreshold." than the value of dhcpv4ServerSubnetFreeAddrLowThreshold."
::= { dhcpv4ServerSharedNetEntry 3 } ::= { dhcpv4ServerSharedNetEntry 3 }
dhcpv4ServerSharedNetFreeAddresses OBJECT-TYPE dhcpv4ServerSharedNetFreeAddresses OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of IP addresses which are available within this "The number of IPv4 addresses which are available within this
shared network. If the server does not count free addresses by shared network. If the server does not count free addresses
shared network segment, this value will be zero." by shared network segment, this value will be zero."
::= { dhcpv4ServerSharedNetEntry 4 } ::= { dhcpv4ServerSharedNetEntry 4 }
dhcpv4ServerSharedNetReservedAddresses OBJECT-TYPE dhcpv4ServerSharedNetReservedAddresses OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of IP addresses which are reserved (not available "The number of IPv4 addresses which are reserved (not
for assignment) within this shared network. If the server does available for assignment) within this shared network. If the
not count reserved addresses by shared network segment, this server does not count reserved addresses by shared network
value will be zero." segment, this value will be zero."
::= { dhcpv4ServerSharedNetEntry 5 } ::= { dhcpv4ServerSharedNetEntry 5 }
dhcpv4ServerSharedNetTotalAddresses OBJECT-TYPE dhcpv4ServerSharedNetTotalAddresses OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of IP addresses which are available within this "The number of IPv4 addresses which are available within this
shared network. If the server does not count total addresses shared network. If the server does not count total addresses
by shared network segment, this value will be zero." by shared network segment, this value will be zero."
::= { dhcpv4ServerSharedNetEntry 6 } ::= { dhcpv4ServerSharedNetEntry 6 }
-- dhcpv4ServerSubnetObjects Group -- dhcpv4ServerSubnetObjects Group
dhcpv4ServerSubnetTable OBJECT-TYPE dhcpv4ServerSubnetTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dhcpv4ServerSubnetEntry SYNTAX SEQUENCE OF Dhcpv4ServerSubnetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 24, line 44 skipping to change at page 18, line 37
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A logical row in the dhcpv4ServerSubnetTable." "A logical row in the dhcpv4ServerSubnetTable."
INDEX { INDEX {
dhcpv4ServerSubnetAddress dhcpv4ServerSubnetAddress
} }
::= { dhcpv4ServerSubnetTable 1 } ::= { dhcpv4ServerSubnetTable 1 }
Dhcpv4ServerSubnetEntry ::= SEQUENCE { Dhcpv4ServerSubnetEntry ::= SEQUENCE {
dhcpv4ServerSubnetAddress InetAddressIPv4, dhcpv4ServerSubnetAddress InetAddressIPv4,
dhcpv4ServerSubnetMask InetAddressPrefixLength, dhcpv4ServerSubnetMask
InetAddressPrefixLength,
dhcpv4ServerSubnetSharedNetworkName SnmpAdminString, dhcpv4ServerSubnetSharedNetworkName SnmpAdminString,
dhcpv4ServerSubnetFreeAddrLowThreshold Unsigned32, dhcpv4ServerSubnetFreeAddrLowThreshold Unsigned32,
dhcpv4ServerSubnetFreeAddrHighThreshold Unsigned32, dhcpv4ServerSubnetFreeAddrHighThreshold Unsigned32,
dhcpv4ServerSubnetFreeAddresses Unsigned32 dhcpv4ServerSubnetFreeAddresses Unsigned32
} }
dhcpv4ServerSubnetAddress OBJECT-TYPE dhcpv4ServerSubnetAddress OBJECT-TYPE
SYNTAX InetAddressIPv4 SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the subnet entry in the "The IPv4 address of the subnet entry in the
dhcpv4ServerSubnetTable." dhcpv4ServerSubnetTable."
::= { dhcpv4ServerSubnetEntry 1 } ::= { dhcpv4ServerSubnetEntry 1 }
dhcpv4ServerSubnetMask OBJECT-TYPE dhcpv4ServerSubnetMask OBJECT-TYPE
SYNTAX InetAddressPrefixLength 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."
::= { dhcpv4ServerSubnetEntry 2 } ::= { dhcpv4ServerSubnetEntry 2 }
dhcpv4ServerSubnetSharedNetworkName OBJECT-TYPE dhcpv4ServerSubnetSharedNetworkName OBJECT-TYPE
skipping to change at page 25, line 36 skipping to change at page 19, line 29
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."
::= { dhcpv4ServerSubnetEntry 3 } ::= { dhcpv4ServerSubnetEntry 3 }
dhcpv4ServerSubnetFreeAddrLowThreshold OBJECT-TYPE dhcpv4ServerSubnetFreeAddrLowThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The low threshold for available free addresses in this subnet. "The low threshold for available free addresses in this
If the value for available free addresses in this subnet subnet. If the value for available free addresses in this
becomes equal to or less than this value, a subnet becomes equal to or less than this value, a
dhcpv4ServerSubnetFreeAddrLowThreshold event will be generated dhcpv4ServerSubnetFreeAddrLowThreshold event will be generated
for this shared network. No more for this shared network. No more
dhcpv4ServerSubnetFreeAddrLowThreshold events will be generated dhcpv4ServerSubnetFreeAddrLowThreshold events will be
for this subnet during this execution of the DHCP server until generated for this subnet during this execution of the DHCP
the value for available free addresses has exceeded the value server until the value for available free addresses has
of dhcpv4ServerSubnetFreeAddrHighThreshold." exceeded the value of
dhcpv4ServerSubnetFreeAddrHighThreshold."
::= { dhcpv4ServerSubnetEntry 4 } ::= { dhcpv4ServerSubnetEntry 4 }
dhcpv4ServerSubnetFreeAddrHighThreshold OBJECT-TYPE dhcpv4ServerSubnetFreeAddrHighThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The high threshold for available free addresses in this "The high threshold for available free addresses in this
subnet. If a dhcpv4ServerSubnetFreeAddrLowThreshold event has subnet. If a dhcpv4ServerSubnetFreeAddrLowThreshold event has
been generated for this subnet, and the value for available been generated for this subnet, and the value for available
free addresses has exceeded the value of free addresses has exceeded the value of
dhcpv4ServerSubnetFreeAddrHighThreshold, then a dhcpv4ServerSubnetFreeAddrHighThreshold, then a
dhcpv4ServerFreeAddressHigh event will be generated. No more dhcpv4ServerFreeAddressHigh event will be generated. No more
dhcpv4ServerFreeAddressHigh events will be generated for this dhcpv4ServerFreeAddressHigh events will be generated for this
subnet during this execution of the DHCP server until the value subnet during this execution of the DHCP server until the
for available free addresses becomes equal to or less than the value for available free addresses becomes equal to or less
value of dhcpv4ServerSubnetFreeAddrLowThreshold." than the value of dhcpv4ServerSubnetFreeAddrLowThreshold."
::= { dhcpv4ServerSubnetEntry 5 } ::= { dhcpv4ServerSubnetEntry 5 }
dhcpv4ServerSubnetFreeAddresses OBJECT-TYPE dhcpv4ServerSubnetFreeAddresses OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of free IP addresses which are available in this "The number of free IPv4 addresses which are available in this
subnet." subnet."
::= { dhcpv4ServerSubnetEntry 6 } ::= { dhcpv4ServerSubnetEntry 6 }
-- dhcpv4ServerRangeObjects Group -- dhcpv4ServerRangeObjects Group
dhcpv4ServerRangeTable OBJECT-TYPE dhcpv4ServerRangeTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerRangeEntry SYNTAX SEQUENCE OF Dhcpv4ServerRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of ranges that are configured on this server." "A list of ranges that are configured on this server."
::= { dhcpv4ServerConfiguration 3 } ::= { dhcpv4ServerConfiguration 3 }
dhcpv4ServerRangeEntry OBJECT-TYPE dhcpv4ServerRangeEntry OBJECT-TYPE
SYNTAX ServerRangeEntry SYNTAX Dhcpv4ServerRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A logical row in the dhcpv4ServerRangeTable." "A logical row in the dhcpv4ServerRangeTable."
INDEX { INDEX {
dhcpv4ServerRangeStartAddress, dhcpv4ServerRangeStartAddress,
dhcpv4ServerRangeEndAddress dhcpv4ServerRangeEndAddress
} }
::= { dhcpv4ServerRangeTable 1 } ::= { dhcpv4ServerRangeTable 1 }
ServerRangeEntry ::= SEQUENCE { Dhcpv4ServerRangeEntry ::= SEQUENCE {
dhcpv4ServerRangeStartAddress InetAddressIPv4, dhcpv4ServerRangeStartAddress InetAddressIPv4,
dhcpv4ServerRangeEndAddress InetAddressIPv4, dhcpv4ServerRangeEndAddress InetAddressIPv4,
dhcpv4ServerRangeSubnetMask InetAddressPrefixLength, dhcpv4ServerRangeSubnetMask InetAddressPrefixLength,
dhcpv4ServerRangeInUse Gauge32, dhcpv4ServerRangeInUse Gauge32,
dhcpv4ServerRangeOutstandingOffers Gauge32 dhcpv4ServerRangeOutstandingOffers Gauge32
} }
dhcpv4ServerRangeStartAddress OBJECT-TYPE dhcpv4ServerRangeStartAddress OBJECT-TYPE
SYNTAX InetAddressIPv4 SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the first address in the range. The value "The IPv4 address of the first address in the range. The
of dhcpv4ServerRangeStartAddress must be less than or equal to value of dhcpv4ServerRangeStartAddress MUST be less than or
the value of dhcpv4ServerRangeEndAddress." equal to the value of dhcpv4ServerRangeEndAddress."
::= { dhcpv4ServerRangeEntry 1 } ::= { dhcpv4ServerRangeEntry 1 }
dhcpv4ServerRangeEndAddress OBJECT-TYPE dhcpv4ServerRangeEndAddress OBJECT-TYPE
SYNTAX InetAddressIPv4 SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last address in the range. The value of "The IPv4 address of the last address in the range. The value
dhcpv4ServerRangeEndAddress must be greater than or equal to of dhcpv4ServerRangeEndAddress MUST be greater than or equal
the value of dhcpv4ServerRangeStartAddress." to the value of dhcpv4ServerRangeStartAddress."
::= { dhcpv4ServerRangeEntry 2 } ::= { dhcpv4ServerRangeEntry 2 }
dhcpv4ServerRangeSubnetMask OBJECT-TYPE dhcpv4ServerRangeSubnetMask OBJECT-TYPE
SYNTAX InetAddressPrefixLength 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."
::= { dhcpv4ServerRangeEntry 3 } ::= { dhcpv4ServerRangeEntry 3 }
skipping to change at page 27, line 48 skipping to change at page 21, line 43
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)."
::= { dhcpv4ServerRangeEntry 4 } ::= { dhcpv4ServerRangeEntry 4 }
dhcpv4ServerRangeOutstandingOffers OBJECT-TYPE dhcpv4ServerRangeOutstandingOffers OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outstanding DHCPOFFER messages for this range is "The number of outstanding DHCPOFFER messages for this range
reported with this value. An offer is outstanding if the is reported with this value. An offer is outstanding if the
server has sent a DHCPOFFER message to a client, but has not server has sent a DHCPOFFER message to a client, but has not
yet received a DHCPREQUEST message from the client nor has the yet received a DHCPREQUEST message from the client nor has the
server-specific timeout (limiting the time in which a client server-specific timeout (limiting the time in which a client
can respond to the offer message) for the offer message can respond to the offer message) for the offer message
expired." expired."
::= { dhcpv4ServerRangeEntry 5 } ::= { dhcpv4ServerRangeEntry 5 }
-- dhcpv4ServerAddressObjects Group -- dhcpv4ServerClientObjects Group
dhcpv4ServerClientTable OBJECT-TYPE
dhcpv4ServerAddressTable OBJECT-TYPE SYNTAX SEQUENCE OF Dhcpv4ServerClientEntry
SYNTAX SEQUENCE OF Dhcpv4ServerAddressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An optional list of addresses that are known by this server. "An optional list of addresses that are known by this server.
The list MUST contain addresses that have not expired. The The list MUST contain addresses that have not expired. The
list MUST NOT contain addresses that have never been assigned list MUST NOT contain addresses that have never been assigned
by the server UNLESS the lease is pre-configured in the server by the server UNLESS the lease is pre-configured in the server
(e.g., a static lease for a host). Expired leases MAY appear (e.g., a static lease for a host). Expired leases MAY appear
during the time they are 'remembered' by the server for during the time they are 'remembered' by the server for
subsequent assignment to the same host." subsequent assignment to the same host."
::= { dhcpv4ServerConfiguration 4 } ::= { dhcpv4ServerConfiguration 4 }
dhcpv4ServerAddressEntry OBJECT-TYPE dhcpv4ServerClientEntry OBJECT-TYPE
SYNTAX Dhcpv4ServerAddressEntry SYNTAX Dhcpv4ServerClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A logical row in the dhcpv4ServerAddressTable." "A logical row in the dhcpv4ServerClientTable."
INDEX { INDEX {
dhcpv4ServerAddress dhcpv4ServerClient
} }
::= { dhcpv4ServerAddressTable 1 } ::= { dhcpv4ServerClientTable 1 }
Dhcpv4ServerAddressEntry ::= SEQUENCE { Dhcpv4ServerClientEntry ::= SEQUENCE {
dhcpv4ServerAddress InetAddressIPv4, dhcpv4ServerClient InetAddressIPv4,
dhcpv4ServerAddressSubnetMask InetAddressPrefixLength, dhcpv4ServerClientSubnetMask InetAddressPrefixLength,
dhcpv4ServerAddressRange InetAddressIPv4, dhcpv4ServerClientRange InetAddressIPv4,
dhcpv4ServerAddressLeaseType INTEGER, dhcpv4ServerClientLeaseType INTEGER,
dhcpv4ServerAddressTimeRemaining Unsigned32, dhcpv4ServerClientTimeRemaining Unsigned32,
dhcpv4ServerAddressAllowedProtocol INTEGER, dhcpv4ServerClientAllowedProtocol INTEGER,
dhcpv4ServerAddressServedProtocol INTEGER, dhcpv4ServerClientServedProtocol INTEGER,
dhcpv4ServerAddressPhysicalAddress DhcpPhysicalAddress, dhcpv4ServerClientPhysicalAddress Dhcpv4PhysicalAddress,
dhcpv4ServerAddressClientId OCTET STRING, dhcpv4ServerClientClientId OCTET STRING,
dhcpv4ServerAddressHostName SnmpAdminString, dhcpv4ServerClientHostName SnmpAdminString,
dhcpv4ServerAddressDomainName SnmpAdminString dhcpv4ServerClientDomainName SnmpAdminString
} }
dhcpv4ServerAddress OBJECT-TYPE dhcpv4ServerClient OBJECT-TYPE
SYNTAX InetAddressIPv4 SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of this entry in the dhcpv4ServerAddressTable." "The IPv4 address of this entry in the
::= { dhcpv4ServerAddressEntry 1 } dhcpv4ServerClientTable."
::= { dhcpv4ServerClientEntry 1 }
dhcpv4ServerAddressSubnetMask OBJECT-TYPE dhcpv4ServerClientSubnetMask OBJECT-TYPE
SYNTAX InetAddressPrefixLength 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
this address. The subnet, resulting from logically ANDing the offered this address. The subnet, resulting from logically
subnet mask with the entry's IP address, must be configured on ANDing the subnet mask with the entry's IPv4 address, MUST be
this server and appear as a row in the dhcpSubnetTable." configured on this server and appear as a row in the
::= { dhcpv4ServerAddressEntry 2 } dhcpSubnetTable."
::= { dhcpv4ServerClientEntry 2 }
dhcpv4ServerAddressRange OBJECT-TYPE dhcpv4ServerClientRange OBJECT-TYPE
SYNTAX InetAddressIPv4 SYNTAX InetAddressIPv4
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting IP address (dhcpv4ServerRangeStartAddress object) "The starting IPv4 address (dhcpv4ServerRangeStartAddress
of the range to which this address belongs. If the address object) of the range to which this address belongs. If the
does not fall into one of the configured ranges (e.g., a address does not fall into one of the configured ranges (e.g.,
statically configured address on a subnet) the range may be a statically configured address on a subnet) the range MAY be
0.0.0.0." 0.0.0.0."
::= { dhcpv4ServerAddressEntry 3 } ::= { dhcpv4ServerClientEntry 3 }
dhcpv4ServerAddressLeaseType OBJECT-TYPE dhcpv4ServerClientLeaseType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
static(1), static(1),
dynamic(2), dynamic(2),
expired(3), expired(3),
configurationReserved(4), configurationReserved(4),
serverReserved(5) serverReserved(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 30, line 4 skipping to change at page 23, line 50
(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 server, and 'remembered' for subsequent assignment to
the same host. the 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 IPv4 address or a DHCPDECLINE message
has been received for the IP address." has been received for the IPv4 address."
::= { dhcpv4ServerAddressEntry 4 } ::= { dhcpv4ServerClientEntry 4 }
dhcpv4ServerClientTimeRemaining OBJECT-TYPE
dhcpv4ServerAddressTimeRemaining OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds until the lease expires. A value of "The number of seconds until the lease expires. A value of
4294967295 (i.e., 0xFFFFFFFF) should be used for leases that 4294967295 (i.e., 0xFFFFFFFF) SHOULD be used for leases that
have a lease time which is 'infinite' and for BOOTP leases." have a lease time which is 'infinite' and for BOOTP leases."
::= { dhcpv4ServerAddressEntry 5 } ::= { dhcpv4ServerClientEntry 5 }
dhcpv4ServerAddressAllowedProtocol OBJECT-TYPE dhcpv4ServerClientAllowedProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
bootp(2), bootp(2),
dhcp(3), dhcp(3),
bootpOrDhcp(4) bootpOrDhcp(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of protocol that is allowed to be used to serve this "The type of protocol that is allowed to be used to serve this
address. A type of none (1) indicates that the address is not address. A type of none (1) indicates that the address is not
available to be served (e.g., a reserved address). Type (2) available to be served (e.g., a reserved address). Type (2)
are reserved for BOOTP only devices, while type (3) are is reserved for BOOTP only devices, while type (3) is reserved
reserved for DHCP only devices. A type of bootp-or-dhcp (4) for DHCP only devices. A type of bootp-or-dhcp (4) can be
may be offered to any type of client." offered to any type of client."
::= { dhcpv4ServerAddressEntry 6 } ::= { dhcpv4ServerClientEntry 6 }
dhcpv4ServerAddressServedProtocol OBJECT-TYPE dhcpv4ServerClientServedProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
bootp(2), bootp(2),
dhcp(3) dhcp(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of protocol that was used when this address was "The type of protocol that was used when this address was
assigned. This object will have the value of none (1) if the assigned. This object will have the value of none (1) if the
address has not been served." address has not been served."
::= { dhcpv4ServerAddressEntry 7 } ::= { dhcpv4ServerClientEntry 7 }
dhcpv4ServerAddressPhysicalAddress OBJECT-TYPE dhcpv4ServerClientPhysicalAddress OBJECT-TYPE
SYNTAX DhcpPhysicalAddress SYNTAX Dhcpv4PhysicalAddress
MAX-ACCESS read-only MAX-ACCESS read-only
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. This object may from the 'chaddr' field of the BOOTP packet. This object MAY
be empty if the address has not been previously served." be empty if the address has not been previously served."
::= { dhcpv4ServerAddressEntry 8 } ::= { dhcpv4ServerClientEntry 8 }
dhcpv4ServerAddressClientId OBJECT-TYPE dhcpv4ServerClientClientId OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
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
The client-id is the value specified in option 61 (client-id lease. The client-id is the value specified in option 61
option) when the lease was assigned. This object may be empty (client-id option) when the lease was assigned. This object
if the lease has not been previously assigned or if the client- MAY be empty if the lease has not been previously assigned or
id option was not specified when the address was assigned." if the client-id option was not specified when the address was
::= { dhcpv4ServerAddressEntry 9 } assigned."
::= { dhcpv4ServerClientEntry 9 }
dhcpv4ServerAddressHostName OBJECT-TYPE dhcpv4ServerClientHostName OBJECT-TYPE
SYNTAX SnmpAdminString (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
dhcpv4ServerAddressDomainName must be, in practice, less than dhcpv4ServerClientDomainName MUST be, in practice, less than
256 octets." 256 octets."
::= { dhcpv4ServerAddressEntry 10 } ::= { dhcpv4ServerClientEntry 10 }
dhcpv4ServerAddressDomainName OBJECT-TYPE dhcpv4ServerClientDomainName OBJECT-TYPE
SYNTAX SnmpAdminString (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
a Domain Name part is currently limited to 255 octets, less the and a Domain Name part is currently limited to 255 octets,
separator ('.') character. Therefore, the sum of the string less the separator ('.') character. Therefore, the sum of the
lengths for this object and the dhcpv4ServerAddressHostName string lengths for this object and the
must be, in practice, less than 256 octets." dhcpv4ServerClientHostName MUST be, in practice, less than 256
::= { dhcpv4ServerAddressEntry 11 } octets."
-- dhcpv4ServerClientObjects Group ::= { dhcpv4ServerClientEntry 11 }
dhcpv4ServerClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dhcpv4ServerClientEntry
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
dhcpv4ServerAddressTable using the
dhcpv4ServerClientHardwareAddress, and
dhcpv4ServerClientAddress objects. This table is indexed first
by the MAC address of the client and then by the subnet address
on which the client resides. The subnet is included as an
index since a MAC address is only guaranteed to be unique
within a subnet (i.e., a MAC address is not globally unique)."
::= { dhcpv4ServerConfiguration 5 }
dhcpv4ServerClientEntry OBJECT-TYPE
SYNTAX Dhcpv4ServerClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A logical row in the dhcpv4ServerClientTable. An entry in
this table may be a client that requested an address, but was
refused (e.g., not authorized.) Servers MAY track these types
of clients if desired and may choose to remove such client
entries using a server-defined algorithm. As an example, a
server may choose to keep client request that does not map to
an address for a one hour time period before removing that
entry from this table."
INDEX {
dhcpv4ServerClientHardwareAddress,
dhcpv4ServerClientAddress
}
::= { dhcpv4ServerClientTable 1 }
Dhcpv4ServerClientEntry ::= SEQUENCE {
dhcpv4ServerClientHardwareAddress DhcpPhysicalAddress,
dhcpv4ServerClientAddress InetAddressIPv4,
dhcpv4ServerClientSubnetMask InetAddressPrefixLength,
dhcpv4ServerClientLastRequestTime DhcpTimeInterval,
dhcpv4ServerClientLastRequestType INTEGER,
dhcpv4ServerClientLastResponseType INTEGER
}
dhcpv4ServerClientHardwareAddress OBJECT-TYPE
SYNTAX DhcpPhysicalAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The hardware type and hardware address of the client that has
been assigned this lease."
::= { dhcpv4ServerClientEntry 1 }
dhcpv4ServerClientAddress OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP address of the entry, used to index into the
dhcpv4ServerAddressTable. May be 0.0.0.0 if an address is not
associated with this client."
::= { dhcpv4ServerClientEntry 2 }
dhcpv4ServerClientSubnetMask OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The subnet mask (DHCP option 1) applied to
dhcpv4ServerClientAddress."
::= { dhcpv4ServerClientEntry 3 }
dhcpv4ServerClientLastRequestTime OBJECT-TYPE
SYNTAX DhcpTimeInterval
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The timestamp of the last request received, to millisecond
precision if available on the server."
::= { dhcpv4ServerClientEntry 4 }
dhcpv4ServerClientLastRequestType OBJECT-TYPE
SYNTAX INTEGER {
bootprequest(0),
dhcpdiscover(1),
dhcprequest(3),
dhcpdecline(4),
dhcprelease(7),
dhcpinform(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the last request message received for this 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-
04.txt."
::= { dhcpv4ServerClientEntry 5 }
dhcpv4ServerClientLastResponseType OBJECT-TYPE
SYNTAX INTEGER {
bootpreply(1),
dhcpoffer(2),
dhcpack(5),
dhcpnak(6),
dhcpforcerenew(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the last response message sent to this 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-
04.txt"
::= { dhcpv4ServerClientEntry 6 }
-- dhcpv4ServerNotifyObjects Group -- dhcpv4ServerNotifyObjects Group
dhcpv4ServerNotifyDuplicateIpAddr OBJECT-TYPE dhcpv4ServerNotifyDuplicateIpAddr OBJECT-TYPE
SYNTAX InetAddressIPv4 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 IPv4 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, or by a client issuing a offering an IPv4 address lease, or by a client issuing a
gratuitous ARP message and reported through a DHCPDECLINE gratuitous ARP message and reported through a DHCPDECLINE
message." message."
::= { dhcpv4ServerNotifyObjects 1 } ::= { dhcpv4ServerNotifyObjects 1 }
dhcpv4ServerNotifyDuplicateMac OBJECT-TYPE dhcpv4ServerNotifyDuplicateMac OBJECT-TYPE
SYNTAX DhcpPhysicalAddress SYNTAX Dhcpv4PhysicalAddress
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 IPv4
to be detected, if captured by the server, else 00-00-00-00-00- address to be detected, if captured by the server, else 00-00-
00." 00-00-00-00."
::= { dhcpv4ServerNotifyObjects 2 } ::= { dhcpv4ServerNotifyObjects 2 }
dhcpv4ServerNotifyClientOrServerDetected OBJECT-TYPE dhcpv4ServerNotifyClientOrServerDetected OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
client(1), client(1),
server(2) server(2)
} }
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Duplicate IP addresses may be detected either by a server, "Duplicate IPv4 addresses can be detected either by a server,
using an ICMP ECHO message, or by a client using ARP. This using an ICMP ECHO message, or by a client using ARP. This
object is set by the server to (1) if the client used object is set by the server to (1) if the client used
DHCPDECLINE to mark the offered address as in-use, or to (2) if DHCPDECLINE to mark the offered address as in-use, or to (2)
the server discovered the address in use by some client before if the server discovered the address in use by some client
offering it." before offering it."
::= { dhcpv4ServerNotifyObjects 3 } ::= { dhcpv4ServerNotifyObjects 3 }
dhcpv4ServerNotifyServerStart OBJECT-TYPE dhcpv4ServerNotifyServerStart OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The date and time when the server began operation." "The date and time when the server began operation."
::= { dhcpv4ServerNotifyObjects 4 } ::= { dhcpv4ServerNotifyObjects 4 }
skipping to change at page 35, line 50 skipping to change at page 27, line 25
dhcpv4ServerNotifications OBJECT IDENTIFIER dhcpv4ServerNotifications OBJECT IDENTIFIER
::= { dhcpv4ServerNotificationPrefix 0 } ::= { dhcpv4ServerNotificationPrefix 0 }
dhcpv4ServerFreeAddressLow NOTIFICATION-TYPE dhcpv4ServerFreeAddressLow NOTIFICATION-TYPE
OBJECTS { OBJECTS {
dhcpv4ServerSharedNetFreeAddrLowThreshold, dhcpv4ServerSharedNetFreeAddrLowThreshold,
dhcpv4ServerSharedNetFreeAddresses dhcpv4ServerSharedNetFreeAddresses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the number of available IP "This notification signifies that the number of available IPv4
addresses for a particular shared network has fallen below the addresses for a particular shared network has fallen below the
value of dhcpv4ServerSharedNetFreeAddrLowThreshold for that value of dhcpv4ServerSharedNetFreeAddrLowThreshold for that
shared network." shared network."
::= { dhcpv4ServerNotifications 1 } ::= { dhcpv4ServerNotifications 1 }
dhcpv4ServerFreeAddressHigh NOTIFICATION-TYPE dhcpv4ServerFreeAddressHigh NOTIFICATION-TYPE
OBJECTS { OBJECTS {
dhcpv4ServerSharedNetFreeAddrHighThreshold, dhcpv4ServerSharedNetFreeAddrHighThreshold,
dhcpv4ServerSharedNetFreeAddresses dhcpv4ServerSharedNetFreeAddresses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the number of available IP "This notification signifies that the number of available IPv4
addresses for a particular shared network has risen above the addresses for a particular shared network has risen above the
value of dhcpv4ServerSharedNetFreeAddrHighThreshold for that value of dhcpv4ServerSharedNetFreeAddrHighThreshold for that
shared network." shared network."
::= { dhcpv4ServerNotifications 2 } ::= { dhcpv4ServerNotifications 2 }
dhcpv4ServerStartTime NOTIFICATION-TYPE dhcpv4ServerStartTime NOTIFICATION-TYPE
OBJECTS { dhcpv4ServerNotifyServerStart } OBJECTS { dhcpv4ServerNotifyServerStart }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the server of the specified "This notification signifies that the server of the specified
skipping to change at page 36, line 47 skipping to change at page 28, line 21
::= { dhcpv4ServerNotifications 4 } ::= { dhcpv4ServerNotifications 4 }
dhcpv4ServerDuplicateAddress NOTIFICATION-TYPE dhcpv4ServerDuplicateAddress NOTIFICATION-TYPE
OBJECTS { OBJECTS {
dhcpv4ServerNotifyDuplicateIpAddr, dhcpv4ServerNotifyDuplicateIpAddr,
dhcpv4ServerNotifyDuplicateMac, dhcpv4ServerNotifyDuplicateMac,
dhcpv4ServerNotifyClientOrServerDetected dhcpv4ServerNotifyClientOrServerDetected
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that a duplicate IP address has "This notification signifies that a duplicate IPv4 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
address was in use. In either case, the DHCP server marks the address was in use. In either case, the DHCP server marks the
IP address as unavailable for leasing to clients. The IPv4 address as unavailable for leasing to clients. The
dhcpv4ServerNotifyClientOrServerDetected object indicates dhcpv4ServerNotifyClientOrServerDetected object indicates
whether the client or server detected this condition." whether the client or server detected this condition."
::= { dhcpv4ServerNotifications 5 } ::= { dhcpv4ServerNotifications 5 }
-- Conformance -- Conformance
dhcpv4ServerConformance OBJECT-IDENTITY dhcpv4ServerConformance OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP server conformance objects are all defined in this "DHCP server conformance objects are all defined in this
skipping to change at page 37, line 30 skipping to change at page 29, line 7
dhcpv4ServerGroups OBJECT IDENTIFIER dhcpv4ServerGroups OBJECT IDENTIFIER
::= { dhcpv4ServerConformance 2 } ::= { dhcpv4ServerConformance 2 }
-- Compliance groups -- Compliance groups
dhcpv4ServerCompliance MODULE-COMPLIANCE dhcpv4ServerCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group describes the requirements for conformance to the "This group describes the requirements for conformance to the
DHCP Server MIB. A DHCPv4 server implementation is only DHCP Server MIB. A DHCPv4 server implementation is only
required to support IPv4 addresses. In particular, this REQUIRED to support IPv4 addresses. In particular, this
comment applies to the following objects with MAX-ACCESS not- comment applies to the following objects with MAX-ACCESS not-
accessible: accessible:
dhcpv4ServerSubnet dhcpv4ServerSubnet
dhcpv4ServerRangeStart dhcpv4ServerRangeStart
dhcpv4ServerRangeEnd dhcpv4ServerRangeEnd
dhcpv4ServerAddress dhcpv4ServerClient."
dhcpv4ServerClientAddress."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
dhcpv4ServerSystemObjects, dhcpv4ServerSystemObjects,
bootpCounterObjects, bootpCounterObjects,
dhcpv4RecvdPacketCounterObjects, dhcpv4CounterObjects,
dhcpv4SentPacketCounterObjects,
dhcpv4ErrorPacketCounterObjects,
dhcpv4ServerSharedNetObjects, dhcpv4ServerSharedNetObjects,
dhcpv4ServerSubnetObjects, dhcpv4ServerSubnetObjects,
dhcpv4ServerRangeObjects, dhcpv4ServerRangeObjects,
dhcpv4ServerAddressObjects,
dhcpv4ServerClientObjects, dhcpv4ServerClientObjects,
dhcpv4ServerNotifyObjectsGroup, dhcpv4ServerNotifyObjectsGroup,
dhcpv4ServerNotificationsGroup dhcpv4ServerNotificationsGroup
} }
GROUP bootpOptionalStatisticObjects
DESCRIPTION
"Mandatory only for servers that capture the optional BOOTP
statistics."
GROUP dhcpv4OptionalStatisticObjects
DESCRIPTION
"Mandatory only for servers that capture the optional DHCPv4
statistics."
::= { dhcpv4ServerCompliances 1 } ::= { dhcpv4ServerCompliances 1 }
-- Object groups -- Object groups
dhcpv4ServerSystemObjects OBJECT-GROUP dhcpv4ServerSystemObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerSystemDescr, dhcpv4ServerSystemDescr,
dhcpv4ServerSystemObjectID dhcpv4ServerSystemObjectID
} }
STATUS current STATUS current
skipping to change at page 38, line 42 skipping to change at page 30, line 4
bootpCountRequests, bootpCountRequests,
bootpCountInvalids, bootpCountInvalids,
bootpCountReplies, bootpCountReplies,
bootpCountDroppedUnknownClients, bootpCountDroppedUnknownClients,
bootpCountDroppedNotServingSubnet bootpCountDroppedNotServingSubnet
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the bootpBounterObjects group." "Objects belonging to the bootpBounterObjects group."
::= { dhcpv4ServerGroups 2 } ::= { dhcpv4ServerGroups 2 }
dhcpv4CounterObjects OBJECT-GROUP
dhcpv4RecvdPacketCounterObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4CountDiscovers, dhcpv4CountDiscovers,
dhcpv4CountOffers,
dhcpv4CountRequests, dhcpv4CountRequests,
dhcpv4CountReleases,
dhcpv4CountDeclines, dhcpv4CountDeclines,
dhcpv4CountInforms
}
STATUS current
DESCRIPTION
"Objects belonging to the dhcpv4RecvdPacketCounterObjects
group."
::= { dhcpv4ServerGroups 3 }
dhcpv4SentPacketCounterObjects OBJECT-GROUP
OBJECTS {
dhcpv4CountOffers,
dhcpv4CountAcks, dhcpv4CountAcks,
dhcpv4CountNaks, dhcpv4CountNaks,
dhcpv4CountForcedRenews dhcpv4CountReleases,
} dhcpv4CountInforms,
STATUS current dhcpv4CountForcedRenews,
DESCRIPTION
"Objects belonging to the dhcpv4SentPacketCounterObjects
group."
::= { dhcpv4ServerGroups 4 }
dhcpv4ErrorPacketCounterObjects OBJECT-GROUP
OBJECTS {
dhcpv4CountInvalids, dhcpv4CountInvalids,
dhcpv4CountDroppedUnknownClient, dhcpv4CountDroppedUnknownClient,
dhcpv4CountDroppedNotServingSubnet dhcpv4CountDroppedNotServingSubnet
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ErrorPacketCounterObjects "Objects belonging to the dhcpv4CounterObjects group."
group." ::= { dhcpv4ServerGroups 3 }
::= { dhcpv4ServerGroups 5 }
bootpOptionalStatisticObjects OBJECT-GROUP
OBJECTS {
bootpStatMinArrivalInterval,
bootpStatMaxArrivalInterval,
bootpStatLastArrivalTime,
bootpStatSumSquaresArrivalTime,
bootpStatMinResponseTime,
bootpStatMaxResponseTime,
bootpStatSumResponseTime,
bootpStatSumSquaresResponseTime
}
STATUS current
DESCRIPTION
"Objects belonging to the bootpOptionalStatisticObjects group."
::= { dhcpv4ServerGroups 6 }
dhcpv4OptionalStatisticObjects OBJECT-GROUP
OBJECTS {
dhcpv4StatMinArrivalInterval,
dhcpv4StatMaxArrivalInterval,
dhcpv4StatLastArrivalTime,
dhcpv4StatSumSquaresArrivalTime,
dhcpv4StatMinResponseTime,
dhcpv4StatMaxResponseTime,
dhcpv4StatSumResponseTime,
dhcpv4StatSumSquaresResponseTime
}
STATUS current
DESCRIPTION
"Objects belonging to the dhcpv4OptionalStatisticObjects
group."
::= { dhcpv4ServerGroups 7 }
dhcpv4ServerSharedNetObjects OBJECT-GROUP dhcpv4ServerSharedNetObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerSharedNetFreeAddrLowThreshold, dhcpv4ServerSharedNetFreeAddrLowThreshold,
dhcpv4ServerSharedNetFreeAddrHighThreshold, dhcpv4ServerSharedNetFreeAddrHighThreshold,
dhcpv4ServerSharedNetFreeAddresses, dhcpv4ServerSharedNetFreeAddresses,
dhcpv4ServerSharedNetReservedAddresses, dhcpv4ServerSharedNetReservedAddresses,
dhcpv4ServerSharedNetTotalAddresses dhcpv4ServerSharedNetTotalAddresses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ServerSharedNetObjects group." "Objects belonging to the dhcpv4ServerSharedNetObjects group."
::= { dhcpv4ServerGroups 8 } ::= { dhcpv4ServerGroups 4 }
dhcpv4ServerSubnetObjects OBJECT-GROUP dhcpv4ServerSubnetObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerSubnetMask, dhcpv4ServerSubnetMask,
dhcpv4ServerSubnetSharedNetworkName, dhcpv4ServerSubnetSharedNetworkName,
dhcpv4ServerSubnetFreeAddrLowThreshold, dhcpv4ServerSubnetFreeAddrLowThreshold,
dhcpv4ServerSubnetFreeAddrHighThreshold, dhcpv4ServerSubnetFreeAddrHighThreshold,
dhcpv4ServerSubnetFreeAddresses dhcpv4ServerSubnetFreeAddresses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ServerSubnetObjects group." "Objects belonging to the dhcpv4ServerSubnetObjects group."
::= { dhcpv4ServerGroups 9 } ::= { dhcpv4ServerGroups 5 }
dhcpv4ServerRangeObjects OBJECT-GROUP dhcpv4ServerRangeObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerRangeSubnetMask, dhcpv4ServerRangeSubnetMask,
dhcpv4ServerRangeInUse, dhcpv4ServerRangeInUse,
dhcpv4ServerRangeOutstandingOffers dhcpv4ServerRangeOutstandingOffers
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ServerRangeObjects group." "Objects belonging to the dhcpv4ServerRangeObjects group."
::= { dhcpv4ServerGroups 10 } ::= { dhcpv4ServerGroups 6 }
dhcpv4ServerAddressObjects OBJECT-GROUP
OBJECTS {
dhcpv4ServerAddressSubnetMask,
dhcpv4ServerAddressRange,
dhcpv4ServerAddressLeaseType,
dhcpv4ServerAddressTimeRemaining,
dhcpv4ServerAddressAllowedProtocol,
dhcpv4ServerAddressServedProtocol,
dhcpv4ServerAddressPhysicalAddress,
dhcpv4ServerAddressClientId,
dhcpv4ServerAddressHostName,
dhcpv4ServerAddressDomainName
}
STATUS current
DESCRIPTION
"Objects belonging to the dhcpv4ServerAddressObjects group."
::= { dhcpv4ServerGroups 11 }
dhcpv4ServerClientObjects OBJECT-GROUP dhcpv4ServerClientObjects OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerClientSubnetMask, dhcpv4ServerClientSubnetMask,
dhcpv4ServerClientLastRequestTime, dhcpv4ServerClientRange,
dhcpv4ServerClientLastRequestType, dhcpv4ServerClientLeaseType,
dhcpv4ServerClientLastResponseType dhcpv4ServerClientTimeRemaining,
dhcpv4ServerClientAllowedProtocol,
dhcpv4ServerClientServedProtocol,
dhcpv4ServerClientPhysicalAddress,
dhcpv4ServerClientClientId,
dhcpv4ServerClientHostName,
dhcpv4ServerClientDomainName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ServerClientObjects group." "Objects belonging to the dhcpv4ServerClientObjects group."
::= { dhcpv4ServerGroups 12 } ::= { dhcpv4ServerGroups 7 }
dhcpv4ServerNotifyObjectsGroup OBJECT-GROUP dhcpv4ServerNotifyObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpv4ServerNotifyDuplicateIpAddr, dhcpv4ServerNotifyDuplicateIpAddr,
dhcpv4ServerNotifyDuplicateMac, dhcpv4ServerNotifyDuplicateMac,
dhcpv4ServerNotifyClientOrServerDetected, dhcpv4ServerNotifyClientOrServerDetected,
dhcpv4ServerNotifyServerStart, dhcpv4ServerNotifyServerStart,
dhcpv4ServerNotifyServerStop dhcpv4ServerNotifyServerStop
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpv4ServerNotifyObjects group." "Objects belonging to the dhcpv4ServerNotifyObjects group."
::= { dhcpv4ServerGroups 13 } ::= { dhcpv4ServerGroups 8 }
dhcpv4ServerNotificationsGroup NOTIFICATION-GROUP dhcpv4ServerNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dhcpv4ServerFreeAddressLow, dhcpv4ServerFreeAddressLow,
dhcpv4ServerFreeAddressHigh, dhcpv4ServerFreeAddressHigh,
dhcpv4ServerStartTime, dhcpv4ServerStartTime,
dhcpv4ServerStopTime, dhcpv4ServerStopTime,
dhcpv4ServerDuplicateAddress dhcpv4ServerDuplicateAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications belonging to the dhcpv4ServerNotifications "Notifications belonging to the dhcpv4ServerNotifications
group." group."
::= { dhcpv4ServerGroups 14 } ::= { dhcpv4ServerGroups 9 }
END END
5. 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.
Copies of claims of rights made available for publication and any Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use
such proprietary rights by implementers or users of this of 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.
6. Acknowledgements 6. Acknowledgements
This document is the result of work undertaken the by DHCP working This document is the result of work undertaken by the 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 initial development of this great deal of useful feedback during the initial development of this
MIB. MIB, and to Rich Woundy for his excellent suggestions that helped
bring the work to closure.
Thanks to Nathan Lane, Kim Kinnear, Yannick Koehler, Rick Geesen, Jin
Tao, James Brister, Alan Hackert, Patrick Cosmo, Taeko Saito, and
Devrapratap Baul for their review, comments, and contributions.
Special thanks to Rich Woundy for his excellent suggestions that
contributed to the --08 draft: any lingering errors are to be blamed
solely on the editors.
7. IANA Considerations 7. IANA Considerations
IANA must fill in the value of the RFC number when it is assigned to IANA MUST fill in the value of the RFC number when it is assigned to
this memo. It is represented as "xxxx" in the DESCRIPTION section of this memo. It is represented as "xxxx" in the DESCRIPTION section
MODULE-IDENTITY. of MODULE-IDENTITY.
One specific value for a MIB object requires completion before this One specific value for a MIB object requires completion before this
memo can advance to RFC status. It is: memo can advance to RFC status. It is:
o OID value for "dhcp" see MODULE-IDENTITY o OID value for "dhcp" -- see MODULE-IDENTITY
8. 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
for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without
protection can have a negative effect on network operations. proper protection can have a negative effect on network operations.
Therefore, if this MIB is implemented correctly, there is no risk Therefore, if this MIB is implemented correctly, there is no risk
that an intruder can alter or create any management objects of this that an intruder can alter or create any management objects of this
MIB via direct SNMP SET operations. MIB via direct SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with
MAX-ACCESS other than not-accessible) may be considered sensitive or a MAX-ACCESS other than not-accessible) may be considered sensitive
vulnerable in some network environments. It is thus important to or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o dhcpv4ServerRangeTable o dhcpv4ServerRangeTable
o dhcpv4ServerAddressTable o dhcpv4ServerClientTable
These two objects, in conjunction, provide an observer with a current These two objects, in conjunction, provide an observer with a
view of the available and assigned addresses allocated by this current view of the available and assigned addresses allocated by
server. Such knowledge can be used to manually configure a host this server. Such knowledge can be used to manually configure a
computer with a valid IP address for the network managed by the DHCP host computer with a valid IPv4 address for the network managed by
server. This could be part of either a Theft of Service scheme or a the DHCP server. This could be part of either a Theft of Service
Denial of Service attack wherein rogue (pseudo-)hosts simply claim scheme or a Denial of Service attack wherein rogue (pseudo-)hosts
and defend IP addresses either to subvert accounting for their use or simply claim and defend IPv4 addresses either to subvert accounting
to disrupt the network for legitimate hosts. for their use or to disrupt the network for legitimate hosts.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these objects when sending possibly to even encrypt the values of these objects when sending
them over the network via SNMP. Not all versions of SNMP provide them over the network via SNMP. Not all versions of SNMP provide
features for such a secure environment. features for such a secure environment.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the
in this MIB. objects in this MIB.
It is recommended that the implementers consider the security It is RECOMMENDED that the implementers consider the security
features as provided by the SNMPv3 framework (see [RFC3410], section features as provided by the SNMPv3 framework (see [RFC3410], section
8), including full support for the SNMPv3 cryptographic mechanisms 8), including full support for the SNMPv3 cryptographic mechanisms
(for authentication and privacy). (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (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
server resources processing SNMP messages. The authors know of no and server resources processing SNMP messages. The authors know of
way to wholly prevent such attacks, but have attempted to construct no way to wholly prevent such attacks, but have attempted to
relatively simple tables to minimize the work required to respond to construct relatively simple tables to minimize the work required to
messages. respond to messages.
9. References 9. References
One normative reference is currently an Internet-Draft, nearly ready One normative reference is currently an Internet-Draft, nearly ready
for Working Group Last Call. This reference MUST be updated when the for Working Group Last Call. This reference MUST be updated when
draft advances to RFC status. the draft advances to RFC status.
9.1. Normative References 9.1. Normative References
[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.
[RFC2578] Case, J., McCloghrie, K., Perkins, D., Rose, M., [RFC2578] Case, J., McCloghrie, K., Perkins, D., Rose, M.,
Schoenwaelder, J., and S. Waldbusser, "Structure of Management Schoenwaelder, J., and S. Waldbusser, "Structure of Management
Information for Version 2 of the Simple Network Management Protocol Information for Version 2 of the Simple Network Management
(SNMPv2)," RFC 2578, April 1999. Protocol (SNMPv2)," RFC 2578, April 1999.
[RFC2579] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and [RFC2579] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and
S. Waldbusser, "Textual Conventions for Version 2 of the Simple S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)," RFC 2579, April 1999. Network Management Protocol (SNMPv2)," RFC 2579, April 1999.
[RFC2580] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and [RFC2580] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and
S. Waldbusser, "Conformance Statements for Version 2 of the Simple S. Waldbusser, "Conformance Statements for Version 2 of the Simple
Network Management Protocol (SNMPv2)," RFC 2580, April 1999. Network Management Protocol (SNMPv2)," RFC 2580, April 1999.
[RFC3203], Yves T'Joens and Christian Hublet, Peter De Schrijver, [RFC3203], Yves T'Joens and Christian Hublet, Peter De Schrijver,
"The DHCP Reconfigure Extension," July 2001 "The DHCP Reconfigure Extension," July 2001
<draft-ietf-dhc-leasequery-04.txt> Rich Woundy and Kim Kinnear, "DHCP
Lease Query," November 2003.
9.2. Informative References 9.2. Informative References
[DEN] Directory Enabled Networks Working Group,
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.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-Standard "Introduction and Applicability Statements for Internet-Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
10. Editors' Addresses 10. Editors' Addresses
Richard Barr Hibbs Richard Barr Hibbs
skipping to change at page 46, line 45 skipping to change at page 36, line 31
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 11. Full Copyright Statement
Copyright (C), 2003, The Internet Society. All Rights Reserved. Copyright (C), 2004, The Internet Society. 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
included on all such copies and derivative works. However, this are 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
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
 End of changes. 

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