draft-ietf-rserpool-mib-00.txt   draft-ietf-rserpool-mib-01.txt 
Network Working Group J. Mulik Network Working Group T. Dreibholz
Internet-Draft P. Conrad Internet-Draft University of Duisburg-Essen
Expires: November 6, 2002 K. Pinzhoffer Expires: December 12, 2005 J. Mulik
Temple University Temple University
May 8, 2002 P. Conrad
University of Delaware
K. Pinzhoffer
Temple University
Jun 10, 2005
Reliable Server Pooling : Management Information Base using SMIv2 Reliable Server Pooling : Management Information Base using SMIv2
draft-ietf-rserpool-mib-00.txt draft-ietf-rserpool-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, each author represents that any
all provisions of Section 10 of RFC2026. applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at
www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 6, 2002. This Internet-Draft will expire on December 12, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
RserPool [20] is a framework to provide reliable server pooling. RSerPool [20] is a framework to provide reliable server pooling.
This document defines a SMIv2 compliant Management Information Base This document defines a SMIv2 compliant Management Information Base
(MIB) providing access to managed object in an RSerPool (MIB) providing access to managed objects in an RSerPool
implementation. implementation.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The SNMP Management Framework . . . . . . . . . . . . . . . . 4
3. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 6
3.1 Access to managed objects on an ENRP nameserver . . . . . . . 7
3.2 Access to managed objects on Pool Elements . . . . . . . . . . 8
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This memo defines a Management Information Base (MIB) module which This memo defines a Management Information Base (MIB) module which
describes managed objects for RserPool implementations. The MIB describes managed objects for RserPool implementations. The MIB
defined in this memo is described using the Structure of Management defined in this memo is described using the Structure of Management
Information version 2, as defined in RFC1902 [6], RFC1903 [7], and Information version 2, as defined in RFC1902 [6], RFC1903 [7], and
RFC1904 [8]. RFC1904 [8].
2. The SNMP Management Framework 2. The SNMP Management Framework
skipping to change at page 6, line 11 skipping to change at page 6, line 11
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3. Structure of the MIB 3. Structure of the MIB
The following diagram illustrates the structure of the MIB. The following diagram illustrates the structure of the MIB.
Structure of MIB Structure of MIB
rserpoolMIB +--rserpoolMIB(12345)
| |
+----------------+-------------------+ +--enrpServers(1)
| | | |
nameserver poolElements | +-- -R-- Counter enrpServerCount(1)
| | | |
|--poolHandleCount |--poolHandleCount | +--enrpServerTable(2)
| | |
| | +--enrpServerEntry(1)
| | | Index: enrpServerIndex
| | |
| | +-- ---- INTEGER enrpServerIndex(1)
| | | Textual Convention: ENRPServerIndex
| | | Range: 1..2147483647
| | +-- -R-- INTEGER enrpServerIdentifier(2)
| | | Textual Convention: ENRPServerIdentifier
| | | Range: 1..2147483647
| | +-- -R-- INTEGER enrpServerOperationScope(3)
| | | Textual Convention: PoolElementIdentifier
| | | Range: 1..2147483647
| | +-- -R-- TimeTicks enrpServerUptime(4)
| | +-- -R-- String enrpServerDescription(5)
| | | Textual Convention: ENRPServerDescription
| | | Size: 0..255
| | +-- -R-- INTEGER enrpPort(6)
| | | Range: 1..65535
| | +-- -R-- Counter enrpAddrCount(7)
| | +-- -R-- Counter peerCount(8)
| | +-- -R-- Counter poolCount(9)
| | +-- -R-- INTEGER enrpServerASAPAnnouncePort(10)
| | | Range: 1..65535
| | +-- -R-- String enrpServerASAPAnnounceAddr(11)
| | | Textual Convention: InetAddress
| | | Size: 0..255
| | +-- -R-- INTEGER enrpServerENRPAnnouncePort(12)
| | | Range: 1..65535
| | +-- -R-- String enrpServerENRPAnnounceAddr(13)
| | Textual Convention: InetAddress
| | Size: 0..255
| | | |
|--poolHandleTable |--poolHandleTable | +--poolTable(3)
| | | | | | |
| +--poolHandleEntry | +--poolHandleEntry | | +--poolEntry(1)
| | | | | | | Index: enrpServerIndex, poolIndex
| |--poolHandleIndex | |--poolHandleIndex | | |
| | | | | | +-- ---- INTEGER poolIndex(1)
| |--poolElementCount | |--poolElementCount | | | Textual Convention: PoolIndex
| | | | | | | Range: 1..2147483647
| +--poolHandle | +--poolHandle | | +-- -R-- Counter poolElementCount(2)
| | +-- -R-- String poolHandle(3)
| | Textual Convention: PoolHandle
| | | |
| +--poolElementTable(4)
| | |
| | +--poolElementEntry(1)
| | | Index: enrpServerIndex, poolIndex, poolElementIndex
| | |
| | +-- -R-- INTEGER poolElementIndex(1)
| | | Textual Convention: PoolElementIndex
| | | Range: 1..2147483647
| | +-- -R-- INTEGER asapTransportPort(2)
| | | Range: 1..65535
| | +-- -R-- Counter asapTransportAddrCount(3)
| | +-- -R-- INTEGER userTransportProtocol(4)
| | | Range: 0..255
| | +-- -R-- INTEGER userTransportPort(5)
| | | Range: 1..65535
| | +-- -R-- EnumVal userTransportUse(6)
| | | Textual Convention: TransportUse
| | | Values: dataOnly(0), dataPlusControl(1)
| | +-- -R-- Counter userTransportAddrCount(7)
| | +-- -R-- INTEGER policyType(8)
| | | Textual Convention: PolicyType
| | | Range: 0..255
| | +-- -R-- String policyDescr(9)
| | | Textual Convention: PolicyDescription
| | | Size: 0..255
| | +-- -R-- INTEGER policyWeight(10)
| | | Textual Convention: PolicyWeight
| | | Range: 0..16777215
| | +-- -R-- INTEGER policyLoad(11)
| | | Textual Convention: PolicyLoad
| | | Range: 0..16777215
| | +-- -R-- INTEGER policyLoadDegradation(12)
| | | Textual Convention: PolicyLoad
| | | Range: 0..16777215
| | +-- -R-- TimeTicks registrationLife(13)
| | +-- -R-- INTEGER homeENRPServer(14)
| | Textual Convention: ENRPServerIdentifier
| | Range: 1..2147483647
| | | |
|--poolElementTable |--poolElementTable | +--asapTransportAddrListTable(5)
| | | | | | |
| +--poolElementEntry | +--poolElementEntry | | +--asapTransportAddrListTableEntry(1)
| | | | | | | Index: enrpServerIndex, poolIndex, poolElementIndex,
| |--poolElementIndex | |--poolElementIndex | | | asapTransportAddrListTableIndex
| | | | | | |
| |--poolElementIPAddrCount | |--poolElementIPAddrCount | | +-- ---- Unsigned asapTransportAddrListTableIndex(1)
| | | | | | | Range: 1..2147483647
| |--poolElementHostname | |--poolElementHostname | | +-- -R-- INTEGER networkLayerProtocol(2)
| | | | | | | Range: 0..255
| |--policyType | |--policyType | | +-- -R-- String networkLayerAddress(3)
| | | | | | Textual Convention: InetAddress
| |--policyValue | |--policyValue | | Size: 0..255
| | | |
| |--noOfRequests | |--noOfRequests
| | | |
| |--noOfRequestsInQueue | |--noOfRequestsInQueue
| | | |
| |--SCTPPort | |--SCTPPort
| | | |
| +--uptimePE | +--uptimePE
| | | |
|--addrListTable +--addrListTable | +--userTransportAddrListTable(6)
| | | | | |
| +--addrListTableEntry +--addrListTableEntry | | +--userTransportAddrListTableEntry(1)
| | | Index: enrpServerIndex, poolIndex, poolElementIndex,
| | | userTransportAddrListTableIndex
| | | | | |
| |--addrListTableIndex |--addrListTableIndex | | +-- ---- Unsigned userTransportAddrListTableIndex(1)
| | | Range: 1..2147483647
| | +-- -R-- INTEGER networkLayerProtocol(2)
| | | Range: 0..255
| | +-- -R-- String networkLayerAddress(3)
| | Textual Convention: InetAddress
| | Size: 0..255
| |
| +--enrpAddrListTable(7)
| | | | | |
| +--hostIPAddress +--hostIPAddress | | +--enrpAddrListTableEntry(1)
| | | Index: enrpIndex, enrpAddrListTableIndex
| | |
| | +-- ---- Unsigned enrpAddrListTableIndex(1)
| | | Range: 1..2147483647
| | +-- -R-- INTEGER networkLayerProtocol(2)
| | | Range: 0..255
| | +-- -R-- String networkLayerAddress(3)
| | Textual Convention: InetAddress
| | Size: 0..255
| |
| +--peerTable(8)
| | |
| | +--peerEntry(1)
| | | Index: peerIndex
| | |
| | +-- ---- Unsigned peerIndex(1)
| | | Range: 1..2147483647
| | +-- -R-- Unsigned peerIdentifier(2)
| | +-- -R-- INTEGER peerPort(3)
| | | Range: 1..65535
| | +-- -R-- TimeTicks peerLastHeard(4)
| | +-- -R-- TimeTicks peerAddrCount(5)
| |
| +--peerAddrListTable(9)
| |
| +--peerAddrListTableEntry(1)
| | Index: peerIndex, peerAddrListTableIndex
| |
| +-- ---- Unsigned peerAddrListTableIndex(1)
| | Range: 1..2147483647
| +-- -R-- INTEGER networkLayerProtocol(2)
| | Range: 0..255
| +-- -R-- String networkLayerAddress(3)
| Textual Convention: InetAddress
| Size: 0..255
| |
+--uptimeNS +--poolElements(2)
As the figure shows, the MIB is in two main branches. The first ...
branch, "nameserver" is used to access managed objects at an ENRP ...
server. The second branch, "poolElements" is used to access managed ...
objects in the set of Pool Elements that are running on a given host.
In fact, the structure of the two branches is identical, except for +--poolUsers(3)
one detail: the nameserver branch has an extra element called
uptimeNS, which indicates the uptime of the ENRP server process ...
itself. We now proceed with a separate description of the two ...
branches. Because the two branches are so similar, we describe only ...
As the figure shows, the MIB consists of three main branches:
"enrpServers", "poolElements" and "poolUsers". The first branch,
"enrpServers" is used to access managed objects in the set of ENRP
servers running on a given host. While it is assumed that it does
not make much sense to run multiple ENRP servers for the same
operation scope on one host, running multiple ENRP servers for
different operation scopes is very likely when the ENRP server
processes run on routers. Therefore, the MIB has to be able to
manage multiple ENRP servers on the same host. "poolElements" is used
to access managed objects in the set of Pool Elements that are
running on a given host and the third branch, "poolUsers" is used to
access managed objects in the set of Pool Users that are running on a
given host. In fact, the structure of the three branches is very
similar. Because the two branches are so similar, we describe only
the first branch in detail, and provide a summary description of the the first branch in detail, and provide a summary description of the
second branch. second and third branch. We now proceed with a description of the
branches.
3.1 Access to managed objects on an ENRP nameserver 3.1 Access to managed objects on ENRP servers
The first branch describes managed objects at an ENRP nameserver. The first branch describes managed objects at a set of ENRP servers.
Any given ENRP server will, at a certain moment in time, have Any given ENRP server of this set will, at a certain moment in time,
registration information for a set of active poolHandles. Each of have registration information for a set of active pools. Each of
these poolHandles in turn may have a list of poolElements that are these pools in turn may have a list of pool elements that are
registered under that poolHandle. To allow this information to be registered under that pool. To allow this information to be
retrieved via SNMP, the nameserver branch of the RSerPool MIB uses retrieved via SNMP, the ERNP server branch of the RSerPool MIB uses
the table-in-table technique described in [21]. Specifically, the the table-in-table technique described in [21]. Specifically, the
nameserver branch creates three levels of nesting, as indicated in ENRP servers branch creates four levels of nesting, as indicated in
the following diagram: the following diagram:
Nesting of Nameserver Branch Nesting of Nameserver Branch
Nesting Structure: Nesting Structure:
Level 1: poolHandleTable Level 1: enrpServerTable
Level 2: poolElementTable
Level 3: addrListTable
The nameserver branch contains five elements. The first element is Level 2: poolTable
the poolHandleCount, which indicates the total number of server pools Level 3: poolElementTable
currently registered with this name server. It is mainly used as a Level 4: asapTransportAddrListTable
means of indexing into the poolHandleTable, which is the second userTransportAddrListTable
element on this branch. The poolHandleTable contains a single entry
for each poolHandle that is currently registered. Each "conceptual Level 2: enrpAddrListTable
row" in the poolHandleTable consists of a poolHandleEntry, with three
elements: a poolHandleIndex, a poolElementCount, and an OCTET STRING Level 2: peerTable
representation of the pool handle itself. The poolElementCount is Level 3: peerAddrListTable
the number of pool elements registered with this pool handle. The
poolHandleIndex is simply an integer that is used to index into the The ENRP servers branch contains a table of the host's ENRP server
poolHandleTable and the poolElementTable. The value of this integer instances. Its purpose is to provide an index to an ENRP server for
is between zero and (poolHandleCount - 1). Note that the value of all other tables. Each "conceptual row" in the enrpServerTable
poolHandleIndex is defined as "not-accessible" in the MAX-ACCESS contains the server's ENRP Identifier, the number of pools, PEs and
clause; this is a standard technique used when defining a table-in- peers, the amount of ENRP endpoint addresses, the server's uptime and
table data structure. The third element on the nameserver branch is a textual description of the server. The poolTable contains a single
the poolElementTable. Because the poolElementTable is the "inner" entry for each pool that is currently registered. Each "conceptual
table of the table-in-table structure, its index consists of a pair, row" in the poolTable consists of a poolTableEntry, with three
as indicated in the clause "INDEX { poolHandleIndex, poolElementIndex elements: a poolIndex, a poolElementCount, and an OCTET STRING
}". The fourth element of the nameserver branch takes the nesting to representation of the pool handle. The poolElementCount is the
one additional level, listing the various IP addresses associated number of pool elements registered with this pool handle. The
with a particular poolElement, and thus is indexed by a triple: poolIndex is simply an integer that is used to index into the
"INDEX { poolHandleIndex, poolElementIndex, addrListTableIndex }". poolTable and the poolElementTable. The value of this integer is
The fifth and final element on the nameserver branch is the uptimeNS, between zero and (poolCount - 1). Note that the value of poolIndex
which simply provides the uptime of the ENRP server since the last is defined as "not-accessible" in the MAX-ACCESS clause; this is a
restart of the ENRP server process. standard technique used when defining a table-in-table data
structure. The third element on the ENRP servers branch is the
poolElementTable. Because the poolElementTable is the "inner" table
of the table-in-table structure, its index consists of a pair, as
indicated in the clause "INDEX { enrpServerIndex, poolIndex,
poolElementIndex }". The fourth element of the ENRP servers branch
takes the nesting to one additional level, listing the various
addresses associated with a particular poolElement in form of ASAP
endpoint addresses and user transport addresses, and thus are indexed
by the 4-tuples "INDEX { enrpServerIndex, poolIndex,
poolElementIndex, asapTransportAddrListTableIndex }" and "INDEX {
enrpServerIndex, poolIndex, poolElementIndex,
userTransportAddrListTableIndex }". The ENRP endpoint addresses of
an ENRP server are bound to its instance in the enrpAddrListTable by
"INDEX { enrpIndex, enrpAddrListTableIndex }". Finally, an ENRP
server has a peer table of its known peers. They are bound to a
server instance by the peerTable; analogously, the addresses of a
peer are bound to a peerTable's entry in the peerAddrListTable.
3.2 Access to managed objects on Pool Elements 3.2 Access to managed objects on Pool Elements
Note that on a given host, there may be an ENRP server process along The construction of the Pool Elements branch is very similar to the
with a set of pool element processes. The nameserver branch ENRP servers branch. But in this case, the nesting step of the
provides access to information about pool elements that has been enrpServerTable can be omitted and pools and their corresponding pool
communicated to an ENRP server via the ASAP protocol. By contrast, elements be directly defined. That is, the nesting structure is as
the "poolElements" branch of the MIB provides direct access to follows:
managed objects in the pool elements themselves. It is anticipated
that a manager may want to query the pool elements directly when Level 1: poolTable
investigating network problems related to communication between an Level 2: poolElementTable
ENRP server and a pool element. Any given host may have, at a Level 3: asapTransportAddrListTable
certain point in time, several active pool element processes. These userTransportAddrListTable
processes might or might not all have unique poolHandles. Clearly,
it is feasible that a given host may be running multiple servers, The description of the contained structures is the same as for the
each with a separate poolHandle. What may be less obvious is that ENRP servers branch.
there may also be multiple servers with the same poolhandle;
consider, for example, a host with multiple CPUs that might have one TODO: There should be the server table (ENRP servers learned by their
server process per CPU, all providing the same service and thus announces) plus the multicast address the PE expects the announces to
sharing the same pool handle, but with distinct poolElement be sent to.
characteristics such as load, SCTPPort, policy value, etc.
Therefore, as on the nameserver branch, the table-in-table technique 3.3 Access to managed objects on Pool Users
is indicated. For simplicity, we use the exact same structure.
The construction of the Pool Elements branch is analogous to the ENRP
servers branch: multiple PU instances can run on the same host.
Therefore, it is first necessary to hold a table of them.
Level 1: poolUserTable
...
TODO: How should a PU be defined? PH, server table and current
address(es)?
4. Definitions 4. Definitions
RSERPOOL--MIB DEFINITIONS ::= BEGIN RSERPOOL-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
TimeTicks, TimeTicks,
Unsigned32 Unsigned32
FROM SNMPv2-SMI; FROM SNMPv2-SMI
InetAddress
FROM INET-ADDRESS-MIB;
-- ## Module definition ###########################################
rserpoolMIB MODULE-IDENTITY rserpoolMIB MODULE-IDENTITY
LAST-UPDATED "200111120000Z" LAST-UPDATED "200506100820Z"
ORGANIZATION "Netlab, TEMPLE UNIVERSITY" ORGANIZATION "IEM-TdR, UNIVERSITY OF DUISBURG-ESSEN"
CONTACT-INFO CONTACT-INFO
" JAIWANT-MULIK " THOMAS-DREIBHOLZ
Postal: University of Duisburg-Essen
Institute for Experimental Mathematics
Ellernstrasse 29
D-45326 Essen
Germany
Phone: +49 201-183 7637
Email: dreibh@exp-math.uni-essen.de
JAIWANT-MULIK
PHILLIP-CONRAD PHILLIP-CONRAD
KEVIN-PINZHOFFER KEVIN-PINZHOFFER
Postal: 1805, N Broad St. Postal: 1805, N Broad St.
Philadelphia, PA Philadelphia, PA
USA 19121 USA 19121
Phones: +1 215 204 7910 Phones: +1 215 204 7910
Emails: jmulik@temple.edu Emails: jmulik@temple.edu
conrad@acm.org conrad@acm.org
kpinzhof@temple.edu" kpinzhof@temple.edu"
DESCRIPTION DESCRIPTION
"The MIB module for managing a RserPool implementation" "The MIB module for managing a RSerPool implementation"
::= { xxxx } -- IANA Assigned ::= { mib-2 12345 } -- To be IANA Assigned!!!
-- ## RSerPool type definitions ###################################
ENRPServerIdentifier ::= INTEGER (1..4294967295)
ENRPServerDescription ::= OCTET STRING (0..255)
OperationScope ::= OCTET STRING
-- Top level definitions PoolHandle ::= OCTET STRING
nameServer OBJECT IDENTIFIER ::= { rserpoolMIB 1 } PoolElementIdentifier ::= INTEGER (1..4294967295)
PolicyType ::= INTEGER (0..255)
PolicyDescription ::= OCTET STRING (0..255)
PolicyLoad ::= INTEGER (0..16777215)
PolicyWeight ::= INTEGER (0..16777215)
TransportUse ::= INTEGER {
dataOnly(0),
dataPlusControl(1)
}
ENRPServerIndex ::= INTEGER (1..2147483647)
PoolIndex ::= INTEGER (1..2147483647)
PoolElementIndex ::= INTEGER (1..2147483647)
-- ## Top-level definitions #######################################
enrpServers OBJECT IDENTIFIER ::= { rserpoolMIB 1 }
poolElements OBJECT IDENTIFIER ::= { rserpoolMIB 2 } poolElements OBJECT IDENTIFIER ::= { rserpoolMIB 2 }
poolUsers OBJECT IDENTIFIER ::= { rserpoolMIB 3 }
-- Definition of the pool handle table -- ## Definition of the ENRP server table #########################
enrpServerCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of ENRP servers on this host"
::= { enrpServers 1 }
poolHandleCount OBJECT-TYPE enrpServerTable OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX SEQUENCE OF enrpServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual table listing of the ENRP servers
on this host"
::= { enrpServers 2 }
enrpServerEntry OBJECT-TYPE
SYNTAX ENRPServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual row in enrpServerTable"
INDEX { enrpServerIndex }
::= { enrpServerTable 1 }
ENRPServerEntry ::= SEQUENCE {
enrpServerIndex ENRPServerIndex,
enrpServerElementCount Counter32,
enrpServerIdentifier ENRPServerIdentifier,
enrpServerUptime timeTicks,
enrpServerDescription ENRPServerDescription,
enrpPort INTEGER,
enrpAddrCount Counter32,
peerCount Counter32,
poolCount Counter32,
enrpServerASAPAnnouncePort INTEGER,
enrpServerASAPAnnounceAddr InetAddress,
enrpServerENRPAnnouncePort INTEGER,
enrpServerENRPAnnounceAddr InetAddress }
enrpServerIndex OBJECT-TYPE
SYNTAX ENRPServerIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index to the enrpServerTable"
::= { enrpServerEntry 1 }
enrpServerIdentifier OBJECT-TYPE
SYNTAX ENRPServerIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of pool handles supported by this name server" "This is the ENRP server identifier of this row"
::= { nameServer 1 } ::= { enrpServerEntry 2 }
poolHandleTable OBJECT-TYPE enrpServerOperationScope OBJECT-TYPE
SYNTAX SEQUENCE OF poolHandleEntry SYNTAX PoolElementIdentifier
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual table listing the pool handles served "This is the operation scope of this row"
by this name server" ::= { enrpServerEntry 3 }
::= { nameServer 2 } enrpServerUptime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is the uptime of this row"
::= { enrpServerEntry 4 }
poolHandleEntry OBJECT-TYPE enrpServerDescription OBJECT-TYPE
SYNTAX PoolHandleEntry SYNTAX ENRPServerDescription
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual row in poolHandleTable." "This is the description of this row"
INDEX { poolHandleIndex } ::= { enrpServerEntry 5 }
::= { poolHandleTable 1 }
PoolHandleEntry ::= SEQUENCE { enrpPort OBJECT-TYPE
poolHandleIndex Unsigned32, SYNTAX INTEGER (1..65535)
poolElementCount Unsigned32, MAX-ACCESS read-only
poolHandle OCTET STRING } STATUS current
DESCRIPTION
"Contains the ENRP transport protocol's port
number of a pool element"
::= { enrpServerEntry 6 }
poolHandleIndex OBJECT-TYPE enrpAddrCount OBJECT-TYPE
SYNTAX UNSIGNED32 SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ENRP address count of this row"
::= { enrpServerEntry 7 }
peerCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of peers of this ENRP server"
::= { enrpServerEntry 8 }
poolCount OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of pools of this ENRP server"
::= { enrpServerEntry 9 }
enrpServerASAPAnnouncePort OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Contains the ASAP/UDP port number the announces
are sent to"
::= { enrpServerEntry 10 }
enrpServerASAPAnnounceAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Contains the ASAP/UDP multicast address the
announces are sent to"
::= { enrpServerEntry 11 }
enrpServerENRPAnnouncePort OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Contains the ENRP/UDP port number the announces
are sent to"
::= { enrpServerEntry 12 }
enrpServerENRPAnnounceAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Contains the ENRP/UDP multicast address the
announces are sent to"
::= { enrpServerEntry 13 }
-- ## Definition of the pool table ################################
poolTable OBJECT-TYPE
SYNTAX SEQUENCE OF poolEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index to the poolHandleTable. This value is between, "The conceptual table listing of the pool served
0 and (poolHandleCount-1)" by this handlespace"
::= { poolHandleEntry 1} ::= { enrpServers 3 }
poolEntry OBJECT-TYPE
SYNTAX PoolEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual row in poolTable"
INDEX { enrpServerIndex poolIndex }
::= { poolTable 1 }
PoolEntry ::= SEQUENCE {
poolIndex PoolIndex,
poolElementCount Counter32,
poolHandle PoolHandle }
poolIndex OBJECT-TYPE
SYNTAX PoolIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index to the poolTable"
::= { poolEntry 1}
poolElementCount OBJECT-TYPE poolElementCount OBJECT-TYPE
SYNTAX UNSIGNED32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of pool elements that belong to this "The number of pool elements that belong to this
pool handle" pool handle"
::= { poolHandleEntry 2 } ::= { poolEntry 2 }
poolHandle OBJECT-TYPE poolHandle OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX PoolHandle
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The pool handle of this row" "The pool handle of this row"
::= { poolHandleEntry 3 } ::= { poolEntry 3 }
-- Definition of pool element table
-- ## Definition of the pool element table ########################
poolElementTable OBJECT-TYPE poolElementTable OBJECT-TYPE
SYNTAX SEQUENCE OF poolElementEntry SYNTAX SEQUENCE OF poolElementEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual table listing the PEs per pool handle" "The conceptual table listing the PEs per
::= { nameServer 3 } pool handle"
::= { enrpServers 4 }
poolElementEntry OBJECT-TYPE poolElementEntry OBJECT-TYPE
SYNTAX PoolELementEntry SYNTAX PoolELementEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The conceptual row in poolElementTable. Note the compound "The conceptual row in poolElementTable. Note the
index element. We are using the table-in-table idea here." compound index element. We are using the
INDEX { poolHandleIndex, poolElementIndex } table-in-table idea here."
INDEX { enrpServerIndex, poolIndex,
poolElementIndex }
::= { poolElementTable 1 } ::= { poolElementTable 1 }
PoolElementEntry ::= SEQUENCE { PoolElementEntry ::= SEQUENCE {
poolElementIndex Unsigned32, poolElementIndex PoolElementIndex,
poolElementIPAddressCount Unsigned32, asapTransportPort INTEGER,
poolElementHostname OCTET STRING, asapTransportAddrCount Counter32,
policyType Unsigned32, userTransportProtocol INTEGER,
policyValue Unsigned32, userTransportPort INTEGER,
noOfRequests Unsigned32, userTransportUse TransportUse,
noOfRequestsInQueue Unsigned32, userTransportAddrCount Counter32,
sctpPort INTEGER, policyType PolicyType,
upTimePE TimeTicks } policyDescr PolicyDescription,
polcyWeight PolicyWeight,
polcyLoad PolicyLoad,
polcyLoadDegradation PolicyLoad,
registrationLife TimeTicks,
homeENRPServer ENRPServerIdentifier }
poolElementIndex OBJECT-TYPE poolElementIndex OBJECT-TYPE
SYNTAX UNSIGNED32 SYNTAX PoolElementIndex
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indexes into the poolElementTable. This value is between, "This is the index into the poolElementTable"
0 and (poolElementCount-1) of the
corresponding poolHandleTable"
::={ poolElementEntry 1 } ::={ poolElementEntry 1 }
poolElementIPAddressCount OBJECT-TYPE asapTransportPort OBJECT-TYPE
SYNTAX UNSIGNED32 SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the number of IP addresses assigned to a hostname" "Contains the ASAP transport protocol's port
number of a pool element"
::= { poolElementEntry 2 } ::= { poolElementEntry 2 }
asapTransportAddrCount OBJECT-TYPE
poolElementHostname OBJECT-TYPE SYNTAX Counter32
SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Hostname of a pool element" "Counts the number of ASAP network-layer
addresses assigned to a pool element"
::= { poolElementEntry 3 } ::= { poolElementEntry 3 }
policyType OBJECT-TYPE userTransportProtocol OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The policy type for this pool element" "Contains the user transport protocol ID of a
pool element"
::= { poolElementEntry 4 } ::= { poolElementEntry 4 }
policyValue OBJECT-TYPE userTransportPort OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The policy value for this pool element" "Contains the user transport protocol's port
number of a pool element"
::= { poolElementEntry 5 } ::= { poolElementEntry 5 }
noOfRequests OBJECT-TYPE userTransportUse OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TransportUse
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of service requests that this PE is currenly processing" "Contains the user transport use of a pool
element"
::= { poolElementEntry 6} ::= { poolElementEntry 6}
noOfRequestsInQueue OBJECT-TYPE userTransportAddrCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of service requests currently queued by the PE" "Counts the number of user transport
network-layer addresses assigned to a
pool element"
::= { poolElementEntry 7 } ::= { poolElementEntry 7 }
sctpPort OBJECT-TYPE
SYNTAX INTEGER (0..65535) policyType OBJECT-TYPE
SYNTAX PolicyType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SCTP port from this pool elements PE parameter" "The policy type of this pool element"
::= { poolElementEntry 8 } ::= { poolElementEntry 8 }
upTimePE OBJECT-TYPE policyDescr OBJECT-TYPE
SYNTAX TimeTicks SYNTAX PolicyDescription
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since last start of the PE" "The policy description of this pool element"
::= { poolElementEntry 9 } ::= { poolElementEntry 9 }
--- Definition of addresslist Table policyWeight OBJECT-TYPE
SYNTAX PolicyWeight
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The policy's weight parameter of this pool element"
::= { poolElementEntry 10 }
addrListTable OBJECT-TYPE policyLoad OBJECT-TYPE
SYNTAX SEQUENCE OF addrListTableEntry SYNTAX PolicyLoad
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table holds all the IP addresses of a multi-homed host" "The policy's load parameter of this pool element"
::= { nameServer 4 } ::= { poolElementEntry 11 }
addrListTableEntry OBJECT-TYPE policyLoadDegradation OBJECT-TYPE
SYNTAX AddrListTableEntry SYNTAX PolicyLoad
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
INDEX { poolHandleIndex, poolElementIndex, addrListTableIndex }
DESCRIPTION DESCRIPTION
"A row in the addrList table" "The policy's load degradation parameter of this
::= { addrListTable 1 } pool element"
::= { poolElementEntry 12 }
AddrListTableEntry ::= SEQUENCE { registrationLife OBJECT-TYPE
addrListTableIndex Unsigned32, SYNTAX TimeTicks
hostIPAddress IpAddress } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The registration life of the pool element"
::= { poolElementEntry 13 }
homeENRPServer OBJECT-TYPE
SYNTAX ENRPServerIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ID of the home ENRP server of the pool element"
::= { poolElementEntry 14 }
addrListTableIndex OBJECT-TYPE -- ## Definition of asap transport address list table #############
SYNTAX Unsigned32 asapTransportAddrListTable OBJECT-TYPE
SYNTAX SEQUENCE OF asapTransportAddrListTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indexes into the addrListTable. This values is between "This table holds all the IP addresses of a
0 and (poolElementIPAddressCount-1)." multi-homed host"
::= { addrListTableEntry 1} ::= { enrpServers 5 }
hostIPAddress OBJECT-TYPE asapTransportAddrListTableEntry OBJECT-TYPE
SYNTAX IpAddress SYNTAX ASAPTransportAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in the asapTransportAddrList table"
INDEX { enrpServerIndex, poolIndex, poolElementIndex,
asapTransportAddrListTableIndex }
::= { asapTransportAddrListTable 1 }
ASAPTransportAddrListTableEntry ::= SEQUENCE {
asapTransportAddrListTableIndex Unsigned32,
networkLayerProtocol INTEGER,
networkLayerAddress InetAddress }
asapTransportAddrListTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index into the
asapTransportAddrListTable"
::= { asapTransportAddrListTableEntry 1 }
networkLayerProtocol OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The address column in the addrListTable " "The protocol column in the
::= { addrListTableEntry 2 } asapTransportAddrListTable"
::= { asapTransportAddrListTableEntry 2 }
-- networkLayerAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address column in the
asapTransportAddrListTable"
::= { asapTransportAddrListTableEntry 3 }
uptimeNS OBJECT-TYPE -- ## Definition of user transport address list table #############
userTransportAddrListTable OBJECT-TYPE
SYNTAX SEQUENCE OF userTransportAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table holds all the IP addresses of a
multi-homed host"
::= { enrpServers 6 }
userTransportAddrListTableEntry OBJECT-TYPE
SYNTAX UserTransportAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in the userTransportAddrList table"
INDEX { enrpServerIndex, poolIndex, poolElementIndex,
userTransportAddrListTableIndex }
::= { userTransportAddrListTable 1 }
UserTransportAddrListTableEntry ::= SEQUENCE {
userTransportAddrListTableIndex Unsigned32,
networkLayerProtocol INTEGER,
networkLayerAddress InetAddress }
userTransportAddrListTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index into the
userTransportAddrListTable"
::= { userTransportAddrListTableEntry 1 }
networkLayerProtocol OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The protocol column in the
userTransportAddrListTable"
::= { userTransportAddrListTableEntry 2 }
networkLayerAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address column in the
userTransportAddrListTable"
::= { userTransportAddrListTableEntry 3 }
-- ## Definition of ENRP address list table #######################
enrpAddrListTable OBJECT-TYPE
SYNTAX SEQUENCE OF enrpAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table holds all the IP addresses of a
multi-homed host"
::= { enrpServers 7 }
enrpAddrListTableEntry OBJECT-TYPE
SYNTAX PeerAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in the enrpAddrList table"
INDEX { enrpIndex, enrpAddrListTableIndex }
::= { enrpAddrListTable 1 }
PeerAddrListTableEntry ::= SEQUENCE {
enrpAddrListTableIndex Unsigned32,
networkLayerProtocol INTEGER,
networkLayerAddress InetAddress }
enrpAddrListTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index into the enrpAddrListTable"
::= { enrpAddrListTableEntry 1 }
networkLayerProtocol OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The protocol column in the enrpAddrListTable"
::= { enrpAddrListTableEntry 2 }
networkLayerAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address column in the enrpAddrListTable"
::= { enrpAddrListTableEntry 3 }
-- ## Definition of peer table ####################################
peerTable OBJECT-TYPE
SYNTAX SEQUENCE OF peerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual table listing of the peer of
this ENRP server"
::= { enrpServers 8 }
peerEntry OBJECT-TYPE
SYNTAX PeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The conceptual row in peerTable"
INDEX { peerIndex }
::= { peerTable 1 }
PeerEntry ::= SEQUENCE {
peerIndex Unsigned32,
peerIdentifier OCTET STRING,
peerPort INTEGER,
peerLastHeard TimeTicks
peerAddrCount Counter32 }
peerIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index to the peerTable"
::= { peerEntry 1 }
peerIdentifier OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The peer ENRP identifier of this row"
::= { peerEntry 2 }
peerPort OBJECT-TYPE
SYNTAX INTEGER (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The poort's port number"
::= { peerEntry 3 }
peerLastHeard OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time since the last start of this service" "The peer last heard information of this row"
::= { nameServer 5 } ::= { peerEntry 4 }
peerAddrCount OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The peer address count of this row"
::= { peerEntry 5 }
-- ## Definition of peer address list table #######################
peerAddrListTable OBJECT-TYPE
SYNTAX SEQUENCE OF peerAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table holds all the IP addresses of a
multi-homed host"
::= { enrpServers 9 }
peerAddrListTableEntry OBJECT-TYPE
SYNTAX PeerAddrListTableEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A row in the peerAddrList table"
INDEX { peerIndex, peerAddrListTableIndex }
::= { peerAddrListTable 1 }
PeerAddrListTableEntry ::= SEQUENCE {
peerAddrListTableIndex Unsigned32,
networkLayerProtocol INTEGER,
networkLayerAddress InetAddress }
peerAddrListTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This is the index into the peerAddrListTable"
::= { peerAddrListTableEntry 1 }
networkLayerProtocol OBJECT-TYPE
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The protocol column in the peerAddrListTable"
::= { peerAddrListTableEntry 2 }
networkLayerAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address column in the peerAddrListTable"
::= { peerAddrListTableEntry 3 }
END END
The definitions of the managed objects under the "poolElements" For sake of brevity and to avoid inadvertant inconsistencies due to
branch are identical to those under the nameserver branch with the typos, we omit the full elaboration of the poolElements and poolUsers
single exception that the uptimeNS element is not present. branch. However, we repeat for emphasis that the semantics of the
Therefore, for sake of brevity and to avoid inadvertant two branches are different, as noted earlier in this memo.
inconsistencies due to typos, we omit the full elaboration of the
poolElement branch. However, we repeat for emphasis that the
semantics of the two branches are different, as noted earlier in this
memo.
5. Security Considerations 5. Security Considerations
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), there is no control as
control as to who on the secure network is allowed to access and GET/ to who on the secure network is allowed to access and GET/SET (read/
SET (read/change/create/delete) the objects in this MIB. change/create/delete) the 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. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [15] and the View-based of the User-based Security Model RFC 2574 [15] and the View-based
Access Control Model RFC 2575 [16] is recommended. Access Control Model RFC 2575 [16] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (change/ (users) that have legitimate rights to indeed GET or SET (change/
create/delete) them. create/delete) them.
6. IANA Considerations 6. IANA Considerations
IANA will need to assign an OID prefix for the RSerPool MIB. IANA will need to assign an OID prefix for the RSerPool MIB.
References 7. References
[1] Rose, M. and K. McCloghrie, "Structure and identification of [1] Rose, M. and K. McCloghrie, "Structure and identification of
management information for TCP/IP-based internets", STD 16, RFC management information for TCP/IP-based internets", STD 16,
1155, May 1990. RFC 1155, May 1990.
[2] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple [2] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol (SNMP)", STD 15, RFC 1157, May Network Management Protocol (SNMP)", STD 15, RFC 1157,
1990. May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB definitions", STD 16, [3] Rose, M. and K. McCloghrie, "Concise MIB definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
[4] Rose, M., "Convention for defining traps for use with the [4] Rose, M., "Convention for defining traps for use with the
SNMP", RFC 1215, March 1991. SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Case, J., McCloghrie, K., Rose, M. and S. [5] Case, J., McCloghrie, K., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996. January 1996.
[6] McCloghrie, K., Case, J., McCloghrie, K., Rose, M. and S. [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Waldbusser, "Structure of Management Information for Version 2 "Structure of Management Information for Version 2 of the
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
[7] McCloghrie, K., Case, J., Rose, M. and S. Waldbusser, "Textual [7] McCloghrie, K., Case, J., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1903, January 1996. Protocol (SNMPv2)", RFC 1903, January 1996.
[8] McCloghrie, K., Case, J., Rose, M. and S. Waldbusser, [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Conformance Statements for Version 2 of the Simple Network "Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996. Management Protocol (SNMPv2)", RFC 1904, January 1996.
[9] McCloghrie, K., Case, J., Rose, M. and S. Waldbusser, "Protocol [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Operations for Version 2 of the Simple Network Management "Protocol Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[10] McCloghrie, K., Case, J., Rose, M. and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction [11] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
to Version 3 of the Internet-standard Network Management to Version 3 of the Internet-standard Network Management
Framework", RFC 2570, April 1999. Framework", RFC 2570, April 1999.
[12] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for [12] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, May 1999. for Describing SNMP Management Frameworks", RFC 2571,
April 1999.
[13] Case, J., Harrington, D., Presuhn, R. and B. Wijnen, "Message [13] Case, J., Harrington, D., Presuhn, R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, May 1999. Protocol (SNMP)", RFC 2572, April 1999.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications",
2573, April 1999. RFC 2573, April 1999.
[15] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [15] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999. (SNMPv3)", RFC 2574, April 1999.
[16] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[17] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [17] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Ed., "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2)", STD 58, RFC 2578, STD 58, RFC 2578, April 1999.
April 1999.
[18] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [18] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579,
Conventions for SMIv2", STD 58, RFC 2579, April 1999. April 1999.
[19] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance [19] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[20] Ong, L., Shore, M., Stillman, M., Xie, Q., Loughney, J., [20] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Loughney, J., and
Tuexen, M. and M. Stewart, "Architecture for Reliable Server A. Silverton, "Architecture for Reliable Server Pooling",
Pooling", draft-ietf-rserpool-arch-02 (work in progress), April draft-ietf-rserpool-arch-09 (work in progress), February 2005.
2002.
[21] Perkins, D. and E. McGinnis, "Understanding SNMP MIBs", 1997, [21] Perkins, D. and E. McGinnis, "Understanding SNMP MIBs", 1997.
<http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-
00.txt>.
Authors' Addresses Authors' Addresses
Thomas Dreibholz
University of Duisburg-Essen, Institute for Experimental Mathematics
Ellernstrasse 29
45326 Essen, Nordrhein-Westfalen
Germany
Phone: +49-201-1837637
Fax: +49-201-1837673
Email: dreibh@exp-math.uni-essen.de
URI: http://www.exp-math.uni-essen.de/~dreibh/
Jaiwant Mulik Jaiwant Mulik
Temple University Temple University
CIS Department CIS Department
Room 303, Computer Building (038-24) Room 303, Computer Building (038-24)
1805 N. Broad St. 1805 N. Broad St.
Philadelphia, PA 19122 Philadelphia, PA 19122
US US
Phone: +1 215 204 3197 Phone: +1 215 204 3197
EMail: jmulik@temple.edu Email: jmulik@temple.edu
URI: http://unix.temple.edu/~jmulik URI: http://unix.temple.edu/~jmulik
Phillip T. Conrad Phillip Conrad
Temple University University of Delaware
CIS Department 103 Smith Hall
Room 303, Computer Building (038-24) Newark DE 19716
1805 N. Broad St. USA
Philadelphia, PA 19122
US
Phone: +1 215 204 7910 Phone: +1 302 831 8622
EMail: conrad@joda.cis.temple.edu Email: conrad@acm.org
URI: http://www.cis.temple.edu/~conrad
Kevin Pinzhoffer Kevin Pinzhoffer
Temple University Temple University
CIS Department CIS Department
Room 303, Computer Building (038-24) Room 303, Computer Building (038-24)
1805 N. Broad St. 1805 N. Broad St.
Philadelphia, PA 19122 Philadelphia, PA 19122
US US
Phone: +1 215 204 3197 Phone: +1 215 204 3197
EMail: kpinzhof@temple.edu Email: kpinzhof@temple.edu
Full Copyright Statement Intellectual Property Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
This document and translations of it may be copied and furnished to Copies of IPR disclosures made to the IETF Secretariat and any
others, and derivative works that comment on or otherwise explain it assurances of licenses to be made available, or the result of an
or assist in its implementation may be prepared, copied, published attempt made to obtain a general license or permission for the use of
and distributed, in whole or in part, without restriction of any such proprietary rights by implementers or users of this
kind, provided that the above copyright notice and this paragraph are specification can be obtained from the IETF on-line IPR repository at
included on all such copies and derivative works. However, this http://www.ietf.org/ipr.
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The IETF invites any interested party to bring to its attention any
revoked by the Internet Society or its successors or assigns. copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
This document and the information contained herein is provided on an Disclaimer of Validity
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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