IETF Logo Mail Archive

Re: [IPFIX] WG: I-D Action: draft-ietf-ipfix-flow-selection-tech-06.txt

Benoit Claise <bclaise@cisco.com> Fri, 27 May 2011 14:16 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDCEE06DA for <ipfix@ietfa.amsl.com>; Fri, 27 May 2011 07:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[AWL=0.579, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7EQuNEUFdzzs for <ipfix@ietfa.amsl.com>; Fri, 27 May 2011 07:16:41 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id BDFFCE06CE for <ipfix@ietf.org>; Fri, 27 May 2011 07:16:40 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4REGder014400; Fri, 27 May 2011 16:16:39 +0200 (CEST)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4REGdJb020445; Fri, 27 May 2011 16:16:39 +0200 (CEST)
Message-ID: <4DDFB247.5070106@cisco.com>
Date: Fri, 27 May 2011 16:16:39 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paul Aitken <paitken@cisco.com>
References: <20110523092128.18082.9981.idtracker@ietfa.amsl.com> <804B13F8F3D94A4AB18B9B01ACB68FA1044F55B0@EXCHSRV.fokus.fraunhofer.de> <4DDF7F20.1000004@cisco.com> <3474FB4B-5E2C-4D7F-99C3-78D793957941@tik.ee.ethz.ch> <4DDF9C37.4020407@cisco.com> <4DDFB137.207@cisco.com>
In-Reply-To: <4DDFB137.207@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ipfix@ietf.org
Subject: Re: [IPFIX] WG: I-D Action: draft-ietf-ipfix-flow-selection-tech-06.txt
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2011 14:16:41 -0000

On 27/05/2011 16:12, Paul Aitken wrote:
> Benoit,
>
>> See RFC5101
>>
>>  Metering Process
>>
>>       The Metering Process generates Flow Records.  Inputs to the
>>       process are packet headers and characteristics observed at an
>>       Observation Point, and packet treatment at the Observation Point
>>       (for example, the selected output interface).
>>
>> Considering that there are no flows as input to the Metering Process, 
>> ...
>
> A mediator may receive packets containing flow records from other 
> exporters.
A mediator, so an Intermediate Process.
We're in synch.

Regards, Benoit
>
> The number of flows contained in those those packets counts as a 
> "packet characteristic" per the RFC 5101 definition above.
>
> If the mediator wanted to report the number of bytes, packets, and 
> flows which it observed, I'd expect it to use fields #1, #2 and #3.
>
> P.

v2.23.0 | Report a Bug | By Email