[Gen-art] RE: Gen-ART review of draft-ietf-ips-scsi-mib-08

Harald Tveit Alvestrand <harald@alvestrand.no> Tue, 17 January 2006 16:17 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytWN-0003nw-7q; Tue, 17 Jan 2006 11:17:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytWL-0003ke-4R; Tue, 17 Jan 2006 11:17:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27745; Tue, 17 Jan 2006 11:15:56 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyteU-00064s-PG; Tue, 17 Jan 2006 11:25:47 -0500
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7B5082596E0; Tue, 17 Jan 2006 17:16:05 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25614-07; Tue, 17 Jan 2006 17:15:59 +0100 (CET)
Received: from [192.168.1.160] (163.80-203-220.nextgentel.com [80.203.220.163]) by eikenes.alvestrand.no (Postfix) with ESMTP id 5AB3A2596DF; Tue, 17 Jan 2006 17:15:59 +0100 (CET)
Date: Tue, 17 Jan 2006 17:17:03 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Black_David@emc.com, gen-art@ietf.org
Message-ID: <D7F64900FC87FC28C1F68B20@svartdal.hjemme.alvestrand.no>
In-Reply-To: <F222151D3323874393F83102D614E055013E906C@CORPUSMX20A.corp.emc.com>
References: <F222151D3323874393F83102D614E055013E906C@CORPUSMX20A.corp.emc.c om>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: mbakke@cisco.com, marjorie_krueger@hp.com, mankin@psg.com, yaronled@bezeqint.net, ips@ietf.org, michele@sanrad.com, kzm@cisco.com
Subject: [Gen-art] RE: Gen-ART review of draft-ietf-ips-scsi-mib-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Thanks for the quick feedback, David!

I'm happy to leave this in your hands - one comment only:

--On tirsdag, januar 17, 2006 11:02:36 -0500 Black_David@emc.com wrote:

>> The term "running at high speed" is a gating criterion for whether or
>> not  the HS counters are mandatory, but I can't see that it's defined in
>> a  testable way. Might have missed it - it would logically seem to
>> belong in  section 7.5.
>
> Unfortunately, it's fuzzy and not testable in all cases.  Here's what
> RFC 4181 (Section 4.6.1.2) has to say about this issue:
>
>    Henceforth "standard" MIB modules MAY
>    use the Counter64 type when it makes sense to do so, and MUST use
>    Counter64 if the information being modelled would wrap in less than
>    one hour if the Counter32 type was used instead.
>
> It clearly "makes sense" to use the Counter64 type, as there are SCSI
> implementations that clearly need it based on the "would wrap in less
> than one hour" criterion.  Would adapting the quoted RFC 4181 text
> (with a reference to RFC 4181) be sufficient to satisfy your concern?

What I'd like to see is something that makes it a complete no-brainer 
whether or not the HC counters are needed, for instance:

  If the interconnect speed is higher than 4 Gbits/second, the HC counters
  MUST be implemented, since that makes it possible to spin the counters
  in one hour (see [RFC4181]).

I wouldn't like someone to say "but... my implementation has a 10G 
interface, but it's so badly implemented that I can't possibly get more 
than 1 million operations per second through it, so I don't need to 
implement the HC counters, do I?"

(4G is picked out of thin air, but illustrates the problem... if The Number 
is 3G, then 4G FC needs to implement it; if The Number is 9G, then only 
people with 10GE and Infiniband interfaces need bother...)

But you know this stuff, I don't....

                     Harald




_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art