From owner-if-mib@padauk.vnd.tek.com  Fri Mar 10 12:15:29 2000
Received: from fw1.tek.com (fw1.tek.com [192.65.17.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25796
	for <ifmib-archive@odin.ietf.org>; Fri, 10 Mar 2000 12:15:26 -0500 (EST)
Received: from fw1.tek.com (root@localhost)
	by fw1.tek.com with ESMTP id JAA00954
	for <ifmib-archive@odin.ietf.org>; Fri, 10 Mar 2000 09:14:57 -0800 (PST)
Received: from padauk.vnd.tek.com (padauk.vnd.tek.com [128.181.192.78])
	by fw1.tek.com with ESMTP id JAA00947
	for <ifmib-archive@lists.ietf.org>; Fri, 10 Mar 2000 09:14:56 -0800 (PST)
Received: (from majordomo@localhost) by padauk.vnd.tek.com (8.7.5/8.7.3) id JAA29640 for if-mib-outgoing; Fri, 10 Mar 2000 09:11:40 -0800 (PST)
X-Authentication-Warning: padauk.vnd.tek.com: majordomo set sender to owner-if-mib@domo.vnd.tek.com using -f
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200003101705.JAA01063@foxhound.cisco.com>
Subject: Re: nits in <draft-ietf-ifmib-ifmib2-02.txt>
To: schoenw@ibr.cs.tu-bs.de (Juergen Schoenwaelder)
Date: Fri, 10 Mar 2000 09:05:41 -0800 (PST)
Cc: kzm@cisco.com, kasten@argon.com, if-mib@vnd.tek.com
In-Reply-To: <200003101325.OAA11073@henkell.ibr.cs.tu-bs.de> from "Juergen Schoenwaelder" at Mar 10, 2000 02:25:21 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-if-mib@vnd.tek.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Thanks for your careful reading.  I'll fix them all.
  
Keith.
 
> I just found some nits in <draft-ietf-ifmib-ifmib2-02.txt>:
> 
> 1. The third and fourth paragraph on page 10 talk about compliance
>    statements. They refer to SNMPv1 and SNMPv2 where they should
>    refer to SMIv1 and SMIv2.
> 
> 2. The third paragraph on page 12 contains the phrase "SNMP's GetNext
>    (and SNMPv2's GetBulk) operation". You may want to change that to
>    just "SNMP's GetNext (and GetBulk) operation" (perhaps even
>    removing the braces).
> 
> 3. Item (2) on page 16 says that "64-bit counters are a new feature,
>    introduced in SNMPv2." I suggest to replace SNMPv2 with SMIv2.
> 
> 4. First paragraph in section 3.1.18 refers to "noSuchInstance for
>    SNMPv2". You may want to change that to "(e.g., noSuchInstance for
>    SNMPv3)" or "(e.g., noSuchInstance for the second version of SNMP
>    protocol operations)" or just "(e.g., noSuchName or noSuchInstance)".
> 
> Thats it.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder      Technical University Braunschweig
> <schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
> Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
> Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
> 
> 
> 
> 



