draft-ietf-rtfm-applicability-statement-02.txt   draft-ietf-rtfm-applicability-statement-03.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
Expires October 1999 Expires December 1999
RTFM: Applicability Statement RTFM: Applicability Statement
<draft-ietf-rtfm-applicability-statement-02.txt> <draft-ietf-rtfm-applicability-statement-03.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 RFC2026. provisions of Section 10 of RFC2026.
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 6, line 24 skipping to change at page 6, line 24
5 Security Considerations 5 Security Considerations
These are discussed in detail in the Architecture and Meter MIB These are discussed in detail in the Architecture and Meter MIB
documents. In brief, an RTFM Meter is an SNMP agent which observes a 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 and collects flow data from it. Since it doesn't control the
network directly, it has no direct effect on network security. network directly, it has no direct effect on network security.
On the other hand, the flow data itself may well be valuable - to the 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 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 modify that data, or the meter's ruleset(s)). It is therefore
to take proper precautions to ensure that access to the meter and its important to take proper precautions to ensure that access to the meter
data is sufficiently secure. and its data is sufficiently secure.
For example, a meter port attached to a network should be passive, so 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 that it cannot respond to login attempts of any kind. Control and data
connections to a meter should be via a secure management network. connections to a meter should be via a secure management network.
Finally, suitable security should be established for the meter, as it Finally, suitable security should be established for the meter, as it
would be for any other SNMP agent. would be for any other SNMP agent.
Meters may, like any other network component, be subjected to Denial of Meters may, like any other network component, be subjected to Denial of
Service and other attacks. These are outside the RTFM Architecture - Service and other attacks. These are outside the RTFM Architecture -
countermeasures for them are available, but are also outside RTFM. countermeasures for them are available, but are also outside RTFM.
skipping to change at page 9, line 25 skipping to change at page 9, line 28
TimeFilter: to select the flows to be read TimeFilter: to select the flows to be read
DataPackage: to select the attributes required for each flow DataPackage: to select the attributes required for each flow
GetBulk: to read many flows with a single SNMP PDU GetBulk: to read many flows with a single SNMP PDU
provides a very effective way to read flow data from a traffic meter. provides a very effective way to read flow data from a traffic meter.
9 References 9 References
[1] Mills, C., Hirsch, G. and Ruth, G., "Internet Accounting [1] Mills, C., Hirsch, G. and Ruth, G., "Internet Accounting
Background", RFC 1272, Bolt Beranek and Newman Inc., Meridian Background", RFC 1272, Bolt Beranek and Newman Inc.,
Technology Corporation, November 1991. Meridian Technology Corporation, November 1991.
[2] Brownlee, N., Mills, C., and Ruth, G., "Traffic Flow [2] Brownlee, N., Mills, C., and Ruth, G., "Traffic Flow
Measurement: Architecture", RFC 2063, The University of Measurement: Architecture", RFC 2063, The University of
Auckland, GTE Laboratories Inc, January 1997. Auckland, GTE Laboratories Inc, January 1997.
[3] Brownlee, N., "Traffic Flow Measurement: Meter MIB", RFC [3] Brownlee, N., "Traffic Flow Measurement: Meter MIB",
2064, The University of Auckland, January 1997. RFC 2064, The University of Auckland, January 1997.
[4] Brownlee, N., "SRL: A Language for Describing Traffic Flows [4] Brownlee, N., "SRL: A Language for Describing Traffic Flows
and Specifying Actions for Flow Groups," Internet Draft, and Specifying Actions for Flow Groups," Internet Draft,
'Working draft' to become an Informational RFC, The University 'Working draft' to become an Informational RFC,
of Auckland. The University of Auckland.
[5] Handelman, S.W., Brownlee, N., Ruth, G., Stibler, S., "New [5] Handelman, S.W., Brownlee, N., Ruth, G., Stibler, S.,
Attributes for Traffic Flow Measurment," Internet Draft, "New Attributes for Traffic Flow Measurment," Internet Draft,
'Working draft' to become an Experimental RFC, IBM, The 'Working draft' to become an Experimental RFC,
University of Auckland, GTE Laboratories Inc, IBM. IBM, The University of Auckland, GTE Laboratories Inc, IBM.
[6] Brownlee, N., "Traffic Flow Measurement: Experiences with [6] Brownlee, N., "Traffic Flow Measurement: Experiences with
NeTraMet," RFC 2123, The University of Auckland, March 1997. NeTraMet," RFC 2123, The University of Auckland, March 1997.
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
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 October 1999 Expires December 1999
 End of changes. 9 change blocks. 
16 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/