Network Working Group N. Brownlee
Request for Comments: 2721 The University of Auckland
Category: Informational October 1999
Network Working Group N. Brownlee
Request for Comments: 2721 The University of Auckland
Category: Informational October 1999
RTFM: Applicability Statement
RTFM：适用性声明
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This document provides an overview covering all aspects of Realtime Traffic Flow Measurement, including its area of applicability and its limitations.
本文件概述了实时交通流测量的各个方面，包括其适用范围和局限性。
Table of Contents
目录
1 The RTFM Documents . . . . . . . . . . . . . . . . . . . . . . 2
2 Brief Technical Specification (TS) . . . . . . . . . . . . . . 3
3 Applicability Statement (AS) . . . . . . . . . . . . . . . . . 3
4 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 4
5 Security Considerations . . . . . . . . . . . . . . . . . . . 5
6 Policy Considerations . . . . . . . . . . . . . . . . . . . . 6
7 Soundness . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8 Appendix A: WG Report on the Meter MIB . . . . . . . . . . . . 8
9 References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9
11 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 10
1 The RTFM Documents . . . . . . . . . . . . . . . . . . . . . . 2
2 Brief Technical Specification (TS) . . . . . . . . . . . . . . 3
3 Applicability Statement (AS) . . . . . . . . . . . . . . . . . 3
4 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . 4
5 Security Considerations . . . . . . . . . . . . . . . . . . . 5
6 Policy Considerations . . . . . . . . . . . . . . . . . . . . 6
7 Soundness . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8 Appendix A: WG Report on the Meter MIB . . . . . . . . . . . . 8
9 References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 9
11 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 10
1 The RTFM Documents
1 RTFM文件
The RTFM Traffic Measurement System has been developed by the Realtime Traffic Flow Measurement Working Group. It is described in six other documents, as follows:
RTFM交通测量系统由实时交通流测量工作组开发。其他六份文件对此作了如下描述：
[ACT-BKG] Internet Accounting: Background (Informational)
[ACT-BKG]互联网会计：背景（信息）
Sets out the requirements for a usage reporting system for network traffic. Sketches out the RTFM Architecture (meters, meter readers and managers) allowing for multiple meters and meter readers, with asynchronous reading from the meters. Proposes methods of classifying traffic flows, the need for flows to be bi-directional (with separate sets of counters for each direction) and the need for each packet to be counted in a single flow (the ' count in one bucket' principle).
列出网络流量使用情况报告系统的要求。勾勒出RTFM体系结构（仪表、仪表读卡器和管理器），允许多个仪表和仪表读卡器从仪表异步读取。提出了对流量进行分类的方法，流量需要是双向的（每个方向有单独的计数器组），每个数据包需要在单个流量中计数（“一个桶中计数”原则）。
[RTFM-ARC] RTFM Architecture (Informational)
[RTFM-ARC]RTFM体系结构（信息性）
Defines the RTFM Architecture, giving descriptions of each component. Explains how traffic flows are viewed as logical entities described in terms of their address-attribute values, so that each is defined by the attributes of its end-points. Gives a detailed description of the RTFM traffic meter, with full details of how flows are stored in the meter's flow table, and how packets are matched in accordance with rules stored in a ruleset.
定义RTFM体系结构，给出每个组件的描述。解释如何将通信流视为根据其地址属性值描述的逻辑实体，以便每个实体都由其端点的属性定义。给出RTFM流量表的详细说明，以及流量如何存储在流量表中的完整细节，以及数据包如何根据存储在规则集中的规则进行匹配。
[RTFM-MIB] RTFM Meter MIB (Proposed Standard)
[RTFM-MIB]RTFM仪表MIB（拟定标准）
Describes the SNMP Management Information Base for an RTFM meter, including its flow table, rule table (storing the meter's rulesets) and the control tables used for managing a meter and reading flow data from it.
描述RTFM电表的SNMP管理信息库，包括其流量表、规则表（存储电表的规则集）以及用于管理电表和从中读取流量数据的控制表。
[RTFM-SRL] SRL: A Language for Describing Traffic (Informational) Flows and Specifying Actions for Flow Groups
[RTFM-SRL]SRL：用于描述流量（信息）流和指定流组操作的语言
An RTFM ruleset is an array of rules, used by the meter to decide which flows are of interest, which end-point is the flow source, and how much detail (i.e. what attribute values) must be saved for each flow. SRL is a high-level language providing a clear, logical way to write rulesets. It should also be useful for other applications which select flows and perform actions upon them, e.g. packet-marking gateways, RSVP policy agents, etc.
RTFM规则集是一个规则数组，计量器使用它来决定哪些流是感兴趣的，哪个端点是流源，以及每个流必须保存多少细节（即哪些属性值）。SRL是一种高级语言，提供了编写规则集的清晰、逻辑的方法。它还应适用于选择流并对其执行操作的其他应用程序，例如包标记网关、RSVP策略代理等。
[RTFM-NEW] RTFM New Attributes (Experimental)
[RTFM-NEW]RTFM新属性（实验）
There has been considerable interest from users in extending the RTFM Architecture so as to allow a meter to report on an increased number of flow-related measures. This RFC documents work on specifying such measures (the 'new' attributes) and reports on experience of implementing them.
用户对扩展RTFM体系结构非常感兴趣，以便允许仪表报告更多流量相关测量。本RFC文件规定了此类措施（“新”属性），并报告了实施这些措施的经验。
[RTFM-NTM] RTFM: Experiences with NeTraMet (Informational)
[RTFM-NTM]RTFM:NeTraMet的体验（信息）
NeTraMet is a free software implementation of the RTFM Architecture which has been available since 1993. This RFC records RTFM implementation experience gained with NeTraMet up to late 1996. One particularly important result is the realisation that groups of rules which test the same attribute using the same mask can be implemented as a single hashed comparison, allowing the meter to rapidly determine whether a packet belongs to one of a large number of networks.
NeTraMet是RTFM体系结构的一个自由软件实现，自1993年起就开始使用。本RFC记录了截至1996年底NeTraMet的RTFM实施经验。一个特别重要的结果是认识到，使用相同掩码测试相同属性的规则组可以实现为单个散列比较，从而允许仪表快速确定数据包是否属于大量网络中的一个。
2 Brief Technical Specification (TS)
2简要技术规范（TS）
RTFM provides for the measurement of network traffic 'flows', i.e.
RTFM提供网络流量“流量”的测量，即。
- a method of specifying traffic flows within a network - a hierarchy of devices (meters, meter readers, managers) for measuring the specified flows - a mechanism for configuring meters and meter readers, and for collecting the flow data from remote meters
- 一种在网络中指定流量的方法-用于测量指定流量的设备（仪表、仪表读卡器、管理器）层次结构-配置仪表和仪表读卡器以及从远程仪表收集流量数据的机制
RTFM provides high time resolution for flow first- and last-packet times. Counters for long-duration flows may be read at intervals determined by a manager. The RTFM Meter is designed so as to do as much data reduction work as possible, which minimizes the amount of data to be read and the amount of processing needed to produce useful reports from it.
RTFM为流的第一个和最后一个数据包时间提供了高时间分辨率。长持续时间流的计数器可以按管理器确定的间隔读取。RTFM仪表的设计目的是尽可能多地进行数据简化工作，从而最大限度地减少要读取的数据量和从中生成有用报告所需的处理量。
RTFM flow data can be used for a wide range of purposes, such as usage accounting, long-term recording of network usage (classified by IP address attributes) and real-time analysis of traffic flows at remote metering points.
RTFM流量数据可用于多种用途，如使用情况核算、网络使用情况的长期记录（按IP地址属性分类）和远程计量点流量的实时分析。
3 Applicability Statement (AS)
3适用性声明（AS）
To use RTFM for collecting network traffic information one must first consider where in the network traffic flows are to be measured. Once that is decided, an RTFM Meter must be installed at each chosen measurement point.
要使用RTFM收集网络流量信息，首先必须考虑网络流量中要测量的位置。一旦确定，必须在每个选定的测量点安装RTFM仪表。
At least one Meter Reader is needed to collect the measured data from the meters, and a single Manager is needed to control the meters and meter readers.
至少需要一个仪表读取器来收集仪表的测量数据，并且需要一个管理器来控制仪表和仪表读取器。
RTFM Meters may be single- or multi-user hosts running a meter program (one such program is available as free software, a second is under development at IBM Research). Alternatively, meters could be run as firmware in switches or routers. A hybrid approach in which an RTFM meter takes raw traffic data from a router provides another useful implementation path.
RTFM电表可以是运行电表程序的单用户或多用户主机（其中一个程序作为自由软件提供，另一个正在IBM Research开发）。或者，仪表可以在交换机或路由器中作为固件运行。RTFM表从路由器获取原始流量数据的混合方法提供了另一个有用的实现路径。
RTFM Managers are programs running on a host, communicating with meters and meter readers via the network. For this purpose meters are SNMP agents implementing the RTFM Meter MIB, and managers are SNMP clients using the Meter MIB to store and access the flow data.
RTFM管理器是在主机上运行的程序，通过网络与仪表和仪表读卡器进行通信。为此，仪表是实现RTFM仪表MIB的SNMP代理，管理器是使用仪表MIB存储和访问流量数据的SNMP客户端。
4 Limitations
4限制
RTFM is designed to measure traffic flows for traffic passing a point in a network. If packets for a flow pass the metering point in both directions the meter will match them up, providing counters for each direction. If packets only pass in one direction the meter can only provide counts for that direction.
RTFM设计用于测量通过网络中某一点的流量。如果流的数据包在两个方向上通过计量点，计量器将匹配它们，为每个方向提供计数器。如果数据包只在一个方向通过，则仪表只能提供该方向的计数。
Users of RTFM should note that installing meters, meter readers and managers merely provides one with the capability to collect flow data. Further installation work will be needed to develop configuration files (RTFM rulesets) for each meter, data processing applications to analyse the flow data, and various scripts, cron jobs, etc. so as to create a useful production-quality measurement system which suits a user's particular needs.
RTFM的用户应注意，安装仪表、仪表读卡器和管理器仅提供收集流量数据的功能。需要进行进一步的安装工作，为每个仪表开发配置文件（RTFM规则集）、分析流量数据的数据处理应用程序、各种脚本、cron作业等，以便创建一个适合用户特殊需求的有用的生产质量测量系统。
One of the strengths of RTFM is its ability to collect flow data at whatever level of detail (or 'granularity') is required. It can be tempting to simply collect 'all possible data', but there are severe resource constraints. If one tries to save the complete address-attribute value for all attributes of every possible flow a very large amount of data may be produced rapidly, but the meter has only a finite amount of memory for its flow table. A better approach is to save the minimum amount of data required to achieve the measurement system goals.
RTFM的一个优点是它能够收集所需的任何详细级别（或“粒度”）的流数据。简单地收集“所有可能的数据”很有诱惑力，但存在严重的资源限制。如果试图保存每个可能流量的所有属性的完整地址属性值，可能会快速生成大量数据，但流量计的流量表内存有限。更好的方法是保存实现测量系统目标所需的最小数据量。
For example, to collect usage data so as to bill subscribers identified by their IP address one could just save the full IP address, nothing more. The RTFM meter would produce flow data for each subscriber IP address, with PDU and Octet counts for data sent and received, which would be the minimum needed to produce bills. In practice one would probably want to save at least part of the
例如，要收集使用情况数据以便向通过IP地址识别的订户计费，只需保存完整的IP地址即可，仅此而已。RTFM仪表将为每个用户IP地址生成流量数据，发送和接收数据的PDU和八位字节计数将是生成账单所需的最低值。在实践中，人们可能希望至少节约一部分资金
Destination IP address, which would allow the production of usage logs showing subscriber activity over time.
目标IP地址，这将允许生成使用日志，显示订阅者在一段时间内的活动。
The simplest way to determine how much detail can be collected is to create an initial ruleset which collects the minimum amount, then to modify it step by step, gradually increasing the amount of information saved for each flow. An RTFM meter ought to provide some measures of its own performance (e.g. number of active flows, percentage idle processor time, packets metered, packets not metered). Such measures will be implementation-specific, but should allow a user to assess the impact of each change to the ruleset.
确定可以收集多少详细信息的最简单方法是创建一个收集最小数量的初始规则集，然后逐步修改它，逐渐增加为每个流保存的信息量。RTFM仪表应提供其自身性能的一些度量（例如，活动流的数量、空闲处理器时间的百分比、已计量的数据包、未计量的数据包）。此类措施将针对具体实施，但应允许用户评估规则集每次变更的影响。
If the network data rate is too high, i.e. the meter reports that it cannot meter all the packets even with the initial ruleset above, one may be able to use other strategies. For example one could
如果网络数据速率太高，即仪表报告即使使用上述初始规则集也无法测量所有数据包，则可以使用其他策略。例如，可以
- run the meter on a faster computer, e.g. move from a DOS PC to a workstation, or perhaps use a meter implemented in firmware within a switch or router.
- 在速度更快的计算机上运行仪表，例如从DOS PC移动到工作站，或者可能使用交换机或路由器中固件实现的仪表。
- use sampling. The details of such sampling are not defined within the RTFM Architecture, but the Meter MIB provides one simple method by allowing one to specify that only every nth packet on an interface will be metered. This would probably not be acceptable for producing billing data, but might well be acceptable for traffic engineering purposes.
- 使用抽样。这种采样的细节没有在RTFM体系结构中定义，但是Meter MIB提供了一种简单的方法，它允许用户指定只对接口上的每N个数据包进行测量。这对于生成计费数据来说可能是不可接受的，但是对于流量工程来说可能是可以接受的。
5 Security Considerations
5安全考虑
These are discussed in detail in the Architecture and Meter MIB documents. In brief, an RTFM Meter is an SNMP agent which observes a network and collects flow data from it. Since it doesn't control the network directly, it has no direct effect on network security.
架构和仪表MIB文档中详细讨论了这些问题。简而言之，RTFM仪表是一个SNMP代理，它观察网络并从中收集流量数据。由于它不直接控制网络，因此对网络安全没有直接影响。
On the other hand, the flow data itself may well be valuable - to the network operator (as billing data) or to an attacker (who may wish to modify that data, or the meter's ruleset(s)). It is therefore important to take proper precautions to ensure that access to the meter and its data is sufficiently secure.
另一方面，流量数据本身可能很有价值——对于网络运营商（作为计费数据）或攻击者（可能希望修改该数据或仪表的规则集）。因此，必须采取适当的预防措施，以确保对电表及其数据的访问足够安全。
For example, a meter port attached to a network should be passive, so that it cannot respond to login attempts of any kind. Control and data connections to a meter should be via a secure management network. Finally, suitable security should be established for the meter, as it would be for any other SNMP agent.
例如，连接到网络的仪表端口应该是被动的，因此它不能响应任何类型的登录尝试。仪表的控制和数据连接应通过安全管理网络进行。最后，应该为仪表建立适当的安全性，就像任何其他SNMP代理一样。
Meters may, like any other network component, be subjected to Denial of Service and other attacks. These are outside the RTFM Architecture - countermeasures for them are available, but are also outside RTFM.
电表可能与任何其他网络组件一样，受到拒绝服务和其他攻击。这些都在RTFM体系结构之外-它们的对策是可用的，但也在RTFM之外。
6 Policy Considerations
6政策考虑
When collecting traffic data, one must have well-defined operations policies covering points such as:
收集交通数据时，必须制定明确的运营政策，包括以下几点：
- Exactly what data is to be collected, at what level of detail? - How long will the data be kept? - What may the data be used for? - Who will be allowed to see the raw data? - May summaries of the data be shown to other people?
- 究竟要收集哪些数据，在何种详细程度上数据将保留多长时间？-这些数据可以用于什么目的谁将被允许查看原始数据可以向其他人展示数据摘要吗？
Policy issues such as these should normally be considered as part of an organisation's Network Security Policy.
此类政策问题通常应视为组织网络安全政策的一部分。
Other policy issues relating more directly to the traffic data are essentially part of the measurement system design, such as:
与交通数据更直接相关的其他政策问题基本上是测量系统设计的一部分，例如：
- How much time resolution is required for the data? (Less resolution implies longer collection intervals, but that may require more memory in the meters to hold flow data between collections).
- 数据需要多少时间分辨率？（分辨率越低意味着采集间隔越长，但这可能需要仪表中的更多内存来保存采集之间的流量数据）。
- What level of hardware redundancy is needed? (A single meter and meter reader is generally enough. For greater reliability, meters and meter readers can be duplicated).
- 需要什么级别的硬件冗余？（一般来说，一个抄表器就足够了。为了更高的可靠性，可以复制抄表器）。
- Who is allowed to use the system? (Approved users will need permissions to download rulesets to the meters, and to collect their data, possibly via their own meter readers).
- 谁可以使用这个系统？（经批准的用户将需要权限将规则集下载到电表，并可能通过自己的电表阅读器收集数据）。
7 Soundness
7健全性
NeTraMet, the first implementation of the RTFM Architecture, has been in use worldwide since 1994. Currently there are many organisations, large and small, using it to collect traffic data for billing purposes.
NeTraMet是RTFM体系结构的第一个实现，自1994年以来一直在世界范围内使用。目前，有许多组织，无论大小，都使用它来收集流量数据以进行计费。
One example of these is Kawaihiko, the New Zealand Universities' Network, which has seven RTFM meters located at sites throughout New Zealand. One of the sites is NZIX, the New Zealand Internet eXchange at the University of Waikato, where Kawaihiko has a meter (attached to a 100baseT network) observing traffic flows across the exchange to
其中一个例子是新西兰大学网络Kawaihiko，该网络在新西兰各地有七个RTFM电表。其中一个网站是NZIX，位于怀卡托大学的新西兰互联网交换中心，在那里，Kawaihiko有一个表（附在100BasetNetwork）上，观察跨交流的交通流。
each of Kawaihiko's three international Internet Service Providers. 5-minute Octet counts are collected from all the Kawaihiko meters by a single meter reader at Auckland. Traffic data from the meters is used to determine the cost per month for each of the Kawaihiko sites.
Kawaihiko的三家国际互联网服务提供商。奥克兰的一个仪表读数器从所有的Kawaihiko仪表中收集5分钟的八隅体计数。流量表中的流量数据用于确定每个川口子站点的每月成本。
It is difficult to estimate how many organisations are using RTFM traffic measurement. There are about 250 people on the NeTraMet mailing list, which often carries questions like 'why doesn't this ruleset do what I meant'? Once new users have the system running, however, they tend to simply use it without further comment.
很难估计有多少组织正在使用RTFM流量测量。NeTraMet邮件列表上大约有250人，其中经常有这样的问题：“为什么这个规则集不符合我的意思？”？然而，一旦新用户运行了系统，他们倾向于简单地使用它而无需进一步评论。
From time to time the list provides useful feedback. For example, early in 1998 there were two very significant user contributions:
该列表不时提供有用的反馈。例如，1998年初有两个非常重要的用户贡献：
- Jacek Kowalski (Telstra, Melbourne) described an improved hash algorithm for NeTraMet's flow table, which provided almost an order of magnitude improvement in packet-handling performance.
- Jacek Kowalski（墨尔本Telstra）描述了NeTraMet的流表的改进哈希算法，该算法在数据包处理性能方面提供了几乎一个数量级的改进。
- Kevin Hoadley (JANET, U.K.) reported having problems with very large rulesets. These were resolved, and better methods of downloading rules developed, allowing NeTraMet to work well for rulesets with more than 32,000 rules.
- Kevin Hoadley（珍妮特，英国）报道了非常大的规则集存在问题。解决了这些问题，开发了更好的规则下载方法，使NeTraMet能够很好地处理超过32000条规则的规则集。
Perhaps one reason why there is little discussion of NeTraMet's use in collecting billing data is that users may consider that the way collect their data is a commercially sensitive matter.
也许很少有人讨论NeTraMet在收集计费数据中的用途是，用户可能会认为收集数据的方式是商业敏感的事情。
8 Appendix A: WG Report on the Meter MIB
8附录A：仪表MIB工作组报告
The Meter MIB (in its current form) was developed early in 1996. It was produced as an SNMPv2 MIB, following a number of detailed (and continuing) discussions with David Perkins beginning at the Dallas IETF meeting in December 1995.
仪表MIB（当前形式）于1996年初开发。在1995年12月达拉斯IETF会议开始时，在与David Perkins进行了多次详细（持续）讨论之后，它作为SNMPv2 MIB生成。
There are two current implementations:
目前有两种实现方式：
- NeTraMet (Nevil Brownlee, The University of Auckland)
- NeTraMet（Nevil Brownlee，奥克兰大学）
- IBM Meter (Sig Handelman & Stephen Stibler, IBM Research, N.Y, Bert Wijnen provided further help with SNMP)
- IBM Meter（Sig Handelman&Stephen Stibler，纽约IBM研究所，Bert Wijnen提供了有关SNMP的进一步帮助）
The NeTraMet meter is a stand-alone SNMP agent using an SNMPv2C implementation derived from CMU SNMPv2.
NeTraMet meter是一个独立的SNMP代理，使用从CMU SNMPv2派生的SNMPv2C实现。
The IBM meter runs as a sub-agent on an AIX system. All the meter code has been written by Stephen Stibler - it was not derived from the NeTraMet code. Stephen has found it useful to use nifty, one of NeTraMet's manager/reader programs, to test the IBM meter.
IBMMeter作为AIX系统上的子代理运行。所有的计量器代码都是由斯蒂芬·斯蒂布勒编写的——它不是从NeTraMet代码派生出来的。Stephen发现使用NeTraMet的manager/reader程序之一nifty测试IBM meter很有用。
As indicated above, there have only been two implementors to date, and the Working Group consensus has been very strong.
如上所述，迄今只有两个实施者，工作组的共识非常强烈。
The MIB has one unusual aspect: the method used to read large amounts of data from its Flow Table. An earlier SNMPv1 version of the MIB was in use from 1992 to 1997; it used opaque objects to read column slices from the flow table for flows which had been active since a specified time. This was very non-standard (or at least very application-specific).
MIB有一个不寻常的方面：用于从其流表中读取大量数据的方法。从1992年到1997年，MIB的早期SNMPv1版本在使用；它使用不透明对象从流表中读取自指定时间以来一直处于活动状态的流的列切片。这是非常不标准的（或者至少非常特定于应用程序）。
With the change to SNMPv2 we were able to use 64-bit counters for PDUs and Octets, RowStatus variables for control tables and GETBULK requests to read rows from the flow table. We also use the TimeFilter convention from the RMON2 MIB to select flows to be read; this gives the meter MIB a strong resemblance to RMON2.
通过对SNMPv2的更改，我们能够为PDU和八位字节使用64位计数器，为控制表使用RowStatus变量，并通过GETBULK请求从流表中读取行。我们还使用RMON2 MIB中的TimeFilter约定来选择要读取的流；这使仪表MIB与RMON2非常相似。
The current MIB introduces a better way of reading large amounts of data from the flow table. This is the 'DataPackage' convention, which specifies the attribute values to be read from a flow table row. The meter returns the values for each required attribute within a BER-encoded sequence. This means there is only one object identifier for the whole sequence, greatly reducing the number of bytes required to retrieve the data. The combination of
当前的MIB引入了从流表中读取大量数据的更好方法。这是“数据包”约定，它指定要从流表行读取的属性值。仪表返回BER编码序列中每个必需属性的值。这意味着整个序列只有一个对象标识符，大大减少了检索数据所需的字节数。结合
TimeFilter: to select the flows to be read DataPackage: to select the attributes required for each flow GetBulk: to read many flows with a single SNMP PDU
TimeFilter:选择要读取的流DataPackage:选择每个流所需的属性GetBulk:使用单个SNMP PDU读取多个流
provides a very effective way to read flow data from a traffic meter.
提供了一种从交通量表读取流量数据的非常有效的方法。
9 References
9参考文献
[ACT-BKG] Mills, C., Hirsch, G. and G. Ruth, "Internet Accounting Background", RFC 1272, November 1991.
[ACT-BKG]Mills，C.，Hirsch，G.和G.Ruth，“互联网会计背景”，RFC 1272，1991年11月。
[RTFM-ARC] Brownlee, N., Mills, C. and G. Ruth, "Traffic Flow Measurement: Architecture", RFC 2722, October 1999.
[RTFM-ARC]Brownlee，N.，Mills，C.和G.Ruth，“交通流测量：架构”，RFC2721999年10月。
[RTFM-MIB] Brownlee, N., "Traffic Flow Measurement: Meter MIB", RFC 2720, October 1999.
[RTFM-MIB]北布朗利，“交通流量测量：米MIB”，RFC2720，1999年10月。
[RTFM-NEW] Handelman, S., Stibler, S., Brownlee, N. and G. Ruth, "RTFM: New Attributes for Traffic Flow Measurement", RFC 2724, October 1999.
[RTFM-NEW]Handelman，S.，Stibler，S.，Brownlee，N.和G.Ruth，“RTFM：交通流测量的新属性”，RFC 27241999年10月。
[RTFM-NTM] Brownlee, N., "Traffic Flow Measurement: Experiences with NeTraMet", RFC 2123, March 1997.
[RTFM-NTM]布朗利，N.，“交通流测量：网络框架的经验”，RFC2123，1997年3月。
[RTFM-SRL] Brownlee, N., "SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow Groups", RFC 2723, October 1999.
[RTFM-SRL]布朗利，N.，“SRL：描述交通流和指定流组动作的语言”，RFC2723，1999年10月。
10 Author's Address
10作者地址
Nevil Brownlee Information Technology Systems & Services The University of Auckland Private Bag 92-019 Auckland, New Zealand
NevelBrnnLee信息技术系统与服务奥克兰大学奥克兰私人包92-019，新西兰
Phone: +64 9 373 7599 x8941
EMail: n.brownlee@auckland.ac.nz
Phone: +64 9 373 7599 x8941
EMail: n.brownlee@auckland.ac.nz
11 Full Copyright Statement
11完整版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。