draft-ietf-forces-mib-01.txt   draft-ietf-forces-mib-02.txt 
Forwarding and Control Element R. Haas Forwarding and Control Element R. Haas
Separation (forces) IBM Separation (forces) IBM
Expires: October 22, 2006 Expires: October 3, 2006
ForCES MIB ForCES MIB
draft-ietf-forces-mib-01 draft-ietf-forces-mib-02
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 34 skipping to change at page 1, line 34
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 October 22, 2006. This Internet-Draft will expire on October 3, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a Management Information Base (MIB) for use with This memo defines a Management Information Base (MIB) for use with
network management protocols in the Internet community. In network management protocols in the Internet community. In
particular, it defines a MIB for the Forwarding and Control Element particular, it defines a MIB for the Forwarding and Control Element
skipping to change at page 2, line 12 skipping to change at page 2, line 12
is defining a protocol to allow a Control Element (CE) to control the is defining a protocol to allow a Control Element (CE) to control the
behavior of a Forwarding Element (FE). behavior of a Forwarding Element (FE).
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Design of the ForCES MIB . . . . . . . . . . . . . . . . . . . 3 3. Design of the ForCES MIB . . . . . . . . . . . . . . . . . . . 3
4. Association State . . . . . . . . . . . . . . . . . . . . . . 3 4. Association State . . . . . . . . . . . . . . . . . . . . . . 3
5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 4 5. ForCES MIB Definition . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Normative References . . . . . . . . . . . . . . . . . . . . . 8 8. Changes from Previous Draft Revisions . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . . . 13
1. Requirements notation 1. Requirements notation
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].
2. Introduction 2. Introduction
The ForCES MIB is a primarily read-only MIB that captures information The ForCES MIB is a primarily read-only MIB that captures information
related to the ForCES protocol ([RFC3654] and [RFC3746]). This related to the ForCES protocol ([RFC3654], [RFC3746], [forces-
includes state information about the associations between CE(s) and applicability-draft] and [forces-protocol-draft]).
FE(s) in the NE.
The ForCES MIB does not include information that is specified in The ForCES MIB does not include information that is specified in
other MIBs, such as packet counters for interfaces, etc. other MIBs, such as packet counters for interfaces, etc.
More specifically, the information in the ForCES MIB relative to More specifically, the information in the ForCES MIB relative to
associations includes: associations that are up includes:
o identifiers of the elements in the association, o identifiers of the elements in the association,
o state of the association,
o configuration parameters of the association, and o configuration parameters of the association, and
o statistics of the association. o statistics of the association.
3. Design of the ForCES MIB 3. Design of the ForCES MIB
In an NE composed of one or more FEs and a single CE, the CE is In an NE composed of one or more FEs and a single CE, the CE is
clearly aware of all associations and hence can provide this clearly aware of all associations and hence can provide this
information in a single ForCES MIB. In contrast, in an NE composed information in a single ForCES MIB. In contrast, in an NE composed
of more than one CE, such association information is distributed and of more than one CE, such association information is distributed and
hence more than one ForCES MIB may be necessary, unless this hence more than one ForCES MIB may be necessary, unless this
information is aggregated into a single ForCES MIB by some means information is aggregated into a single ForCES MIB by some means
beyond the scope of this document. Nevertheless, the ForCES MIB beyond the scope of this document. Nevertheless, the ForCES MIB
design is compatible with both the single-CE and the multiple-CE design is compatible with both the single-CE and the multiple-CE
case. case.
4. Association State 4. Association State
Association state as shown in the MIB is considered from the CE's Only associations that are UP are shown in the MIB. Associations
point of view: enter the UP state as soon as the CE has sent to the FE an
Association Setup Response message containing a successful
o An association is in the DOWN state if the CE has not received any Association Setup Result.
message (heartbeat or other protocol message) from the FE within a
given time period or if an Association Teardown message has been
sent by the CE.
o An association is in the ESTABLISHING state as long as no message
has been received from the FE after the CE has sent a positive
Association Setup Response message.
o An association is in the UP state in all other cases.
Note that it is left to the implementers to choose how long entries Associations are removed from the MIB as soon as they leave the UP
of associations in the DOWN state remain in the MIB until they are state, i.e., if the CE has not received any message (Heartbeat or
removed, if at all. other protocol message) from the FE within a given time period or if
an Association Teardown message has been sent by the CE.
5. ForCES MIB Definition 5. ForCES MIB Definition
For each association identified by the pair CE ID and FE ID, the The MIB contains the latest ForCES protocol version supported by the
following information is provided by the MIB: CE. Note that the CE must also allow interaction with FEs supporting
earlier versions.
o Current state of the association: For each association identified by the pair CE ID and FE ID, the
following associated information is provided by the MIB:
* DOWN: the CE(s) indicated by the CE ID and FE(s) indicated by o Version number of the ForCES protocol running in this association.
the FE ID are not associated.
* ESTABLISHING: transient state until the association has been o Time when the association entered the UP state.
established. See Section 4 above for details.
* UP: the CE(s) indicated by the CE ID and FE(s) indicated by the o Time when the association left the UP state. Note that this is
FE ID are associated. only used for notification purposes as the association is removed
from the MIB immediately after it leaves the UP state.
o Time when the association attained the UP state. o Number of ForCES Heartbeat messages sent from the CE and received
by the CE since the association is UP.
o Time when the association appeared in the MIB. o Number of other ForCES messages sent from the CE and received by
the CE since the association is UP. Only messages other than
Heartbeat, Association Setup, Association Setup Response, and
Association Teardown are counted.
o Number of transitions to ESTABLISHING state since the association Finally, the MIB defines the following notifications:
appeared in the MIB.
o Number of transitions to UP state since the association appeared o Whenever an association enters the UP state, a notification is
in the MIB. issued containing the CE and FE IDs.
o Number of ForCES messages sent/received since the association o Whenever an association leaves the UP state, a notification is
attained the UP state. issued containing the CE and FE IDs as well as all other
associated information for this association. The reason is that
the association and all its associated information will be removed
from the MIB immediately after this notification has been issued.
FORCES-MIB DEFINITIONS ::= BEGIN FORCES-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, MODULE-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Counter32, Unsigned32 Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TimeStamp
TEXTUAL-CONVENTION, RowStatus, TimeInterval, TimeStamp
FROM SNMPv2-TC; FROM SNMPv2-TC;
forcesMIB MODULE-IDENTITY forcesMIB MODULE-IDENTITY
LAST-UPDATED "200604201200Z" -- Apr 20, 2006 LAST-UPDATED "200606261200Z" -- Jun 26, 2006
ORGANIZATION "Forwarding and Control Element Separation ORGANIZATION "Forwarding and Control Element Separation
(ForCES) Working Group" (ForCES) Working Group"
CONTACT-INFO CONTACT-INFO
"Robert Haas (rha@zurich.ibm.com), IBM" "Robert Haas (rha@zurich.ibm.com), IBM"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC yyyy. This MIB "Initial version, published as RFC yyyy. This MIB
contains managed object definitions for the ForCES contains managed object definitions for the ForCES
Protocol." Protocol."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
--**************************************************************** --****************************************************************
ForcesID ::= TEXTUAL-CONVENTION ForcesID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES identifier is a four octet quantity." "The ForCES identifier is a four octet quantity."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
ForcesAssociationState ::= TEXTUAL-CONVENTION ForcesProtocolVersion ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value down(1) indicates that the current state "ForCES protocol version number."
of the association is down. SYNTAX INTEGER (1..255)
establishing(2) indicates that the association is
in the process of being set up.
up(3) indicates that the association is up."
SYNTAX INTEGER {
down(1),
establishing(2),
up(3)
}
forcesAssociations OBJECT IDENTIFIER ::= { forcesMIB 1 } forcesLatestProtocolVersionSupported OBJECT-TYPE
SYNTAX ForcesProtocolVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ForCES protocol version supported by the CE.
The current protocol version is 1.
Note that the CE must also allow interaction
with FEs supporting earlier versions."
::= { forcesMIB 1 }
forcesAssociations OBJECT IDENTIFIER ::= { forcesMIB 2 }
forcesAssociationTable OBJECT-TYPE forcesAssociationTable OBJECT-TYPE
SYNTAX SEQUENCE OF ForcesAssociationEntry SYNTAX SEQUENCE OF ForcesAssociationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table of associations." "The (conceptual) table of associations."
::= { forcesAssociations 1 } ::= { forcesAssociations 1 }
forcesAssociationEntry OBJECT-TYPE forcesAssociationEntry OBJECT-TYPE
SYNTAX ForcesAssociationEntry SYNTAX ForcesAssociationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A (conceptual) entry for one association." "A (conceptual) entry for one association."
INDEX { forcesAssociationCEID, forcesAssociationFEID } INDEX { forcesAssociationCEID, forcesAssociationFEID }
::= { forcesAssociationTable 1 } ::= { forcesAssociationTable 1 }
skipping to change at page 6, line 22 skipping to change at page 6, line 22
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A (conceptual) entry for one association." "A (conceptual) entry for one association."
INDEX { forcesAssociationCEID, forcesAssociationFEID } INDEX { forcesAssociationCEID, forcesAssociationFEID }
::= { forcesAssociationTable 1 } ::= { forcesAssociationTable 1 }
ForcesAssociationEntry ::= SEQUENCE { ForcesAssociationEntry ::= SEQUENCE {
forcesAssociationCEID ForcesID, forcesAssociationCEID ForcesID,
forcesAssociationFEID ForcesID, forcesAssociationFEID ForcesID,
forcesAssociationState ForcesAssociationState,
forcesAssociationUptime TimeStamp, forcesAssociationRunningProtocolVersion
forcesAssociationCreated TimeStamp, ForcesProtocolVersion,
forcesAssociationTransitionsEstablishing Counter32,
forcesAssociationTransitionsUp Counter32, forcesAssociationTimeUp TimeStamp,
forcesAssociationMsgSent Counter32, forcesAssociationTimeDown TimeStamp,
forcesAssociationMsgReceived Counter32
} forcesAssociationHBMsgSent Counter32,
forcesAssociationHBMsgReceived Counter32,
forcesAssociationOtherMsgSent Counter32,
forcesAssociationOtherMsgReceived Counter32 }
forcesAssociationCEID OBJECT-TYPE forcesAssociationCEID OBJECT-TYPE
SYNTAX ForcesID SYNTAX ForcesID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES ID of the CE." "The ForCES ID of the CE."
::= { forcesAssociationEntry 1 } ::= { forcesAssociationEntry 1 }
forcesAssociationFEID OBJECT-TYPE forcesAssociationFEID OBJECT-TYPE
SYNTAX ForcesID SYNTAX ForcesID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ForCES ID of the FE." "The ForCES ID of the FE."
::= { forcesAssociationEntry 2 } ::= { forcesAssociationEntry 2 }
forcesAssociationRunningProtocolVersion OBJECT-TYPE
forcesAssociationState OBJECT-TYPE SYNTAX ForcesProtocolVersion
SYNTAX ForcesAssociationState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational state of the association "The current ForCES protocol version used in this
described by this row of the table." association.
The current protocol version is 1."
::= { forcesAssociationEntry 3 } ::= { forcesAssociationEntry 3 }
forcesAssociationUptime OBJECT-TYPE forcesAssociationTimeUp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time when this association came up." "The value of sysUpTime at the time this
association entered the UP state.
If this association started prior to the last
initialization of the network subsystem, then
this object contains a zero value."
::= { forcesAssociationEntry 4 } ::= { forcesAssociationEntry 4 }
forcesAssociationCreated OBJECT-TYPE forcesAssociationTimeDown OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time when this entry in the table was "The value of sysUpTime at the time this
created for this association." association left the UP state."
::= { forcesAssociationEntry 5 } ::= { forcesAssociationEntry 5 }
forcesAssociationTransitionsEstablishing OBJECT-TYPE forcesAssociationHBMsgSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many times this association "A counter of how many heartbeat messages have
state changed from down to establishing." have been sent by the CE on this association
since it is up.
If this association started prior to the last
initialization of the network subsystem, then
this object contains the value since the
initialization."
::= { forcesAssociationEntry 6} ::= { forcesAssociationEntry 6}
forcesAssociationTransitionsUp OBJECT-TYPE forcesAssociationHBMsgReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many times this association "A counter of how many heartbeat messages
state changed from establishing to up." have been received by the CE on this association
since it is up.
If this association started prior to the last
initialization of the network subsystem, then
this object contains the value since the
initialization."
::= { forcesAssociationEntry 7} ::= { forcesAssociationEntry 7}
forcesAssociationMsgSent OBJECT-TYPE forcesAssociationOtherMsgSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many messages have been sent "A counter of how many messages other than
on this association since it is up." heartbeat (i.e., config and query)
have been sent by the CE on this association
since it is up.
If this association started prior to the last
initialization of the network subsystem, then
this object contains the value since the
initialization."
::= { forcesAssociationEntry 8} ::= { forcesAssociationEntry 8}
forcesAssociationMsgReceived OBJECT-TYPE
forcesAssociationOtherMsgReceived OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A counter of how many messages have been received "A counter of how many messages other than
on this association since it is up." heartbeat (i.e., config response, query response,
event notification, and packet redirect)
have been received by the CE on this association
since it is up.
If this association started prior to the last
initialization of the network subsystem, then
this object contains the value since the
initialization."
::= { forcesAssociationEntry 9} ::= { forcesAssociationEntry 9}
forcesAssociationEntryUp NOTIFICATION-TYPE
OBJECTS {
forcesAssociationCEID,
forcesAssociationFEID
}
STATUS current
DESCRIPTION
"This notification is generated when a
forcesAssociationEntry object is created."
::= { forcesAssociations 2 }
forcesAssociationEntryDown NOTIFICATION-TYPE
OBJECTS {
forcesAssociationCEID,
forcesAssociationFEID,
forcesAssociationRunningProtocolVersion,
forcesAssociationTimeUp,
forcesAssociationTimeDown,
forcesAssociationHBMsgSent,
forcesAssociationHBMsgReceived,
forcesAssociationOtherMsgSent,
forcesAssociationOtherMsgReceived }
STATUS current
DESCRIPTION
"This notification is generated when a
forcesAssociationEntry object is destroyed."
::= { forcesAssociations 3 }
END END
6. Security Considerations 6. Security Considerations
Some of the readable objects in this MIB module may be considered Some of the readable objects in this MIB module may be considered
sensitive or vulnerable in some network environment. sensitive or vulnerable in some network environment.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
skipping to change at page 8, line 43 skipping to change at page 10, line 14
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
IANA will need to assign a number to this MIB. IANA will need to assign a number to this MIB.
8. Normative References 8. Changes from Previous Draft Revisions
Changes from draft-ietf-forces-mib-01. The changes are in response
to the Working Group Last Call:
o Addition of two traps/notifications to signal the associations
that enter or leave the UP state.
o Suppression of the DOWN and ESTABLISHING states. Only
associations in the UP state are kept in the table.
o Split of the Message counters into Heartbeat and other messages.
o Addition of the current running version of ForCES protocol for
each association in the UP state.
o Addition of the latest version of the ForCES protocol supported by
the CE.
9. References
9.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.
[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.
[RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation [RFC3654] Khosravi, H. and T. Anderson, "Requirements for Separation
of IP Control and Forwarding", RFC 3654, November 2003. of IP Control and Forwarding", RFC 3654, November 2003.
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, [RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal,
"Forwarding and Control Element Separation (ForCES) "Forwarding and Control Element Separation (ForCES)
Framework", RFC 3746, April 2004. Framework", RFC 3746, April 2004.
[forces-protocol-draft]
Doria, A., Haas, R., Hadi Salim, J., Khosravi, H., and W.
Wang, "ForCES Protocol Specification", ID Document:
draft-ietf-forces-protocol-08.txt, March 2006.
9.2. Informative References
[forces-applicability-draft]
Crouch, A., Khosravi, H., Handley, M., and A. Doria,
"ForCES Applicability Statement", ID Document:
draft-ietf-forces-applicability-04.txt, February 2006.
Appendix A. Acknowledgments
The author gratefully acknowledges the contributions of: Jinrong
Fenggen, Xiaoyi Guo, and Jamal Hadi Salim.
Author's Address Author's Address
Robert Haas Robert Haas
IBM IBM
Saeumerstrasse 4 Saeumerstrasse 4
Rueschlikon 8803 Rueschlikon 8803
CH CH
Email: rha@zurich.ibm.com Email: rha@zurich.ibm.com
URI: http://www.zurich.ibm.com/~rha URI: http://www.zurich.ibm.com/~rha
 End of changes. 45 change blocks. 
96 lines changed or deleted 195 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/