Re: [IPFIX] No active/inactive timeout definitions in any IPFIX RFCs? Idle versus inactive terminology? (part of draft-ietf-bmwg-ipflow-meth-09 review)
Benoit Claise <bclaise@cisco.com> Wed, 18 April 2012 10:51 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 18A8521F8554 for <ipfix@ietfa.amsl.com>; Wed, 18 Apr 2012 03:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level:
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AF8oG7OoNkp5 for <ipfix@ietfa.amsl.com>; Wed, 18 Apr 2012 03:51:19 -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 1E2AB21F85C3 for <ipfix@ietf.org>; Wed, 18 Apr 2012 03:51:18 -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 q3IApB9U007599; Wed, 18 Apr 2012 12:51:11 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q3IApA11024537; Wed, 18 Apr 2012 12:51:10 +0200 (CEST)
Message-ID: <4F8E9C9E.4080404@cisco.com>
Date: Wed, 18 Apr 2012 12:51:10 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Gerhard Muenz <muenz@net.in.tum.de>
References: <4F841487.8090604@cisco.com> <4F846107.7040907@net.in.tum.de>
In-Reply-To: <4F846107.7040907@net.in.tum.de>
Content-Type: multipart/alternative; boundary="------------060401040308010109050608"
Cc: Ron Bonica <rbonica@juniper.net>, Al Morton <acmorton@att.com>, "ipfix@ietf.org" <ipfix@ietf.org>
Subject: Re: [IPFIX] No active/inactive timeout definitions in any IPFIX RFCs? Idle versus inactive terminology? (part of draft-ietf-bmwg-ipflow-meth-09 review)
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: Wed, 18 Apr 2012 10:51:24 -0000
Dear all, I believe that consistency is important amongst all the IPFIX documents. What Brian expressed "Given that 5102 predates all other (directly-IPFIX-related) references, and there's an IE in the IANA registry called flowIdleTimeout, I'd tend to go with "idle" for this one." is I believe the right way forward. And Gerhard mentioned " We could change the name in the MIB and in ipfix-config if consistency is important." So let me propose the following: - http://tools.ietf.org/html/draft-ietf-ipfix-configuration-model-10, in the RFC-editor queue: we could still change inactive to idle - http://tools.ietf.org/html/draft-ietf-ipfix-rfc5815bis-03, in the RFC-editor queue we could still change inactive to idle - Editorial errata on RFC5472: "inactive" -> "idle" Potentially, an extra sentence such as: "note that the idle timeout is sometimes called the inactive timeout in the industry" - http://www.ietf.org/id/draft-ietf-bmwg-ipflow-meth-09.txt replace inactive by idle. Any objections? Regards, Benoit. > Hi Benoit, > > The parameter was always called inactive timeout in IPFIX MIB. > ipfix-config changed from idleTimeout to inactiveTimeout in > draft-ietf-ipfix-configuration-model-02 to be consistent with the MIB. > > We could change the name in the MIB and in ipfix-config if consistency > is important. > > Gerhard > > > On 10.04.2012 13:07, Benoit Claise wrote: >> Dear all, >> >> Reading draft-ietf-bmwg-ipflow-meth-09.txt, I realized that this >> draft defines two new terms: Active Timeout and Inactive Timeout. >> I was thinking: surely, we have defined those terms already in some >> IPFIX RFCs. >> Actually, I was unable to find any references.... Have I overlooked >> something? >> >> The only pointers I could find are in RFC5102 >> >> >> 5.11.1. flowActiveTimeout >> >> >> Description: >> The number of seconds after which an active Flow is timed out >> anyway, even if there is still a continuous flow of packets. >> Abstract Data Type: unsigned16 >> ElementId: 36 >> Status: current >> Units: seconds >> >> >> 5.11.2. flowIdleTimeout >> >> >> >> Description: >> A Flow is considered to be timed out if no packets belonging to >> the Flow have been observed for the number of seconds specified by >> this field. >> Abstract Data Type: unsigned16 >> ElementId: 37 >> Status: current >> Units: seconds >> >> >> 5.11.3. flowEndReason >> >> Description: >> The reason for Flow termination. The range of values includes the >> following: >> >> 0x01: idle timeout >> The Flow was terminated because it was considered to be >> idle. >> >> 0x02: active timeout >> The Flow was terminated for reporting purposes while it was >> still active, for example, after the maximum lifetime of >> unreported Flows was reached. >> >> ... >> >> Here is one issue. >> Some documents refer to inactive timeout >> RFC5472, >> ipfixMeteringProcessCacheInactiveTimeout in >> http://tools.ietf.org/html/draft-ietf-ipfix-rfc5815bis-03 >> inactiveTimeout in >> http://tools.ietf.org/html/draft-ietf-ipfix-configuration-model-10 >> While some others refer to idle timeout >> RFC 5102, >> draft-ietf-bmwg-ipflow-meth-09 >> >> Any proposal to fix this problem? >> >> Regards, Benoit (OPS A.D.) >> >> >> >> _______________________________________________ >> IPFIX mailing list >> IPFIX@ietf.org >> https://www.ietf.org/mailman/listinfo/ipfix
- [IPFIX] No active/inactive timeout definitions in… Benoit Claise
- Re: [IPFIX] No active/inactive timeout definition… Jan Novak (janovak)
- Re: [IPFIX] No active/inactive timeout definition… Brian Trammell
- Re: [IPFIX] No active/inactive timeout definition… Gerhard Muenz
- Re: [IPFIX] No active/inactive timeout definition… Simon Leinen
- Re: [IPFIX] No active/inactive timeout definition… Brian Trammell
- Re: [IPFIX] No active/inactive timeout definition… Jan Novak (janovak)
- Re: [IPFIX] No active/inactive timeout definition… Benoit Claise
- Re: [IPFIX] No active/inactive timeout definition… Paul Aitken
- Re: [IPFIX] No active/inactive timeout definition… Brian Trammell
- Re: [IPFIX] No active/inactive timeout definition… Andrew Feren