draft-ietf-rtfm-meter-mib-10.txt   draft-ietf-rtfm-meter-mib-11.txt 
Internet Engineering Task Force Nevil Brownlee Internet Engineering Task Force Nevil Brownlee
INTERNET-DRAFT The University of Auckland INTERNET-DRAFT The University of Auckland
August 1999 September 1999
Expires February 2000
Traffic Flow Measurement: Meter MIB Traffic Flow Measurement: Meter MIB
<draft-ietf-rtfm-meter-mib-10.txt> <draft-ietf-rtfm-meter-mib-11.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line ? skipping to change at page 2, line ?
retrieving flow data from the meter using SNMP. Security issues retrieving flow data from the meter using SNMP. Security issues
concerning the operation of traffic meters are summarised. concerning the operation of traffic meters are summarised.
Contents Contents
1 Introduction 2 1 Introduction 2
2 The SNMP Management Framework 2 2 The SNMP Management Framework 2
3 Overview 3 3 Overview 3
3.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 4 3.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 3
3.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . 4 3.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . 4
4 Definitions 6 4 Definitions 6
5 Security Considerations 44 5 Security Considerations 44
5.1 SNMP Concerns . . . . . . .. . . . . . . . . . . . . . . . . 44 5.1 SNMP Concerns . . . . . . .. . . . . . . . . . . . . . . . . 44
5.2 Traffic Meter Concerns . .. . . . . . . . . . . . . . . . . 45 5.2 Traffic Meter Concerns . .. . . . . . . . . . . . . . . . . 45
6 IANA Considerations 46 6 IANA Considerations 46
7 Appendix A: Changes Introduced Since RFC 2064 47 7 Appendix A: Changes Introduced Since RFC 2064 47
8 Acknowledgements 48 8 Acknowledgements 47
9 References 48 9 References 48
10 Author's Address 50 10 Author's Address 50
1 Introduction 1 Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes objects for managing and collecting data from particular, it describes objects for managing and collecting data from
skipping to change at page 3, line 38 skipping to change at page 3, line 35
and the view-based access control mechanism described in RFC 2575 and the view-based access control mechanism described in RFC 2575
[RFC2575]. [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in [RFC2570]. can be found in [RFC2570].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined using Management Information Base or MIB. Objects in the MIB are defined using
the mechanisms defined in the SMI. the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A MIB
MIB conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3 Overview 3 Overview
skipping to change at page 6, line 48 skipping to change at page 6, line 48
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Counter64, Integer32, mib-2 Counter32, Counter64, Integer32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue TEXTUAL-CONVENTION, RowStatus, TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex ifIndex
FROM RFC1213-MIB FROM IF-MIB
OwnerString
FROM RMON-MIB
TimeFilter TimeFilter
FROM RMON2-MIB; FROM RMON2-MIB;
flowMIB MODULE-IDENTITY flowMIB MODULE-IDENTITY
LAST-UPDATED "9908191010Z" LAST-UPDATED "9908301250Z"
ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group" ORGANIZATION "IETF Realtime Traffic Flow Measurement Working Group"
CONTACT-INFO CONTACT-INFO
"Nevil Brownlee, The University of Auckland "Nevil Brownlee, The University of Auckland
Postal: Information Technology Sytems & Services Postal: Information Technology Sytems & Services
The University of Auckland The University of Auckland
Private Bag 92-019 Private Bag 92-019
Auckland, New Zealand Auckland, New Zealand
Phone: +64 9 373 7599 x8941 Phone: +64 9 373 7599 x8941
E-mail: n.brownlee@auckland.ac.nz" E-mail: n.brownlee@auckland.ac.nz"
DESCRIPTION DESCRIPTION
"MIB for the RTFM Traffic Flow Meter." "MIB for the RTFM Traffic Flow Meter."
REVISION "9908301250Z"
DESCRIPTION
"UTF8OwnerString Textual Convention added, and used to
replace OwnerString. Conceptually the same as OwnerString,
but facilitating internationalisation by using UTF-8
encoding for its characters rather than US-ASCII."
REVISION "9908191010Z" REVISION "9908191010Z"
DESCRIPTION DESCRIPTION
"Changes to SIZE specification for two variables: "Changes to SIZE specification for two variables:
- flowRuleInfoName SIZE specified as (0..127) - flowRuleInfoName SIZE specified as (0..127)
- flowRuleIndex SIZE increased to (1..2147483647)" - flowRuleIndex SIZE increased to (1..2147483647)"
REVISION "9712230937Z" REVISION "9712230937Z"
DESCRIPTION DESCRIPTION
"Two further variables deprecated: "Two further variables deprecated:
- flowRuleInfoRulesReady (use flowRuleInfoStatus intead) - flowRuleInfoRulesReady (use flowRuleInfoStatus intead)
skipping to change at page 8, line 7 skipping to change at page 8, line 13
flowControl OBJECT IDENTIFIER ::= { flowMIB 1 } flowControl OBJECT IDENTIFIER ::= { flowMIB 1 }
flowData OBJECT IDENTIFIER ::= { flowMIB 2 } flowData OBJECT IDENTIFIER ::= { flowMIB 2 }
flowRules OBJECT IDENTIFIER ::= { flowMIB 3 } flowRules OBJECT IDENTIFIER ::= { flowMIB 3 }
flowMIBConformance OBJECT IDENTIFIER ::= { flowMIB 4 } flowMIBConformance OBJECT IDENTIFIER ::= { flowMIB 4 }
-- Textual Conventions -- Textual Conventions
MediumType ::= TEXTUAL-CONVENTION UTF8OwnerString ::= TEXTUAL-CONVENTION
STATUS current DISPLAY-HINT "127t"
DESCRIPTION
"Specifies the type of a MediumAddress (see below). The
values used for IEEE 802 media are from the 'Network
Management Parameters (ifType definitions)' section of the
Assigned Numbers RFC [ASG-NBR]. Other medium types may also
be used, provided only that they are identified by their
assigned ifType numbers."
SYNTAX INTEGER {
ethernet(7), -- ethernet-like [ENET-OBJ],
-- includes ethernet-csmacd(6)
tokenring(9),
fddi(15) }
MediumAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the value of a Medium Access Control (MAC) address. "An administratively assigned name for the owner of a
Address format depends on the actual medium, as follows: resource, conceptually the same as OwnerString in the RMON
MIB [RMON-MIB].
Ethernet: ethernet(7)
6-octet 802.3 MAC address in 'canonical' order
Token Ring: tokenring(9)
6-octet 802.5 MAC address in 'canonical' order
FDDI: fddi(15) To facilitate internationalisation, this name information
FddiMACLongAddress, i.e. a 6-octet MAC address is represented using the ISO/IEC IS 10646-1 character set,
in 'canonical' order (defined in [FDDI-MIB]) encoded as an octet string using the UTF-8 transformation
" format described in the UTF-8 standard [UTF-8]."
SYNTAX OCTET STRING (SIZE (6..20)) SYNTAX OCTET STRING (SIZE (0..127))
PeerType ::= TEXTUAL-CONVENTION PeerType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of a PeerAddress (see below). The values "Indicates the type of a PeerAddress (see below). The values
used are from the 'Address Family Numbers' section of the used are from the 'Address Family Numbers' section of the
Assigned Numbers RFC [ASG-NBR]. Peer types from other address Assigned Numbers RFC [ASG-NBR]. Peer types from other address
families may also be used, provided only that they are families may also be used, provided only that they are
identified by their assigned Address Family numbers." identified by their assigned Address Family numbers."
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 9, line 40 skipping to change at page 9, line 27
DECnet: decnet(13) DECnet: decnet(13)
1-octet Area number (in low-order six bits), 1-octet Area number (in low-order six bits),
2-octet Host number (in low-order ten bits) 2-octet Host number (in low-order ten bits)
" "
SYNTAX OCTET STRING (SIZE (3..20)) SYNTAX OCTET STRING (SIZE (3..20))
AdjacentType ::= TEXTUAL-CONVENTION AdjacentType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of an adjacent address. "Indicates the type of an adjacent address. May be a medium
Is a superset of MediumType and PeerType." type or (if metering is taking place inside a tunnel) a
PeerType (see above).
The values used for IEEE 802 medium types are from the 'Network
Management Parameters (ifType definitions)' section of the
Assigned Numbers RFC [ASG-NBR]. Other medium types may also
be used, provided only that they are identified by their
assigned ifType numbers."
SYNTAX INTEGER { SYNTAX INTEGER {
ip(1), ip(1),
nsap(3), nsap(3),
ethernet(7), ethernet(7), -- ethernet-like [ENET-OBJ],
-- includes ethernet-csmacd(6)
tokenring(9), tokenring(9),
ipx(11), ipx(11),
appletalk(12), appletalk(12),
decnet(13), decnet(13),
fddi(15) } fddi(15) }
AdjacentAddress ::= TEXTUAL-CONVENTION AdjacentAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the value of an adjacent address. "Specifies the value of an adjacent address. May be a Medium
Is a superset of MediumAddress and PeerAddress." Access Control (MAC) address or (if metering is taking place
inside a tunnel) a PeerAddress (see above).
MAC Address format depends on the actual medium, as follows:
Ethernet: ethernet(7)
6-octet 802.3 MAC address in 'canonical' order
Token Ring: tokenring(9)
6-octet 802.5 MAC address in 'canonical' order
FDDI: fddi(15)
FddiMACLongAddress, i.e. a 6-octet MAC address
in 'canonical' order (defined in [FDDI-MIB])
"
SYNTAX OCTET STRING (SIZE (3..20)) SYNTAX OCTET STRING (SIZE (3..20))
TransportType ::= TEXTUAL-CONVENTION TransportType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of a TransportAddress (see below). Values "Indicates the type of a TransportAddress (see below). Values
will depend on the actual protocol; for IP they will be those will depend on the actual protocol; for IP they will be those
given in the 'Protocol Numbers' section of the Assigned Numbers given in the 'Protocol Numbers' section of the Assigned Numbers
RFC [ASG-NBR], including icmp(1), tcp(6) and udp(17)." RFC [ASG-NBR], including icmp(1), tcp(6) and udp(17)."
SYNTAX Integer32 (1..255) SYNTAX Integer32 (1..255)
skipping to change at page 14, line 17 skipping to change at page 14, line 26
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular RuleSet." "Information about a particular RuleSet."
INDEX { flowRuleInfoIndex } INDEX { flowRuleInfoIndex }
::= { flowRuleSetInfoTable 1 } ::= { flowRuleSetInfoTable 1 }
FlowRuleSetInfoEntry ::= SEQUENCE { FlowRuleSetInfoEntry ::= SEQUENCE {
flowRuleInfoIndex Integer32, flowRuleInfoIndex Integer32,
flowRuleInfoSize Integer32, flowRuleInfoSize Integer32,
flowRuleInfoOwner OwnerString, flowRuleInfoOwner UTF8OwnerString,
flowRuleInfoTimeStamp TimeStamp, flowRuleInfoTimeStamp TimeStamp,
flowRuleInfoStatus RowStatus, flowRuleInfoStatus RowStatus,
flowRuleInfoName OCTET STRING, flowRuleInfoName OCTET STRING,
flowRuleInfoRulesReady TruthValue, flowRuleInfoRulesReady TruthValue,
flowRuleInfoFlowRecords Integer32 flowRuleInfoFlowRecords Integer32
} }
flowRuleInfoIndex OBJECT-TYPE flowRuleInfoIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 14, line 45 skipping to change at page 15, line 4
flowRuleInfoSize OBJECT-TYPE flowRuleInfoSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of rules in this RuleSet. Setting this variable will "Number of rules in this RuleSet. Setting this variable will
cause the meter to allocate space for these rules." cause the meter to allocate space for these rules."
::= { flowRuleSetInfoEntry 2 } ::= { flowRuleSetInfoEntry 2 }
flowRuleInfoOwner OBJECT-TYPE flowRuleInfoOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX UTF8OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the manager which 'owns' this RuleSet. A manager "Identifies the manager which 'owns' this RuleSet. A manager
must set this variable when creating a row in this table." must set this variable when creating a row in this table."
::= { flowRuleSetInfoEntry 3 } ::= { flowRuleSetInfoEntry 3 }
flowRuleInfoTimeStamp OBJECT-TYPE flowRuleInfoTimeStamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 18, line 19 skipping to change at page 18, line 31
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular meter reader." "Information about a particular meter reader."
INDEX { flowReaderIndex } INDEX { flowReaderIndex }
::= { flowReaderInfoTable 1 } ::= { flowReaderInfoTable 1 }
FlowReaderInfoEntry ::= SEQUENCE { FlowReaderInfoEntry ::= SEQUENCE {
flowReaderIndex Integer32, flowReaderIndex Integer32,
flowReaderTimeout Integer32, flowReaderTimeout Integer32,
flowReaderOwner OwnerString, flowReaderOwner UTF8OwnerString,
flowReaderLastTime TimeStamp, flowReaderLastTime TimeStamp,
flowReaderPreviousTime TimeStamp, flowReaderPreviousTime TimeStamp,
flowReaderStatus RowStatus, flowReaderStatus RowStatus,
flowReaderRuleSet Integer32 flowReaderRuleSet Integer32
} }
flowReaderIndex OBJECT-TYPE flowReaderIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 18, line 48 skipping to change at page 19, line 9
DESCRIPTION DESCRIPTION
"Specifies the maximum time (in seconds) between flow data "Specifies the maximum time (in seconds) between flow data
collections for this meter reader. If this time elapses collections for this meter reader. If this time elapses
without a collection, the meter should assume that this meter without a collection, the meter should assume that this meter
reader has stopped collecting, and delete this row from the reader has stopped collecting, and delete this row from the
table. A value of zero indicates that this row should not be table. A value of zero indicates that this row should not be
timed out." timed out."
::= { flowReaderInfoEntry 2 } ::= { flowReaderInfoEntry 2 }
flowReaderOwner OBJECT-TYPE flowReaderOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX UTF8OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the meter reader which created this row." "Identifies the meter reader which created this row."
::= { flowReaderInfoEntry 3 } ::= { flowReaderInfoEntry 3 }
flowReaderLastTime OBJECT-TYPE flowReaderLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 21, line 13 skipping to change at page 21, line 25
variable to false(2)." variable to false(2)."
INDEX { flowManagerIndex } INDEX { flowManagerIndex }
::= { flowManagerInfoTable 1 } ::= { flowManagerInfoTable 1 }
FlowManagerInfoEntry ::= SEQUENCE { FlowManagerInfoEntry ::= SEQUENCE {
flowManagerIndex Integer32, flowManagerIndex Integer32,
flowManagerCurrentRuleSet Integer32, flowManagerCurrentRuleSet Integer32,
flowManagerStandbyRuleSet Integer32, flowManagerStandbyRuleSet Integer32,
flowManagerHighWaterMark Integer32, flowManagerHighWaterMark Integer32,
flowManagerCounterWrap INTEGER, flowManagerCounterWrap INTEGER,
flowManagerOwner OwnerString, flowManagerOwner UTF8OwnerString,
flowManagerTimeStamp TimeStamp, flowManagerTimeStamp TimeStamp,
flowManagerStatus RowStatus, flowManagerStatus RowStatus,
flowManagerRunningStandby TruthValue flowManagerRunningStandby TruthValue
} }
flowManagerIndex OBJECT-TYPE flowManagerIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 36 skipping to change at page 22, line 48
they reach the top of their range (normal behaviour for they reach the top of their range (normal behaviour for
Counter64 objects), or whether their scale factors should Counter64 objects), or whether their scale factors should
be used instead. The combination of counter and scale be used instead. The combination of counter and scale
factor allows counts to be returned as non-negative binary factor allows counts to be returned as non-negative binary
floating point numbers, with 64-bit mantissas and 8-bit floating point numbers, with 64-bit mantissas and 8-bit
exponents." exponents."
DEFVAL { wrap } DEFVAL { wrap }
::= { flowManagerInfoEntry 5 } ::= { flowManagerInfoEntry 5 }
flowManagerOwner OBJECT-TYPE flowManagerOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX UTF8OwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the manager which created this row." "Identifies the manager which created this row."
::= { flowManagerInfoEntry 6 } ::= { flowManagerInfoEntry 6 }
flowManagerTimeStamp OBJECT-TYPE flowManagerTimeStamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 50, line 21 skipping to change at page 50, line 26
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", Information Version 2 (SMIv2)",
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
[RMON-MIB] Waldbusser, S., "Remote Network Monitoring Management
Information Base," RFC 1757, February 1995.
[RMON2-MIB] Waldbusser, S., "Remote Network Monitoring Management [RMON2-MIB] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2," RFC 2021, Information Base Version 2 using SMIv2," RFC 2021,
January 1997. January 1997.
[RTFM-ARC] Brownlee, N., Mills, C. and G. Ruth, "Traffic Flow [RTFM-ARC] Brownlee, N., Mills, C. and Ruth, G., "Traffic Flow
Measurement: Architecture", RFC 2063, January 1997. Measurement: Architecture", RFC 2063, January 1997.
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646,"
RFC 2279. January 1998.
[V6-ADDR] Hinden, R.and Deering, S., "IP Version 6 Addressing [V6-ADDR] Hinden, R.and Deering, S., "IP Version 6 Addressing
Architecture," RFC 2373, July 1998. Architecture," RFC 2373, July 1998.
10 Author's Address 10 Author's Address
Nevil Brownlee Nevil Brownlee
Information Technology Systems & Services Information Technology Systems & Services
The University of Auckland The University of Auckland
Private Bag 92-019 Private Bag 92-019
Auckland, New Zealand Auckland, New Zealand
Phone: +64 9 373 7599 x8941 Phone: +64 9 373 7599 x8941
E-mail: n.brownlee@auckland.ac.nz E-mail: n.brownlee@auckland.ac.nz
Expires February 2000
 End of changes. 24 change blocks. 
53 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/