From netramet-owner  Tue Nov  7 20:22:03 1995
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) id UAA07589 for netramet-outgoing; Tue, 7 Nov 1995 20:18:07 +1300 (NZDT)
Received: from dcns.csc.cuhk.hk (hp712c.csc.cuhk.hk [137.189.28.103]) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) with SMTP id UAA07584 for <[email protected]>; Tue, 7 Nov 1995 20:17:57 +1300 (NZDT)
Received: (from ktso@localhost) by dcns.csc.cuhk.hk (8.6.12/8.6.12) id PAA18546 for [email protected]; Tue, 7 Nov 1995 15:22:07 +0800
From: SO Kwok Tsun <[email protected]>
Message-Id: <[email protected]>
Subject: No. of Octet including Ethernet header?
To: [email protected]
Date: Tue, 7 Nov 1995 15:22:07 +0800 (HKT)
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Hi,

We are planning to use NeTraMet for IP accounting of our International Link.

We would like to know whether the number of Octets include the Ethernet
header. Can anyone tell me?

Regards,
SO Kwok-tsun Alan
Information Technology Service Unit
The Chinese University of Hong Kong

From netramet-owner  Wed Nov  8 17:20:09 1995
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) id RAA14541 for netramet-outgoing; Wed, 8 Nov 1995 17:19:29 +1300 (NZDT)
Received: from ccu1.auckland.ac.nz ([email protected] [130.216.3.1]) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) with ESMTP id RAA14535 for <[email protected]>; Wed, 8 Nov 1995 17:19:28 +1300 (NZDT)
Received: (from nevil@localhost) by ccu1.auckland.ac.nz (8.7.1/8.7.1) id RAA15714 for [email protected]; Wed, 8 Nov 1995 17:19:27 +1300 (NDT)
From: J Nevil Brownlee <[email protected]>
Message-Id: <[email protected]>
Subject: 3.3 release ready for testing
To: [email protected] (NeTraMet mailing list)
Date: Wed, 8 Nov 1995 17:19:27 +1300 (NDT)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Hello all:

The beta release of NeTraMet version 3.3 is now available from
  ftp://ftp.auckland.ac.nz/pub/iawg/NeTraMet

The files are
  33beta.NeTraMet.tar.gz       Source and make files
                               (full description of all changes is in
                                  doc/NeTraMet/version.history)
  33Irix.tar.gz, 33Linux.tar.gz,       Binaries for Irix, linux,
  33Solaris.tar.gz                        Solaris

  netramet.exe                 PC meter
  NeTraMet.zip                 PC meter source and make files

3.3 corrects many problems, e.g. meter crashes caused by SNMP probe
packets, Unix meters busy-waiting.  It has now been extensively
tested metering an FDDI interface on Solaris; this works fine.

3.3 has six new example rule files; these have been developed over
the last few months in response to user requests, i.e. they are
all 'real-life' rule files.

3.3 includes a new program: nm_rc.  This is a simple 'remote console'
program.  It combines fd_filter with a simplified (one meter only, no
log or flow data files) version of NeMaC, and displays the busiest nnn
flows every sss seconds.  nm_rc is documented in
doc/NeTraMet/rc-man.txt.

I'd appreciate any bug reports or general feedback.  I plan to finish
writing documentation so as to complete the 'official' 3.3 release
by late November.

Cheers, Nevil

+-----------------------------------------------------------------------+
| Nevil Brownlee                       Director, Technology Development |
| Phone: +64 9 373 7599 x8941          ITSS, The University of Auckland |
|   FAX: +64 9 373 7425        Private Bag 92019, Auckland, New Zealand |
+-----------------------------------------------------------------------C

From netramet-owner  Mon Nov 13 17:35:44 1995
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) id RAA18703 for netramet-outgoing; Mon, 13 Nov 1995 17:31:25 +1300 (NZDT)
Received: from ccu1.auckland.ac.nz ([email protected] [130.216.3.1]) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) with ESMTP id RAA18698; Mon, 13 Nov 1995 17:31:23 +1300 (NZDT)
Received: (from nevil@localhost) by ccu1.auckland.ac.nz (8.7.1/8.7.1) id RAA23765; Mon, 13 Nov 1995 17:31:20 +1300 (NDT)
From: J Nevil Brownlee <[email protected]>
Message-Id: <[email protected]>
Subject: Dallas Traffic Measurement BOF Agenda
To: [email protected] (iawg mailing list),
       [email protected] (NeTraMet mailing list),
       [email protected] (IEPG mailing list),
       [email protected] (Cisco users' mailing list )
Date: Mon, 13 Nov 1995 17:31:20 +1300 (NDT)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

Hello everyone:

1) I've sent this to four mailing lists, all of which I believe will
  be interested.  Just the same I apologise (in advance) to those who
  receive multiple copies.

