draft-ietf-rtfm-new-traffic-flow-06.txt   draft-ietf-rtfm-new-traffic-flow-07.txt 
skipping to change at page 2, line ? skipping to change at page 1, line 18
U of Auckland, NZ U of Auckland, NZ
Greg Ruth Greg Ruth
GTE Laboratories, Inc GTE Laboratories, Inc
Waltham, MA USA Waltham, MA USA
S. Stibler S. Stibler
IBM IBM
Hawthorne, NY USA Hawthorne, NY USA
October 3, 1998 April, 1999
expires expires
April 3, 1999 October, 1999
RTFM Working Group - New Attributes for Traffic Flow Measurement RTFM Working Group - New Attributes for Traffic Flow Measurement
<draft-ietf-rtfm-new-traffic-flow-06.txt> <draft-ietf-rtfm-new-traffic-flow-07.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC2026.
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To view the entire list of current Internet-Drafts, please check the The list of current Internet-Drafts can be accessed at
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific The list of Internet-Draft Shadow Directories can be accessed at
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). http://www.ietf.org/shadow.html.
2. Introduction 2. Introduction
The Real-Time Flow Measurement (RTFM) Working Group (WG) has The Real-Time Flow Measurement (RTFM) Working Group (WG) has
developed a system for measuring and reporting information about developed a system for measuring and reporting information about
traffic flows in the Internet. This document explores the definition traffic flows in the Internet. This document explores the definition
of extensions to the flow measurements as currently defined in [1]. of extensions to the flow measurements as currently defined in [1].
The new attributes described in this document will be useful for The new attributes described in this document will be useful for
monitoring network performance and will expand the scope of RTFM monitoring network performance and will expand the scope of RTFM
beyond simple measurement of traffic volumes. A companion document beyond simple measurement of traffic volumes. A companion document
skipping to change at page 14, line 25 skipping to change at page 14, line 25
flow's destination network flow's destination network
Some of the above, e.g. SourceASN and DestASN, might sensibly be Some of the above, e.g. SourceASN and DestASN, might sensibly be
allocated attribute numbers below 64, making them part of the 'base' allocated attribute numbers below 64, making them part of the 'base'
RTFM meter attributes. RTFM meter attributes.
To support use of the RTFM meter as an 'Edge Device' for implementing To support use of the RTFM meter as an 'Edge Device' for implementing
Differentiated Services, and/or for metering traffic carried via such Differentiated Services, and/or for metering traffic carried via such
services, two more attributes will be useful: services, two more attributes will be useful:
SourceDSfield(118) DS field value for S->D packets DSCodePoint(118) DS Code Point (6 bits) for packets in this flow
DestDSfield(119) DS field value for D->S packets
Note that since the DS Code Point is a single field within a packet's
IP header, it is not possible to have both Source- and Dest-
CodePoint attributes. Possible uses of DSCodePoint include
aggregating flows using the same Code Points, and separating flows
having the same end-point addresses but using different Code Points.
6. Security Considerations 6. Security Considerations
The attributes considered in this document represent properties of The attributes considered in this document represent properties of
traffic flows; they do not present any security issues in themselves. traffic flows; they do not present any security issues in themselves.
The attributes may, however, be used in measuring the behaviour of The attributes may, however, be used in measuring the behaviour of
traffic flows, and the collected traffic flow data could be of traffic flows, and the collected traffic flow data could be of
considerable value. Suitable precautions should be taken to keep such considerable value. Suitable precautions should be taken to keep such
data safe. data safe.
skipping to change at line 690 skipping to change at page 15, line 53
Base," RFC 1757, 1995, and RFC 2021, 1997. Base," RFC 1757, 1995, and RFC 2021, 1997.
[7] Brownlee, N: "Traffic Flow Measurement: Meter MIB", [7] Brownlee, N: "Traffic Flow Measurement: Meter MIB",
RFC 2064, The University of Auckland, January 1997. RFC 2064, The University of Auckland, January 1997.
[8] Maiocchi, S: "NeTraMet & NeMaC for IIS Accounting: User's Guide", [8] Maiocchi, S: "NeTraMet & NeMaC for IIS Accounting: User's Guide",
CEFRIEL, Milan, 5 May 1998. (See also http://www.cefriel.it/ntw) CEFRIEL, Milan, 5 May 1998. (See also http://www.cefriel.it/ntw)
[9] Shenker, S., Partridge, C., Guerin, R.: "Specification of [9] Shenker, S., Partridge, C., Guerin, R.: "Specification of
Guaranteed Quality of Service," RFC 2212, 1997. Guaranteed Quality of Service," RFC 2212, 1997.
Expires October 1999
 End of changes. 7 change blocks. 
14 lines changed or deleted 22 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/