draft-ietf-rserpool-mib-12.txt   rfc5525.txt 
Network Working Group T. Dreibholz Network Working Group T. Dreibholz
Internet-Draft University of Duisburg-Essen Request for Comments: 5525 University of Duisburg-Essen
Intended status: Experimental J. Mulik Category: Experimental J. Mulik
Expires: September 10, 2009 Delaware State University Delaware State University
March 9, 2009
Reliable Server Pooling MIB Module Definition Reliable Server Pooling MIB Module Definition
draft-ietf-rserpool-mib-12.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 10, 2009. This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
Reliable Server Pooling (RSerPool) is a framework to provide reliable Reliable Server Pooling (RSerPool) is a framework to provide reliable
server pooling. The RSerPool frameworks consists of the two server pooling. The RSerPool framework consists of two protocols:
protocols ASAP (Aggregate Server Access Protocol) and ENRP (Endpoint ASAP (Aggregate Server Access Protocol) and ENRP (Endpoint
Handlespace Redundancy Protocol). This document defines a SMIv2 Handlespace Redundancy Protocol). This document defines an SMIv2-
compliant Management Information Base (MIB) module providing access compliant (Structure of Management Information Version 2) Management
to managed objects in an RSerPool implementation. Information Base (MIB) module providing access to managed objects in
an RSerPool implementation.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3 2. The Reliable Server Pooling (RSerPool) Framework ................2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions .....................................................2
4. The Internet-Standard Management Framework . . . . . . . . . . 3 4. The Internet-Standard Management Framework ......................2
5. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 5. Structure of the MIB ............................................3
5.1. Access to managed objects on ENRP servers . . . . . . . . 10 5.1. Access to Managed Objects on ENRP Servers .................10
5.2. Access to managed objects on Pool Elements . . . . . . . . 11 5.2. Access to Managed Objects on Pool Elements ................10
5.3. Access to managed objects on Pool Users . . . . . . . . . 11 5.3. Access to Managed Objects on Pool Users ...................11
5.4. Persistency Behavior . . . . . . . . . . . . . . . . . . . 11 5.4. Persistency Behavior ......................................11
6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Definitions ....................................................11
7. Operational Considerations . . . . . . . . . . . . . . . . . . 41 7. Operational Considerations .....................................42
8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 8. Security Considerations ........................................42
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 9. IANA Considerations ............................................43
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43 10. Acknowledgments ...............................................43
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 11. References ....................................................44
11.1. Normative References . . . . . . . . . . . . . . . . . . . 44 11.1. Normative References .....................................44
11.2. Informative References . . . . . . . . . . . . . . . . . . 44 11.2. Informative References ...................................44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction 1. Introduction
This memo defines a Management Information Base (MIB) module which This memo defines a Management Information Base (MIB) module that
describes managed objects for RSerPool implementations. describes managed objects for RSerPool implementations.
2. The Reliable Server Pooling (RSerPool) Framework 2. The Reliable Server Pooling (RSerPool) Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Reliable Server Pooling (RSerPool) framework, please refer to Reliable Server Pooling (RSerPool) framework, please refer to
[RFC3237], [RFC5351], [RFC5352], [RFC5353], [RFC5354], [RFC5355] and [RFC3237], [RFC5351], [RFC5352], [RFC5353], [RFC5354], [RFC5355], and
[RFC5356]. A more informal introduction can be found at [RFC5356]. A more informal introduction can be found at
[RSerPoolPage] as well as in [Dre2006], [LCN2005] and [IJHIT2008]. [RSerPoolPage] as well as in [Dre2006], [LCN2005], and [IJHIT2008].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
4. The Internet-Standard Management Framework 4. 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
skipping to change at page 3, line 46 skipping to change at page 3, line 18
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. The textual conventions are compliant to RFC 4001 [RFC2580]. The textual conventions are compliant to RFC 4001
[RFC4001]. [RFC4001].
5. Structure of the MIB 5. 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(XXX) +--rserpoolMIB(125)
| |
+--rserpoolMIBObjects(1) +--rserpoolMIBObjects(1)
| | | |
| +--rserpoolENRPServers(1) | +--rserpoolENRPServers(1)
| | | | | |
| | +--rserpoolENRPTable(1) | | +--rserpoolENRPTable(1)
| | | | | | | |
| | | +--rserpoolENRPEntry(1) | | | +--rserpoolENRPEntry(1)
| | | | Index: rserpoolENRPIndex | | | | Index: rserpoolENRPIndex
| | | | | | | |
skipping to change at page 10, line 4 skipping to change at page 9, line 18
| |
+--rserpoolMIBCompliances(1) +--rserpoolMIBCompliances(1)
| | | |
| +--rserpoolMIBCompliance(1) | +--rserpoolMIBCompliance(1)
| |
+--rserpoolMIBGroups(2) +--rserpoolMIBGroups(2)
| |
+--rserpoolENRPGroup(1) +--rserpoolENRPGroup(1)
+--rserpoolPEGroup(2) +--rserpoolPEGroup(2)
+--rserpoolPUGroup(3) +--rserpoolPUGroup(3)
As the figure shows, the MIB consists of three main branches: As the figure shows, the MIB consists of three main branches:
"rserpoolENRP", "rserpoolPoolElements" and "rserpoolPoolUsers". The "rserpoolENRPServers", "rserpoolPoolElements", and
first branch, "rserpoolENRP" is used to access managed objects in the "rserpoolPoolUsers". The first branch, "rserpoolENRPServers", is
set of ENRP servers running on a given host. While it is assumed used to access managed objects in the set of ENRP servers running on
that it does not make much sense to run multiple ENRP servers for the a given host. While it is assumed that it does not make much sense
same operation scope on one host, running multiple ENRP servers for to run multiple ENRP servers for the same operation scope on one
different operation scopes is very likely when the ENRP server host, running multiple ENRP servers for different operation scopes is
processes run on routers. Therefore, the MIB has to be able to very likely when the ENRP server processes run on routers.
manage multiple ENRP servers on the same host. "rserpoolPoolElements" Therefore, the MIB has to be able to manage multiple ENRP servers on
is used to access managed objects in the set of Pool Elements that the same host.
are running on a given host. The third branch, "rserpoolPoolUsers"
is used to access managed objects in the set of Pool Users that are
running on a given host. Note: "rserpoolENRPServers" is filled on
hosts running ENRP server instances, "rserpoolPoolElements" is filled
on hosts running Pool Element instances and "rserpoolPoolUsers" is
filled on hosts running Pool User instances. Of course, multiple
different components may run on the same host, which leads to filling
of multiple different branches. 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 second and third branch. We now proceed with a
description of the branches.
5.1. Access to managed objects on ENRP servers "rserpoolPoolElements" is used to access managed objects in the set
of pool elements that are running on a given host.
The third branch, "rserpoolPoolUsers", is used to access managed
objects in the set of pool users that are running on a given host.
Note: "rserpoolENRPServers" is filled on hosts running ENRP server
instances, "rserpoolPoolElements" is filled on hosts running pool
element instances, and "rserpoolPoolUsers" is filled on hosts running
pool user instances. Of course, multiple different components may
run on the same host, which leads to filling of multiple different
branches.
In fact, the structure of the three branches is very similar.
Because the other two branches are so similar, we describe only the
first branch in detail, and provide a summary description of the
second and third branch. We now proceed with a description of the
branches.
5.1. Access to Managed Objects on ENRP Servers
The first branch describes managed objects at a set of ENRP servers. The first branch describes managed objects at a set of ENRP servers.
Any given ENRP server of this set will, at a certain moment in time, Any given ENRP server of this set will, at a certain moment in time,
have registration information for a set of active pools. Each of have registration information for a set of active pools. Each of
these pools in turn may have a list of pool elements that are these pools in turn may have a list of pool elements that are
registered under that pool. To allow this information to be registered under that pool. To allow this information to be
retrieved via SNMP, the ERNP server 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 [SNMPMIBS]. Specifically, the table-in-table technique described in [SNMPMIBS].
the ENRP servers branch creates four levels of nesting, as indicated
in the following diagram: Specifically, the ENRP servers branch creates four levels of nesting,
as indicated in the following diagram:
Nesting of the ENRP Server Branch Nesting of the ENRP Server Branch
Nesting Structure: Nesting Structure:
Level 1: rserpoolENRPTable Level 1: rserpoolENRPTable
Level 2: rserpoolENRPPoolTable Level 2: rserpoolENRPPoolTable
Level 3: rserpoolENRPPoolElementTable Level 3: rserpoolENRPPoolElementTable
Level 4: rserpoolENRPASAPAddrTable Level 4: rserpoolENRPASAPAddrTable
rserpoolENRPUserAddrTable rserpoolENRPUserAddrTable
Level 2: rserpoolENRPENRPAddrTable Level 2: rserpoolENRPENRPAddrTable
Level 2: rserpoolENRPPeerTable Level 2: rserpoolENRPPeerTable
Level 3: rserpoolENRPPeerAddrTable Level 3: rserpoolENRPPeerAddrTable
5.2. Access to managed objects on Pool Elements 5.2. Access to Managed Objects on Pool Elements
The construction of the Pool Elements branch is very similar to the The construction of the Pool Elements branch is very similar to the
pool elements table of the ENRP servers branch. But instead of pool elements table of the ENRP servers branch. But instead of
grouping the pool elements into pools (which does not make sense grouping the pool elements into pools (which does not make sense
here), the pool elements table is the top of the hierarchy and each here), the pool elements table is the top of the hierarchy, and each
pool element entry specifies its operation scope and pool handle. pool element entry specifies its operation scope and pool handle.
That is, the nesting structure is as follows: That is, the nesting structure is as follows:
Nesting of the Pool Elements Branch Nesting of the Pool Elements Branch
Level 1: rserpoolPETable Level 1: rserpoolPETable
Level 2: rserpoolPEASAPAddrTable Level 2: rserpoolPEASAPAddrTable
rserpoolPEUserAddrTable rserpoolPEUserAddrTable
5.3. Access to managed objects on Pool Users 5.3. Access to Managed Objects on Pool Users
For the pool users branch, it is only necessary to list the pool user For the Pool Users branch, it is only necessary to list the pool user
instances, including their operation scope and pool handle. instances, including their operation scope and pool handle.
5.4. Persistency Behavior 5.4. Persistency Behavior
Upon changes of writable objects, an implementation SHOULD store the Upon changes of writable objects, an implementation SHOULD store the
new values in a persistent manner if it has the capability to do new values in a persistent manner if it has the capability to do
this. An implementation SHOULD use these stored values upon reset or this. An implementation SHOULD use these stored values upon reset or
reinitialization. reinitialization.
6. Definitions 6. Definitions
skipping to change at page 12, line 21 skipping to change at page 11, line 35
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InetAddressType, InetAddress, InetPortNumber InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
-- ## Module definition ########################################### -- ## Module definition ###########################################
rserpoolMIB MODULE-IDENTITY rserpoolMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200903071111Z" -- March 07, 2009 "200904070000Z" -- April 07, 2009
ORGANIZATION ORGANIZATION
"IEM-TdR, UNIVERSITY OF DUISBURG-ESSEN" "IEM-TdR, UNIVERSITY OF DUISBURG-ESSEN"
CONTACT-INFO CONTACT-INFO
" THOMAS-DREIBHOLZ " THOMAS-DREIBHOLZ
Postal: University of Duisburg-Essen Postal: University of Duisburg-Essen
Institute for Experimental Mathematics Institute for Experimental Mathematics
Ellernstrasse 29 Ellernstrasse 29
D-45326 Essen D-45326 Essen
Germany Germany
skipping to change at page 12, line 50 skipping to change at page 12, line 18
1200 N. DuPont Hw 1200 N. DuPont Hw
Dover, DE Dover, DE
USA 19904 USA 19904
Phone: +1-302-857-7910 Phone: +1-302-857-7910
Fax: +1-302-857-6552 Fax: +1-302-857-6552
Email: jaiwant@mulik.com" Email: jaiwant@mulik.com"
DESCRIPTION DESCRIPTION
"The MIB module for managing an RSerPool implementation. "The MIB module for managing an RSerPool implementation.
Copyright (c) 2009 IETF Trust and the persons identified as Copyright (c) 2009 IETF Trust and the persons identified as
authors of RFC XXXX. authors of the code. All rights reserved.
This version of this MIB module is part of RFC XXXX; see the
RFC itself for full legal notices." Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the
following conditions are met:
- Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
- Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
- Neither the name of Internet Society, IETF or IETF Trust,
nor the names of specific contributors, may be used to
endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
This version of this MIB module is part of RFC 5525;
see the RFC itself for full legal notices."
REVISION REVISION
"200903071111Z" -- March 07, 2009 "200904070000Z" -- April 07, 2009
DESCRIPTION DESCRIPTION
"This version of the MIB module is published as RFC XXXX" "This version of the MIB module is published as RFC 5525"
::= { experimental XXX } -- To be IANA Assigned!!! ::= { experimental 125 }
-- ## RSerPool type definitions ################################### -- ## RSerPool type definitions ###################################
RSerPoolENRPServerIdentifierTC ::= TEXTUAL-CONVENTION RSerPoolENRPServerIdentifierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "x" DISPLAY-HINT "x"
STATUS current STATUS current
DESCRIPTION "The ID of an ENRP server" DESCRIPTION "The ID of an ENRP server"
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
RSerPoolOperationScopeTC ::= TEXTUAL-CONVENTION RSerPoolOperationScopeTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1024t" DISPLAY-HINT "1024t"
skipping to change at page 16, line 7 skipping to change at page 16, line 10
"The ENRP server identifier of this ENRP server." "The ENRP server identifier of this ENRP server."
REFERENCE REFERENCE
"Section 3.1 of RFC 5351 explains the ENRP server identifier." "Section 3.1 of RFC 5351 explains the ENRP server identifier."
::= { rserpoolENRPEntry 3 } ::= { rserpoolENRPEntry 3 }
rserpoolENRPDescription OBJECT-TYPE rserpoolENRPDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of this ENRP server, e.g. its location "A textual description of this ENRP server, e.g., its location
and a contact address of its administrator. and a contact address of its administrator.
This object SHOULD be maintained in a persistent manner." This object SHOULD be maintained in a persistent manner."
::= { rserpoolENRPEntry 4 } ::= { rserpoolENRPEntry 4 }
rserpoolENRPUptime OBJECT-TYPE rserpoolENRPUptime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ENRP service uptime of this ENRP server." "The ENRP service uptime of this ENRP server."
::= { rserpoolENRPEntry 5 } ::= { rserpoolENRPEntry 5 }
rserpoolENRPPort OBJECT-TYPE rserpoolENRPPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SCTP port number of the ENRP protocol endpoint of "The Stream Control Transmission Protocol (SCTP) port number of
this ENRP server." the ENRP protocol endpoint of this ENRP server."
REFERENCE REFERENCE
"RFC 5353 defines the ENRP protocol." "RFC 5353 defines the ENRP protocol."
::= { rserpoolENRPEntry 6 } ::= { rserpoolENRPEntry 6 }
rserpoolENRPASAPAnnouncePort OBJECT-TYPE rserpoolENRPASAPAnnouncePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination UDP port number ASAP multicast announce "The destination UDP port number to which ASAP multicast announce
messages are sent to." messages are sent."
REFERENCE REFERENCE
"Section 3.2 of RFC 5351 explains the server discovery mechanism "Section 3.2 of RFC 5351 explains the server-discovery mechanism
using ASAP announces." using ASAP announces."
::= { rserpoolENRPEntry 7 } ::= { rserpoolENRPEntry 7 }
rserpoolENRPASAPAnnounceAddrType OBJECT-TYPE rserpoolENRPASAPAnnounceAddrType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network-layer protocol ASAP multicast announce messages "The network-layer protocol over which ASAP multicast announce
are sent over." messages are sent."
REFERENCE REFERENCE
"Section 3.2 of RFC 5351 explains the server discovery mechanism "Section 3.2 of RFC 5351 explains the server-discovery mechanism
using ASAP announces." using ASAP announces."
::= { rserpoolENRPEntry 8 } ::= { rserpoolENRPEntry 8 }
rserpoolENRPASAPAnnounceAddr OBJECT-TYPE rserpoolENRPASAPAnnounceAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE(4|16)) SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination IP multicast address ASAP multicast "The destination IP multicast address to which ASAP multicast
announce messages are sent to. The type of this address is announce messages are sent. The type of this address is
given in rserpoolENRPASAPAnnounceAddrType." given in rserpoolENRPASAPAnnounceAddrType."
REFERENCE REFERENCE
"Section 3.2 of RFC 5351 explains the server discovery mechanism "Section 3.2 of RFC 5351 explains the server-discovery mechanism
using ASAP announces." using ASAP announces."
::= { rserpoolENRPEntry 9 } ::= { rserpoolENRPEntry 9 }
rserpoolENRPENRPAnnouncePort OBJECT-TYPE rserpoolENRPENRPAnnouncePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination UDP port number ENRP multicast announce "The destination UDP port number to which ENRP multicast announce
messages are sent to." messages are sent."
REFERENCE REFERENCE
"Section 3.1 of RFC 5353 explains the ENRP multicast "Section 3.1 of RFC 5353 explains the ENRP multicast
announce mechanism." announce mechanism."
::= { rserpoolENRPEntry 10 } ::= { rserpoolENRPEntry 10 }
rserpoolENRPENRPAnnounceAddrType OBJECT-TYPE rserpoolENRPENRPAnnounceAddrType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network-layer protocol ENRP multicast announce messages "The network-layer protocol over which ENRP multicast announce
are sent over." messages are sent."
REFERENCE REFERENCE
"Section 3.1 of RFC 5353 explains the ENRP multicast "Section 3.1 of RFC 5353 explains the ENRP multicast
announce mechanism." announce mechanism."
::= { rserpoolENRPEntry 11 } ::= { rserpoolENRPEntry 11 }
rserpoolENRPENRPAnnounceAddr OBJECT-TYPE rserpoolENRPENRPAnnounceAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE(4|16)) SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination multicast IP address ENRP multicast "The destination multicast IP address to which ENRP multicast
announce messages are sent to. The type of this address announce messages are sent. The type of this address
is given in rserpoolENRPENRPAnnounceAddrType." is given in rserpoolENRPENRPAnnounceAddrType."
REFERENCE REFERENCE
"Section 3.1 of RFC 5353 explains the ENRP multicast "Section 3.1 of RFC 5353 explains the ENRP multicast
announce mechanism." announce mechanism."
::= { rserpoolENRPEntry 12 } ::= { rserpoolENRPEntry 12 }
-- ## Definition of the pool table ################################ -- ## Definition of the pool table ################################
rserpoolENRPPoolTable OBJECT-TYPE rserpoolENRPPoolTable OBJECT-TYPE
SYNTAX SEQUENCE OF RserpoolENRPPoolEntry SYNTAX SEQUENCE OF RserpoolENRPPoolEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 19, line 48 skipping to change at page 20, line 7
rserpoolENRPRegistrationLife TimeTicks, rserpoolENRPRegistrationLife TimeTicks,
rserpoolENRPHomeENRPServer RSerPoolENRPServerIdentifierTC } rserpoolENRPHomeENRPServer RSerPoolENRPServerIdentifierTC }
rserpoolENRPPoolElementIndex OBJECT-TYPE rserpoolENRPPoolElementIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer to uniquely identify a pool element. Note, "An integer to uniquely identify a pool element. Note,
that uniqueness of a pool element identifier in the pool that uniqueness of a pool element identifier in the pool
is not enforced, therefore this index is required here!" is not enforced; therefore, this index is required here!"
::={ rserpoolENRPPoolElementEntry 1 } ::={ rserpoolENRPPoolElementEntry 1 }
rserpoolENRPPoolElementID OBJECT-TYPE rserpoolENRPPoolElementID OBJECT-TYPE
SYNTAX RserpoolPoolElementIdentifierTC SYNTAX RserpoolPoolElementIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The pool element identifier of this pool element." "The pool element identifier of this pool element."
REFERENCE REFERENCE
"Section 2.2 of RFC 5351 explains the pool element identifier "Section 2.2 of RFC 5351 explains the pool element identifier
skipping to change at page 22, line 36 skipping to change at page 22, line 44
"The registration life of this pool element." "The registration life of this pool element."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the Registration Life." "Section 3.10 of RFC 5354 defines the Registration Life."
::= { rserpoolENRPPoolElementEntry 12 } ::= { rserpoolENRPPoolElementEntry 12 }
rserpoolENRPHomeENRPServer OBJECT-TYPE rserpoolENRPHomeENRPServer OBJECT-TYPE
SYNTAX RSerPoolENRPServerIdentifierTC SYNTAX RSerPoolENRPServerIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ID of the home ENRP server of this pool element." "The ID of the Home ENRP server of this pool element."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the Home ENRP Server "Section 3.10 of RFC 5354 defines the Home ENRP Server
Identifier." Identifier."
::= { rserpoolENRPPoolElementEntry 13 } ::= { rserpoolENRPPoolElementEntry 13 }
-- ## Definition of the ASAP transport address list table ######### -- ## Definition of the ASAP transport address list table #########
rserpoolENRPASAPAddrTable OBJECT-TYPE rserpoolENRPASAPAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF RserpoolENRPASAPAddrTableEntry SYNTAX SEQUENCE OF RserpoolENRPASAPAddrTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 25, line 7 skipping to change at page 25, line 12
rserpoolENRPUserAddrTableIndex Unsigned32, rserpoolENRPUserAddrTableIndex Unsigned32,
rserpoolENRPUserL3Type InetAddressType, rserpoolENRPUserL3Type InetAddressType,
rserpoolENRPUserL3Addr InetAddress, rserpoolENRPUserL3Addr InetAddress,
rserpoolENRPUserL3Opaque RSerPoolOpaqueAddressTC } rserpoolENRPUserL3Opaque RSerPoolOpaqueAddressTC }
rserpoolENRPUserAddrTableIndex OBJECT-TYPE rserpoolENRPUserAddrTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier for the IP address of an user transport "A unique identifier for the IP address of a user transport
endpoint." endpoint."
::= { rserpoolENRPUserAddrTableEntry 1 } ::= { rserpoolENRPUserAddrTableEntry 1 }
rserpoolENRPUserL3Type OBJECT-TYPE rserpoolENRPUserL3Type OBJECT-TYPE
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network-layer protocol (IPv4 or IPv6) of an IP address "The network-layer protocol (IPv4 or IPv6) of an IP address
of an user transport endpoint. Set to unknown for opaque address." of a user transport endpoint. Set to unknown for an opaque
address."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the User Transport Parameter of "Section 3.10 of RFC 5354 defines the User Transport Parameter of
which the network-layer protocol number is given here." which the network-layer protocol number is given here."
::= { rserpoolENRPUserAddrTableEntry 2 } ::= { rserpoolENRPUserAddrTableEntry 2 }
rserpoolENRPUserL3Addr OBJECT-TYPE rserpoolENRPUserL3Addr OBJECT-TYPE
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of an user transport endpoint. The type of "The IP address of a user transport endpoint. The type of
this address is given in rserpoolENRPUserL3Type." this address is given in rserpoolENRPUserL3Type."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the User Transport Parameter of "Section 3.10 of RFC 5354 defines the User Transport Parameter of
which the network-layer address (IPv4 or IPv6) is given here." which the network-layer address (IPv4 or IPv6) is given here."
::= { rserpoolENRPUserAddrTableEntry 3 } ::= { rserpoolENRPUserAddrTableEntry 3 }
rserpoolENRPUserL3Opaque OBJECT-TYPE rserpoolENRPUserL3Opaque OBJECT-TYPE
SYNTAX RSerPoolOpaqueAddressTC SYNTAX RSerPoolOpaqueAddressTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The opaque address of an user transport endpoint." "The opaque address of a user transport endpoint."
REFERENCE REFERENCE
"Section 3.16 of RFC 5354 defines the opaque transport address." "Section 3.16 of RFC 5354 defines the opaque transport address."
::= { rserpoolENRPUserAddrTableEntry 4 } ::= { rserpoolENRPUserAddrTableEntry 4 }
-- ## Definition of ENRP address list table ####################### -- ## Definition of ENRP address list table #######################
rserpoolENRPENRPAddrTable OBJECT-TYPE rserpoolENRPENRPAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF RserpoolENRPENRPAddrTableEntry SYNTAX SEQUENCE OF RserpoolENRPENRPAddrTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 30, line 37 skipping to change at page 30, line 40
rserpoolPERegistrationLife TimeTicks, rserpoolPERegistrationLife TimeTicks,
rserpoolPEHomeENRPServer RSerPoolENRPServerIdentifierTC } rserpoolPEHomeENRPServer RSerPoolENRPServerIdentifierTC }
rserpoolPEIndex OBJECT-TYPE rserpoolPEIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer to uniquely identify a pool element. Note, "An integer to uniquely identify a pool element. Note,
that uniqueness of a pool element identifier in the pool that uniqueness of a pool element identifier in the pool
is not enforced, therefore this index is required here!" is not enforced; therefore, this index is required here!"
::={ rserpoolPEEntry 1 } ::={ rserpoolPEEntry 1 }
rserpoolPEOperationScope OBJECT-TYPE rserpoolPEOperationScope OBJECT-TYPE
SYNTAX RSerPoolOperationScopeTC SYNTAX RSerPoolOperationScopeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operation scope of this pool element." "The operation scope of this pool element."
REFERENCE REFERENCE
"Section 1.2 of RFC 3237 defines the term operation scope." "Section 1.2 of RFC 3237 defines the term operation scope."
skipping to change at page 31, line 32 skipping to change at page 31, line 34
"The pool element identifier of this pool element." "The pool element identifier of this pool element."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the pool element identifier." "Section 3.10 of RFC 5354 defines the pool element identifier."
::={ rserpoolPEEntry 4 } ::={ rserpoolPEEntry 4 }
rserpoolPEDescription OBJECT-TYPE rserpoolPEDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of this pool element, e.g. its location "A textual description of this pool element, e.g., its location
and a contact address of its administrator. and a contact address of its administrator.
This object SHOULD be maintained in a persistent manner." This object SHOULD be maintained in a persistent manner."
::= { rserpoolPEEntry 5 } ::= { rserpoolPEEntry 5 }
rserpoolPEUptime OBJECT-TYPE rserpoolPEUptime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 34, line 33 skipping to change at page 34, line 40
This object SHOULD be maintained in a persistent manner." This object SHOULD be maintained in a persistent manner."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the Registration Life." "Section 3.10 of RFC 5354 defines the Registration Life."
::= { rserpoolPEEntry 16 } ::= { rserpoolPEEntry 16 }
rserpoolPEHomeENRPServer OBJECT-TYPE rserpoolPEHomeENRPServer OBJECT-TYPE
SYNTAX RSerPoolENRPServerIdentifierTC SYNTAX RSerPoolENRPServerIdentifierTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ID of the home ENRP server of this pool element." "The ID of the Home ENRP server of this pool element."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the Home ENRP Server "Section 3.10 of RFC 5354 defines the Home ENRP Server
Identifier." Identifier."
::= { rserpoolPEEntry 17 } ::= { rserpoolPEEntry 17 }
-- ## Definition of the ASAP transport address list table ######### -- ## Definition of the ASAP transport address list table #########
rserpoolPEASAPAddrTable OBJECT-TYPE rserpoolPEASAPAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF RserpoolPEASAPAddrTableEntry SYNTAX SEQUENCE OF RserpoolPEASAPAddrTableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 36, line 46 skipping to change at page 37, line 6
rserpoolPEUserAddrTableIndex Unsigned32, rserpoolPEUserAddrTableIndex Unsigned32,
rserpoolPEUserL3Type InetAddressType, rserpoolPEUserL3Type InetAddressType,
rserpoolPEUserL3Addr InetAddress, rserpoolPEUserL3Addr InetAddress,
rserpoolPEUserL3Opaque RSerPoolOpaqueAddressTC } rserpoolPEUserL3Opaque RSerPoolOpaqueAddressTC }
rserpoolPEUserAddrTableIndex OBJECT-TYPE rserpoolPEUserAddrTableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier for the IP address of an user transport "A unique identifier for the IP address of a user transport
endpoint." endpoint."
::= { rserpoolPEUserAddrTableEntry 1 } ::= { rserpoolPEUserAddrTableEntry 1 }
rserpoolPEUserL3Type OBJECT-TYPE rserpoolPEUserL3Type OBJECT-TYPE
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network-layer protocol of an IP address of an user transport "The network-layer protocol of an IP address of a user transport
endpoint. Set to unknown for opaque address." endpoint. Set to unknown for opaque address."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the User Transport Parameter of "Section 3.10 of RFC 5354 defines the User Transport Parameter of
which the network-layer protocol number is given here." which the network-layer protocol number is given here."
::= { rserpoolPEUserAddrTableEntry 2 } ::= { rserpoolPEUserAddrTableEntry 2 }
rserpoolPEUserL3Addr OBJECT-TYPE rserpoolPEUserL3Addr OBJECT-TYPE
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of an user transport endpoint. The type of "The IP address of a user transport endpoint. The type of
this address is given in rserpoolPEUserL3Addr." this address is given in rserpoolPEUserL3Addr."
REFERENCE REFERENCE
"Section 3.10 of RFC 5354 defines the User Transport Parameter of "Section 3.10 of RFC 5354 defines the User Transport Parameter of
which the network-layer address (IPv4 or IPv6) is given here." which the network-layer address (IPv4 or IPv6) is given here."
::= { rserpoolPEUserAddrTableEntry 3 } ::= { rserpoolPEUserAddrTableEntry 3 }
rserpoolPEUserL3Opaque OBJECT-TYPE rserpoolPEUserL3Opaque OBJECT-TYPE
SYNTAX RSerPoolOpaqueAddressTC SYNTAX RSerPoolOpaqueAddressTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The opaque address of an user transport endpoint." "The opaque address of a user transport endpoint."
REFERENCE REFERENCE
"Section 3.16 of RFC 5354 defines the opaque transport address." "Section 3.16 of RFC 5354 defines the opaque transport address."
::= { rserpoolPEUserAddrTableEntry 4 } ::= { rserpoolPEUserAddrTableEntry 4 }
-- ################################################################ -- ################################################################
-- #### Pool Users Section #### -- #### Pool Users Section ####
-- ################################################################ -- ################################################################
-- ## Definition of the pool user table ########################### -- ## Definition of the pool user table ###########################
rserpoolPUTable OBJECT-TYPE rserpoolPUTable OBJECT-TYPE
skipping to change at page 39, line 10 skipping to change at page 39, line 19
This object SHOULD be maintained in a persistent manner." This object SHOULD be maintained in a persistent manner."
REFERENCE REFERENCE
"Section 1.2 of RFC 3237 defines the term pool handle." "Section 1.2 of RFC 3237 defines the term pool handle."
::={ rserpoolPUEntry 3 } ::={ rserpoolPUEntry 3 }
rserpoolPUDescription OBJECT-TYPE rserpoolPUDescription OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of this pool user, e.g. its location "A textual description of this pool user, e.g., its location
and a contact address of its administrator. and a contact address of its administrator.
This object SHOULD be maintained in a persistent manner." This object SHOULD be maintained in a persistent manner."
::= { rserpoolPUEntry 4 } ::= { rserpoolPUEntry 4 }
rserpoolPUUptime OBJECT-TYPE rserpoolPUUptime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 36 skipping to change at page 39, line 45
rserpoolMIBConformance 1 rserpoolMIBConformance 1
} }
rserpoolMIBGroups OBJECT IDENTIFIER ::= { rserpoolMIBGroups OBJECT IDENTIFIER ::= {
rserpoolMIBConformance 2 rserpoolMIBConformance 2
} }
rserpoolMIBCompliance MODULE-COMPLIANCE rserpoolMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
RSerPool." RSerPool."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
rserpoolENRPGroup, rserpoolENRPGroup,
rserpoolPEGroup, rserpoolPEGroup,
rserpoolPUGroup } rserpoolPUGroup }
::= { rserpoolMIBCompliances 1 } ::= { rserpoolMIBCompliances 1 }
rserpoolENRPGroup OBJECT-GROUP rserpoolENRPGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 41, line 47 skipping to change at page 42, line 7
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group contains all pool user instances "The group contains all pool user instances
running on the system" running on the system"
::= { rserpoolMIBGroups 3 } ::= { rserpoolMIBGroups 3 }
END END
7. Operational Considerations 7. Operational Considerations
The RSerPool MIB is an experimental track MIB module, since the The RSerPool MIB is an Experimental track MIB module, since the
RSerPool documents are Experimental RFCs. RSerPool documents are Experimental RFCs.
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
skipping to change at page 43, line 32 skipping to change at page 43, line 41
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.
9. IANA Considerations 9. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER Value Descriptor OBJECT IDENTIFIER Value
---------- ----------------------- ---------- -----------------------
rserpoolMIB { experimental XXX } rserpoolMIB { experimental 125 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for XXX under the experimental subtree
and to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace XXX
(here and in the MIB module) with the assigned value and to remove
this note.
10. Acknowledgments 10. Acknowledgments
The authors would like to express a special note of thanks to Phillip The authors would like to express a special note of thanks to Phillip
Conrad and Kevin Pinzhoffer for their efforts in the early formation Conrad and Kevin Pinzhoffer for their efforts in the early formation
of this draft. Furthermore, the authors would like to thank Bert of this document. Furthermore, the authors would like to thank Bert
Wijnen and Dan Romascanu for their valuable comments on this Wijnen and Dan Romascanu for their valuable comments on this
document. Finally, the authors would like to thank Nihad Cosic, Dirk document. Finally, the authors would like to thank Nihad Cosic, Dirk
Hoffstadt, Michael Kohnen, Jobin Pulinthanath, Randall Stewart, Hoffstadt, Michael Kohnen, Jobin Pulinthanath, Randall Stewart,
Michael Tuexen and Xing Zhou for their support. Michael Tuexen, and Xing Zhou for their support.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet
Addresses", RFC 4001, February 2005. Network Addresses", RFC 4001, February 2005.
[RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, [RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP)", RFC 5352, "Aggregate Server Access Protocol (ASAP)", RFC 5352,
September 2008. September 2008.
[RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. [RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and
Silverton, "Endpoint Handlespace Redundancy Protocol A. Silverton, "Endpoint Handlespace Redundancy
(ENRP)", RFC 5353, September 2008. Protocol (ENRP)", RFC 5353, September 2008.
[RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, [RFC5354] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP) and Endpoint "Aggregate Server Access Protocol (ASAP) and Endpoint
Handlespace Redundancy Protocol (ENRP) Parameters", Handlespace Redundancy Protocol (ENRP) Parameters",
RFC 5354, September 2008. RFC 5354, September 2008.
[RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling [RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling
Policies", RFC 5356, September 2008. Policies", RFC 5356, September 2008.
11.2. Informative References 11.2. Informative References
[RFC3237] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., [RFC3237] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L.,
Loughney, J., and M. Stillman, "Requirements for Reliable Loughney, J., and M. Stillman, "Requirements for
Server Pooling", RFC 3237, January 2002. Reliable Server Pooling", RFC 3237, January 2002.
[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- "Introduction and Applicability Statements for
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An [RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An
Overview of Reliable Server Pooling Protocols", RFC 5351, Overview of Reliable Server Pooling Protocols",
September 2008. RFC 5351, September 2008.
[RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S.,
Holdrege, "Threats Introduced by Reliable Server Pooling and M. Holdrege, "Threats Introduced by Reliable
(RSerPool) and Requirements for Security in Response to Server Pooling (RSerPool) and Requirements for
Threats", RFC 5355, September 2008. Security in Response to Threats", RFC 5355,
September 2008.
[Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, [Dre2006] Dreibholz, T., "Reliable Server Pooling --
Optimization and Extension of a Novel IETF Architecture", Evaluation, Optimization and Extension of a Novel
Ph.D. Thesis University of Duisburg-Essen, Faculty of IETF Architecture", Ph.D. Thesis University of
Economics, Institute for Computer Science and Business Duisburg-Essen, Faculty of Economics, Institute for
Information Systems, URL: http:// Computer Science and Business Information Systems,
duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ March 2007, <http://duepublico.uni-duisburg-essen.de/
Derivate-16326/Dre2006-final.pdf, March 2007. servlets/DerivateServlet/Derivate-16326/
Dre2006-final.pdf>.
[LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of
Reliable Server Pooling Systems", Proceedings of the 30th Reliable Server Pooling Systems", Proceedings of the
IEEE Local Computer Networks Conference, November 2005. 30th IEEE Local Computer Networks Conference,
November 2005.
[IJHIT2008] [IJHIT2008] Dreibholz, T. and E. Rathgeb, "An Evaluation of the
Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool Pool Maintenance Overhead in Reliable Server Pooling
Maintenance Overhead in Reliable Server Pooling Systems", Systems", International Journal of Hybrid Information
International Journal of Hybrid Information Technology Technology (IJHIT) Volume 1, Number 2, April 2008.
(IJHIT) Volume 1, Number 2, April 2008.
[RSerPoolPage] [RSerPoolPage] Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
Dreibholz, T., "Thomas Dreibholz's RSerPool Page", <http://tdrwww.iem.uni-due.de/dreibholz/rserpool/>.
URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/.
[SNMPMIBS] [SNMPMIBS] Perkins, D. and E. McGinnis, "Understanding SNMP
Perkins, D. and E. McGinnis, "Understanding SNMP MIBs", MIBs", 1997.
1997.
Authors' Addresses Authors' Addresses
Thomas Dreibholz Thomas Dreibholz
University of Duisburg-Essen, Institute for Experimental Mathematics University of Duisburg-Essen, Institute for Experimental Mathematics
Ellernstrasse 29 Ellernstrasse 29
45326 Essen, Nordrhein-Westfalen 45326 Essen, Nordrhein-Westfalen
Germany Germany
Phone: +49-201-1837637 Phone: +49-201-1837637
Fax: +49-201-1837673 Fax: +49-201-1837673
Email: dreibh@iem.uni-due.de EMail: dreibh@iem.uni-due.de
URI: http://www.iem.uni-due.de/~dreibh/ URI: http://www.iem.uni-due.de/~dreibh/
Jaiwant Mulik Jaiwant Mulik
Delaware State University Delaware State University
CIS Department CIS Department
Room 306A, Science Center North Room 306A, Science Center North
1200 N. DuPont Hwy 1200 N. DuPont Hwy
Dover, DE 19904 Dover, DE 19904
USA USA
Phone: +1-302-857-7910 Phone: +1-302-857-7910
Fax: +1-302-857-6552 Fax: +1-302-857-6552
Email: jaiwant@mulik.com EMail: jaiwant@mulik.com
URI: http://netlab.cis.desu.edu URI: http://netlab.cis.desu.edu
 End of changes. 68 change blocks. 
178 lines changed or deleted 198 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/