2) We're holding a BOF session at the Dallas IETF meeting to talk about
  measuring traffic flows, with the intention of forming a Working
  Group to develop a standard for this.  If you're interested in this
  area and are in Dallas, we'd appreciate your support!  If you can't
  be at the meeting, it will be multicast, so you can still take part.

  If you have any questions relating to the RTFM effort, please post
  them to [email protected]

Cheers, Nevil

+-----------------------------------------------------------------------+
| Nevil Brownlee                       Director, Technology Development |
| Phone: +64 9 373 7599 x8941          ITSS, The University of Auckland |
|   FAX: +64 9 373 7425        Private Bag 92019, Auckland, New Zealand |
+-----------------------------------------------------------------------C

IETF Dallas Meeting:

Agenda for Realtime Traffic Flow Measurement (RTFM) BOF,
Wednesday, 6 Dec 95, 1530-1730
This session will be multicast

Co-chairs: Nevil Brownlee, Peter Lothberg, Bill Manning

A brief background paper for this group is attached below.
The BOF agenda is:

Presentations
* Introduction:  what do we mean by 'traffic measurement?'
    Bill Manning, 15 minutes
* Work of the Internet Accounting Group
    Nevil Brownlee, 15 minutes
* The IBM implementation
    Sig Handelman & team, 20-30 minutes
* NeTraMet; description, 'real-life' examples
    Nevil Brownlee, 20 minutes

Discussion of proposed RTFM WG charter
    40 minutes

------------------------------------------------------------------------

Realtime Traffic Flow Management (RTFM) - A Background Paper

Nevil Brownlee, Peter Lothberg, Bill Manning  30 Oct 95

The Need
--------

Network Operators need effective ways to measure the flow of traffic
in their networks.  This information is needed for short-term
monitoring and trouble-shooting of network activity, and for
longer-term activities such as capacity planning.  Examples of traffic
flow measurements include:

* broadcast packets - e.g. service announcements on a LAN
* host-server traffic on a LAN
* traffic from a network to other networks, classified into groups
  such as 'local,' 'within the same country' and 'other countries.'
* transit traffic through an exchange point

At present there are many possible ways to measure traffic.  The RMON
MIB provides host traffic matrices, but a user cannot specify which
flows are of interest or how they should be counted.  Network software
such as tcpdump can also be used, but this tends to be very
IP-specific.  Some router vendors provide proprietary methods
(e.g. Cisco's IP Accounting).

The IPPM (Provider Metrics) effort within the Benchmarking Work Group
also has some interests in common with RTFM, but overall there is no
standard way to measure traffic flows.

Meeting the Need
----------------

The IETF Internet Accounting Working Group produced a generalised
model of traffic flows and their measurement, the 'Internet Accounting
Model.'  This defines 'traffic flows' in terms of a set of flow
attributes, which have the same meaning for any protocol.

Flows are measured by traffic 'meters' located at points in the
network where the required flows can be observed.  Flow data is
collected from each meter by one or more 'collectors.'  Collections do
not have to be synchronised, making it easy to use redundant
collectors.  Meters and collectors are co-ordinated by a 'manager.'

A network operator specifies exactly how the flows are to be counted
by writing a set of packet-matching rules.  Such a 'rule set' is
downloaded to a meter where it is used by the meter's packet-matching
engine to decide whether a packet is to be counted, and which flow it
is to be counted in.  Rule sets can be very complex (many hundreds of
rules), allowing the operator to reduce the data to a workably small
set of reported traffic flows.  Flows are bi-directional; the rules
specify which is the 'forward' flow direction, and the meter counts
both 'forward' and 'backward' packets.

Implementations
---------------

The first implementation of the Internet Accounting Model was NeTraMet
(the meter) and NeMaC (a collector/manager for NeTraMet).  NeTraMet
has been in the field since October 93, and is now used at about 100
user sites world-wide.  It measures traffic flows passing an Ethernet
or FDDI interface.

An IBM research group is working on an independent implementation.

RTFM Charter
------------

Network operators want to make traffic flow measurements at any point
in their networks, i.e. in routers, switches and repeaters; this
requires a standard Traffic Meter MIB which vendors of these devices
can implement.

To develop a Traffic Meter MIB a new IETF Working Group is proposed:
Realtime Traffic Flow Measurement (RTFM).  As a starting point for its
charter it should:

* Review earlier work in traffic flow measurement, particularly that
  of the RMON and Internet Accounting Working Groups

* Produce an improved Traffic Flow Model, considering at least the
  following:
   - Simpler ways to specify rule sets
   - Extension of the Accounting Model to higher protocol layers
   - Effect of IPv6 packets on traffic measurement
   - Better ways to manage multiple meters and collectors

* Develop the RTFM Meter MIB as a 'standards track' document within
  the IETF

------------------------------------------------------------------------

From netramet-owner  Mon Nov 13 17:40:12 1995
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) id RAA18923 for netramet-outgoing; Mon, 13 Nov 1995 17:40:11 +1300 (NZDT)
Received: from ccu1.auckland.ac.nz ([email protected] [130.216.3.1]) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) with ESMTP id RAA18918 for <[email protected]>; Mon, 13 Nov 1995 17:40:10 +1300 (NZDT)
Received: (from nevil@localhost) by ccu1.auckland.ac.nz (8.7.1/8.7.1) id RAA24082 for netramet@auckland; Mon, 13 Nov 1995 17:40:08 +1300 (NDT)
From: J Nevil Brownlee <[email protected]>
Message-Id: <[email protected]>
Subject: Ethernet counts do include headers
To: [email protected]
Date: Mon, 13 Nov 1995 17:40:08 +1300 (NDT)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: [email protected]
Precedence: bulk

