draft-ietf-rtfm-meter-mib-01.txt   draft-ietf-rtfm-meter-mib-02.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
September 1997
Traffic Flow Measurement: Meter MIB Traffic Flow Measurement: Meter MIB
<draft-ietf-rtfm-meter-mib-01.txt> <draft-ietf-rtfm-meter-mib-02.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. This Internet Draft is a product of the documents as Internet Drafts. This Internet Draft is a product of the
Realtime Traffic Flow Measurement Working Group of the IETF. Realtime Traffic Flow Measurement Working Group of the IETF.
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts are draft documents valid for a maximum of six months.
skipping to change at page 2, line ? skipping to change at page 2, line ?
A 'Traffic Meter' collects data relating to traffic flows within a A 'Traffic Meter' collects data relating to traffic flows within a
network. This document defines a Management Information Base (MIB) for network. This document defines a Management Information Base (MIB) for
use in controlling a traffic meter, in particular for specifying the use in controlling a traffic meter, in particular for specifying the
flows to be measured. It also provides an efficient mechanism for flows to be measured. It also provides an efficient mechanism for
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 1
2 The Network Management Framework 2 2 The Network Management Framework 2
3 Objects 3 3 Objects 2
3.1 Format of Definitions . . . . . . . . . . . . . . . . . . . . 4 3.1 Format of Definitions . . . . . . . . . . . . . . . . . . . . 3
4 Overview 4 4 Overview 3
4.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 4 4.1 Scope of Definitions, Textual Conventions . . . . . . . . . . 4
4.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . . 5 4.2 Usage of the MIB variables . . . . . . . . . . . . . . . . . . 4
5 Changes Introduced Since RFC 2064 6 5 Changes Introduced Since RFC 2064 6
6 Definitions 7 6 Definitions 7
7 Security Considerations 42 7 Security Considerations 42
8 Acknowledgements 44 8 Acknowledgements 43
9 References 44 9 References 43
10 Author's Address 45 10 Author's Address 45
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
network Realtime Traffic Flow Meters, as described in [9]. network Realtime Traffic Flow Meters, as described in [9].
skipping to change at page 8, line 23 skipping to change at page 8, line 23
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."
VERSION "9706041620Z" REVISION "9707071715Z"
DESCRIPTION DESCRIPTION
"Significant changes since RFC 2064 include: "Significant changes since RFC 2064 include:
- flowDataPackageTable added - flowDataPackageTable added
- flowColumnActivityTable deprecated - flowColumnActivityTable deprecated
- flowManagerCounterWrap depreacted" - flowManagerCounterWrap deprecated"
VERSION "9603080208Z" REVISION "9603080208Z"
DESCRIPTION DESCRIPTION
"Initial version of this MIB (RFC 2064)" "Initial version of this MIB (RFC 2064)"
::= { mib-2 40 } ::= { mib-2 40 }
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 }
skipping to change at page 18, line 48 skipping to change at page 18, line 48
flowReaderOwner OBJECT-TYPE flowReaderOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
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-write MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time this meter reader began its most recent data collection. "Time this meter reader began its most recent data collection.
This variable should be written by a meter reader as its first This variable should be written by a meter reader as its first
step in reading flow data. The meter will set this LastTime step in reading flow data. The meter will set this LastTime
value to sysUptime and set its PreviousTime value (below) to value to sysUptime and set its PreviousTime value (below) to
the old LastTime. This allows the meter to recover flows the old LastTime. This allows the meter to recover flows
which have been inactive since PreviousTime, for these have which have been inactive since PreviousTime, for these have
been collected at least once. been collected at least once.
skipping to change at page 45, line 4 skipping to change at page 44, line 50
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Conformance Statements for version 2 of the Simple Network "Conformance Statements for version 2 of the Simple Network
Managemenet Protocol (SNMPv2)," RFC 1904, SNMP Research Inc., Managemenet Protocol (SNMPv2)," RFC 1904, SNMP Research Inc.,
Hughes LAN Systems, Dover Beach Consulting, Carnegie Mellon Hughes LAN Systems, Dover Beach Consulting, Carnegie Mellon
University, January 1996. University, January 1996.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Coexistence between version 1 and version 2 of the "Coexistence between version 1 and version 2 of the
Internet-standard Network Management Framework," RFC 1908, SNMP Internet-standard Network Management Framework," RFC 1908, SNMP
Research Inc., Hughes LAN Systems, Dover Beach Consulting, Research Inc., Hughes LAN Systems, Dover Beach Consulting,
Carnegie Mellon University, JAnuary 1996. Carnegie Mellon University, January 1996.
[6] Information processing systems - Open Systems [6] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax Notation One Interconnection - Specification of Abstract Syntax Notation One
(ASN.1), International Organization for Standardization, (ASN.1), International Organization for Standardization,
International Standard 8824, December 1987. International Standard 8824, December 1987.
[7] Information processing systems - Open Systems [7] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules for Interconnection - Specification of Basic Encoding Rules for
Abstract Notation One (ASN.1), International Organization for Abstract Notation One (ASN.1), International Organization for
Standardization, International Standard 8825, December 1987. Standardization, International Standard 8825, December 1987.
 End of changes. 12 change blocks. 
13 lines changed or deleted 15 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/