draft-ietf-rserpool-mib-05.txt   draft-ietf-rserpool-mib-06.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: Standards Track J. Mulik
Expires: July 13, 2008 Delaware State University Expires: January 12, 2009 Delaware State University
January 10, 2008 July 11, 2008
Reliable Server Pooling: Management Information Base using SMIv2 Reliable Server Pooling: Management Information Base using SMIv2
draft-ietf-rserpool-mib-05.txt draft-ietf-rserpool-mib-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. 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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 July 13, 2008. This Internet-Draft will expire on January 12, 2009.
Copyright Notice Abstract
Copyright (C) The IETF Trust (2008). RSerPool [I-D.ietf-rserpool-arch] is a framework to provide reliable
server pooling. This document defines a SMIv2 compliant Management
Information Base (MIB) providing access to managed objects in an
RSerPool implementation.
Abstract Table of Contents
RSerPool [2] is a framework to provide reliable server pooling. This 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
document defines a SMIv2 compliant Management Information Base (MIB) 2. The Reliable Server Pooling (RSerPool) Framework . . . . . . . 3
providing access to managed objects in an RSerPool implementation. 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3
4.1. Access to managed objects on ENRP servers . . . . . . . . 9
4.2. Access to managed objects on Pool Elements . . . . . . . . 11
4.3. Access to managed objects on Pool Users . . . . . . . . . 11
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 36
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.1. Normative References . . . . . . . . . . . . . . . . . . . 37
9.2. Informative References . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
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 [1], Reliable Server Pooling (RSerPool) framework, please refer to
[2], [3], [4], [5] and [6]. A more informal introduction can be [RFC3237], [I-D.ietf-rserpool-arch], [I-D.ietf-rserpool-asap],
found at [18]. [I-D.ietf-rserpool-enrp], [I-D.ietf-rserpool-policies] and
[I-D.ietf-rserpool-common-param]. A more informal introduction can
be found at [RSerPoolPage].
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 [12]. 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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [9], STD 58, RFC 2579 [10] and STD 58, RFC 2580 [11]. RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
4. Structure of the MIB 4. 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(????????)
| |
+--enrpServers(1) +--enrpServers(1)
skipping to change at page 12, line 5 skipping to change at page 9, line 36
branches. branches.
4.1. Access to managed objects on ENRP servers 4.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 [20]. Specifically, the the table-in-table technique described in [SNMPMIBS]. Specifically,
ENRP servers branch creates four levels of nesting, as indicated in the ENRP servers branch creates four levels of nesting, as indicated
the following diagram: in the following diagram:
Nesting of ENRP Server Branch Nesting of ENRP Server Branch
Nesting Structure: Nesting Structure:
Level 1: enrpServerTable Level 1: enrpServerTable
Level 2: enrpServerPoolTable Level 2: enrpServerPoolTable
Level 3: enrpServerPoolElementTable Level 3: enrpServerPoolElementTable
Level 4: enrpServerASAPAddrListTable Level 4: enrpServerASAPAddrListTable
skipping to change at page 14, line 25 skipping to change at page 12, line 13
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 "200706181012Z" -- June 18, 2007 LAST-UPDATED "200807111012Z" -- July 11, 2008
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
Fax: +49-201-183-7673 Fax: +49-201-183-7673
Email: dreibh@exp-math.uni-essen.de Email: dreibh@iem.uni-due.de
JAIWANT-MULIK JAIWANT-MULIK
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 "200706181012Z" -- June 18, 2007 REVISION "200807111012Z" -- July 11, 2008
DESCRIPTION DESCRIPTION
"Version 05, published as draft-ietf-rserpool-mib-05.txt." "Version 05, published as draft-ietf-rserpool-mib-05.txt."
::= { mib-2 xxxxxxxxxx } -- To be IANA Assigned!!! ::= { mib-2 xxxxxxxxxx } -- 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)
skipping to change at page 39, line 14 skipping to change at page 36, line 36
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 [7] and the View-based of the User-based Security Model RFC 2574 [RFC2574] and the View-
Access Control Model RFC 2575 [8] is recommended. based Access Control Model RFC 2575 [RFC2575] 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 42, line 9 skipping to change at page 37, line 15
8. Acknowledgments 8. 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. of this draft.
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., Loughney, [RFC3237] Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L.,
J., and M. Stillman, "Requirements for Reliable Server Loughney, J., and M. Stillman, "Requirements for Reliable
Pooling", RFC 3237, January 2002. Server Pooling", RFC 3237, January 2002.
[2] Tuexen, M., "Architecture for Reliable Server Pooling", [I-D.ietf-rserpool-arch]
draft-ietf-rserpool-arch-10 (work in progress), July 2005. Tuexen, M., "Architecture for Reliable Server Pooling",
draft-ietf-rserpool-arch-12 (work in progress),
November 2006.
[3] Stewart, R., "Aggregate Server Access Protocol (ASAP)", [I-D.ietf-rserpool-asap]
draft-ietf-rserpool-asap-13 (work in progress), February 2006. Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP)",
draft-ietf-rserpool-asap-20 (work in progress), May 2008.
[4] Stewart, R., "Endpoint Handlespace Redundancy Protocol (ENRP)", [I-D.ietf-rserpool-enrp]
draft-ietf-rserpool-enrp-13 (work in progress), February 2006. Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", draft-ietf-rserpool-enrp-20 (work in progress),
May 2008.
[5] Tuexen, M. and T. Dreibholz, "Reliable Server Pooling [I-D.ietf-rserpool-policies]
Policies", draft-ietf-rserpool-policies-02 (work in progress), Tuexen, M. and T. Dreibholz, "Reliable Server Pooling
February 2006. Policies", draft-ietf-rserpool-policies-09 (work in
progress), May 2008.
[6] Stewart, R., "Aggregate Server Access Protocol (ASAP) and [I-D.ietf-rserpool-common-param]
Endpoint Handlespace Redundancy Protocol (ENRP) Parameters", Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
draft-ietf-rserpool-common-param-10 (work in progress), "Aggregate Server Access Protocol (ASAP) and Endpoint
February 2006. Handlespace Redundancy Protocol (ENRP) Parameters",
draft-ietf-rserpool-common-param-17 (work in progress),
May 2008.
[7] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
for version 3 of the Simple Network Management Protocol (USM) for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, April 1999. Protocol (SNMPv3)", RFC 2574, April 1999.
[8] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management Protocol Access Control Model (VACM) for the Simple Network
(SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[9] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Ed., "Structure of Management Information Version 2 (SMIv2)", Schoenwaelder, Ed., "Structure of Management Information
STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[10] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, Schoenwaelder, Ed., "Textual Conventions for SMIv2",
April 1999. STD 58, RFC 2579, April 1999.
[11] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Statements for SMIv2", STD 58, RFC 2580, April 1999. "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[12] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
and Applicability Statements for Internet-Standard Management "Introduction and Applicability Statements for Internet-
Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[13] Dreibholz, T., "Handle Resolution Option for ASAP", [I-D.dreibholz-rserpool-asap-hropt]
draft-dreibholz-rserpool-asap-hropt-00 (work in progress), Dreibholz, T., "Handle Resolution Option for ASAP",
June 2007. draft-dreibholz-rserpool-asap-hropt-01 (work in progress),
January 2008.
[14] Dreibholz, T. and X. Zhou, "Definition of a Delay Measurement [I-D.dreibholz-rserpool-delay]
Infrastructure and Delay-Sensitive Least-Used Policy for Dreibholz, T. and X. Zhou, "Definition of a Delay
Reliable Server Pooling", draft-dreibholz-rserpool-delay-00 Measurement Infrastructure and Delay-Sensitive Least-Used
(work in progress), June 2007. Policy for Reliable Server Pooling",
draft-dreibholz-rserpool-delay-01 (work in progress),
January 2008.
[15] Dreibholz, T., "Applicability of Reliable Server Pooling for [I-D.dreibholz-rserpool-applic-distcomp]
Real-Time Distributed Computing", Dreibholz, T., "Applicability of Reliable Server Pooling
draft-dreibholz-rserpool-applic-distcomp-01 (work in progress), for Real-Time Distributed Computing",
February 2006. draft-dreibholz-rserpool-applic-distcomp-04 (work in
progress), January 2008.
[16] Dreibholz, T. and J. Pulinthanath, "Applicability of Reliable [I-D.dreibholz-rserpool-applic-mobility]
Server Pooling for SCTP-Based Endpoint Mobility", Dreibholz, T. and J. Pulinthanath, "Applicability of
draft-dreibholz-rserpool-applic-mobility-00 (work in progress), Reliable Server Pooling for SCTP-Based Endpoint Mobility",
March 2006. draft-dreibholz-rserpool-applic-mobility-03 (work in
progress), January 2008.
[17] Coene, L., "Reliable Server Pooling Applicability for IP Flow [I-D.coene-rserpool-applic-ipfix]
Information Exchange", draft-coene-rserpool-applic-ipfix-03 Coene, L., "Reliable Server Pooling Applicability for IP
(work in progress), August 2006. Flow Information Exchange",
draft-coene-rserpool-applic-ipfix-05 (work in progress),
January 2008.
9.2. Informative References 9.2. Informative References
[18] Dreibholz, T., "Thomas Dreibholz's RSerPool Page", [RSerPoolPage]
URL: http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/. Dreibholz, T., "Thomas Dreibholz's RSerPool Page", URL:
http://tdrwww.exp-math.uni-essen.de/dreibholz/rserpool/.
[19] Dreibholz, T., "Reliable Server Pooling -- Evaluation, [Dre2006] Dreibholz, T., "Reliable Server Pooling -- Evaluation,
Optimization and Extension of a Novel IETF Architecture", Ph.D. Optimization and Extension of a Novel IETF Architecture",
Thesis University of Duisburg-Essen, Faculty of Economics, Ph.D. Thesis University of Duisburg-Essen, Faculty of
Institute for Computer Science and Business Information Economics, Institute for Computer Science and Business
Systems, URL: http://duepublico.uni-duisburg-essen.de/servlets/ Information Systems, URL: http://
DerivateServlet/Derivate-16326/Dre2006-final.pdf, March 2007. duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/
Derivate-16326/Dre2006-final.pdf, March 2007.
[20] Perkins, D. and E. McGinnis, "Understanding SNMP MIBs", 1997. [SNMPMIBS]
Perkins, D. and E. McGinnis, "Understanding SNMP MIBs",
1997.
[21] Dreibholz, T. and E. Rathgeb, "On the Performance of Reliable [LCN2005] Dreibholz, T. and E. Rathgeb, "On the Performance of
Server Pooling Systems", Proceedings of the 30th IEEE Local Reliable Server Pooling Systems", Proceedings of the 30th
Computer Networks Conference, November 2005. IEEE Local Computer Networks Conference, November 2005.
[22] Dreibholz, T. and E. Rathgeb, "The Performance of Reliable [Tencon2005]
Server Pooling Systems in Different Server Capacity Scenarios", Dreibholz, T. and E. Rathgeb, "The Performance of Reliable
Proceedings of the IEEE TENCON, November 2005. Server Pooling Systems in Different Server Capacity
Scenarios", Proceedings of the IEEE TENCON, November 2005.
[23] Dreibholz, T. and E. Rathgeb, "Implementing the Reliable Server [Contel2005]
Pooling Framework", Proceedings of the 8th IEEE International Dreibholz, T. and E. Rathgeb, "Implementing the Reliable
Conference on Telecommunications, June 2005. Server Pooling Framework", Proceedings of the 8th IEEE
International Conference on Telecommunications, June 2005.
[24] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load Distribution [ICN2005] Dreibholz, T., Rathgeb, E., and M. Tuexen, "Load
Performance of the Reliable Server Pooling Framework", Distribution Performance of the Reliable Server Pooling
Proceedings of the 4th IEEE International Conference on Framework", Proceedings of the 4th IEEE International
Networking, April 2005. Conference on Networking, April 2005.
[25] Dreibholz, T. and E. Rathgeb, "RSerPool -- Providing Highly [Euromicro2005]
Available Services using Unreliable Servers", Dreibholz, T. and E. Rathgeb, "RSerPool -- Providing
Proceedings Proceedings of the 31st IEEE EuroMirco Conference Highly Available Services using Unreliable Servers",
on Software Engineering and Advanced Applications, August 2005. Proceedings Proceedings of the 31st IEEE EuroMirco
Conference on Software Engineering and Advanced
Applications, August 2005.
[26] Dreibholz, T., Zhou, X., and E. Rathgeb, "A Performance [Euromicro2007]
Evaluation of RSerPool Server Selection Policies in Varying Dreibholz, T., Zhou, X., and E. Rathgeb, "A Performance
Heterogeneous Capacity Scenarios", Proceedings of the 33rd IEEE Evaluation of RSerPool Server Selection Policies in
EuroMirco Conference on Software Engineering and Advanced Varying Heterogeneous Capacity Scenarios", Proceedings of
Applications, August 2007. the 33rd IEEE EuroMirco Conference on Software Engineering
and Advanced Applications, August 2007.
[27] Dreibholz, T. and E. Rathgeb, "An Application Demonstration of [Infocom2005]
the Reliable Server Pooling Framework", Proceedings of the 24th Dreibholz, T. and E. Rathgeb, "An Application
IEEE Infocom, March 2005. Demonstration of the Reliable Server Pooling Framework",
Proceedings of the 24th IEEE Infocom, March 2005.
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@exp-math.uni-essen.de Email: dreibh@iem.uni-due.de
URI: http://www.exp-math.uni-essen.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
skipping to change at page 46, line 44 skipping to change at line 1859
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 44 change blocks. 
110 lines changed or deleted 157 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/