In response to a recent posting:

> We are planning to use NeTraMet for IP accounting of our International Link.
> We would like to know whether the number of Octets include the Ethernet
> header. Can anyone tell me?

The counts produce by NeTraMet are the Ethernet packet sizes, including
the ethernet (14-byte) header.  Some other systems, e.g. Cisco's
IP Accounting, don't do this - they only count the payload.

Cheers, Nevil

+-----------------------------------------------------------------------+
| Nevil Brownlee                       Director, Technology Development |
| Phone: +64 9 373 7599 x8941          ITSS, The University of Auckland |
|   FAX: +64 9 373 7425        Private Bag 92019, Auckland, New Zealand |
+-----------------------------------------------------------------------C

From netramet-owner  Tue Nov 21 01:45:04 1995
Received: (from majordom@localhost) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) id BAA00790 for netramet-outgoing; Tue, 21 Nov 1995 01:42:48 +1300 (NZDT)
Received: from sun4nl.NL.net (sun4nl.NL.net [193.78.240.1]) by mailhost.auckland.ac.nz (8.7.1/8.7.1-ua) with SMTP id BAA00783 for <[email protected]>; Tue, 21 Nov 1995 01:42:38 +1300 (NZDT)
Received: from icim12 by sun4nl.NL.net via EUnet
       id AA10017 (5.65b/CWI-3.3); Mon, 20 Nov 1995 13:42:33 +0100
Received: from icim37.icim.nl by icim12.icim.nl with SMTP
       (16.6/16.2f) id AA26379; Mon, 20 Nov 95 13:40:37 +0100
Received: by icim37.icim.nl
       (1.38.193.5/15.6d) id AA04378; Mon, 20 Nov 1995 13:40:36 +0100
From: kouters herman <[email protected]>
Message-Id: <[email protected]>
Subject: Where can I find gzip?
To: [email protected]
Date: Mon, 20 Nov 1995 13:40:36 MET
X-Mailer: Elm [revision: 109.14]
Sender: [email protected]
Precedence: bulk

Hi,

I would like to find out what exactly is possible with NeTraMet, so I
downloaded the SUN-package, which is compressed by gzip. Because I've only
limited possibilities for connections to the Internet, I would like to know
where I can find software to 'un-gzip' these files.

Herman

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Herman Kouters                              EDS Nederland BV
Communications Engineer/ICP                 P.O. Box 486
                                           3200 AL  Spijkenisse
                                           The Netherlands
Email : SMTP : [email protected]              Tel. +31 1880 - 51277
       X400 : C=NL  A=400NET               Fax. +31 1880 - 24118
              P=ICIM400  O=ICIM
              S=KOUTERS  G=HERMAN
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.