Re: [BEHAVE] [behave] #15: DThaler comments on nat-mib-06
Simon Perreault <simon.perreault@viagenie.ca> Mon, 24 June 2013 11:00 UTC
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DC711E80FB for <behave@ietfa.amsl.com>; Mon, 24 Jun 2013 04:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
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 dSb73Nc4mlHJ for <behave@ietfa.amsl.com>; Mon, 24 Jun 2013 04:00:14 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4330711E8127 for <behave@ietf.org>; Mon, 24 Jun 2013 04:00:10 -0700 (PDT)
Received: from [127.0.0.1] (h228.viagenie.ca [206.123.31.228]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5E4FB403D1; Mon, 24 Jun 2013 07:00:08 -0400 (EDT)
Message-ID: <51C7F88F.1090406@viagenie.ca>
Date: Mon, 24 Jun 2013 09:43:11 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: behave@ietf.org
References: <065.3afc93e0d2a3edd9af1ed12f11c3a4b7@trac.tools.ietf.org>
In-Reply-To: <065.3afc93e0d2a3edd9af1ed12f11c3a4b7@trac.tools.ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: behave issue tracker <trac+behave@trac.tools.ietf.org>, draft-ietf-behave-nat-mib@tools.ietf.org, dthaler@microsoft.com
Subject: Re: [BEHAVE] [behave] #15: DThaler comments on nat-mib-06
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 11:00:19 -0000
Meta-comment: I would prefer if we don't make use of the issue tracker for this draft. I already have my process for tracking issues, so this just makes my job a bit more tedious. Thanks. Le 2013-06-22 22:39, behave issue tracker a écrit : > #15: DThaler comments on nat-mib-06 > > 1) Section 5 of the current draft has > " Some of the readable objects in this MIB module (i.e., objects with a > MAX-ACCESS other than not-accessible) may be considered sensitive or > vulnerable in some network environments. It is thus important to > control even GET and/or NOTIFY access to these objects and possibly > to even encrypt the values of these objects when sending them over > the network via SNMP." > > Per http://trac.tools.ietf.org/area/ops/trac/wiki/mib-security > that's supposed to be followed with > " These are the tables and objects and their > sensitivity/vulnerability: > > <list the tables and objects and state why they are sensitive>" > > Also the document has 2 paragraphs of text "There are a number of managed > objects in this MIB that may contain ... > versions of SNMP provide features for such a secure environment." > which do not appear in the current MIB boilerplate at the link above. > Should those 2 paragraphs be removed? Fixed in my local copy. > 2) Section 5 contains MUST, SHOULD, etc. But the document is missing > the boilerplate reference to RFC 2119. Added. > 3) Section 6 does not say whether any additional actions for IANA are > needed. Suggest adding "No IANA actions are required by this document." Added. > 4) The MIB compiler I used complained about this: > > natMappingPool OBJECT-TYPE > > SYNTAX NatPoolId (0|1..4294967295) > Because of > > NatPoolId ::= TEXTUAL-CONVENTION > > SYNTAX Unsigned32 (1..4294967295) > > That is, NatPoolId does not allow 0, and so natMappingPool cannot add it > and still use the NatPoolId syntax. Fixed. Simon
- [BEHAVE] [behave] #15: DThaler comments on nat-mi… behave issue tracker
- Re: [BEHAVE] [behave] #15: DThaler comments on na… Simon Perreault
- Re: [BEHAVE] [behave] #15: DThaler comments on na… Dave Thaler