draft-ietf-rserpool-mib-08.txt   draft-ietf-rserpool-mib-09.txt 
Network Working Group T. Dreibholz Network Working Group T. Dreibholz
Internet-Draft University of Duisburg-Essen Internet-Draft University of Duisburg-Essen
Intended status: Standards Track J. Mulik Intended status: Experimental J. Mulik
Expires: May 21, 2009 Delaware State University Expires: July 10, 2009 Delaware State University
November 17, 2008 January 6, 2009
Reliable Server Pooling: Management Information Base using SMIv2 Reliable Server Pooling: Management Information Base using SMIv2
draft-ietf-rserpool-mib-08.txt draft-ietf-rserpool-mib-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 The list of current Internet-Drafts can be accessed at
http://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 May 21, 2009. This Internet-Draft will expire on July 10, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
RSerPool [RFC5351] is a framework to provide reliable server pooling. RSerPool [RFC5351] 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 objects in an RSerPool (MIB) providing access to managed objects in an RSerPool
implementation. implementation.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3 2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 2, line 11 skipping to change at page 2, line 15
This document defines a SMIv2 compliant Management Information Base This document defines a SMIv2 compliant Management Information Base
(MIB) providing access to managed objects in an RSerPool (MIB) providing access to managed objects in an RSerPool
implementation. implementation.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3 2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3
4.1. Access to managed objects on ENRP servers . . . . . . . . 9 4.1. Access to managed objects on ENRP servers . . . . . . . . 10
4.2. Access to managed objects on Pool Elements . . . . . . . . 11 4.2. Access to managed objects on Pool Elements . . . . . . . . 11
4.3. Access to managed objects on Pool Users . . . . . . . . . 11 4.3. Access to managed objects on Pool Users . . . . . . . . . 11
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 37 6. Security Considerations . . . . . . . . . . . . . . . . . . . 37
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.1. Normative References . . . . . . . . . . . . . . . . . . . 37 9.1. Normative References . . . . . . . . . . . . . . . . . . . 37
9.2. Informative References . . . . . . . . . . . . . . . . . . 38 9.2. Informative References . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
Intellectual Property and Copyright Statements . . . . . . . . . . 41
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. 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]. [RSerPoolPage] as well as in [Dre2006], [LCN2005] and [IJHIT2008].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 7, line 5 skipping to change at page 7, line 5
| | +-- ---- Unsigned enrpServerPeerIndex(1) | | +-- ---- Unsigned enrpServerPeerIndex(1)
| | | Range: 1..-1 | | | Range: 1..-1
| | +-- -R-- Unsigned enrpServerPeerIdentifier(2) | | +-- -R-- Unsigned enrpServerPeerIdentifier(2)
| | +-- -R-- Unsigned enrpServerPeerPort(3) | | +-- -R-- Unsigned enrpServerPeerPort(3)
| | | Range: 1..65535 | | | Range: 1..65535
| | +-- -R-- TimeTicks enrpServerPeerLastHeard(4) | | +-- -R-- TimeTicks enrpServerPeerLastHeard(4)
| | | |
| +--enrpServerPeerAddrTable(9) | +--enrpServerPeerAddrTable(9)
| | | |
| +--enrpServerPeerAddrTableEntry(1) | +--enrpServerPeerAddrTableEntry(1)
| | Index: enrpServerPeerIndex, enrpServerPeerAddrTableIndex | | Index: enrpServerPeerIndex,
| | enrpServerPeerAddrTableIndex
| | | |
| +-- ---- Unsigned enrpServerPeerAddrTableIndex(1) | +-- ---- Unsigned enrpServerPeerAddrTableIndex(1)
| | Range: 1..-1 | | Range: 1..-1
| +-- -R-- EnumVal enrpServerPeerL3Proto(2) | +-- -R-- EnumVal enrpServerPeerL3Proto(2)
| | Textual Convention: InetAddressType | | Textual Convention: InetAddressType
| | Values: unknown(0), ipv4(1), ipv6(2), ipv4z(3), | | Values: unknown(0), ipv4(1), ipv6(2), ipv4z(3),
| | | ipv6z(4), dns(16) | | | ipv6z(4), dns(16)
| +-- -R-- String enrpServerPeerL3Addr(3) | +-- -R-- String enrpServerPeerL3Addr(3)
| Textual Convention: InetAddress | Textual Convention: InetAddress
| Size: 0..255 | Size: 0..255
skipping to change at page 11, line 34 skipping to change at page 11, line 38
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:
Level 1: poolElementTable Level 1: poolElementTable
Level 2: poolElementASAPAddrListTable Level 2: poolElementASAPAddrListTable
poolElementUserAddrListTable poolElementUserAddrListTable
The description of the contained structures is the same as for the The description of the contained structures is the same as for the
ENRP servers branch. ENRP servers branch.
TODO: There should be the server table (ENRP servers learned by their
announces) plus the multicast address the PE expects the announces to
be sent to.
4.3. Access to managed objects on Pool Users 4.3. Access to managed objects on Pool Users
For the pool users branch, it is only necessary to list the pool For the pool users branch, it is only necessary to list the pool
users, including their operation scope and pool handle. users, including their operation scope and pool handle.
TODO: There should be the server table (ENRP servers learned by their
announces) plus the multicast address the PE expects the announces to
be sent to.
5. Definitions 5. Definitions
RSERPOOL-MIB DEFINITIONS ::= BEGIN RSERPOOL-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, mib-2,
TimeTicks, TimeTicks,
Unsigned32 Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
skipping to change at page 12, line 20 skipping to change at page 12, line 17
FROM SNMPv2-SMI FROM SNMPv2-SMI
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 InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
-- ## Module definition ########################################### -- ## Module definition ###########################################
rserpoolMIB MODULE-IDENTITY rserpoolMIB MODULE-IDENTITY
LAST-UPDATED "200811131012Z" -- November 13, 2008 LAST-UPDATED "200901061012Z" -- January 06, 2009
ORGANIZATION "IEM-TdR, UNIVERSITY OF DUISBURG-ESSEN" ORGANIZATION "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
Phone: +49-201-183-7637 Phone: +49-201-183-7637
skipping to change at page 12, line 46 skipping to change at page 12, line 43
Postal: Delaware State University Postal: Delaware State University
CIS Department CIS Department
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 a RSerPool implementation" "The MIB module for managing a RSerPool implementation"
REVISION "200811131012Z" -- November 13, 2008 REVISION "200901061012Z" -- January 06, 2009
DESCRIPTION DESCRIPTION
"Version 08, published as draft-ietf-rserpool-mib-08.txt." "Version 09, published as draft-ietf-rserpool-mib-09.txt."
::= { mib-2 xxxxxxxx } -- To be IANA Assigned!!! ::= { mib-2 xxxxxxxx } -- To be IANA Assigned!!!
-- ## RSerPool type definitions ################################### -- ## RSerPool type definitions ###################################
ENRPServerIdentifierType ::= TEXTUAL-CONVENTION ENRPServerIdentifierType ::= 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)
OperationScopeType ::= TEXTUAL-CONVENTION OperationScopeType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1024t"
STATUS current STATUS current
DESCRIPTION "The ID of an operation scope" DESCRIPTION "The ID of an operation scope"
SYNTAX OCTET STRING SYNTAX OCTET STRING
PoolHandleType ::= TEXTUAL-CONVENTION PoolHandleType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1024t"
STATUS current STATUS current
DESCRIPTION "The pool handle" DESCRIPTION "The pool handle"
SYNTAX OCTET STRING SYNTAX OCTET STRING
PoolElementIdentifierType ::= TEXTUAL-CONVENTION PoolElementIdentifierType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "x" DISPLAY-HINT "x"
STATUS current STATUS current
DESCRIPTION "The pool element ID" DESCRIPTION "The pool element ID"
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
skipping to change at page 14, line 4 skipping to change at page 14, line 5
DESCRIPTION "The weight of a pool element" DESCRIPTION "The weight of a pool element"
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
TransportUseType ::= TEXTUAL-CONVENTION TransportUseType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The load status of a pool element" DESCRIPTION "The load status of a pool element"
SYNTAX INTEGER { SYNTAX INTEGER {
dataOnly(0), dataOnly(0),
dataPlusControl(1) dataPlusControl(1)
} }
OpaqueAddressType ::= TEXTUAL-CONVENTION OpaqueAddressType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1024t"
STATUS current STATUS current
DESCRIPTION "Opaque address" DESCRIPTION "Opaque address"
SYNTAX OCTET STRING SYNTAX OCTET STRING
-- ## Top-level definitions ####################################### -- ## Top-level definitions #######################################
enrpServers OBJECT IDENTIFIER ::= { rserpoolMIB 1 } enrpServers OBJECT IDENTIFIER ::= { rserpoolMIB 1 }
poolElements OBJECT IDENTIFIER ::= { rserpoolMIB 2 } poolElements OBJECT IDENTIFIER ::= { rserpoolMIB 2 }
poolUsers OBJECT IDENTIFIER ::= { rserpoolMIB 3 } poolUsers OBJECT IDENTIFIER ::= { rserpoolMIB 3 }
-- ################################################################ -- ################################################################
skipping to change at page 37, line 14 skipping to change at page 37, line 19
6. Security Considerations 6. 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), there is no control as itself is secure (for example by using IPSec), there is no control as
to who on the secure network is allowed to access and GET/SET (read/ to who on the secure network is allowed to access and GET/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 [RFC2574] and the View- of the User-based Security Model RFC 3414 [RFC3414] and the View-
based Access Control Model RFC 2575 [RFC2575] is recommended. based Access Control Model RFC 3415 [RFC3415] 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.
7. IANA Considerations 7. 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.
skipping to change at page 38, line 22 skipping to change at page 38, line 31
RFC 5354, September 2008. RFC 5354, September 2008.
[RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M. [RFC5355] Stillman, M., Gopal, R., Guttman, E., Sengodan, S., and M.
Holdrege, "Threats Introduced by Reliable Server Pooling Holdrege, "Threats Introduced by Reliable Server Pooling
(RSerPool) and Requirements for Security in Response to (RSerPool) and Requirements for Security in Response to
Threats", RFC 5355, September 2008. Threats", RFC 5355, 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.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", STD 62, RFC 3415,
December 2002.
[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 Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 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.
[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 Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
9.2. Informative References 9.2. Informative References
[RSerPoolPage] [RSerPoolPage]
Dreibholz, T., "Thomas Dreibholz's RSerPool Page", URL: Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/. URL: http://tdrwww.iem.uni-due.de.de/dreibholz/rserpool/.
[Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation, [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation,
Optimization and Extension of a Novel IETF Architecture", Optimization and Extension of a Novel IETF Architecture",
Ph.D. Thesis University of Duisburg-Essen, Faculty of Ph.D. Thesis University of Duisburg-Essen, Faculty of
Economics, Institute for Computer Science and Business Economics, Institute for Computer Science and Business
Information Systems, URL: http:// Information Systems, URL: http://
duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/ duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/
Derivate-16326/Dre2006-final.pdf, March 2007. Derivate-16326/Dre2006-final.pdf, March 2007.
[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 30th
IEEE Local Computer Networks Conference, November 2005. IEEE Local Computer Networks Conference, November 2005.
[IJHIT2008] [IJHIT2008]
Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool Dreibholz, T. and E. Rathgeb, "An Evalulation of the Pool
Maintenance Overhead in Reliable Server Pooling Systems", Maintenance Overhead in Reliable Server Pooling Systems",
International Journal of Hybrid Information Technology International Journal of Hybrid Information Technology
(IJHIT) Volume 1, Number 2, April 2008. (IJHIT) Volume 1, Number 2, April 2008.
[Infocom2005]
Dreibholz, T. and E. Rathgeb, "An Application
Demonstration of the Reliable Server Pooling Framework",
Proceedings of the 24th IEEE Infocom, March 2005.
[SNMPMIBS] [SNMPMIBS]
Perkins, D. and E. McGinnis, "Understanding SNMP MIBs", Perkins, D. and E. McGinnis, "Understanding SNMP MIBs",
1997. 1997.
[I-D.dreibholz-rserpool-asap-hropt]
Dreibholz, T., "Handle Resolution Option for ASAP",
draft-dreibholz-rserpool-asap-hropt-03 (work in progress),
October 2008.
[I-D.dreibholz-rserpool-delay]
Dreibholz, T. and X. Zhou, "Definition of a Delay
Measurement Infrastructure and Delay-Sensitive Least-Used
Policy for Reliable Server Pooling",
draft-dreibholz-rserpool-delay-02 (work in progress),
July 2008.
[I-D.dreibholz-rserpool-applic-distcomp]
Dreibholz, T., "Applicability of Reliable Server Pooling
for Real-Time Distributed Computing",
draft-dreibholz-rserpool-applic-distcomp-05 (work in
progress), July 2008.
[I-D.dreibholz-rserpool-applic-mobility]
Dreibholz, T. and J. Pulinthanath, "Applicability of
Reliable Server Pooling for SCTP-Based Endpoint Mobility",
draft-dreibholz-rserpool-applic-mobility-04 (work in
progress), July 2008.
[I-D.coene-rserpool-applic-ipfix]
Dreibholz, T., Coene, L., and P. Conrad, "Reliable Server
Pooling Applicability for IP Flow Information Exchange",
draft-coene-rserpool-applic-ipfix-06 (work in progress),
July 2008.
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
skipping to change at page 41, line 4 skipping to change at line 1810
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
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST 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.
Intellectual Property
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.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
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.
 End of changes. 29 change blocks. 
69 lines changed or deleted 44 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/