IETF Logo Mail Archive

draft-atlas-rtgwg-ipfrr-ip-mib-00.txt

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 11 November 2004 18:53 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11864 for <rtgwg-web-archive@ietf.org>; Thu, 11 Nov 2004 13:53:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSK60-0001IQ-LX for rtgwg-web-archive@ietf.org; Thu, 11 Nov 2004 13:55:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJwD-0008Sq-Ku; Thu, 11 Nov 2004 13:44:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJs8-0007Qi-DS for rtgwg@megatron.ietf.org; Thu, 11 Nov 2004 13:40:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11059 for <rtgwg@ietf.org>; Thu, 11 Nov 2004 13:40:39 -0500 (EST)
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJtK-00013B-Of for rtgwg@ietf.org; Thu, 11 Nov 2004 13:41:56 -0500
Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by ranger.systems.pipex.net (Postfix) with ESMTP id 3D656E000138; Thu, 11 Nov 2004 18:40:06 +0000 (GMT)
Received: from Puppy ([130.129.135.167] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 11 Nov 2004 18:39:09 +0000
Message-ID: <005001c4c81d$d2d7c7a0$a7878182@Puppy>
From: Adrian Farrel <adrian@olddog.co.uk>
To: rtgwg@ietf.org, aatlas@avici.com
References: <24685528.20041109092848@psg.com>
Date: Thu, 11 Nov 2004 18:38:48 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 11 Nov 2004 18:39:09.0127 (UTC) FILETIME=[BB10E570:01C4C81D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: draft-atlas-rtgwg-ipfrr-ip-mib-00.txt
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

A few nits, probably worth getting them out early.

1. Please say "MIB module" not "MIB"

2. As suggested at the mic, do consider SNMP Notifications, but also consider the amount
of information overload that might arise on recovery from a single network fault. Probably
much more interesting to keep statistics and history about actions and errors.

3. Please split references into normative and informational.
I suspect draft-ietf-ipv6-rfc2096-update-07 is needed as a normative reference

4. I agree that write access will be needed for some objects.

Adrian





_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg

v2.23.0 | Report a Bug | By Email