IETF Logo Mail Archive

[Gen-art] Re: Genart review of draft-ietf-radext-dynauth-server-mib-05 / draft-ietf-radext-dynauth-client-mib-05

stefaan.de_cnodder@alcatel.be Thu, 08 June 2006 12:11 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoJMC-0003Xf-TR; Thu, 08 Jun 2006 08:11:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoHZi-0000Jb-Mp for gen-art@ietf.org; Thu, 08 Jun 2006 06:17:14 -0400
Received: from smail.alcatel.fr ([62.23.212.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoHZg-0008W0-6w for gen-art@ietf.org; Thu, 08 Jun 2006 06:17:14 -0400
Received: from bemail06.netfr.alcatel.fr (bemail06.netfr.alcatel.fr [155.132.251.30]) by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k58AHAL7015361; Thu, 8 Jun 2006 12:17:10 +0200
Received: from [172.31.131.155] ([172.31.131.155]) by bemail06.netfr.alcatel.fr (Lotus Domino Release 5.0.13aHF163) with ESMTP id 2006060812170911:2581 ; Thu, 8 Jun 2006 12:17:09 +0200
Message-ID: <4487F924.4040505@alcatel.be>
Date: Thu, 08 Jun 2006 12:17:08 +0200
From: stefaan.de_cnodder@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ron Bonica <rbonica@juniper.net>
References: <448725D6.30902@juniper.net>
In-Reply-To: <448725D6.30902@juniper.net>
X-MIMETrack: Itemize by SMTP Server on BEMAIL06/BE/ALCATEL(Release 5.0.13aHF163 | June 23, 2005) at 06/08/2006 12:17:09, Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.13aHF163 | June 23, 2005) at 06/08/2006 12:17:10, Serialize complete at 06/08/2006 12:17:10
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
X-Mailman-Approved-At: Thu, 08 Jun 2006 08:11:23 -0400
Cc: gen-art@ietf.org, radiusext@ops.ietf.org
Subject: [Gen-art] Re: Genart review of draft-ietf-radext-dynauth-server-mib-05 / draft-ietf-radext-dynauth-client-mib-05
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>
Errors-To: gen-art-bounces@ietf.org

Hi Ron,

Thanks for the review, see below for some answers

Ron Bonica wrote:

> I am the assigned Gen-ART reviewer for:
> draft-ietf-radext-dynauth-server-mib-05
>           -and-
> draft-ietf-radext-dynauth-client-mib-05
> 
> 
> For background on Gen-ART, please see the FAQ at
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html.
> Please resolve these comments along with any other Last Call comments
> you may receive.
> 
> This draft is ready for publication as a Standards Track document,
> except for the following nit:
> 

In fact, the 2 documents are informational.

> - The client MIB contains a note to the RFC editor about the reference
> [DYNSERV]. However, there is no such reference.
> 

I checked it and the client MIB is Ok, in the server MIB it seems that 
the RFC ed note is incorrect and [DYNSERV] should be replaced by 
[DYNCLNT]. The references in both of the drafts are correct, with the 
exception of the RFC ed note in the server MIB.


> And two substantial questions:
> 
> - Can I assume that it has passed MIB Rx Review? (It compiles clean).
> 

Not sure what MIB Rx review is. I compliled the MIB with Smilent.

> - Should this MIB *ever* be used in conjuntion with SNMPv1? I know that
> you *recommend* against it. But it seems that divulging the information
> in this mib to a hostile party might be pretty bad.
> 

http://www.ops.ietf.org/mib-security.html contains preformatted text for 
the security section and that text was put in the draft. See the text on 
that webpage in the section "-- else if there are no read-write objects 
in your MIB module". The text in the draft is more or less a copy/paste 
from that webpage. Also the other Radius MIBs like 
draft-ietf-radext-rfc2618bis-03.txt are also following the guidelines on 
the mentioned webpage.

regards,
Stefaan


>                                       Ron
> 
> 

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

v2.23.0 | Report a Bug | By Email