Re: [DNSOP] New Version Notification for draft-perreault-dnsop-stats-mib-01.txt

Simon Perreault <simon.perreault@viagenie.ca> Mon, 23 July 2012 13:12 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0275A21F86DC for <dnsop@ietfa.amsl.com>; Mon, 23 Jul 2012 06:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, NO_RELAYS=-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 a5scIfofyFN0 for <dnsop@ietfa.amsl.com>; Mon, 23 Jul 2012 06:12:40 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC4321F86DB for <dnsop@ietf.org>; Mon, 23 Jul 2012 06:12:40 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:fdd9:bf18:7680:9905]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 84EF0400B1 for <dnsop@ietf.org>; Mon, 23 Jul 2012 09:12:39 -0400 (EDT)
Message-ID: <500D4DC6.6010102@viagenie.ca>
Date: Mon, 23 Jul 2012 09:12:38 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20120716154655.20530.97681.idtracker@ietfa.amsl.com> <50043870.4000405@viagenie.ca> <20120723104754.GA15804@nic.fr>
In-Reply-To: <20120723104754.GA15804@nic.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [DNSOP] New Version Notification for draft-perreault-dnsop-stats-mib-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 13:12:41 -0000

Le 2012-07-23 06:47, Stephane Bortzmeyer a écrit :
> Main comment: I am not convinced by the whole idea of "Discontinuity
> Time". Isn't the whole idea of SNMP to have dumb agents, often without
> stable memory, and the manager is supposed to know that, to detect
> discontinuities and to deal with it? Why is DNS different from typical
> MIB-II counters, which can go back to zero when the router reboots?

The main use case is when the DNS daemon restarts and loses state. This 
creates a discontinuity in the DNS MIB counters but not in the global 
MIB-II counters. That's why we introduced a separate discontinuity 
indicator that the manager can monitor to identify discontinuities, just 
like it does with MIB-II.

Other MIBs use the same technique (e.g. the OSPFv2 MIB [RFC4750]).

> Second, the draft requires a mention of RFC 6168, which covers also
> statistics.

Clearly we can add a reference to that RFC.

But it looks like it doesn't go into much detail about what statistics 
are needed, just that some are. So, not much guidance for us. Or did I 
overlook something?

> Otherwise, the draft seems sensible, addresses a real problem for DNS
> operators who have subcontractors, and, IMHO, correctly answer the
> warnings of RFC 3197.

Thank you! That's very encouraging!

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca