[IPFIX] AD review of draft-ietf-ipfix-psamp-mib-03.txt
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 01 June 2011 10:19 UTC
Return-Path: <dromasca@avaya.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 22BEBE07A6 for <ipfix@ietfa.amsl.com>; Wed, 1 Jun 2011 03:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level:
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[AWL=-0.816, BAYES_00=-2.599, FF_IHOPE_YOU_SINK=2.166, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 KemsmamZsV9Q for <ipfix@ietfa.amsl.com>; Wed, 1 Jun 2011 03:19:16 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 70A2AE0787 for <ipfix@ietf.org>; Wed, 1 Jun 2011 03:19:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAE0R5k3GmAcF/2dsb2JhbABTpiJ3p3eDWgKbGIYgBJU1ikg
X-IronPort-AV: E=Sophos;i="4.65,302,1304308800"; d="scan'208";a="249227222"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Jun 2011 06:19:14 -0400
X-IronPort-AV: E=Sophos;i="4.65,302,1304308800"; d="scan'208";a="628308273"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jun 2011 06:19:14 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 01 Jun 2011 12:19:12 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04032BD0BD@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: AD review of draft-ietf-ipfix-psamp-mib-03.txt
Thread-Index: AcwgRVpKL+rIVnCXROu/usNykoC0lg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: IPFIX Working Group <ipfix@ietf.org>
Subject: [IPFIX] AD review of draft-ietf-ipfix-psamp-mib-03.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: Wed, 01 Jun 2011 10:19:17 -0000
Hi, I have performed the AD review of draft-ietf-ipfix-psamp-mib-03.txt. This document is in good shape and I am sending it to IETF Last Call. Please address the comments below together with the other IETF LC comments. The technical comments are marked T and the editorial comments are marked E. T1. Float64TC FROM FLOAT-TC-MIB -- draft-ietf-opsawg-mib-float Actually will need to be published before or simultaneously with this document, in order to satisfy the normative reference. Leaving draft-ietf-opsawg-mib-float would be confusing, we need the RFC number here. I suggest to include here (as a comment) a note to the RFC Editor that mentions that draft-ietf-opsawg-mib-float is to be replaced with the RFC number of that document, and the note deleted. T2. Why do psampSampCountBasedAvail, psampSampTimeBasedAvail, psampSampRandOutOfNAvail, psampSampUniProbAvail, psampFiltPropMatchAvail, psampFiltHashAvail have DEFVAL clauses? These are read-only objects, so the values must be configured by some other means (not by SNMP) and just read by the agent. T3. There is no need to include the following in the IANA considerations section: psampSampCountBased { ipfixSelectorFunctions 2 } psampSampTimeBased { ipfixSelectorFunctions 3 } psampSampRandOutOfN { ipfixSelectorFunctions 4 } psampSampUniProb { ipfixSelectorFunctions 5 } psampFiltPropMatch { ipfixSelectorFunctions 6 } psampFiltHash { ipfixSelectorFunctions 7 } These are already assigned in the MIB module and no IANA action is required for them. E1. The contents of sections 3 and 4 are similar, but the formatting of the texts in the two sections is different. I suggest to fix this using for section 4 the same format as in section 3, which is easier to read. E2. Page 5 - second paragraph s/as defiend/as defined/ E3. Please explain the meaning of each enumerated value in the DESCRIPTION clause of psampFiltHashFunction E4. Please detail the 'corresponding sampling function' in the DESCRIPTION clause of each one of the conformance groups under MODULE-COMPLIANCE. Thanks and Regards, Dan
- [IPFIX] AD review of draft-ietf-ipfix-psamp-mib-0… Romascanu, Dan (Dan)
- Re: [IPFIX] AD review of draft-ietf-ipfix-psamp-m… Romascanu, Dan (Dan)
- Re: [IPFIX] AD review of draft-ietf-ipfix-psamp-m… Thomas Dietz
- Re: [IPFIX] AD review of draft-ietf-ipfix-psamp-m… Thomas Dietz