draft-ietf-frnetmib-frmrelay-service-04.txt   draft-ietf-frnetmib-frmrelay-service-05.txt 
Definitions of Managed Objects Definitions of Managed Objects
for Frame Relay Service Level Definitions for Frame Relay Service Level Definitions
May 1, 2001 June 18, 2001
draft-ietf-frnetmib-frmrelay-service-04.txt draft-ietf-frnetmib-frmrelay-service-05.txt
Robert A. Steinberger Robert A. Steinberger
Paradyne Networks Paradyne Networks
robert.steinberger@fnc.fujitsu.com robert.steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D Orly Nicklass, Ph.D
RAD Data Communications Ltd. RAD Data Communications Ltd.
Orly_n@rad.co.il Orly_n@rad.co.il
Status of this Memo Status of this Memo
skipping to change at page 2, line 44 skipping to change at page 2, line 44
3.6.9. Frame Delivery Ratio .................................... 20 3.6.9. Frame Delivery Ratio .................................... 20
3.6.10. Data Delivery Ratio .................................... 21 3.6.10. Data Delivery Ratio .................................... 21
3.6.11. Service Availability ................................... 21 3.6.11. Service Availability ................................... 21
4. Relation to Other MIB Modules ............................... 22 4. Relation to Other MIB Modules ............................... 22
5. Structure of the MIB Module ................................. 23 5. Structure of the MIB Module ................................. 23
5.1. frsldPvcCtrlTable ......................................... 23 5.1. frsldPvcCtrlTable ......................................... 23
5.2. frsldSmplCtrlTable ........................................ 24 5.2. frsldSmplCtrlTable ........................................ 24
5.3. frsldPvcDataTable ......................................... 24 5.3. frsldPvcDataTable ......................................... 24
5.4. frsldPvcSampleTable ....................................... 24 5.4. frsldPvcSampleTable ....................................... 24
5.5. frsldCapabilities ......................................... 24 5.5. frsldCapabilities ......................................... 24
6. Object Definitions .......................................... 24 6. Persistence of Data ......................................... 24
7. Acknowledgments ............................................. 58 7. Object Definitions .......................................... 24
8. References .................................................. 59 8. Acknowledgments ............................................. 59
9. Security Considerations ..................................... 62 9. References .................................................. 60
10. Authors' Addresses ......................................... 62 10. Security Considerations .................................... 63
11. Copyright Section .......................................... 63 11. Authors' Addresses ......................................... 63
12. Copyright Section .......................................... 64
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 24, line 27 skipping to change at page 24, line 27
This table contains samples of the delivery and availability This table contains samples of the delivery and availability
information from the data table as well as delay information information from the data table as well as delay information
calculated over the sample period. It relies on configuration from calculated over the sample period. It relies on configuration from
both the control table and the sample control table. both the control table and the sample control table.
5.5. frsldCapabilities 5.5. frsldCapabilities
This is a group of objects that define write capabilities of the This is a group of objects that define write capabilities of the
read-create objects in the tables above. read-create objects in the tables above.
6. Object Definitions 6. Persistence of Data
The data in frsldPvcCtrlTable and frsldSmplCtrlTable SHOULD persist
through power cycles. Note, however, that the symantics of readiness
for the rows still applies. This means that it is possible for a row
to be reprovisioned as notReady(3) if the underlying DLCI does not
persist. The data collected in the other tables SHOULD NOT persist
through power cycles in that the reference TimeStamp is no longer
valid.
7. Object Definitions
FRSLD-MIB DEFINITIONS ::= BEGIN FRSLD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Gauge32, Integer32, Counter32, Gauge32, Integer32,
Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI Counter64, TimeTicks, mib-2 FROM SNMPv2-SMI
CounterBasedGauge64 FROM HCNUM-TC CounterBasedGauge64 FROM HCNUM-TC
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TimeStamp FROM SNMPv2-TC TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM IF-MIB; ifIndex FROM IF-MIB;
frsldMIB MODULE-IDENTITY frsldMIB MODULE-IDENTITY
LAST-UPDATED "200105011500Z" -- May 1, 2001 LAST-UPDATED "200106181500Z" -- June 18, 2001
ORGANIZATION "IETF Frame Relay Service MIB Working Group" ORGANIZATION "IETF Frame Relay Service MIB Working Group"
CONTACT-INFO CONTACT-INFO
"IETF Frame Relay Service MIB (frnetmib) Working Group "IETF Frame Relay Service MIB (frnetmib) Working Group
WG Charter: http://www.ietf.org/html.charters/ WG Charter: http://www.ietf.org/html.charters/
frnetmib-charter.html frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
Chair: Andy Malis Chair: Andy Malis
Lucent Technologies Lucent Technologies
Email: amalis@lucent.com Email: amalis@lucent.com
WG editor: Robert Steinberger WG editor: Robert Steinberger
Paradyne Networks and Paradyne Networks and
Fujitsu Network Communications Fujitsu Network Communications
Email: robert.steinberger@fnc.fujitsu.com Email: robert.steinberger@fnc.fujitsu.com
Co-author: Orly Nicklass Co-author: Orly Nicklass
skipping to change at page 25, line 19 skipping to change at page 25, line 30
Paradyne Networks and Paradyne Networks and
Fujitsu Network Communications Fujitsu Network Communications
Email: robert.steinberger@fnc.fujitsu.com Email: robert.steinberger@fnc.fujitsu.com
Co-author: Orly Nicklass Co-author: Orly Nicklass
RAD Data Communications Ltd. RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il" EMail: Orly_n@rad.co.il"
DESCRIPTION DESCRIPTION
"The MIB module to describe generic objects for "The MIB module to describe generic objects for
FRF.13 Frame Relay Service Level Definitions." FRF.13 Frame Relay Service Level Definitions."
REVISION "200106181500Z"
DESCRIPTION
"o Added text about persistence to RowStatus objects.
o Added text to description of frsldPvcDataMissed-
Polls.
o Changed badValue to inconsistentValue in
frsldMaxPvcCtrls and frsldMaxSmplCtrls."
REVISION "200105011500Z" REVISION "200105011500Z"
DESCRIPTION DESCRIPTION
"o Added FrsldTxRP and FrsldRxRP TCs for reference "o Added FrsldTxRP and FrsldRxRP TCs for reference
points and changed frsldPvcCtrlTransmitRP and points and changed frsldPvcCtrlTransmitRP and
frsldPvcCtrlReceiveRP to use new TCs. frsldPvcCtrlReceiveRP to use new TCs.
o Added REFERENCE clauses. o Added REFERENCE clauses.
o Added frsldMaxPvcCtrls, frsldNumPvcCtrls, o Added frsldMaxPvcCtrls, frsldNumPvcCtrls,
frsldMaxSmplCtrls and frsldNumSmplCtrls frsldMaxSmplCtrls and frsldNumSmplCtrls
for memory control. for memory control.
o Made HC Data groups conditionally mandatory o Made HC Data groups conditionally mandatory
skipping to change at page 31, line 14 skipping to change at page 31, line 33
affect the data and sample tables. affect the data and sample tables.
The rows added to this table MUST have a valid The rows added to this table MUST have a valid
ifIndex and an ifType related to frame relay. Further, ifIndex and an ifType related to frame relay. Further,
the reference points referred to by frsldPvcCtrlTransmitRP the reference points referred to by frsldPvcCtrlTransmitRP
and frsldPvcCtrlReceiveRP MUST be supported (see the and frsldPvcCtrlReceiveRP MUST be supported (see the
frsldRPCaps object). frsldRPCaps object).
If at any point the row is not in the active(1) state If at any point the row is not in the active(1) state
and the DLCI no longer exists, the state SHOULD and the DLCI no longer exists, the state SHOULD
report notReady(3)." report notReady(3).
The data in this table SHOULD persist through power
cycles. The symantics of readiness for the rows still
applies. This means that it is possible for a row to be
reprovisioned as notReady(3) if the underlying DLCI does
not persist."
::= { frsldPvcCtrlEntry 4 } ::= { frsldPvcCtrlEntry 4 }
frsldPvcCtrlPacketFreq OBJECT-TYPE frsldPvcCtrlPacketFreq OBJECT-TYPE
SYNTAX Integer32 (0..3600) SYNTAX Integer32 (0..3600)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The frequency in seconds between initiation of "The frequency in seconds between initiation of
specialized packets used to collect delay and / or specialized packets used to collect delay and / or
skipping to change at page 34, line 51 skipping to change at page 35, line 27
ifIndex, an ifType related to frame relay, ifIndex, an ifType related to frame relay,
frsldPvcCtrlDlci MUST exist for the specified frsldPvcCtrlDlci MUST exist for the specified
ifIndex and frsldPvcCtrlStatus MUST have a ifIndex and frsldPvcCtrlStatus MUST have a
value of active(1). value of active(1).
The value of frsldPvcCtrlStatus MUST be active(1) The value of frsldPvcCtrlStatus MUST be active(1)
to transition this object to active(1). If to transition this object to active(1). If
the value of frsldPvcCtrlStatus becomes anything the value of frsldPvcCtrlStatus becomes anything
other than active(1) when the state of this object other than active(1) when the state of this object
is not active(1), this object SHOULD be set to is not active(1), this object SHOULD be set to
notReady(3)." notReady(3).
The data in this table SHOULD persist through power
cycles. The symantics of readiness for the rows still
applies. This means that it is possible for a row to be
reprovisioned as notReady(3) if the underlying DLCI does
not persist."
::= { frsldSmplCtrlEntry 2 } ::= { frsldSmplCtrlEntry 2 }
frsldSmplCtrlColPeriod OBJECT-TYPE frsldSmplCtrlColPeriod OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time in seconds that defines a "The amount of time in seconds that defines a
period of collection for the statistics. period of collection for the statistics.
skipping to change at page 37, line 4 skipping to change at page 37, line 34
frsldPvcDataHCFrDeliveredE Counter64, frsldPvcDataHCFrDeliveredE Counter64,
frsldPvcDataHCFrOfferedC Counter64, frsldPvcDataHCFrOfferedC Counter64,
frsldPvcDataHCFrOfferedE Counter64, frsldPvcDataHCFrOfferedE Counter64,
frsldPvcDataHCDataDeliveredC Counter64, frsldPvcDataHCDataDeliveredC Counter64,
frsldPvcDataHCDataDeliveredE Counter64, frsldPvcDataHCDataDeliveredE Counter64,
frsldPvcDataHCDataOfferedC Counter64, frsldPvcDataHCDataOfferedC Counter64,
frsldPvcDataHCDataOfferedE Counter64, frsldPvcDataHCDataOfferedE Counter64,
frsldPvcDataUnavailableTime TimeTicks, frsldPvcDataUnavailableTime TimeTicks,
frsldPvcDataUnavailables Counter32 frsldPvcDataUnavailables Counter32
} }
frsldPvcDataMissedPolls OBJECT-TYPE frsldPvcDataMissedPolls OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of polls that have been determined "The total number of polls that have been determined
to be missed." to be missed. These polls are typically associated
with the calculation of delay but may also be
used for the calculation of other statistics. If an
anticipated poll is not received in a reasonable
amount of time, it should be counted as missed.
The value used to determine the reasonable amount
of time is contained in frsldPvcCtrlDelayTimeOut."
::= { frsldPvcDataEntry 1 } ::= { frsldPvcDataEntry 1 }
frsldPvcDataFrDeliveredC OBJECT-TYPE frsldPvcDataFrDeliveredC OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames that were received at "The number of frames that were received at
frsldPvcCtrlReceiveRP and determined to have been frsldPvcCtrlReceiveRP and determined to have been
sent within CIR." sent within CIR."
skipping to change at page 50, line 48 skipping to change at page 51, line 37
::= { frsldCapabilities 3 } ::= { frsldCapabilities 3 }
frsldMaxPvcCtrls OBJECT-TYPE frsldMaxPvcCtrls OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of control rows that can be created "The maximum number of control rows that can be created
in frsldPvcCtrlTable. Sets to this object lower than in frsldPvcCtrlTable. Sets to this object lower than
the current value of frsldNumPvcCtrls should result in the current value of frsldNumPvcCtrls should result in
badValue." inconsistentValue."
::= { frsldCapabilities 4 } ::= { frsldCapabilities 4 }
frsldNumPvcCtrls OBJECT-TYPE frsldNumPvcCtrls OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of rows in frsldPvcCtrlTable." "The current number of rows in frsldPvcCtrlTable."
::= { frsldCapabilities 5 } ::= { frsldCapabilities 5 }
frsldMaxSmplCtrls OBJECT-TYPE frsldMaxSmplCtrls OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of control rows that can be created "The maximum number of control rows that can be created
in frsldSmplCtrlTable. Sets to this object lower than in frsldSmplCtrlTable. Sets to this object lower than
the current value of frsldNumSmplCtrls should result in the current value of frsldNumSmplCtrls should result in
badValue." inconsistentValue."
::= { frsldCapabilities 6 } ::= { frsldCapabilities 6 }
frsldNumSmplCtrls OBJECT-TYPE frsldNumSmplCtrls OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current number of rows in frsldSmplCtrlTable." "The current number of rows in frsldSmplCtrlTable."
::= { frsldCapabilities 7 } ::= { frsldCapabilities 7 }
skipping to change at page 52, line 4 skipping to change at page 52, line 40
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv2 entities "The compliance statement for SNMPv2 entities
which support with Frame Relay Service Level which support with Frame Relay Service Level
Definitions. This group defines the minimum Definitions. This group defines the minimum
level of support required for compliance." level of support required for compliance."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { frsldPvcReqCtrlGroup, MANDATORY-GROUPS { frsldPvcReqCtrlGroup,
frsldPvcReqDataGroup, frsldPvcReqDataGroup,
frsldCapabilitiesGroup} frsldCapabilitiesGroup}
GROUP frsldPvcHCFrameDataGroup GROUP frsldPvcHCFrameDataGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network interfaces "This group is mandatory only for those network
with corresponding instance of ifSpeed greater than interfaces with corresponding instance of ifSpeed
650,000,000 bits/second." greater than 650,000,000 bits/second."
GROUP frsldPvcHCOctetDataGroup GROUP frsldPvcHCOctetDataGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network interfaces "This group is mandatory only for those network
with corresponding instance of ifSpeed greater than interfaces with corresponding instance of ifSpeed
650,000,000 bits/second." greater than 650,000,000 bits/second."
OBJECT frsldPvcCtrlStatus OBJECT frsldPvcCtrlStatus
SYNTAX INTEGER { active(1) } -- subset of RowStatus SYNTAX INTEGER { active(1) } -- subset of RowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Row creation can be done outside of the scope of "Row creation can be done outside of the scope of
the SNMP protocol. If this object is implemented the SNMP protocol. If this object is implemented
with max-access of read-only, then the only value with max-access of read-only, then the only value
that MUST be returned is active(1) and that MUST be returned is active(1) and
frsldPvcCtrlWriteCaps MUST return 0 for the frsldPvcCtrlWriteCaps MUST return 0 for the
frsldPvcCtrlStatus(0) bit." frsldPvcCtrlStatus(0) bit."
skipping to change at page 58, line 22 skipping to change at page 59, line 11
frsldNumSmplCtrls frsldNumSmplCtrls
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of required objects providing "A collection of required objects providing
capability information and control for this capability information and control for this
MIB module." MIB module."
::= { frsldMIBGroups 15 } ::= { frsldMIBGroups 15 }
END END
7. Acknowledgments 8. Acknowledgments
This document was produced by the Frame Relay Service MIB Working This document was produced by the Frame Relay Service MIB Working
Group. It is based on the Frame Relay Forum's implementation Group. It is based on the Frame Relay Forum's implementation
agreement on service level definitions, FRF.13 [17]. agreement on service level definitions, FRF.13 [17].
The editors would like to thank the following people for their The editors would like to thank the following people for their
helpful comments: helpful comments:
o Ken Rehbehn, Visual Networks o Ken Rehbehn, Visual Networks
o Santa Dasu, Quick Eagle Networks o Santa Dasu, Quick Eagle Networks
8. References 9. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems,
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, STD Management Information for TCP/IP-based Internets", RFC 1155, STD
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
STD 16, Performance Systems International, Hughes LAN Systems, March STD 16, Performance Systems International, Hughes LAN Systems, March
1991 1991
skipping to change at page 62, line 5 skipping to change at page 63, line 5
Base Version 2 using SMIv2", RFC 2021, International Network Base Version 2 using SMIv2", RFC 2021, International Network
Service, January 1997. Service, January 1997.
[20]Brown, C., Baker, F., "Management Information Base for Frame Relay [20]Brown, C., Baker, F., "Management Information Base for Frame Relay
DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems, DTEs Using SMIv2", RFC 2115, Cadia Networks, Inc., Cisco Systems,
September 1997. September 1997.
[21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC [21]McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB", RFC
2863, Cisco Systems, Argon Networks, June 2000. 2863, Cisco Systems, Argon Networks, June 2000.
9. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have 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. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
skipping to change at page 62, line 30 skipping to change at page 63, line 30
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 2274 [12] and the View-based of the User-based Security Model RFC 2274 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended. Access Control Model RFC 2275 [15] 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 (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
10. Authors' Addresses 11. Authors' Addresses
Robert Steinberger Robert Steinberger
Fujitsu Network Communications Fujitsu Network Communications
2801 Telecom Parkway 2801 Telecom Parkway
Richardson, TX 75082 Richardson, TX 75082
Phone: 1-972-479-4739 Phone: 1-972-479-4739
Email: robert.steinberger@fnc.fujitsu.com Email: robert.steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D Orly Nicklass, Ph.D
RAD Data Communications Ltd. RAD Data Communications Ltd.
12 Hanechoshet Street 12 Hanechoshet Street
Tel Aviv, Israel 69710 Tel Aviv, Israel 69710
Phone: 972 3 7659969 Phone: 972 3 7659969
Email: Orly_n@rrad.co.il Email: Orly_n@rrad.co.il
11. Copyright Section 12. Copyright Section
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 21 change blocks. 
27 lines changed or deleted 65 lines changed or added

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