Re: [ipfix-as] applicability draft version 06
Benoit Claise <bclaise@cisco.com> Wed, 13 July 2005 10:10 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DseCW-0003Ki-4B for ipfix-archive@megatron.ietf.org; Wed, 13 Jul 2005 06:10:48 -0400
Received: from mil.doit.wisc.edu (mil.doit.wisc.edu [128.104.31.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23139 for <ipfix-archive@lists.ietf.org>; Wed, 13 Jul 2005 06:10:45 -0400 (EDT)
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 1DsdsI-0001px-00 for ipfix-list@mil.doit.wisc.edu; Wed, 13 Jul 2005 04:49:54 -0500
Received: from weird-brew.cisco.com ([144.254.15.118] helo=av-tac-bru.cisco.com) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 1DsdsG-0001pm-00 for ipfix-as@net.doit.wisc.edu; Wed, 13 Jul 2005 04:49:52 -0500
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j6D9nmS24922; Wed, 13 Jul 2005 11:49:48 +0200 (CEST)
Received: from [10.61.64.185] (ams-clip-vpn-dhcp185.cisco.com [10.61.64.185]) by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j6D9nlp24903; Wed, 13 Jul 2005 11:49:47 +0200 (CEST)
Message-ID: <42D4E3BB.9010007@cisco.com>
Date: Wed, 13 Jul 2005 11:49:47 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tanja Zseby <zseby@fokus.fraunhofer.de>
CC: ipfix-as@net.doit.wisc.edu
Subject: Re: [ipfix-as] applicability draft version 06
References: <42C821F1.1080306@fokus.fraunhofer.de>
In-Reply-To: <42C821F1.1080306@fokus.fraunhofer.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
Content-Transfer-Encoding: 7bit
Tanja, Thanks for the new draft. Some minor editorial problems left. 1.An alignment issue. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Set ID = 256 | Length = 32 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 198.18.1.12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 198.18.2.254 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 101110 00 | 987410 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2. RTFM flows, however, are bidirectional, i.e. an RTFM meter matches packets from B to A and A to B as separate parts of a single flow, and maintains two sets of packet and byte counters, one for each direction. IPFIX flow are unidirectional. Users that require bidirectional flows have to match the two directions in post-processing. IPFIX flow are unidirectional -> IPFIX flows are unidirectional I guess that no new draft is needed, as those minor editorial changes can be solved after the IESG review... Regards, Benoit. > Hi all, > > we just submitted a new version of the IPFIX applicability statement > (draft-ietf-ipfix-as-06.txt). The only changes are some editorial > changes from Benoit and Tal Givoly's comments on IP Accounting > /reliability where we mainly referenced in section 2.1.what was stated > in RFC3917. > > Regards > Tanja > -- Help mailto:majordomo@net.doit.wisc.edu and say "help" in message body Unsubscribe mailto:majordomo@net.doit.wisc.edu and say "unsubscribe ipfix" in message body Archive http://ipfix.doit.wisc.edu/archive/
- [ipfix-as] applicability draft version 06 Tanja Zseby
- Re: [ipfix-as] applicability draft version 06 Benoit Claise